Practical guides on ladder logic, structured text, timers, PID control, career paths, and everything else that matters for learning PLC programming.
Latest
A vendor-neutral worked PLC sequence for a suction fan, rotary airlock, material feed, and purge cycle: I/O, permissives, states, timers, trips, restart, and test cases.
Wire a contactor correctly: L1/L2/L3, T1/T2/T3, A1/A2, seal-in and PLC feedback explained with diagrams and an interactive cutaway.
Follow power through a VFD from AC rectifier to DC bus and PWM inverter, then see how a PLC commands speed in an interactive motor lab.
Understand PLCs, I/O, sensors, relays, drives, valves, safety and HMIs as one closed control loop—with interactive component labs.
Understand a DOL motor starter wiring diagram: breaker, contactor, overload, start/stop seal-in, PLC command and feedback—with a live lab.
Compare single-acting, double-acting, rodless, guided and cushioned pneumatic cylinders by motion, force, air failure and PLC feedback.
Trace pressure through the diaphragm, sensing bridge and electronics into a 4–20 mA PLC input, with scaling, wiring and fault examples.
See how direct and pilot solenoid valves move a plunger or spool, how NO/NC states work, and how a PLC output controls the coil.
See how a thermal overload relay protects a motor, how 95-96 and 97-98 work, what trip class means, and test it in an interactive PLC lab.
Learn a repeatable electrical troubleshooting method: establish the safe energy state, read the schematic, half-split the circuit, interpret voltage patterns, diagnose common motor-control faults, and verify the repair.
We analyzed 10,272 graded ladder logic attempts on our browser PLC simulator. 58% of failures were an output that never turned on, 83% failed within two seconds of clicking Run, and the seal-in circuit was the single hardest concept. Full data study.
A practical, from-zero guide to programming a Universal Robots cobot: the teach pendant and PolyScope, frames and the TCP, waypoints, your first pick-and-place, digital I/O and grippers, safety and protective stops, and how to practise without owning a robot.
The difference between movej, movel and movep is the first thing every Universal Robots programmer has to get right. This guide explains joint vs linear vs process moves, when to use each, blend radius, speed and acceleration, and the classic singularity and overshoot pitfalls — with URScript examples.
URScript is the text-based programming language that runs Universal Robots arms. This guide explains what URScript is, how it relates to PolyScope, the core commands (movej, movel, set_digital_out), variables, functions, and how to start learning it without owning a robot.
Modbus TCP vs Modbus RTU compared: both use the same register model and function codes, but RTU runs on serial RS-485 and TCP runs on Ethernet. This post explains the differences, the MBAP header, how to choose, and how to troubleshoot each variant.
Modbus and CAN bus target different environments. Modbus RTU/TCP is the open industrial register protocol for PLCs and process instruments. CAN bus with CANopen profiles connects embedded motion and drive systems. This post explains the architecture, frame format, and when each protocol fits.
Modbus and DNP3 are both fieldbus protocols used to read RTUs and outstations, but DNP3 was purpose-built for utility SCADA — substations, water treatment, and pipelines — with built-in event reporting, data integrity, and time stamping that Modbus lacks. This post explains the differences and when each protocol is the correct choice.
Diagnose DOL motor starter faults across three zones — contactor coil circuit, overload relay, and control circuit. Multimeter sequence, overload trip checklist, and the half-split from PLC output to contactor A1. Links to wiring lab and related posts.
A systematic 7-step PLC fault-finding method covering multimeter discipline, the half-split method, and how to navigate every fault family — from wiring opens to scan-order bugs. Links to live fault scenarios and wiring fault labs.
PROFINET and EtherCAT both run on Ethernet hardware, but they solve different problems. PROFINET integrates Siemens PLCs with drives and I/O in a standard plant network. EtherCAT delivers microsecond cycle times for high-axis-count servo and CNC applications. This post explains how each works and when to choose one over the other.
SCADA and BMS both supervise equipment and collect data — but they target different environments, use different protocols, and serve different operators. This post explains what each system does, where they overlap, and when a building needs both.
SCADA monitors and controls real-time plant operations. MES manages production orders, schedules, quality, and traceability. They operate at different time horizons and different abstraction levels — but they must talk to each other.
Incremental encoders output a pulse train — you count pulses to track relative position, but lose it on power loss. Absolute encoders output a unique digital word for every shaft position — position is retained across power cycles. Learn when to use each, how to wire them, and how PLCs read both types.
Inductive sensors detect metal only. Capacitive sensors detect anything — metal, plastic, liquid, or powder. Learn how each works, how to wire NPN vs PNP output, and how to pick the right sensor for your application.
Every published technical guide remains crawlable and reachable without relying on the interactive load-more control.
Technical reference and worked-example guide
Direct answer
PLC programming resource library becomes useful when it connects the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career with pillar guides to examples, tools, scenarios, vendor references and next-step practice, then proves one article applied to a runnable or worked case with a written expected result under normal, boundary, fault and recovery conditions. The objective is a repeatable engineering or learning result, not merely activity inside a page or tool.
This guide is written for learners, technicians and instructors choosing a reliable next article, runnable example, calculator or career guide from the public library. The intended result is specific: the reader can select a topic by current task and leave with one concept to understand, one activity to run and one piece of evidence to retain.
System map / 02
Treat these as connected checkpoints. Each checkpoint has an expected state, an observable state and a boundary to the next part of the system. That structure prevents a software indication from being mistaken for physical proof.
the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career. For PLC learning-resource navigation, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.
pillar guides to examples, tools, scenarios, vendor references and next-step practice. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected.
one article applied to a runnable or worked case with a written expected result. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability.
prerequisites, vendor version, physical safety, unsupported features and outdated assumptions. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.
a disagreement between an article example, observed behavior and target documentation. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result.
the useful evidence retained and the next article or physical validation selected. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment.
Procedure / 03
Run the steps in order the first time. Later, the same structure becomes a diagnostic loop: define the expected condition, observe the boundary, interpret the difference and choose one proving action.
Convert the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career into initial conditions, one stimulus and observable pass criteria.
Evidence: Another person can repeat the case without guessing the intended result.
Avoid: Using page completion or an animation as the acceptance criterion.
Document pillar guides to examples, tools, scenarios, vendor references and next-step practice and name who owns each state or decision.
Evidence: Every request and result has a source, destination and useful inspection point.
Avoid: Using the same value as command, status and independent feedback.
Apply one article applied to a runnable or worked case with a written expected result from a clean start and record the expected evidence.
Evidence: Repeated runs produce the same bounded result.
Avoid: Changing several parameters before a baseline exists.
Test prerequisites, vendor version, physical safety, unsupported features and outdated assumptions without changing the acceptance contract.
Evidence: Limits, timing and restart behavior reach defined states.
Avoid: Testing only one ideal sequence.
Introduce or analyse a disagreement between an article example, observed behavior and target documentation and locate the first disagreement.
Evidence: The proving action distinguishes the leading hypotheses.
Avoid: Resetting, forcing or replacing before evidence is retained.
Complete the useful evidence retained and the next article or physical validation selected and repeat the affected regression cases.
Evidence: Reference use is complete when inputs, assumptions, units or initial conditions are recorded and the result is independently checked at a useful boundary.
Avoid: Treating an acknowledged message or one successful rerun as handover.
Diagnostic matrix / 04
The table is a reasoning aid, not a parts-replacement chart. Preserve the initial symptom, inspect the named boundary and use the interpretation to choose the next controlled test. Site safety procedures and equipment manuals remain authoritative.
| Observed symptom | Inspect | Interpretation | Next proving action |
|---|---|---|---|
| The expected result is unclear | Requirement, initial state, actor, stimulus, units and pass condition | The technician, programmer and reviewer may be solving different versions of the task. | Rewrite one observable acceptance case before continuing. |
| Internal state changes but the outcome does not | Request, final owner, output or service boundary and independent feedback | A software or interface indication proves intent at one layer, not the complete outcome. | Trace the first boundary after the changing state. |
| Normal case passes but an edge case fails | Limits, timing, simultaneous events, reset and restart assumptions | The implementation contains a hidden assumption exposed by the changed condition. | Add the failed boundary as a permanent regression case. |
| The failure disappears after reset | Original symptom, histories, diagnostics, timestamps and active cause | Reset changed evidence or state without proving the initiating cause. | Reproduce under a controlled condition and preserve pre/post-event data. |
| Simulator and target disagree | Model boundary, software version, task timing, I/O behavior, data types and configuration | A learning model and the intended target do not share one of the recorded assumptions. | Reduce the case and verify against current target documentation. |
| The result cannot be explained | Prediction, observation, proving action, alternative hypotheses and limitations | Activity occurred but the evidence is not yet transferable or reviewable. | Have the learner defend the signal path and repeat a changed case. |
Product evidence / 05
The page connects definitions and worked examples to runnable tools, explicit assumptions and repeatable checks so a formula or pattern can be challenged.
The library is educational and vendor-neutral where stated; current official documentation, employer procedures and supervised physical practice remain authoritative.
Commissioning notebook / 06
Use these as written briefs rather than click-through instructions. For every case, state the expected condition before acting, retain the first useful observation and explain why the final result proves the requirement. A different program or component choice can still be correct when it produces the same bounded behavior and evidence.
Case 01
predict → observe → prove
Engineering context. the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career. For PLC learning-resource navigation, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Write the acceptance case” stage of the workflow: convert the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career into initial conditions, one stimulus and observable pass criteria. The acceptance record should show this result: another person can repeat the case without guessing the intended result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The expected result is unclear” as one bounded deviation. Inspect requirement, initial state, actor, stimulus, units and pass condition The working interpretation is that the technician, programmer and reviewer may be solving different versions of the task. The next proving action is to rewrite one observable acceptance case before continuing. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using page completion or an animation as the acceptance criterion. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What should I learn first about PLC learning-resource navigation? A defensible short answer is: Start with the operating contract and evidence path: the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career, followed by pillar guides to examples, tools, scenarios, vendor references and next-step practice. Add advanced features only after the baseline is predictable.
Case 02
predict → observe → prove
Engineering context. pillar guides to examples, tools, scenarios, vendor references and next-step practice. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Build the map” stage of the workflow: document pillar guides to examples, tools, scenarios, vendor references and next-step practice and name who owns each state or decision. The acceptance record should show this result: every request and result has a source, destination and useful inspection point. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Internal state changes but the outcome does not” as one bounded deviation. Inspect request, final owner, output or service boundary and independent feedback The working interpretation is that a software or interface indication proves intent at one layer, not the complete outcome. The next proving action is to trace the first boundary after the changing state. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using the same value as command, status and independent feedback. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: How do I practise PLC learning-resource navigation effectively? A defensible short answer is: Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
Case 03
predict → observe → prove
Engineering context. one article applied to a runnable or worked case with a written expected result. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Run the baseline” stage of the workflow: apply one article applied to a runnable or worked case with a written expected result from a clean start and record the expected evidence. The acceptance record should show this result: repeated runs produce the same bounded result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Normal case passes but an edge case fails” as one bounded deviation. Inspect limits, timing, simultaneous events, reset and restart assumptions The working interpretation is that the implementation contains a hidden assumption exposed by the changed condition. The next proving action is to add the failed boundary as a permanent regression case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is changing several parameters before a baseline exists. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What counts as proof of competence? A defensible short answer is: A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Case 04
predict → observe → prove
Engineering context. prerequisites, vendor version, physical safety, unsupported features and outdated assumptions. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Challenge assumptions” stage of the workflow: test prerequisites, vendor version, physical safety, unsupported features and outdated assumptions without changing the acceptance contract. The acceptance record should show this result: limits, timing and restart behavior reach defined states. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The failure disappears after reset” as one bounded deviation. Inspect original symptom, histories, diagnostics, timestamps and active cause The working interpretation is that reset changed evidence or state without proving the initiating cause. The next proving action is to reproduce under a controlled condition and preserve pre/post-event data. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is testing only one ideal sequence. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Why test faults and restart behavior? A defensible short answer is: Because a disagreement between an article example, observed behavior and target documentation or prerequisites, vendor version, physical safety, unsupported features and outdated assumptions can expose assumptions that never appear during ideal startup and steady operation.
Case 05
predict → observe → prove
Engineering context. a disagreement between an article example, observed behavior and target documentation. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Isolate one failure” stage of the workflow: introduce or analyse a disagreement between an article example, observed behavior and target documentation and locate the first disagreement. The acceptance record should show this result: the proving action distinguishes the leading hypotheses. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Simulator and target disagree” as one bounded deviation. Inspect model boundary, software version, task timing, I/O behavior, data types and configuration The working interpretation is that a learning model and the intended target do not share one of the recorded assumptions. The next proving action is to reduce the case and verify against current target documentation. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is resetting, forcing or replacing before evidence is retained. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Can browser practice replace official software or hardware? A defensible short answer is: No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.
Case 06
predict → observe → prove
Engineering context. the useful evidence retained and the next article or physical validation selected. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Close the evidence loop” stage of the workflow: complete the useful evidence retained and the next article or physical validation selected and repeat the affected regression cases. The acceptance record should show this result: reference use is complete when inputs, assumptions, units or initial conditions are recorded and the result is independently checked at a useful boundary. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The result cannot be explained” as one bounded deviation. Inspect prediction, observation, proving action, alternative hypotheses and limitations The working interpretation is that activity occurred but the evidence is not yet transferable or reviewable. The next proving action is to have the learner defend the signal path and repeat a changed case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is treating an acknowledged message or one successful rerun as handover. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: How should progress be documented? A defensible short answer is: Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.
Answer surface / 07
These concise answers define the operating, training and product boundaries most often missed in broad summaries. The full workflow and diagnostic table above provide the evidence behind them.
Start with the operating contract and evidence path: the immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career, followed by pillar guides to examples, tools, scenarios, vendor references and next-step practice. Add advanced features only after the baseline is predictable.
Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Because a disagreement between an article example, observed behavior and target documentation or prerequisites, vendor version, physical safety, unsupported features and outdated assumptions can expose assumptions that never appear during ideal startup and steady operation.
No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.
Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.
Check assumptions, version, units and initial state first. Reduce the case, compare one boundary at a time and prefer current primary documentation for target-specific behavior.
Reference use is complete when inputs, assumptions, units or initial conditions are recorded and the result is independently checked at a useful boundary.
Continue the signal path / 08