Plain-English Summary
PLC I/O is the connection between the control program and the real machine. Inputs tell the PLC what is happening. Outputs tell devices what to do.
Why It Matters
PLC I/O problems can stop machines, create false faults, miss unsafe conditions, fire the wrong output, fail to move an actuator, reject good product, miss bad product, or cause sequence confusion.
Field Rule of Thumb
The PLC is not the whole machine. Compare what the real-world device is doing, what the PLC input/output shows, and what the machine should be doing at that step.
Walt - Simple Man Takeaway
Do not argue with the screen until you walk to the machine. The PLC may be showing exactly what the field device is telling it — even if the field device is wrong.
Core Formula / Concept
Inputs are signals coming into the PLC: sensors, pushbuttons, limit switches, pressure switches, vacuum switches, feedback, and safety status. Outputs are commands from the PLC to field devices: solenoid valves, motor starters, relays, lights, alarms, reject devices, and VFD run commands. The PLC program may be correct while the sensor is misaligned, or the output may be on while the field device is mechanically stuck.
Worked Example
A cylinder will not extend. The HMI shows the extend output is on. First checks find the PLC output tag is on, the module LED is on, voltage is present at the valve connector, the solenoid clicks, and the valve shifts — but the cylinder does not move. Air pressure is low and the rod guide is binding. The PLC output was not the root problem.
Common Mistakes
- Assuming the HMI display equals real-world status.
- Forcing I/O casually.
- Replacing modules before checking field wiring, commons, fuses, connectors, and devices.
- Ignoring permissives, modes, recipes, resets, and sequence steps.
- Troubleshooting controls while ignoring mechanics, pneumatics, hydraulics, or drives.
- Not documenting program, wiring, parameter, or device changes.
First Checks / Troubleshooting Flow
- Make the area safe and identify motion hazards.
- Determine whether the issue is input, output, sequence, communication, or field-device related.
- Check real-world device condition.
- Check device LED/status where available.
- Check PLC input/output module LED.
- Check PLC tag or diagnostic screen.
- Check wiring, connector, common, and power supply.
- Check fuses, terminals, and module status.
- Check whether signal type matches the module.
- Check permissives, interlocks, mode, recipe, reset, and sequence step.
- Check related mechanical, pneumatic, hydraulic, or VFD conditions.
- Avoid forcing unless authorized, documented, and safe.
Walt says STOP! - Safety First
Make these checks prior to proceeding.
Stop when forcing I/O is suggested; the output can move a cylinder, motor, robot, conveyor, clamp, gate, press, or reject device; safety logic/interlocks/guards/E-stops are involved; live panel access is required; program changes are considered; or the real-world consequence of a signal is not understood.
Source Notes / References
This page is original Dingfelder practical field guidance. Verify controlled requirements against drawings, OEM documentation, current standards, site procedures, customer requirements, and qualified authority where applicable.