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

    Auto Tool Height Measurement

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    35
    1.8k
    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.
    • fcwiltundefined
      fcwilt @Terry
      last edited by

      @Terry said in Auto Tool Height Measurement:

      This will only be visible if you are testing against an endstop that is different to the one you referenced from in your homing move...

      Different in what way?

      I don't think it is possible to have more than one end stop configured at the same time for a given axis - aside from the situation where you have multiple Z steppers with an end stop for each.


      I did this:

      I moved Z down to 100 and issued G91 G1 H3 Z-150.

      I waited a bit and triggered the end stop - it was around 47.

      M208 now reported min of 47. I reset Z min with M208 Z0:240 which is correct for my printer.

      Moving to 0 and the end stop was just triggered as it should be.


      This I did this:

      I moved Z down to 100 and issued G91 G1 H4 Z-150.

      I waited a bit and triggered the end stop - it was around 53.

      Moving to 0 and the end stop was just triggered as it should be.

      Nothing else appears to have changed.


      Frederick

      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

      1 Reply Last reply Reply Quote 0
      • Terryundefined
        Terry
        last edited by

        Just found G38.2, which appears to be more suitable.

        After testing with

        M558 K1 P8 C"!1.io2.in" F1000
        G38.2 V1 P1
        

        I get the same problem! There appears to be a bug where the machine and user positions are always updated to be equal to the requested destination move, even though the move was interrupted by an endstop or probe trigger.

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

          @Terry said in Auto Tool Height Measurement:

          Just found G38.2, which appears to be more suitable.

          After testing with

          M558 K1 P8 C"!1.io2.in" F1000
          G38.2 V1 P1
          

          I get the same problem! There appears to be a bug where the machine and user positions are always updated to be equal to the requested destination move, even though the move was interrupted by an endstop or probe trigger.

          Perhaps so - because it did not happen in my testing - and the "home" position (which for my testing was 0) remained unchanged.

          I know that 3.2.0 had a bug which prevented my 3 Z stepper printer (each stepper had its own end stop) from homing.

          Frederick

          Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

          1 Reply Last reply Reply Quote 0
          • Terryundefined
            Terry
            last edited by

            Same bug is present on 3.2.2

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

              @Terry said in Auto Tool Height Measurement:

              Same bug is present on 3.2.2

              I wonder why you are seeing that and I'm not.

              What do your end stop configuration look like for the normal axis end stop and this switch end stop.

              Thanks.

              Frederick

              Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

              1 Reply Last reply Reply Quote 0
              • Terryundefined
                Terry
                last edited by

                Axis setup is:

                M569 P1.1 S0
                M584 V1.1
                M208 V0:100
                M92 V400
                M350 V16 I1	
                M566 V400
                M203 V10000
                M201 V6000
                M906 V1500
                M574 V2 S1 P"1.io1.in"
                

                Test macro is:

                M558 K1 P8 C"!1.io2.in" F1000
                G38.2 V1 P1
                
                M117 {move.axes[4].userPosition}
                
                fcwiltundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @Terry
                  last edited by

                  @Terry said in Auto Tool Height Measurement:

                  Axis setup is:

                  M569 P1.1 S0
                  M584 V1.1
                  M208 V0:100
                  M92 V400
                  M350 V16 I1	
                  M566 V400
                  M203 V10000
                  M201 V6000
                  M906 V1500
                  M574 V2 S1 P"1.io1.in"
                  

                  Test macro is:

                  M558 K1 P8 C"!1.io2.in" F1000
                  G38.2 V1 P1
                  
                  M117 {move.axes[4].userPosition}
                  

                  I will have to test using a probe.

                  Why are you echoing the userPosition instead of the machinePosition?

                  Frederick

                  Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                  1 Reply Last reply Reply Quote 0
                  • Terryundefined
                    Terry
                    last edited by

                    Just as a legacy of testing that machinePosition and userPosition were the same, which they are in this instance.

                    1 Reply Last reply Reply Quote 1
                    • fcwiltundefined
                      fcwilt
                      last edited by fcwilt

                      To test G1 H4 I created the following macros:

                      Macro to configure for normal Z end stop:

                      M574 Z1 S1 P"nil"
                      M574 Z1 S1 P"io3.in"
                      

                      Macro to configure for temporary Z end stop:

                      M574 Z1 S1 P"nil"
                      M574 Z1 S1 P"^!io4.in"
                      

                      Macro to test G1 H4

                      G90
                      G1 Z100 F600
                      echo "POST G90 G1 Z100 F600: machinePosition = " ^ move.axes[2].machinePosition ^ " === userPosition = " ^ move.axes[2].userPosition 
                      G60 S0
                      G91
                      G1 H4 Z50 F300
                      echo "POST G91 G1 H4 Z50 F300: machinePosition = " ^ move.axes[2].machinePosition ^ " === userPosition = " ^ move.axes[2].userPosition 
                      G90
                      G1 R0 Z0
                      echo "POST G90 G1 R0 Z0: machinePosition = " ^ move.axes[2].machinePosition ^ " === userPosition = " ^ move.axes[2].userPosition 
                      

                      I ran the macro to configure for the temporary Z end stop
                      I ran the macro to test G1 H4
                      I waited a bit and triggered the temporary Z end stop
                      I ran the macro to configure for the normal Z end stop

                      Here are the echo outputs:

                      POST G90 G1 Z100 F600: machinePosition = 100.000 === userPosition = 100.000

                      POST G91 G1 H4 Z50 F300: machinePosition = 129.786 === userPosition = 129.786

                      POST G90 G1 R0 Z0: machinePosition = 129.786 === userPosition = 100.000


                      The homed status of Z was not changed.


                      Frederick

                      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                      1 Reply Last reply Reply Quote 1
                      • Terryundefined
                        Terry
                        last edited by

                        Good, that seems to confirm that it's an issue with the 3HC firmware.

                        1 Reply Last reply Reply Quote 0
                        • jlipavsky79undefined
                          jlipavsky79
                          last edited by

                          did this ever get resolved? looking to do the exact same thing.....

                          1 Reply Last reply Reply Quote 0
                          • Dougal1957undefined
                            Dougal1957
                            last edited by

                            it may be worth looking into
                            https://jubilee3d.com/index.php?title=ZTATP

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