Section 6.4: PLC Troubleshooting & Ladder Logic

PLC Troubleshooting & Ladder Logic in Postal Operations

When a mail sorter or transport conveyor halts, maintenance technicians must quickly locate and repair the fault. This process involves viewing the running software in real-time, understanding Ladder Diagrams (LD), analyzing timer and counter operations, reading status registers, and physically verifying input/output (I/O) modules.

Ladder Logic Diagram Fundamentals

Ladder Logic is the primary programming language used to program PLCs. It was designed to mimic electrical schematic diagrams of hardwired relay control circuits. The diagram consists of two vertical rails and horizontal rungs:

• The Left Rail represents the hot or energized power rail.
• The Right Rail represents the neutral or return rail.
• The Rungs connect the rails and contain input instructions (contacts) on the left and output instructions (coils) on the right.

For an output to energize, there must be path of closed contacts from the left rail to the right, known as logical continuity.

Basic Ladder Logic Instructions

Technicians must interpret these standard symbols:

• Examine If Closed (XIC): Represented as -[ ]-. This represents a Normally Open (NO) contact. If the memory bit associated with this contact is 1 (ON), the instruction is true, allowing logical continuity.
• Examine If Open (XIO): Represented as -[\\]-. This represents a Normally Closed (NC) contact. If the associated memory bit is 0 (OFF), the instruction is true, allowing logical continuity.
• Output Energize (OTE): Represented as -( )-. This represents a standard output coil. If there is logical continuity across the rung, this coil is energized, writing a 1 to its memory bit and activating the physical output device.
• Output Latch (OTL) and Output Unlatch (OTU): Represented as -( L )- and -( U )-. These are retentive instructions. Once the OTL coil is energized, it remains ON even if logical continuity is lost. It can only be turned OFF by energizing a matching OTU instruction pointing to the same memory bit.

---

Timers and Counters in PLC Logic

Postal equipment relies on precise timing and counting to track mail pieces and monitor system states.

Timer Instructions

Timers measure elapsed time and use three primary variables: the Preset Value (PRE), which is the target time; the Accumulated Value (ACC), which is the current elapsed time; and status bits:

• Timer On-Delay (TON): Delays turning an output on. When the rung becomes true, the timer starts counting. The Timer Timing (TT) bit is ON while counting. Once ACC equals PRE, the Done (DN) bit turns ON. If the rung becomes false before reaching the preset, the timer resets and ACC returns to 0.
• Timer Off-Delay (TOF): Delays turning an output off. When the rung turns from true to false, the timer begins counting, and the DN bit remains ON. Once ACC equals PRE, the DN bit turns OFF.
• Retentive Timer On (RTO): Operates like a TON timer but retains its accumulated value if the rung loses logical continuity. It must be explicitly reset using a separate Reset (RES) instruction.

Counter Instructions

Counters count false-to-true transitions of their controlling rungs:

• Count Up (CTU): Increments its accumulated value by 1 each time the rung goes from false to true. The DN bit turns ON when the ACC value is greater than or equal to the PRE value.
• Count Down (CTD): Decrements the accumulated value by 1 on each false-to-true transition.
• Reset (RES): An instruction used to clear the accumulated value of a counter or retentive timer.

---

Status Registers and Memory Areas

The PLC memory is organized into specific tables to coordinate operations:

• Input Image Table (I): Stores states of physical inputs.
• Output Image Table (O): Stores states of physical outputs.
• Status Files (S): Stores system data such as controller faults, scan times, watchdog timer status, and battery state.
• Bit (Binary) Files (B): Internal storage bits used for intermediate logic states (often called internal coils) that do not directly drive physical outputs.
• Integer (N) and Float (F) Files: Store numeric data such as sensor readings and counts.

---

Troubleshooting PLC I/O and Control Systems

When a conveyor or sorting gate fails to operate, a structured troubleshooting process is key to resolving the issue.

Real-Time Software Diagnostics

Technicians connect a programming laptop to the PLC and go "online" to view the logic in real time. The software highlights active instructions in green to show logical continuity.

1. Locate the Output: Find the coil representing the failed physical device (e.g., O:1/3 for a solenoid).
2. Trace Backwards: Look at the contacts on the left of the coil. Identify which contact is open (not highlighted) and blocking the logical continuity.
3. Verify the Address: Find the tag or address of that open contact (e.g., I:2/1 representing a photoeye).

Physical I/O Module Verification

Once the logical culprit is identified in software, technicians verify the physical hardware:

• Check Status LEDs: Every I/O module has indicator LEDs. If the PLC code shows a photoeye input is OFF, check the input module's corresponding LED. If the physical LED is ON but the software shows OFF, there is a backplane communication error or a module failure.
• Measure Electrical Voltage: Use a Digital Multimeter (DMM) to measure voltage directly at the module terminal block. For a 24VDC input, measure between the input terminal and the common terminal.
  • If a sensor is blocked and the multimeter reads 0V, the fault is in the field wiring or the sensor itself.
  • If the multimeter reads 24V but the input LED is OFF, the input module channel is blown and the module must be replaced.

The Danger of Forces

Technicians can use the programming software to apply a force to an I/O bit, overriding physical conditions (e.g., forcing an input to be ON even if the sensor is blocked).

[!WARNING] Forcing outputs bypasses safety interlocks and programming logic. Forcing a motor contactor output can cause machinery to start unexpectedly, risking serious injury or equipment damage. Forces must be used with extreme caution and removed immediately after testing.

---

Example Troubleshooting Matrix