Duet3D Logo

    Duet3D

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

    Z Probe deploy

    General Discussion
    4
    10
    125
    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.
    • micktol
      micktol last edited by

      I have a duet 2 ethernet running rrf v3. I am trying to set up a z probe which is a servo controlled as here https://www.thingiverse.com/thing:3303618 .

      When I send g30 the probe does not deploy and I receive the probe already triggered message.

      M401 and M402 work correctly and if I deploy the probe then send M30 it probes and retracts at the end.

      How can I get the probe to deploy before the error?

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

        Hi,

        I think with this kind of probe you have to use the M40x codes to deploy/retract the probe.

        Did you try this:

        M401
        G30
        M402

        Frederick

        Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

        1 Reply Last reply Reply Quote 0
        • micktol
          micktol last edited by

          Thank you for your reply.
          When I send M401 then G30 it probes and then retracts so it is half working!

          IF I send just G30 the servo starts to move and then stops with the error, so I thinks it needs a delay but I have no idea how to implement it .

          1 Reply Last reply Reply Quote 0
          • jay_s_uk
            jay_s_uk last edited by

            @micktol have you followed this? https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Software_setup_RepRapFirmware_Num_3

            Can you post your config.g and your deploy and retract files?

            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

            1 Reply Last reply Reply Quote 0
            • Veti
              Veti last edited by

              you could try and set the probe type to P9
              then M401 and M402 are called automatically

              1 Reply Last reply Reply Quote 0
              • micktol
                micktol last edited by

                I am using P9 but the probe deploy seems to be cancelled by the probe already triggered error.

                Veti fcwilt 2 Replies Last reply Reply Quote 0
                • Veti
                  Veti @micktol last edited by Veti

                  @micktol said in Z Probe deploy:

                  I am using P9 but the probe deploy seems to be cancelled by the probe already triggered error.

                  ah then you have to switch to P8 and add the M401 and M402 to the homing scripts

                  1 Reply Last reply Reply Quote 1
                  • fcwilt
                    fcwilt @micktol last edited by

                    @micktol said in Z Probe deploy:

                    I am using P9 but the probe deploy seems to be cancelled by the probe already triggered error.

                    The BLTouch is quick to deploy/retract so I'm guessing the timing that is part of P9 is correct for the slower servo in your probe.

                    The reason for the "already triggered" error is because when the servo unit is retracted it also activates the switch. Since the servo is slow to deploy it appears the switch is still activated when the probe is checked as to it's state.

                    You will need to use one of the types meant for switches and use the M40x commands as needed.

                    Frederick

                    Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

                    1 Reply Last reply Reply Quote 0
                    • micktol
                      micktol last edited by

                      Thanks to everybody who replied, I have now found the solution.

                      In deployprobe.g I added a dwell so now it is:

                      M280 P0 S10
                      g4 s0.5

                      everything works correctly now.

                      fcwilt 1 Reply Last reply Reply Quote 1
                      • fcwilt
                        fcwilt @micktol last edited by

                        @micktol said in Z Probe deploy:

                        Thanks to everybody who replied, I have now found the solution.

                        In deployprobe.g I added a dwell so now it is:

                        M280 P0 S10
                        g4 s0.5

                        everything works correctly now.

                        Very good - I've never used that command but I have heard about it.

                        Thanks.

                        Frederick

                        Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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