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

Spoted a little bug on Z prob I think

Scheduled Pinned Locked Moved Solved
General Discussion
3
6
273
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.
  • undefined
    Donpi
    last edited by 1 Dec 2020, 06:58

    Hi,

    when I home Z and the blTouch senor is allready triggered.
    I get the message that the sensor is allready triggered and no z movement.
    This is the expected behaviour, I hope.

    What I think is a bug is that the Z change state to homed.
    I think It should remain unhomed.

    I use RFF 3.1.1, a Duet 3 and a blTouch.
    And here is my homez.g

    ;Clear bed transformation
    N561
    ;Goto prob position
    G91
    G1 H2 Z5 F6000
    G90
    G1 X150 Y70 F6000
    G91
    ;Reset sensor
    M280 P0 S160
    ;Rough prob
    M402 ; Retract prob
    M401 ; Deploy prob
    G1 H1 Z-305 F6000
    M402 ; Retract prob
    ;Down 5mm
    G1 H2 Z5 F6000
    ;Fine prob
    M402 ; Retract prob
    M401 ; Deploy prob
    G30 ; Prob
    M402 ; Retract prob
    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 1 Dec 2020, 07:28

      I agree, it should remain not homed. I will test this.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators
        last edited by 1 Dec 2020, 12:59

        It's not a bug, it's because you are using the Z probe as an endstop switch in this line:

        G1 H1 Z-305 F6000

        That will mark Z as homed.

        You should use a G30 command for that line too. You can use M558 to set the probing speed (F parameter) to a higher value before the first G30 command, and restore it to the usual value for the second.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        undefined 1 Reply Last reply 1 Dec 2020, 13:49 Reply Quote 1
        • undefined
          Donpi @dc42
          last edited by 1 Dec 2020, 13:49

          @dc42 haha great I did as you said and by the way removed all those unnecessay M401 and M402.
          Now it remains not homed.

          Thank you.

          1 Reply Last reply Reply Quote 0
          • ?
            A Former User
            last edited by 1 Dec 2020, 13:58

            N561
            

            Also I think your code N561 is wrong.

            I think it should be M561: Set Identity Transform

            undefined 1 Reply Last reply 2 Dec 2020, 06:51 Reply Quote 1
            • undefined
              Donpi @A Former User
              last edited by 2 Dec 2020, 06:51

              @CaLviNx Thanks I didn't see this.
              By the way it explain some weird behaviour I had in the past 😛

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