Manual and Auto Modes Fighting Each Other? Give the Output One Owner
A machine can behave unpredictably when manual and automatic routines both write the same actuator command. Each routine may look reasonable in isolation while their interaction depends on execution order. Separate requests from the final command and define how modes transfer control.
General control-architecture method; implementation requires project-specific review.
What is happening?
Mode selection is an arbitration problem. The application needs rules for valid mode, request priority, transition behavior, feedback, and ordinary interlocks. Manual mode should not be assumed to bypass protective functions. A clear final command path makes the rules reviewable and easier to diagnose.
Check these five things
-
List all writers to the actuator command, including HMI tags, jog routines, sequences, and startup logic.
-
Define mutually valid operating modes and the response to invalid or simultaneous mode requests.
-
Keep manual and automatic requests separate from the final command. Apply the reviewed mode and interlock rules in one visible ownership path.
-
Define what happens to pending requests during a mode change. A stale manual command should not become active unexpectedly later.
-
Test every transition, including request held during transfer, lost feedback, and communication recovery, in simulation.
Worked example
In a training model, AutoRequest is true while ManualJog is false. Two direct assignments to MotorCommand make the result depend on order. A separate selected-request calculation followed by one final command assignment exposes the intended priority and prevents an unrelated routine from silently overwriting it.
Quick diagnostic reference
| Design question | Required answer |
|---|---|
| Who requests motion? | Separate named request sources |
| Who owns the output? | One documented arbitration path |
| What happens on transfer? | Defined reset, hold, or recovery behavior |
The mistake to avoid
Do not solve a mode conflict by disabling safety logic in manual operation. Protective functions remain a separate design responsibility.
How to verify the fix
Review the transition matrix with operations and controls personnel. Confirm the observed command path matches it for all accepted and rejected requests.
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: controller and application programming references. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.