[joeavaerage]

Hi,
that guy had not set up the ESS correctly.

Imagine this move:

g31 z-5 f100

The probe will moves until it touches something OR it comes to the end of the move at z=-5mm. The ESS regards a g31 that DOES NOT touch something is a fault, it signals it and stops.
There is an alternative, where you can set the ESS to not fault out.

The probing module in Mach will often need to have the probe traverse from one location to the next. You could program that using either g1 or g0 moves....but what happens if there is something
in the way? The probe will be destroyed. So the programmers used g31 moves to traverse. This would mean if the probe accidently touched something on its way to the next probe location it would
stop and save the probe from being destroyed. Very clever. But it also means that Mach is entirely expecting many of its g31 moves to result in NO PROBE CONTACT. But this would cause the ESS to fault.

Craig

[boydage]

Hi,
that guy had not set up the ESS correctly.

Imagine this move:

g31 z-5 f100

The probe will moves until it touches something OR it comes to the end of the move at z=-5mm. The ESS regards a g31 that DOES NOT touch something is a fault, it signals it and stops.
There is an alternative, where you can set the ESS to not fault out.

The probing module in Mach will often need to have the probe traverse from one location to the next. You could program that using either g1 or g0 moves....but what happens if there is something
in the way? The probe will be destroyed. So the programmers used g31 moves to traverse. This would mean if the probe accidently touched something on its way to the next probe location it would
stop and save the probe from being destroyed. Very clever. But it also means that Mach is entirely expecting many of its g31 moves to result in NO PROBE CONTACT. But this would cause the ESS to fault.

Craig

Ok this had made me think a bit - good robust conversation. So on my own machine that check box is unchecked. And I beleive I did that so I could probe the top/corner operation successfully. I was unable to work out why I needed to do this. So to clarify, a corner probe operation is a 3 part probe with the corresponding moves to position. Its these positioning moves where my machine used to go into Estop. Is it correct then that the positioning moves are also G31 and when during those moves the ESS does not see a strike and errors out? Or am I on the wrong tree here. Anyway, I unchecked that box to get it working and it did.

But, even with that box unchecked, I am experiencing random estops. Although after reading through this I realised I still have a probe "flying lead" setup from the old days. Flying lead meaning just that with an alligator clip on one end and the other is actually grounded to my table. In the old days I clipped the alligator onto the end mill and touched off on the workpiece grounded through the vice/table. It is on a separate input pin but I am wondering if that is A introducing noise, or B somehow picking up an erronous signal which will then be a "wrong probe" contact and also error. So I am going to have a look at that tonight. I also think the only sheilding is on my latest build so yeh, I have something to look at instead of just pointing and crying when it fails again.

Have I missed anything? Lol Thanks guys

[joeavaerage]

Hi,
yes that is correct.

g31 (note the deliberate use of lower case, it is a habit you should get into with Mach4 as well) is if you like a modified g1 move. Recall the a g1 move has a destination and a feed rate. For example:

g1 z-50 f500 will cause the controlled point, wherever it is currently to move in the negative z direction at 500mm/min until z=-50mm. Conversely:

g31 z-50 f500 will cause the controlled point, wherever it is currently to move in the negative z direction at 500mm/min until either it touches something, ie a probe event OR it reaches z=-50mm
With the ESS checkbox checked the ESS would fault if it reached its terminal position WITHOUT encountering a Probe Event.

The programmers of Mach have used the equivalence of g1 and g31 to use g31 to make probe pre-positioning moves. With a prepositioning move Mach DOES NOT expect a probe event, that is normal.
If you wish to use Machs probing module you'll have to uncheck the box or use the M2010 macro as detailed in the ESS tab.

It is on a separate input pin but I am wondering if that is A introducing noise, or B somehow picking up an erronous signal which will then be a "wrong probe" contact and also error.

That is highly likely. Note on that same tab that Mach has four different probe inputs. What happens if you are probing on probe one and while that is happening probe triggers? It may be that represents a collision
in which case you want Mach to Estop. Then again it may have no bearing. There is a check box for that behaviour too.

Second issue is why have a piece of wire dangling around.....its a f.......king antenna....and yes it will collect noise, especially if its not been terminated with a known and suitably low impedance, not only is it an antenna
it could well be a very sensitive antenna to boot.

Craig