Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Tip for servo based Z-Probes!!!

    Tuning and tweaking
    3
    4
    424
    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.
    • brunofporto
      brunofporto last edited by

      My probe, https://www.thingiverse.com/thing:2890290, was having some issues when homing Z. It sometimes had false detections, due to the fact that when it is retracted it is triggered, and was "jumping" the first pass step fo my home z and home all macros.

      All the issues was solved with a simple line after the M280 command within deployprobe.g macro:

      G4 P300 ; Wait 0.3 sec.

      And that is it... Now the probe have time to actually deploy before the Duet try to read it 😄

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

        Does adding an R value to the M558 command have a similar effect?

        brunofporto 1 Reply Last reply Reply Quote 1
        • brunofporto
          brunofporto @Phaedrux last edited by brunofporto

          @phaedrux said in Tip for servo based Z-Probes!!!:

          Does adding an R value to the M558 command have a similar effect?

          I seems so! Much better if it is. I'll try later (printing a calibrating cube now). Thank you!

          But... it is a timer AFTER the trigger.... Maybe it is not the case - I needed a time between deploy and use of the probe so the servo can move.

          dc42 1 Reply Last reply Reply Quote 0
          • dc42
            dc42 administrators @brunofporto last edited by

            The R parameter inserts a delay just before the start of the probing move. So this delay will occur after calling the deploy macro, and also after any travel move to get to the probe point. If you only need the delay immediately after commanding deployment, then the G4 command in deployprobe.g is more optimal.

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