G32 Error:´´ Z probe was not triggered during probing move´´

[dutti]

M280 P0 S160 is working.. now the question is what makes this problem ´..

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt
retract means the pin goes down.
hmm ok
what can it be?

OK we have a word problem.

DEPLOY means lower the pin. RETRACT means raise the pin.

So the M401 command should lower the pin and the M402 command should raise the pin

Is that happening?

Frederick

[dutti]

@fcwilt
ok I´m sry for that..
yes. It works (till the first probe point touches the Bl)

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt
ok I´m sry for that..
yes. It works (till the first probe point touches the Bl)

SO if the printer is just sitting there doing nothing and the BLTouch is far enough away from the bed so that the pin won't touch if it drops can you repeatedly raise and lower the pin using M401/M402 commands without any errors?

Frederick

[dutti]

@fcwilt
yes..

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt
yes..

OK good.

When the problem occurs is the pin hitting the bed when it tries to drop?

IF that happens it will cause an error.

The pin needs to be all the way down BEFORE the bed moves to touch the pin.

Frederick

[dutti]

@fcwilt
No. There is almost 1cm between the pin and the bed.

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt
No. There is almost 1cm between the pin and the bed.

SO the pin drops, does NOT touch the bed before it should, the bed moves towards the pin, touches the pin and THEN the error occurs?

Frederick

[dutti]

@fcwilt exactly

[dutti]

@barbarossa-cologne
and doing g32 it also comes to --: ´´ Z probe was not triggered during probing move´´
not when doing sinlge g30

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt exactly

OK it may be a wiring issue. I have read in more one post that redoing the wiring fixed a similar problem.

Frederick

See attached.

[dutti]

@fcwilt
thanks... it was the red cable
but there is still the problem with:

G29
Error: Z probe was not triggered during probing move

or:G32
Error: Z probe was not triggered during probing move

After the pin touches the bed the first probe point.
no flashing anymore or something else. just probing the first point and then it stops with this text.... help please.

[fcwilt]

@barbarossa-cologne

Well there are the 3 wires that control the BLTouch and the 2 wires the carry the signal FROM the BLTouch to the Duet.

So perhaps there is a problem with those 2 wires not making a connection or there is a wiring error with them.

Or it may be the P500 parameter in your G31 command. I use P25.

Frederick

[dutti]

@fcwilt
no wiring problem..... this time I triple checked everyting.
I try P500, now.

[dutti]

@fcwilt
new: G32
Error: Z probe already triggered before probing move started

[dutti]

@barbarossa-cologne
After reconnect the Bl it´s working fine...
started G32..... but the machine is doing G29. How can that be?
Usually G32 should be 4 probing points...
Is there something wrong in the G code?

I´m sorry to ask that much.... 80 percent of my questions are about the BL Touch.

[fcwilt]

@barbarossa-cologne

G32 invokes bed.g.

In bed.g you have G29 S3 with the comment "Clear bed height map".

You want to use S2 to clear the bed height map.

See if that makes a difference.

Frederick

[dutti]

@fcwilt thanks... I´ll try!

[dutti]

@fcwilt
same problem.... with G29 S2.
Also still a problem: After doing a single z probe, I have to reconnect the BL Touch before it´s working again. When doing G32, it´s doing G29. BUT then the BL is able to make a few probing points without stopping/ flashing.
I hate the BL haha

[dutti]

@barbarossa-cologne
is that normal.... doing G32 --> but the Duet Made a G29