Runnable simulator field guide
Motor start-stop PLC scenario: test checklist
Direct answer
The learner can predict every state, run the normal cycle, detect missing proof and restore operation without bypassing the modeled fault.
Written for beginners and maintenance learners practicing three-wire behavior, PLC command ownership, feedback timing, overload response and recovery.

Scenario setup
Initial state, start and stop inputs, permissive, run command, starter state, motor response, proof timer, trip, reset and restart.
I/O and state map
Operator input through PLC logic and output to modeled starter, motor motion, auxiliary or speed feedback and alarm state.
Normal run
Start, confirmed run, stop, second start and normal reset executed from clean conditions.
Boundary run
Held start, simultaneous commands, missing feedback, overload trip, output stuck, stop during start and restart after reset.
Injected fault
An input, rung-state, output, starter, motor, proof, timer, alarm or recovery mismatch.
Target check
The behavior recreated with site drawings, target instructions, actual starter or drive and supervised acceptance tests.
What should a PLC motor start-stop exercise include?
It should include stop priority, start request, maintained state, permissives, output command, independent run proof, timeout, trip, reset and restart cases.
Why use motor feedback instead of the PLC output bit?
The output bit proves only controller intent. Auxiliary, speed or process feedback provides independent evidence that the downstream equipment responded.