uCNC with bltouch-height map probe alarm and moving z up

[MarcoB979]

I have installed uCNC on my mks DLC32 with a bltouch as a probe. Single probe with macro works (g38, reset alarm after probe touches, set z to zero and move up a little).

When applying the height map feature i expected a similar behaviour. But when i run the height map, the bltouch goes down at the first point and triggers an alarm (which is supposed to happen i think), but the alarm is not reset. Next point bltouch is still in alarm state so z axis moves up a little. Same for all the next points. Would this be something related to uCNC, did I make a mistake or is there something in the software that can be configured?

[deHarro]

Hi Marco!
You are referencing uCNC...
Here we are at OpenCNCPilot.
Are you sure, you are asking in the correct discussion?

If you by mistake mentioned the wrong software and are actually talking about OpenCNCPilot, then you have to know, that the underlying GRBL has no support for standard BlTouch sensors, out of the box.
But you may have a look over here or here (language is German, but at the lower end of each page there is a link to Google translate).

Harry

[deHarro]

Oh, I see... I was totally offroad in seeing uCNC as a software as OCP.
In truth, it is a replacement for GRBL. I missed that fact - Sorry!
Since I do not use uCNC, I'm done... 😊

[deHarro]

But reading again your description...
BlTouch has an inbuild LED displaying the internal state of the sensor (touched, ready for touching, error, ...).
Does the BlTouch show "ready for touching" shortly after the first touch event?
If not, uCNC misses the "lower pen" signal for the sensor to again go into "ready for touching" state.
I don't know the colors for the different states of the sensor, you have to look that up elsewhere.

[MarcoB979]

What happens is the bltouch puts the pin out (blue color), does the probe and gives alarm (red/blue blinking) and normally should release the alarm immediately and stow (red light). Then next point it starts over.

Currently it is not resetting the alarm and was wondering if this could be configured in the opencncpilot software.

At this moment it looks like a missing release alarm instruction in the uCNC software and patiente is looking into this. Apart from that i was wondering if there was some way for opencncpilot to configure what the probe needs to to in each probe motion cycle. But it looks like this should be configured in uCNC

[deHarro]

I'm with you, thinking it's lying in uCNC, as I don't know an adequate option for probing in OCP.
OCP only moves Z up and expects Alarm state going OFF on its own.

[MarcoB979]

So it is doing a z move up and then a g38.x only. Then indeed it has to be fixed/handled in the firmware itself. Working on this with the creator of uCNC allready. To be continued