If an estop occurs, the only information for why the estop is a message in the system log that either says it was caused by a switch triggering or a user triggering.
Since the I/O pins are now programmable, it would be nice to specify which switch triggered the estop. It might also be nice to present a message to the user that specifies which switch triggered an estop.
If an estop occurs, the only information for why the estop is a message in the system log that either says it was caused by a switch triggering or a user triggering.
Since the I/O pins are now programmable, it would be nice to specify which switch triggered the estop. It might also be nice to present a message to the user that specifies which switch triggered an estop.