Probe dive and jog

[rjreese29]

Hi,

I encountered an issue when pressing the z probe button to find the top surface. At that time my probe was monted and was searching for the top surface I must have hit a jog button. It ended up crashing the probe into my work and breaking the ruby stone.

My proper probe tool is mounted using mdi, therefore that as an issue can be ruled out.

Where my issue lies as I have replicated it is to probe z and then hit any jog button x,y and/or z As it is probing. It then at that point has the ability to ignore any relevant or irrelevant probing event and will crash(irrelevant being an event that would trigger a probing error).
An example of this would be probing for the z zero surface, as it actively searching, I can (intentionally , and unintentionally as i have encountered) jog it in any direction, and change directions in all 3 axis. It will then continue in the commanded direction and ignore any probe input, thus crashing.
Upon my retests, it seems avoidable by never hitting a jog button, but the use of an Xbox controller would make it prone to this kind of accident.

I am using an Xbox controller as this may present an issue as this controller has some background functionality. Just a thought.

I will be testing for replicating this on the standard arrow (keyboard) jog keys tonight.
Any suggestions for testing or known errors would be greatly appreciated.
Moving cautiously and putting the controller down when probing;)

Thanks
Rob

[DaveCVI]

Ugh...
I believe this is an undesired side effect of the "asynchronous, no locking, run everything in parallel" aspect of mach that makes me rant and use words my mother would not approve of...

The core problem is that mach has no internal concept of a core state machine for basic CNC controller state. Every control you click causes an action in mach, and there is no internal coordination to provide reasonable lockouts.

I'll also tell you that you should never use the MDI control while a gcode program is running (see MSM release notes 4.20 for this way to crash a machine).

In the case of jogging, I suppose that it may be possible to disable jogging during any probing operation. I'd have to do some serious checking to find out (It's not simple when you start considering all the error recovery paths in the code). I'll think about this some, but can't make any promises as to this.

In the mean time, you know the old joke? "Dr. it hurts when I do this.... so don't do that son..."

Dave