Z Probe deploy
-
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?
-
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
M402Frederick
-
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 .
-
@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?
-
you could try and set the probe type to P9
then M401 and M402 are called automatically -
I am using P9 but the probe deploy seems to be cancelled by the probe already triggered error.
-
@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
-
@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
-
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.5everything works correctly now.
-
@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.5everything works correctly now.
Very good - I've never used that command but I have heard about it.
Thanks.
Frederick