Ladder logic cheat sheet
Contacts and branches
Read a contact as a test of a Boolean tag. Its symbol tells you which tag state lets the rung continue. The tag value and the physical wiring are different things: a normally closed field switch can supply a true input while it is healthy.
| Ladder element | Logical test or action | Common mistake |
|---|---|---|
| Normally open contact | Pass when its tag is true | Assuming the field device must be physically open |
| Normally closed contact | Pass when its tag is false | Treating a true tag as permission to pass |
| Series contacts | All conditions must pass | Expecting either condition to be enough |
| Parallel branches | At least one path must pass | Letting one branch bypass a shared condition |
| Ordinary coil | Assign the rung result to its tag | Expecting the coil to remember a previous true value |
| Latch and reset | Keep or clear stored state | Providing a set condition without a reset path |
Branch example
A fictional pump has two request signals and one level permission. Its run condition is (RequestA OR RequestB) AND LevelPermit. With RequestA = true, RequestB = false and LevelPermit = false, the pump must stay off. This test catches a branch that bypasses the level permission.
Timers and counters
A timer measures a delay; a counter tracks events. A TON-style on-delay needs its input to remain true for the preset interval. A CTU-style counter reacts to a rising edge rather than every scan with a true input. Read the controller’s own instruction documentation for its data types and reset behavior.
The course uses generic instruction names. Rockwell’s timer and counter reference shows that available instructions also depend on the programming language.
Practice the Boolean exercises and the on-delay timer before trying the course projects.