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

    G30 Question

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    6
    262
    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.
    • JADoglioundefined
      JADoglio
      last edited by

      I built a Voron 2.4R2 using a klicky probe. I have a couple macros written to assist with Z offset calibration. I probe the bed using G30 3 times to get the height average for Z offset. The problem is every time I run G30 to get a measurement the firmware docks the klicky then undocks it takes a measurement, then docks and undocks the probe again for each subsequent probe. The macros are included. Is there a command that will just probe the bed without docking and undocking the probe ever time? Thanks

      The process starts with running the macro Z Offset Calibration in the macro file
      M561 ;clear Bed Mesh
      M568 P0 S240 ;set active temperatures for tool 0
      M140 S70 ;set Bed to 60C
      M116 S5 ;wait until bed 0 and tool 0 are up to temperature
      M564 S0 ;allow Z axis to exceed preset limits

      ; Home, but only if homing is needed
      if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
      G28

      G1 E-30 ;retract filament so nozzle does not ooze
      G1 Z55 F12000 ;raise Z axis 50mm for cleaning

      ;M291 P"Clean All Residue From Nozzle before setting Z0"
      M98 P"Clean Nozzle"
      G1 Z2

      ; Home, but only if homing is needed
      if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
      G28
      M291 P"Use to pieces of paper and jog the nozzle down to the right tension on the bed" R"Press Ok when Done?" S3 X1, Y1, Z1 ;instruct user to manualy move nozzle to bed
      G92 Z0 ;Sets current location as Z0 Position
      M98 P"Z Offset Calibration Finish" ;Call Macro to finish job

      Z Offset Calibration Finish
      G90 ;set absolute
      G1 Z30 ;raise Z up 10 mm
      G30 S-1 ;(G30) home z (S-1) record z height
      G4 P1000 ;pause 1 sec
      G1 Z30 ;raise Z up 10 mm
      G30 S-1 ;(G30) home z (S-1) record z height
      G4 P1000 ;pause 1 sec
      G1 Z30 ;raise Z up 10 mm
      G30 S-1 ;(G30) home z (S-1) record z height
      G4 P1000 ;pause 1 sec
      G1 Z30 ;raise Z up 10 mm
      G1 X175 Y175 ;move Hot End to X175 Y175
      M291 P"Check Consul for Results of Probing " ;instruct user to check results in Consol
      ;G28

      chrishammundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators @JADoglio
        last edited by chrishamm

        @JADoglio At present G30 always deploys/retracts the probe because that's required to drive a BLTouch and possibly other probes. Perhaps it would make more sense to define your Z-probe as a second tool and to do the dock/undock procedures in the corresponding tpre/tfree.g.

        Duet software engineer

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

          @JADoglio you could send M401 before running any G30's and then M402 when finished. This should override the deploy for the G30

          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

          JADoglioundefined 1 Reply Last reply Reply Quote 1
          • JADoglioundefined
            JADoglio @chrishamm
            last edited by

            @chrishamm Thanks I will investigate.

            1 Reply Last reply Reply Quote 0
            • JADoglioundefined
              JADoglio @jay_s_uk
              last edited by

              @jay_s_uk Again, thanks I will play with this as well

              JADoglioundefined 1 Reply Last reply Reply Quote 0
              • JADoglioundefined
                JADoglio @JADoglio
                last edited by

                @JADoglio I tried the 401/402 option first since it seemed simpler than creating another tool which I suspect would have also worked. This option worked as expected. Problem solved, Thanks

                1 Reply Last reply Reply Quote 1
                • 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