2/13/2026 at 7:15:06 PM
Interlocks are especially interesting when they have to be integrated with software.For safety, you want the interlock to be performed in hardware (what if SW crashed?) but at the same time, the software should be informed that the interlock is active. e.g., the operator opens the door while the machine is moving. A hardware switch should stop the motion, and the software controller must be told that the door is open and take appropriate action.
The fun part comes in when the interlock is implemented as a hardware switch that turns off power to everything (this is the easiest way to do it!) except the main CPU and then at the last minute, when software is close to completion, inform the software team that "oh, by the way, you have to respond to this interlock triggering at any time during operation and recover gracefully." So now, the first indication that the operator opened the door is that the subsystem you were talking to over a communication link is no longer responding. Is it a comms error? Did the subsystem crash or reset? Or did the user open the door and the interlock powered off the subsystem? Who knows? Just Do the Right Thing.
by HeyLaughingBoy