Interlock or Permissive? This Naming Mix-Up Can Break Restart Logic
Teams often use permissive and interlock differently. Trouble starts when one programmer treats a condition as start-only while another expects it to stop an already running process. Define behavior explicitly instead of relying on the tag name to communicate the requirement.
Project-definition method; terminology and safety responsibilities must be agreed locally.
What is happening?
A useful project convention distinguishes conditions required to start, conditions required to continue, and conditions requiring a latched trip or deliberate recovery. These are application definitions, not universal meanings imposed by every PLC instruction set. Safety functions require their own documented design and validation.
Check these five things
-
List each condition and describe its physical meaning, signal validity, and normal state.
-
Specify its effect before starting, during operation, and after it returns to normal.
-
Define whether recovery is automatic, requires acknowledgement, or requires a new start request.
-
Trace the condition through manual, automatic, and recovery modes so its effect is consistent with the requirements.
-
Test the behavior matrix in simulation, including stale data and conflicting feedback.
Worked example
A training application requires a destination-ready signal before starting a transfer. The requirements must also say what happens if that signal disappears mid-transfer. Calling the tag StartPermissive does not answer whether to stop immediately, finish a controlled step, or enter a recovery state.
Quick diagnostic reference
| Condition phase | Required decision |
|---|---|
| Before start | Allow or reject request |
| During operation | Continue, stop, or controlled transition |
| After recovery | Automatic resume or new deliberate request |
The mistake to avoid
Do not let a recovered permissive automatically restart machinery unless that behavior is explicitly designed and accepted.
How to verify the fix
Have controls and operations review the behavior matrix, then confirm the implemented response and operator message for each condition.
Field-work boundary: These are educational diagnostic guides. Use the exact equipment manuals and approved site procedures. Electrical testing and machinery changes belong to qualified, authorized personnel; control hazardous energy and validate affected functions before release.
Technical reference
Rockwell Automation: application programming references. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.