Probe tripped during non-probe move deadlock

As a result, I started experimenting with Z-axis acceleration settings to reduce braking time. Previously, the acceleration was set to 2000. When I set the acceleration to 6000, no errors occurred over 14 hours of operation (115,000 measurements). When I set the acceleration to 12,000, I got an axis misalignment error. It works acceptably at an acceleration of 9,000.

@AkkiSan
github.com/LinuxCNC/linuxcnc/pull/3971
could you test this?

The axis desynchronization issue was caused by an error in my INI configuration—the parameters I had set required a frequency higher than 50 kHz. I changed the servo period, and the error disappeared.

“Probe tripped during non-probe move” is resolved by setting delays. In my case, using an electrical capacitor. Over 2 million activations.

This leads to the conclusion that it would be appropriate to implement a Probe delay parameter in the machine settings. “Feedback” delay. That is, when the probe triggers, the machine must immediately recognize this and begin braking, and then even execute the next command (typically, recording and rebound). And the specified parameter in seconds or milliseconds should not react to a change in the probe’s state.

I mentioned this here: forum.linuxcnc.org/39-pncconf/58480-conf...g-dual-y-axes#344832

I have "write a better debounce module" on my todo list. No guarantees