"Error: Probe was not triggered during probing move"
-
-
@ignacmc one thing to check, please send G31 with no parameters after running through the last test.
Also to triple check, you are still on RRF 3.4.5?
-
@T3P3Tony Yes. I am still on 3.4.5 (2022-11-30) My birthday by the way ;-)...what a bad luck!
if I do G28, then G30 and finally G31 I got:
By the way even with the nozzle resting on the bed I still get "current reading 0" Is this normal?
Should I try to downgrade the firmware to an older version or upgrade to the latest beta?
Thank you so much for you time, Tony!
-
@ignacmc by the way, other people in my spanish Telegram group are telling me to change the cable, but I am reluctant to do it unless it is the last choice.
If the probe is detecting the bed and going back despite the Error this should prove the wiring is ok, right?
-
@ignacmc I think the wiring is correct, If the probe is resting on the bed with no force then it may still show 0, if you jog it down slightly it should trigger.
The only difference I can see is that you have the threshold set to 500, and I have it set to 100. Just to rule this out try:
G31 P100 X0 Y0 Z-0.1 -
@T3P3Tony Yes I had played with P100 sensivity before, but just in case I have followed your suggestion and retried just now.
Still getting the same error after G30
I am starting to hate this machine....;-) It is kinda cursed!
-
Have you recently disassembled the smart effector and reassembled?
-
-
undefined Phaedrux marked this topic as a question
-
-
@ignacmc Update. I changed the 6 wire cable foint to the effector for a new one and the same Error Persists. I cannot see any other cause than the Duet3Mini or the Smarteffector itself have some hardware problem...
-
-
undefined Phaedrux has marked this topic as solved
-
@ignacmc thanks for confirming!
Any clue about what is happening here? Can it be a hardware fault on the Smarteffector or the Duet3 Mini5+? How could I check this?