How Should Manual and Automatic Machine Modes Work?
For PLC manual auto mode design, start with a written agreement: what each mode permits, who owns commands, and what happens to the active sequence when control changes. Define manual operation around specific permitted actions and automatic operation around an agreed sequence with explicit start, stop and recovery conditions. Design safety-related permissions and transitions with a qualified assessor; selecting manual must never be treated as permission to bypass protective measures.
What should manual and automatic modes permit?
Specify permissions for each machine function, rather than relying on a single description such as “manual gives the operator control”. If a retrofit changes these modes, see when a machine retrofit needs a safety assessment.
For manual mode, list the individual actions available: moving an axis, opening a valve, running a conveyor or testing an actuator. For each action, define its operating conditions, command behaviour and effect on the rest of the machine.
For automatic mode, define the sequence that owns those actions. State what starts a cycle, what permits the next step, and what happens when a required condition disappears.
Use a table like this as a starting point. The entries are illustrative design choices, subject to the machine assessment.
| Decision | Manual mode | Automatic mode |
|---|---|---|
| Who requests movement? | The selected operator station | The active sequence |
| What does Start mean? | No production-cycle command | Request a new cycle when ready |
| Are individual actuator commands available? | Only the explicitly permitted actions | Unavailable unless separately specified |
| What happens after a fault clears? | Await a fresh permitted command | Await the defined recovery and restart action |
| What happens on mode selection? | Apply the agreed transfer procedure | Check readiness; await a separate start request |
Treat setup, cleaning and maintenance as separate requirements. Decide whether each belongs within a defined mode or needs its own operating arrangement.
Who should own machine commands?
Define one accepted source for each operating command at a time. A local panel, operator screen and supervisory system should not independently compete to start the same function.
Keep mode and command ownership separate. “Automatic” describes how the process runs. “Local” or “remote” describes where requests originate. A machine might run automatically under local control while a supervisory system only displays its status.
Write down:
- Which station may request a mode change.
- Which station may issue Start, Stop, Reset and individual movement commands.
- How a station requests and receives ownership.
- What happens if the owning station disconnects.
- Which commands remain available independently of ordinary command ownership.
Define stop functions according to their purpose and assessment; do not let an ordinary ownership rule decide which protective actions are available.
At a transfer, require previously held operating commands to be released before accepting a fresh command. Specify whether pending requests are discarded or retained, and make any retained request visible.
Put these rules in the functional design specification, alongside the interfaces and operating conditions.
How should control transfer between modes?
Treat selection as a request, with acceptance conditions and feedback.
For every transfer direction, define the required machine condition, any stopping action, the treatment of outputs, and what makes the transfer complete. Decide whether the request is rejected, deferred or accepted when those conditions are absent.
For example, a request for manual mode during a cycle could initiate a defined stop and become active only after the required conditions are confirmed. Another process may need a different stopping arrangement. Agree that behaviour for the actual equipment, including material and energy already in the process.
Display the requested mode separately from the active mode while a transfer is pending. Explain the reason for a rejected request in operational terms, such as “Transfer unavailable while discharge is active”.
Keep entry into automatic mode separate from starting production. Require an explicit start action once the agreed readiness conditions are satisfied. Review exceptions, including continuous processes, with the people responsible for operation and safety.
What should happen to the sequence state?
Specify sequence behaviour independently of actuator behaviour. Stopping movement does not answer whether a partially completed cycle remains valid.
For each sequence step, decide whether a transfer:
- Retains the step for a controlled resume.
- Cancels the cycle and requires recovery.
- Completes a defined operation before stopping.
- Moves into a dedicated recovery state.
Record which timers, counts, material records and completion flags are retained or cleared. Avoid a blanket reset without examining what each value represents.
Manual actions also need defined effects. If an operator removes a component or changes an actuator position, the previous sequence assumptions may no longer be valid. Specify which actions invalidate a paused cycle and what checks establish readiness again.
Describe recovery using observable conditions. “Return to ready” should identify the required positions, material condition and unresolved faults. An operator should not need to guess whether the machine remembers an unfinished operation.
Which maintenance actions need separate rules?
Create a maintenance action list with the maintenance team. For each action, record its purpose, permitted mode, command owner, operating conditions, feedback and completion criteria.
Distinguish an ordinary manual command from a diagnostic override. For every proposed override, identify the condition being overridden, who may authorise it, how it is indicated and how normal operation is restored.
Define how the machine prevents an unfinished maintenance arrangement from being carried into production. Include temporary settings, disconnected equipment and altered sequence assumptions in the return-to-service procedure.
Manual mode is not an energy-isolation procedure. Establish the isolation requirements and any arrangements for work requiring power through the machine-specific assessment with a qualified assessor. Do not describe an ordinary screen permission or password as a safety measure.
For a retrofit, include these decisions in the shutdown and commissioning plan so maintenance and operations can review them before the work begins.
What should operators see?
Show the active mode, current command owner and machine state together. Use distinct labels for “Manual”, “Local panel”, “Cycle paused” and “Recovery required”; each answers a different question.
Include:
- The active mode and any pending mode request.
- The station that currently owns operating commands.
- Whether the sequence is ready, running, stopping, paused or awaiting recovery.
- Why an unavailable command cannot be accepted.
- Any active maintenance permissions or overrides.
Use text as well as colour. Place the essential status near the controls it explains.
Keep acknowledgements distinct from physical feedback. “Command accepted” should not be presented as “movement complete”. Define the feedback needed to show that an action has finished.
How can you test the design before handover?
Use a transition checklist that covers interruptions as well as normal operation.
Illustrative example: a transfer station pauses with a component between its loading and discharge positions. An operator requests manual mode to investigate.
The acceptance test should establish:
- What stops, what remains energised and when manual mode becomes active.
- Which station receives operating ownership.
- Which manual movements are permitted in that condition.
- Whether moving or removing the component invalidates the paused cycle.
- What recovery is required before automatic readiness.
- What fresh action starts production again.
Repeat the relevant checks with a held command, an active fault, lost communications and restored power. Record expected and observed behaviour.
Agree power-restoration behaviour explicitly. Do not leave it to incidental retained values or startup logic.
What common mistakes should the design avoid?
Using manual mode as an unrestricted output test. Define permitted actions and their conditions individually.
Letting mode selection start movement. Separate mode acceptance, readiness and the start request.
Resuming from remembered state without checking the machine. Define how physical changes affect sequence validity.
Allowing several stations to own the same command. Specify ownership and transfer rules.
Hiding blocked commands. Show the reason and the required next action.
Using one recovery rule everywhere. Review interrupted operations according to their actual process conditions.
Frequently asked questions
Should manual mode clear every fault?
Define fault acknowledgement, reset and mode selection separately. Specify what each reset changes and which conditions must be restored before operation can continue.
Can automatic mode include operator confirmation?
Yes, as a design choice. Identify the step that waits for confirmation, who may confirm it and which conditions must still be checked before proceeding.
Should returning to automatic resume the previous cycle?
Choose this per sequence and interruption condition. Define what makes resume valid, what requires recovery and which fresh command authorises continuation.
Is a mode selector enough to define the design?
No. Document the permissions, ownership, transitions, sequence treatment and feedback behind each selection. Review them with operations, maintenance and a qualified assessor for safety-related decisions, then verify the agreed behaviour before handover.