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 practice 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
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.
Written for learners, technicians and instructors choosing a reliable next article, runnable example, calculator or career guide from the public library.
The immediate task: learn a concept, write logic, diagnose a fault, compare software or plan a career.
Pillar guides to examples, tools, scenarios, vendor references and next-step practice.
One article applied to a runnable or worked case with a written expected result.
Prerequisites, vendor version, physical safety, unsupported features and outdated assumptions.
A disagreement between an article example, observed behavior and target documentation.
The useful evidence retained and the next article or physical validation selected.