Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Need help with my delta please.

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    48
    1.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • azaelaguirreundefined
      azaelaguirre
      last edited by Phaedrux

      MY VERSION:
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1

      MY ERRORS:
      G30 S-1
      Error: M280: Invalid servo index 0 in M280 command
      Error: Z probe was not triggered during probing move

      MY ZPROBE CONFIG:
      ; Z-Probe
      M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
      G31 P500 X0 Y20 Z0 ; set Z probe trigger value, offset and trigger height
      M557 R150 S45 ; define mesh grid

      MY deployprobe.g:
      M280 P0 S10 I1
      M280 P0 S160 I1 ; deploy BLTouch

      My retractprobe.g:
      M280 P0 S90 ; retract BLTouch

      i dont know whats happen, help please

      DIY-O-Sphereundefined fcwiltundefined 2 Replies Last reply Reply Quote 0
      • DIY-O-Sphereundefined
        DIY-O-Sphere @azaelaguirre
        last edited by

        @azaelaguirre said in PROBLEM WITH BLTOUCH:

        M280 P0 S10 I1
        M280 P0 S160 I1 ; deploy BLTouch

        That is wrong for RRF3

        M280 P0 S10 
        

        Should be right....

        (UTC+1)

        azaelaguirreundefined 1 Reply Last reply Reply Quote 0
        • fcwiltundefined
          fcwilt @azaelaguirre
          last edited by

          @azaelaguirre

          Hi,

          You report that you are using firmware v2.05.1.

          But some of the commands you are using, like M950, are only for firmware v3.x.x.

          I would advise updating to v3.3 BUT know that you have to first update to v3.0 then update to v3.3.

          Firmware v3.4 is in the process of being completed BUT it pushes the limits of the flash memory in the Duet 2 WiFi.

          Frederick

          Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

          azaelaguirreundefined 1 Reply Last reply Reply Quote 1
          • azaelaguirreundefined
            azaelaguirre @DIY-O-Sphere
            last edited by

            @diy-o-sphere I already fixed it and the problem continues

            1 Reply Last reply Reply Quote 0
            • azaelaguirreundefined
              azaelaguirre @fcwilt
              last edited by

              @fcwilt I already updated to 3.3 and the problem continues, when sending G30 S-1 it collides with the bed and does not display the pin

              fcwiltundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @azaelaguirre
                last edited by

                @azaelaguirre said in PROBLEM WITH BLTOUCH:

                @fcwilt I already updated to 3.3 and the problem continues, when sending G30 S-1 it collides with the bed and does not display the pin

                Well you have the X and Y offset values in G31 as 0 which seems unlikely. That would mean the probe pin is right where the hotend nozzle tip is.

                You also have the Z Trigger Height value as 0 which seems unlikely. That would mean the probe triggers when Z=0. Typically the value is a small positive value. For example, on one of my printers the value is 1.8.

                As a test you can set it to Z=5 and re-boot. Then home all and move to Z=10. Check that M401 (deploy probe pin) and M402 (retract probe pin) work.

                If they work move the probe to the center of the bed and issue G30 S-1.

                Frederick

                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                azaelaguirreundefined 1 Reply Last reply Reply Quote 1
                • Phaedruxundefined
                  Phaedrux Moderator @azaelaguirre
                  last edited by

                  @azaelaguirre said in PROBLEM WITH BLTOUCH:

                  @fcwilt I already updated to 3.3 and the problem continues, when sending G30 S-1 it collides with the bed and does not display the pin

                  Are you getting any errors?

                  Can you please send M122 and M98 P"config.g" and post the results?

                  Please share your full config.g, homing files, deploy and retract macros.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  azaelaguirreundefined 2 Replies Last reply Reply Quote 1
                  • azaelaguirreundefined
                    azaelaguirre @Phaedrux
                    last edited by

                    @phaedrux

                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
                    Board ID: 0JD0M-9P6M2-NWNS4-7JKF0-3S46L-KV0MM
                    Used output buffers: 3 of 24 (17 max)
                    === RTOS ===
                    Static ram: 23876
                    Dynamic ram: 74396 of which 112 recycled
                    Never used RAM 16032, free system stack 134 words
                    Tasks: NETWORK(ready,12.2%,244) HEAT(delaying,0.0%,326) Move(notifyWait,0.1%,303) MAIN(running,85.3%,393) IDLE(ready,2.4%,29), total 100.0%
                    Owned mutexes: WiFi(NETWORK)
                    === Platform ===
                    Last reset 00:00:38 ago, cause: software
                    Last software reset at 2022-02-15 18:08, reason: User, GCodes spinning, available RAM 16032, slot 0
                    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                    Error status: 0x00
                    Step timer max interval 0
                    MCU temperature: min 27.5, current 28.4, max 28.7
                    Supply voltage: min 23.7, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
                    Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                    Driver 0: position 70456, standstill, SG min/max 0/34
                    Driver 1: position 70456, standstill, SG min/max 0/70
                    Driver 2: position 70456, standstill, SG min/max 96/272
                    Driver 3: position 0, standstill, SG min/max not available
                    Driver 4: position 0, standstill, SG min/max not available
                    Driver 5: position 0
                    Driver 6: position 0
                    Driver 7: position 0
                    Driver 8: position 0
                    Driver 9: position 0
                    Driver 10: position 0
                    Driver 11: position 0
                    Date/time: 2022-02-15 18:09:27
                    Cache data hit count 1397641552
                    Slowest loop: 5.76ms; fastest: 0.13ms
                    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                    === Storage ===
                    Free file entries: 10
                    SD card 0 detected, interface speed: 20.0MBytes/sec
                    SD card longest read time 3.2ms, write time 0.0ms, max retries 0
                    === Move ===
                    DMs created 83, maxWait 21694ms, bed compensation in use: none, comp offset 0.000
                    === MainDDARing ===
                    Scheduled moves 4, completed moves 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                    === AuxDDARing ===
                    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                    === Heat ===
                    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                    === GCodes ===
                    Segments left: 0
                    Movement lock held by null
                    HTTP is idle in state(s) 0
                    Telnet is idle in state(s) 0
                    File is idle in state(s) 0
                    USB is idle in state(s) 0
                    Aux is idle in state(s) 0
                    Trigger is idle in state(s) 0
                    Queue is idle in state(s) 0
                    LCD is idle in state(s) 0
                    Daemon is idle in state(s) 0
                    Autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 83.18ms; fastest: 0.00ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                    HTTP sessions: 1 of 8

                    • WiFi -
                      Network state is active
                      WiFi module is connected to access point
                      Failed messages: pending 0, notready 0, noresp 0
                      WiFi firmware version 1.26
                      WiFi MAC address 98💿ac:20:34:c3
                      WiFi Vcc 3.43, reset reason Turned on by main processor
                      WiFi flash size 4194304, free heap 23128
                      WiFi IP address 192.168.100.71
                      WiFi signal strength -58dBm, mode 802.11n, reconnections 0, sleep mode modem
                      Clock register 00002002
                      Socket states: 0 0 0 0 0 0 0 0

                    M98 P"config.g"
                    HTTP is enabled on port 80
                    FTP is enabled on port 21
                    TELNET is enabled on port 23
                    Error: M305 has been replaced by M308 and M950 in RepRapFirmware 3
                    Error: M305 has been replaced by M308 and M950 in RepRapFirmware 3
                    Error: in file macro line 97 column 10: M591: expected string expression

                    1 Reply Last reply Reply Quote 0
                    • azaelaguirreundefined
                      azaelaguirre @fcwilt
                      last edited by

                      @fcwilt I already did it, when sending m401 it does nothing

                      fcwiltundefined 1 Reply Last reply Reply Quote 0
                      • azaelaguirreundefined
                        azaelaguirre @Phaedrux
                        last edited by

                        @phaedrux ; Configuration file for Duet WiFi (firmware version 3.3)
                        ; executed by the firmware on start-up
                        ;
                        ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Feb 14 2022 15:51:11 GMT-0600 (hora estándar central)

                        ; General preferences
                        G90 ; send absolute coordinates...
                        M83 ; ...but relative extruder moves
                        M550 P"My Printer" ; set printer name
                        M665 R155 L397.19 B155 H520 ; Set delta radius, diagonal rod length, printable radius and homed height
                        M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them

                        ; Network
                        M551 P"TLM" ; set password
                        M552 S1 ; enable network
                        M586 P0 S1 ; enable HTTP
                        M586 P1 S1 ; enable FTP
                        M586 P2 S1 ; enable Telnet

                        ; Drives
                        M569 P0 S1 ; physical drive 0 goes forwards
                        M569 P1 S1 ; physical drive 1 goes forwards
                        M569 P2 S1 ; physical drive 2 goes forwards
                        M569 P3 S1 ; physical drive 3 goes forwards
                        M584 X0 Y1 Z2 E3 ; set drive mapping
                        M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
                        M92 X80.00 Y80.00 Z80.00 E400.00 ; set steps per mm
                        M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
                        M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
                        M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
                        M906 X1200 Y1200 Z1200 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent
                        M84 S30 ; Set idle timeout

                        ; Axis Limits
                        M208 Z0 S1 ; set minimum Z

                        ; Endstops
                        M574 X2 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop
                        M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
                        M574 Z2 S1 P"zstop" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin zstop

                        ; Z-Probe
                        M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
                        M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
                        G31 P500 X0 Y20 Z5 ; set Z probe trigger value, offset and trigger height
                        M557 R150 S45 ; define mesh grid

                        ; Z-Probe
                        ;M307 H3 A-1 C-1 D-1 ; Disable Heater 3 for use with BLTouch
                        ;M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
                        ;M558 P9 C"^zprobe.in" H5 F120 T12000 ; set Z probe type to bltouch and the dive height +
                        ;G31 P500 X-40 Y2 Z2.5 ; set Z probe trigger value, offset and trigger height
                        ;M557 R150 S45 ; define mesh grid

                        ; Heaters
                        M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
                        M305 P0 T100000 B4350 R4700
                        M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
                        M307 H0 A139.8 C532.3 D4.7 S1.00 V24.1 B0 ; enable bang-bang mode for the bed heater and set PWM limit
                        M140 H0 ; map heated bed to heater 0
                        M143 H0 S120 ; set temperature limit for heater 0 to 120C
                        M308 S1 P"e0temp" Y"thermistor" T100000 B4138
                        M305 P1 T100000 B4350 R4700 ; configure sensor 1 as thermistor on pin e0temp
                        M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
                        M307 H1 R1.885 C176.8 D11.62 S1.00 V23.8 ; disable bang-bang mode for heater and set PWM limit
                        M143 H1 S280 ; set temperature limit for heater 1 to 280C
                        M307 H1 B0 S1.00

                        ; Heaters
                        ;M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 ;configure sensor 0 as thermistor on pin bedtemp
                        ;M305 P0 T100000 B4350 R4700
                        ;M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
                        ;M307 H1 R1.885 C176.8 D11.62 S1.00 V23.8 ; enable bang-bang mode for the bed heater and set PWM limit
                        ;M307 H0 A139.8 C532.3 D4.7 S1.00 V24.1 B0
                        ;M140 H0 ; map heated bed to heater 0
                        ;M143 H0 S100 ; set temperature limit for heater 0 to 100C
                        ;M308 S1 P"e0temp" Y"thermistor" T100000 B4750 R5200 ; configure sensor 1 as thermistor on pin e0temp
                        ;M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to ;sensor 1
                        ;M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

                        ; Fans
                        M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
                        M106 P0 S0.3 H-1 ; set fan 0 value. Thermostatic control is turned off
                        M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
                        M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off

                        ; Tools
                        M563 P0 D0 H1 F0:1 ; define tool 0
                        G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
                        G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

                        ; Custom settings
                        M591 D0 C3 P2 E6.0

                        ; Miscellaneous
                        M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

                        Phaedruxundefined 1 Reply Last reply Reply Quote 0
                        • fcwiltundefined
                          fcwilt @azaelaguirre
                          last edited by fcwilt

                          @azaelaguirre said in PROBLEM WITH BLTOUCH:

                          @fcwilt I already did it, when sending m401 it does nothing

                          Does your deployprobe.g file still have the M280 160 in it?

                          If so remove that line and remove the I1 from the line above it.

                          Frederick

                          Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                          azaelaguirreundefined alankilianundefined 2 Replies Last reply Reply Quote 1
                          • azaelaguirreundefined
                            azaelaguirre @fcwilt
                            last edited by

                            @fcwilt okey thats works !!! thanks a lot, but now i have another problem hahaha when im send auto calibration this happen:

                            15/2/2022, 19:26:57 Error: Probe was not triggered during probing move
                            15/2/2022, 19:26:11 Error: Compensation or calibration cancelled due to probing errors
                            Warning: Skipping grid point X=-45.0, Y=-135.0 because Z probe cannot reach it
                            Warning: Skipping grid point X=0.0, Y=-135.0 because Z probe cannot reach it
                            Warning: Skipping grid point X=45.0, Y=-135.0 because Z probe cannot reach it
                            15/2/2022, 19:25:41 Error: Probe was not triggered during probing move
                            15/2/2022, 19:25:35 G32
                            Error: Probe was not triggered during probing move

                            fcwiltundefined 1 Reply Last reply Reply Quote 0
                            • fcwiltundefined
                              fcwilt @azaelaguirre
                              last edited by

                              @azaelaguirre said in PROBLEM WITH BLTOUCH:

                              @fcwilt okey thats works !!! thanks a lot, but now i have another problem hahaha when im send auto calibration this happen:

                              15/2/2022, 19:26:57 Error: Probe was not triggered during probing move
                              15/2/2022, 19:26:11 Error: Compensation or calibration cancelled due to probing errors
                              Warning: Skipping grid point X=-45.0, Y=-135.0 because Z probe cannot reach it
                              Warning: Skipping grid point X=0.0, Y=-135.0 because Z probe cannot reach it
                              Warning: Skipping grid point X=45.0, Y=-135.0 because Z probe cannot reach it
                              15/2/2022, 19:25:41 Error: Probe was not triggered during probing move
                              15/2/2022, 19:25:35 G32
                              Error: Probe was not triggered during probing move

                              Hi,

                              Please post all of your homing files (4) using the </> tag - one tag per file.

                              Also post your bed.g file, if you have one and your mesh.g file, if you have one.

                              Frederick

                              Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                              azaelaguirreundefined 2 Replies Last reply Reply Quote 2
                              • Phaedruxundefined
                                Phaedrux Moderator @azaelaguirre
                                last edited by

                                @azaelaguirre said in PROBLEM WITH BLTOUCH:

                                G31 P500 X0 Y20 Z5

                                Is your Bltouch trigger height really 5mm? It must be measured.

                                I suggest you work your way through this guide for getting your probe working now that the pin is functioning.

                                https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing

                                Z-Bot CoreXY Build | Thingiverse Profile

                                azaelaguirreundefined 1 Reply Last reply Reply Quote 1
                                • azaelaguirreundefined
                                  azaelaguirre @fcwilt
                                  last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • azaelaguirreundefined
                                    azaelaguirre @fcwilt
                                    last edited by

                                    @fcwilt
                                    this is my home files, i dont have mesh.g

                                    </> ; homeall.g
                                    ; called to home all axes
                                    ;
                                    ; generated by RepRapFirmware Configuration Tool on Tue Oct 09 2018 13:27:56 GMT+0300
                                    G91 ; relative positioning
                                    G1 Z5 F6000 H2 ; lift Z relative to current position
                                    G1 H1 X-355 Y355 F6000 ; move quickly to X or Y endstop and stop there (first pass)
                                    G1 H1 X-355 ; home X axis
                                    G1 H1 Y355 ; home Y axis
                                    G1 X5 Y-5 F6000 ; go back a few mm
                                    G1 H1 X-355 F360 ; move slowly to X axis endstop once more (second pass)
                                    G1 H1 Y355 ; then move slowly to Y axis endstop
                                    G90 ; absolute positioning
                                    ;G1 X152 Y166.4 F6000 ; go to first bed probe point and home Z
                                    G1 X121.5 Y155 F6000 ; Move Probe to middle of bed
                                    G30 ; home Z by probing the bed

                                    ; Uncomment the following lines to lift Z after probing
                                    ;G91 ; relative positioning
                                    ;G1 S2 Z5 F100 ; lift Z relative to current position
                                    ;G90 ; absolute positioning
                                    </>

                                    </>; homedelta.g
                                    ; called to home all towers on a delta printer
                                    ;
                                    ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Feb 14 2022 15:51:11 GMT-0600 (hora estándar central)
                                    G91 ; relative positioning
                                    G1 H1 X705 Y705 Z705 F1800 ; move all towers to the high end stopping at the endstops (first pass)
                                    G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
                                    G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
                                    G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
                                    G90 ; absolute positioning
                                    G1 X0 Y0 F6000 ; move X+Y to the centre
                                    </>

                                    </>; homex.g
                                    ; called to home the X axis
                                    ;
                                    ; generated by RepRapFirmware Configuration Tool on Tue Oct 09 2018 13:27:56 GMT+0300
                                    G91 ; relative positioning
                                    G1 Z5 F1000 H2 ; lift Z relative to current position
                                    G1 H1 X-355 F6000 ; move quickly to X axis endstop and stop there (first pass)
                                    G1 X5 F3000 ; go back a few mm
                                    G1 H1 X-355 F360 ; move slowly to X axis endstop once more (second pass)
                                    G1 Z-5 F1000 H2 ; lower Z again
                                    G90 ; absolute positioning
                                    </>

                                    </>; homey.g
                                    ; called to home the Y axis
                                    ;
                                    ; generated by RepRapFirmware Configuration Tool on Tue Oct 09 2018 13:27:56 GMT+0300
                                    G91 ; relative positioning
                                    G1 Z5 F6000 H2 ; lift Z relative to current position
                                    G1 H1 Y355 F6000 ; move quickly to Y axis endstop and stop there (first pass)
                                    G1 Y-5 F3000 ; go back a few mm
                                    G1 H1 Y355 F360 ; move slowly to Y axis endstop once more (second pass)
                                    G1 Z-5 F1000 H2 ; lower Z again
                                    G90 ; absolute positioning

                                    </>

                                    </>; homez.g
                                    ; called to home the Z axis
                                    ;
                                    ; generated by RepRapFirmware Configuration Tool on Tue Oct 09 2018 13:27:56 GMT+0300
                                    G91 ; relative positioning
                                    G1 Z5 F6000 H2 ; lift Z relative to current position
                                    G90 ; absolute positioning
                                    ;G1 X152 Y166.4 F6000 ; go to first probe point
                                    G1 X121.5 Y155 F6000 ; Move Probe to middle of bed
                                    G30 ; home Z by probing the bed

                                    ; Uncomment the following lines to lift Z after probing
                                    ;G91 ; relative positioning
                                    ;G1 S2 Z5 F100 ; lift Z relative to current position
                                    ;G90 ; absolute positioning
                                    </>

                                    </>; bed.g
                                    ; called to perform automatic delta calibration via G32
                                    ;
                                    ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Feb 14 2022 15:51:11 GMT-0600 (hora estándar central)
                                    M561 ; clear any bed transform
                                    G28
                                    M98 Pdeployprobe.g
                                    ; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation
                                    ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
                                    G30 P0 X0 Y132.28 H0 Z-99999
                                    G30 P1 X121 Y69.86 H0 Z-99999
                                    G30 P2 X129.9 Y-75 H0 Z-99999
                                    G30 P3 X0 Y-150 H0 Z-99999
                                    G30 P4 X-125.9 Y-75 H0 Z-99999
                                    G30 P5 X-121 Y69.86 H0 Z-99999
                                    G30 P6 X0 Y59.15 H0 Z-99999
                                    G30 P7 X56.09 Y32.38 H0 Z-99999
                                    G30 P8 X64.95 Y-37.5 H0 Z-99999
                                    G30 P9 X0 Y-75 H0 Z-99999
                                    G30 P10 X-64.95 Y-37.5 H0 Z-99999
                                    G30 P11 X-56.09 Y32.38 H0 Z-99999
                                    G30 P12 X0 Y0 H0 Z-99999 S6
                                    ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
                                    ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
                                    M98 Pretractprobe.g
                                    G29
                                    </>

                                    1 Reply Last reply Reply Quote 0
                                    • Phaedruxundefined Phaedrux moved this topic from Gcode meta commands
                                    • azaelaguirreundefined
                                      azaelaguirre @Phaedrux
                                      last edited by

                                      @phaedrux I already did that I have the trigger in .79mm

                                      1 Reply Last reply Reply Quote 0
                                      • Phaedruxundefined
                                        Phaedrux Moderator
                                        last edited by

                                        Then you need to update your G31 Z value with your trigger height as well as the XY offsets.

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        azaelaguirreundefined 2 Replies Last reply Reply Quote 1
                                        • azaelaguirreundefined
                                          azaelaguirre @Phaedrux
                                          last edited by azaelaguirre

                                          This post is deleted!
                                          1 Reply Last reply Reply Quote 0
                                          • azaelaguirreundefined
                                            azaelaguirre
                                            last edited by

                                            @phaedrux how i can send you a vid3o ?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA