This may sound like dumb questions, but I have a customer that wants to use a mobile client for a setup application that concerns me. What does Ignition do to prevent “stuck” bit issues if a mobile client drops a connection. The way they currently address this issue on the current platform is that the client, to jog a motor increments a register continuously when a button is held down so that if the client looses connection the register stops incrementing and the jog stops. With the Mobile Client, the way I understand it, if we did this with a script that still would not matter since the script would be running on the server, so a stuck bit would never be detected, unless IA has some watchdog timers going on behind the scenes that would kill the process.
Anyway, don’t know if this is clear what I am asking for, but could someone jump in and state is there a way to implement the current functionality for the equivalent level of validation that they now have.