PLC Online Diagnostics — Monitoring, Forcing, and Fault Tables

PLC Online Diagnostics — Monitoring, Forcing, and Fault Tables

Why Online Diagnostics Matter

When a mechatronic or robotic system stops or behaves unexpectedly, your fastest path to the root cause is often the PLC itself. Modern PLC programming software lets you connect to a running controller, watch every rung of ladder logic in real time, and read a fault table that logs exactly what went wrong and when. Used correctly, these tools let you diagnose many faults without touching a multimeter or opening an enclosure — reducing both downtime and the risk of electrical injury.

Going Online in Monitor Mode

Before connecting to a live PLC, review the machine guarding and energy-control situation. Never force outputs or modify the program without first confirming that personnel are clear of moving parts and that the machine is in a safe state. Refer to OSHA 29 CFR 1910.147 (lockout/tagout) when any physical intervention on the machine is required; for energized electrical work, follow NFPA 70E boundaries and use rated PPE.

To go online:

1. Open the project file in your PLC programming software (e.g., Studio 5000 for Allen-Bradley, TIA Portal for Siemens).

2. Select Go Online or Connect. Choose Monitor Mode — this lets you observe, but prevents accidental program changes.

3. Confirm the software shows a green status indicator and that the processor is in Run or Remote Run mode.

4. Navigate the program tree to the routine you want to inspect.

In monitor mode, energized (true) rungs are highlighted — typically in green or blue depending on the software. Open contacts appear as gaps; closed contacts appear filled. A coil that is energized shows the output bit as logic 1.

Reading Rung States

Each rung in a ladder-logic routine implements a Boolean expression. Reading left to right:

• Normally Open (XIC) contact: passes power when the referenced bit is 1 (ON).
• Normally Closed (XNC) contact: passes power when the referenced bit is 0 (OFF).
• Output Coil (OTE): energizes when all conditions to its left are true.
• Timer and Counter instructions: show current accumulated values alongside preset values in real time online.

When a rung does not energize as expected, step through each contact from left to right. The first contact whose state breaks the logic chain is your suspect. Note the tag name or address (e.g., `Local:1:I.Data.3` in Allen-Bradley or `I0.3` in Siemens) for your root-cause statement.

Forcing Bits

A force overrides the physical state of an input or output bit in software. Forces are diagnostic tools — they are not a permanent fix.

• Input force ON: tells the PLC to treat a physical input as if it were energized, even if the field device is not sending a signal. This lets you test downstream rung logic without the physical sensor.
• Input force OFF: holds the bit at 0 regardless of the physical signal.
• Output force: overrides the PLC's calculated output — use with extreme caution because it can energize actuators unexpectedly.

Safety rule: before applying any output force, confirm personnel are clear and the machine is in a safe state. Document every force you apply, and remove all forces before returning equipment to production. Many systems require supervisor authorization to force outputs.

Forces are typically enabled through a Force Enable toggle that is separate from the individual bit force — both must be active for a force to take effect. Check your specific software's procedure.

The Fault Table

The fault table (sometimes called the Controller Fault Log or Diagnostics Buffer) is a timestamped record of every fault the PLC has detected. Common entries include:

| Fault Type | Example Cause |

|---|---|

| I/O module fault | Module removed, communication lost, or field wiring short |

| Program fault | Divide-by-zero, array index out of range |

| Task watchdog | Scan time overrun |

| Configuration mismatch | Module type does not match project configuration |

For each fault entry, the table typically shows: fault code, fault description, time stamp, severity (major or minor), and the program task or module where the fault occurred. A major fault halts the controller; a minor fault logs the event but allows continued operation.

To clear a major fault and restart the controller, you must address the root cause first — simply clearing the fault without fixing it will cause an immediate re-fault.

Hardware Fault vs. Software/Program Logic Fault

Distinguishing between fault types guides your corrective action:

• Hardware fault: physical device failure — broken wire, failed sensor, blown fuse, damaged output card. Symptoms include an I/O module fault in the fault table and an input or output bit that does not change state even when forced at the field device.
• Software/program logic fault: the ladder logic itself contains an error — wrong address, incorrect preset, missing interlock. The physical hardware works, but the program does not process it correctly. Symptoms include rungs that never energize or energize at the wrong time despite correct physical signals.
• Configuration fault: module type, slot assignment, or communication settings do not match the project file.

Your root-cause statement must specify which type applies, because hardware faults require physical repair while program logic faults require a program change — and program changes must follow your facility's management-of-change procedure.

IEC 61131-3 and This Lesson

Ladder diagram (LD) is one of five IEC 61131-3 programming languages. The contacts and coils you monitor online are the visual representation of Boolean logic that the processor executes every scan cycle. Scan time is typically a few milliseconds — fast enough to catch transient faults that would be invisible on a panel meter.

Key Takeaway

Online monitoring lets you see the machine's logic state in real time. Systematic left-to-right rung analysis, careful use of forces, and accurate fault-table interpretation are the three core skills of PLC-based troubleshooting. Always document your findings and restore forces before leaving the workstation.