Hi,
The only reason I started with Input 2 was when I looked in the Sig Lib there was already entries for Inputs 0 and 1. Just figured it would be easier not to mess with those.
Yes that's good.
Just need to know the motors are working so the machine doesn't rip it self apart if one drops out
That's pretty crude...even for proof of concept. The 'In Range' HLFB is the correct use of the signal, if the servo differs from its commanded position
by greater than an amount you program it will fault. Note that would include one servo shutting down...it would get out of position very quickly and fault,
stopping the machine.
Also, that wouldn't fix the problem of Mach4 not responding to changes in those inputs after the machine is enabled, right?
Wrong. Read section 3.2.4 of the Scripting Manual.pdf in your Docs folder about how signals work.
The simple explanation is that ANYTIME a signal, ANY SIGNAL, in Mach changes state the Signal Script runs. The Signal Script in turn looks
in the SigLib table to see if there is an entry there which matches the changed signal. That is the SigLib table contains only the signals we are interested
in. Thus in this case lets say one of your servos fault in operation....the HLFB will de-assert.....the Input#n to which it is attached will change state....the Signal
Script will run....the SigLib table has an entry [ISIG_INPUTn] and will therefore execute the function attached to the table entry, which will stop Mach and
post a fault report on the status line or in the log if you wish it.
Craig