"Error: Probe was not triggered during probing move"

[ignacmc]

@T3P3Tony Ok. done exactly as you asked me to do: First G28, then G30 and the nozzle hits the bed, gives me the same error again and it goes up to Z 29.90. jogging it down to Z 0 it is still like 10mm above bed. See photo at Z=0

[T3P3Tony]

@ignacmc ok for now set the H value in M665 to 435 and try again.

once this is working, you will need to run delta calibration again anyway.

Are the other M665 parameters correct, e.g. R and L?

[ignacmc]

@T3P3Tony Yes, I had tried with higher H before without success. Now I have just tried with:

M665 R227.445 L440.718 B185 H435

I believe that R, L and B are correct for a Anycubic Predator

Error keeps happening

[T3P3Tony]

@ignacmc ok so with the higher H, go through the steps again:

home the printer

send G30

then jog down and see where Z0 is

[ignacmc]

@T3P3Tony OK, repeating all process with H435 in M665. G28, then G30, touch bed, Error again and now after hitting bed it goes up to Z29.90, jogging down manually, the paper gets gripped at Z4.80 (positive)

[T3P3Tony]

@ignacmc ok this is progress, in the sense its now behaving as expected, other than the error.

@dc42 any ideas?

[T3P3Tony]

@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?

[ignacmc]

@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]

@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?

[T3P3Tony]

@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

[ignacmc]

@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!

[Phaedrux]

Have you recently disassembled the smart effector and reassembled?

[ignacmc]

@Phaedrux No, I left it as it is two years ago:

[ignacmc]

@ignacmc @dc42 Hi David...you are my last hope 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?

Thanks in advance!

[ignacmc]

@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...

[ignacmc]

@ignacmc @jay_s_uk @Phaedrux @T3P3Tony @dc42

FINAL Update: I have updated firmware from 3.4.5 to 3.5.0 beta 3 and the error no longer happens, so it definitely seemed to be a bug in 3.4.5!

BTW, My Duet3 Mini5+ is a FYSETC clone.

YIPEEEEE!!!!!

[T3P3Tony]

@ignacmc thanks for confirming!