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

    M500 P31 NOT saving XY offset of probe

    Scheduled Pinned Locked Moved Solved
    General Discussion
    4
    8
    315
    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.
    • apakundefined
      apak
      last edited by

      M500 P31 NOT saving XY offset of probe

      my config.g

      ; Z-Probe
      M558 P8 C"zprobe.in" H5 F360:500 T9000 R0.4 A3 S0.03 ;B1             ; Set Z probe type mini ir sensor			
      G31 P500 X18 Y-38 Z2.38					    ; set Z probe trigger value, offset and trigger height
      M557 X18:310 Y15:285 P3						; define mesh grid P6 for a 6x6 mesh
      

      running this macro to calculate z offset

      G31 P100 X0 Y0 Z0 										; Reset Z trigger height to 0mm
      M290 R0 S0 												; Reset babystepping
      G29 S2 													; Clear bed mesh
      M561                  									; clear any existing bed transform
      M208 S1 Z-5 											; allow movement below Z0 reaching -5mm below Z0
      if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
              G28												; home all axis without mesh bed level
      G1 X146 Y198 Z10 F6000 									; Move close to the bed
      G30 													; Probe to find a rough Z 0mm
      G1 Z1 F3000 									; Move the nozzle to Z 1mm slowly
      G92 Z3.0 												; Set the Z height to 3mm, allowing moves below 0
      M291 P"Lower the nozzle to until it touches a 0.10mm shim. Click to continue." S2 Z1
      G92 Z0													; Define this point as 0mm
      G1 Z5 F3000										; Move the probe to Z 5mm
      G30 S-3 												; Probe and set the trigger height
      G1 Z20 													; Raise Z to 10mm
      M291 P"Do you want to save new offset to config-override?. Click to continue." S3
      M500 P31												; save Z offset to config-override.g
      M501													; load values from config-override.g
      M208 S1 Z0 												; disallow movement below Z0
      

      when saved at override it saves like this

      ; config-override.g file generated in response to M500 at 2021-11-23 22:11
      ; This is a system-generated file - do not edit
      ; Heater model parameters
      M307 H0 R0.322 C632.982:632.982 D5.13 S1.00 V24.3 B0 I0
      M307 H1 R2.813 C295.614:204.933 D6.24 S1.00 V24.5 B0 I0
      ; Z probe parameters
      G31 K0 P100 X0 Y0 Z1.99
      ; Probed tool offsets
      G10 P0 Z0.00
      ; Workplace coordinates
      G10 L2 P1 X0.00 Y0.00 Z0.00
      G10 L2 P2 X0.00 Y0.00 Z0.00
      G10 L2 P3 X0.00 Y0.00 Z0.00
      G10 L2 P4 X0.00 Y0.00 Z0.00
      G10 L2 P5 X0.00 Y0.00 Z0.00
      G10 L2 P6 X0.00 Y0.00 Z0.00
      G10 L2 P7 X0.00 Y0.00 Z0.00
      G10 L2 P8 X0.00 Y0.00 Z0.00
      G10 L2 P9 X0.00 Y0.00 Z0.00
      

      P value and must of all, X and Y values of G31 line are not saved with current XY offset value.

      How could I save it correctly?

      jay_s_ukundefined pfnundefined Phaedruxundefined 3 Replies Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @apak
        last edited by

        @apak what firmware version?

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        apakundefined 1 Reply Last reply Reply Quote 0
        • apakundefined
          apak @jay_s_uk
          last edited by

          @jay_s_uk

          FW3.3
          DWC3.3
          PanelDue 3.3

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @apak
            last edited by

            @apak I believe it's a known issue and has been fixed in the 3.4 betas

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            apakundefined 1 Reply Last reply Reply Quote 0
            • pfnundefined
              pfn @apak
              last edited by pfn

              @apak I'm confused, doesn't the first line of your macro set X/Y offset to 0? When you save, I would expect it to save 0?

              This situation is clear because you previously had P500 in config.g, but the value saved in config-override is P100, the value from the first line of your macro.

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

                @apak said in M500 P31 NOT saving XY offset of probe:

                G31 P100 X0 Y0

                If you remove the X0 Y0 from the start of your macro does it keep the values set in config.g?

                Z-Bot CoreXY Build | Thingiverse Profile

                apakundefined 1 Reply Last reply Reply Quote 0
                • apakundefined
                  apak @Phaedrux
                  last edited by apak

                  @phaedrux complety missed that, will try right away

                  WORKED!!!! thanks, my bad, didn´t focused on that

                  1 Reply Last reply Reply Quote 0
                  • apakundefined
                    apak @jay_s_uk
                    last edited by

                    @jay_s_uk you where right...my bad

                    1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined Phaedrux marked this topic as a question
                    • Phaedruxundefined Phaedrux has marked this topic as solved
                    • First post
                      Last post
                    Unless otherwise noted, all forum content is licensed under CC-BY-SA