Mesa 7i76E estop

rodw wrote:

If your drivers have alarms, you can connect them to joint.N.amp−fault−in

On the machine with Lam Technologies drives i have that wired ad functioning, had that trigger once due to the new 12 meter long machine torch and torch cable that is unshielded ! Caused some raised eyebrows for several days triggering all kinds of errors at torch fire, turns out a new 12m cable/torch costing a smidge under 500 Euro is cheap for a reason = no shielding.
The fault feature is very nice as it shows the joint/axis that faulted making troubleshooting much easier.

Yes, enabled, checked where it stopped in gcode and gremlin, F9 + run from here.
After some thinking that day it occurred to me that i could roll back to the start of that part>disable the torch>run from here>pause near the point where it failed>use the fwd-rev to position it accurately>enable the torch>resume from pause.
I was sure that it had lost the position as Lam takes a while to send the fault, but luckily the faulted drive was not mowing when it error-ed, it happened on a straight line move on Y axis, the X faulted.
I really have to order some shielding for that torch, i still have the feeling it will do that again, it has not in over 3 weeks, but it will !

Should be easy enough to do using normal inputs tied to pause and "mesage" to alert on what axis drive faulted, but that would also need another button to reset the "enable" on the drives and be interlocked with the normal enable, or have 3 or 4 separate buttons one for each axis drive, since we have enough IO pins.

BTW, mine faulted as "short on motor wires" as it had that torch cable going in parallel with all other cables for over 7 meters.
And motor cables are also not shielded, can not find that here.