PLC Fault Diagnosis Step-by-Step for Roll Forming Machines (Fast Troubleshooting Workflow)

Most “PLC faults” in roll forming plants are not PLC failures.

PLC Fault Diagnosis Step-by-Step

A Practical Troubleshooting Workflow for Roll Forming & Coil Processing Lines

Most “PLC faults” in roll forming plants are not PLC failures.

They’re usually one of these categories:

• Safety chain open (E-stop, guard, safety relay)

• Field device issue (sensor, encoder, solenoid, limit switch)

• Power integrity problem (24VDC drop, loose terminal, grounding)

• Drive fault (VFD/servo trip, enable missing, comms down)

• Logic interlock (machine state not satisfied, missing permissive)

• Noise/EMC issue (false inputs, encoder pulse loss, random resets)

This guide is a repeatable, step-by-step method to diagnose faults quickly, prove the root cause, and avoid recurring downtime.

1) Rule #1: Make It Safe Before You Touch Anything

Before diagnosis:

1. Lockout/Tagout main power when opening cabinets or moving wiring

2. Confirm stored energy is safe:

   • VFD DC bus discharged

   • Hydraulic pressure relieved

   • Pneumatic air isolated if relevant

3. Use the cabinet’s voltage test points (if present) rather than probing random terminals

Safety isn’t a formality on roll forming lines—flying shears, coil handling, and hydraulics escalate risk fast.

2) Step 1 — Define the Fault Precisely (Don’t Diagnose “A Problem”)

Write down:

• Exact alarm text (HMI, PLC, drive keypad)

• When it occurs (startup, ramp-up, shear event, every 30 min, only at high speed)

• What changed recently (new coil grade, new tooling, maintenance, wiring work, parameter change)

• Whether it’s repeatable or random

This prevents chasing symptoms.

3) Step 2 — Identify the Fault Domain in 60 Seconds

Use this quick sorting:

A) Safety domain

• Machine won’t start

• “Safety Not OK”

• Safety relay LEDs show fault

• Contactors won’t pull in

B) Control power domain

• PLC resets, HMI flickers

• Random I/O drops

• Multiple unrelated alarms

• 24V undervoltage events

C) I/O domain

• One sensor “never turns on”

• Solenoid doesn’t actuate

• A limit switch always “stuck”

• Inputs chatter

D) Drive domain

• VFD trip code

• Servo alarm

• “Drive not ready”

• Motor won’t enable

E) Logic domain

• No hardware fault visible

• One permissive missing

• State machine stuck

• Sequence halts at same step

This classification decides your next test.

4) Step 3 — Check the Control Power First (24VDC Integrity)

Do this before deep PLC work—control power issues create fake “logic problems.”

Control power checklist

1. Measure 24VDC at the PLC power terminals (not only at PSU output)

2. Measure 24VDC at the farthest field I/O terminals (worst-case drop)

3. Look for voltage sag when:

   • hydraulic pump starts

   • shear fires

   • stacker engages

4. Inspect for common causes:

   • loose 0V common terminals

   • undersized PSU

   • too many solenoids fed from one branch

   • no fusing/branch distribution

   • poor grounding causing noise on 0V reference

Rule: If 24V is unstable, fix that first—everything else becomes unreliable.

5) Step 4 — Confirm the Safety Chain (Because It Blocks Everything)

Even if the PLC is fine, safety not OK will prevent outputs.

Word-based safety flow (typical)

24VDC → E-STOP loop (dual channel) → Safety relay → Safety outputs → Main contactor / drive enable
Safety relay AUX → PLC input “Safety_OK”

Safety diagnosis steps

1. Check safety relay status LEDs / fault code (if present)

2. Confirm Safety_OK input changes in PLC monitoring

3. Verify each device in chain:

   • E-stop buttons (all stations)

   • guard switches

   • light curtain OSSD if fitted

   • reset button logic (no auto restart)

4. If you must isolate: do it by device-by-device confirmation, not bypassing

Common reality: 70% of “machine won’t start” faults are safety chain open + poor indication.

6) Step 5 — Use PLC Online Monitoring (Inputs First, Then Outputs)

Open your PLC monitoring screen / online view and verify:

A) Inputs change when you actuate devices

• Manually trigger proximity sensor

• Toggle limit switch

• Simulate pressure switch (if safe, by controlled pressure condition)

If the physical device actuates but PLC input doesn’t change:

• wrong sensor type (PNP/NPN mismatch)

• broken wire / loose terminal

• wrong input address mapping

• wrong common reference

B) Outputs command ON when expected

If PLC output turns ON in software but device doesn’t respond:

• output fuse blown

• coil open circuit

• relay/contactor not pulling in

• wrong voltage to actuator

• missing interlock downstream (drive enable chain, safety contactor, etc.)

• Simple discipline:
• Inputs = “Does PLC see reality?”
• Outputs = “Is PLC commanding action?”
• Then verify “Does action happen physically?”

7) Step 6 — Diagnose the Field Device Like an Engineer (Not a Guess)

Sensors (digital)

• Confirm supply at sensor: +24V and 0V

• Confirm signal line changes state at terminal block

• Confirm PLC input LED / bit changes

Solenoids / contactor coils

• Confirm output voltage delivered to coil when commanded

• Check coil resistance (power off)

• Confirm flyback diode (DC) or snubber (AC) exists

• Confirm valve has correct coil voltage (24VDC vs 110VAC)

Encoders (length control faults)

If you see cut-length drift, random shear misfire, or “encoder fault”:

• verify shield separation from motor cables

• check encoder power stability

• confirm high-speed counter input use

• confirm pulse count direction and integrity during VFD operation

Encoder noise shows up under load. Test while drive is running.

8) Step 7 — Drive Faults: Don’t Blame PLC Until You Read the Drive

If motor won’t run or trips:

1. Read VFD fault code on keypad / HMI

2. Confirm enable chain:

   • Safety relay output

   • PLC “Run/Enable” output

   • VFD “Ready” input back to PLC (if used)

3. Check common real-world causes:

   • undervoltage / phase loss

   • overload settings wrong

   • acceleration too aggressive

   • motor cable issues

   • overheating / cooling failure

   • braking resistor wiring faults (if present)

   • comms fault (if controlled via Modbus/Profinet/EIP)

Rule: A drive trip is a drive trip until proven otherwise. PLC only reports the trip.

9) Step 8 — Logic/Sequence Faults: Find the Missing Permissive

When hardware looks fine but the line won’t proceed, you likely have a permissive missing.

Typical permissive chain (word-based)

Safety_OK AND No_Fault AND Drive_Ready AND Hydraulic_OK AND Shear_Home AND Guard_Closed → Allow_Run

Diagnosis method:

1. Identify the “Allow_Run” coil/bit in PLC

2. Look at each permissive input bit

3. Find the one that is FALSE

4. Trace it back to:

   • sensor state

   • wiring

   • PLC mapping

   • interlock logic design

This turns “mystery stops” into a checklist.

10) Step 9 — Separate Random Faults From Repeatable Faults

Repeatable faults (always at same step)

Usually:

• interlock logic

• sensor alignment

• mechanical timing (shear home switch)

• parameter limit reached

Random faults (appear unpredictable)

Usually:

• 24VDC sag

• loose terminals

• EMC noise

• overheating

• communication instability

• vibration damage inside cabinet

Random faults demand evidence capture:

• log timestamps

• record 24V min values

• capture drive fault history

• check cabinet temperature

11) Step 10 — Prove Root Cause With a Before/After Test

A fix is not a fix until proven.

Example proof method:

• Fault occurs every time shear fires → measure 24V at PLC during shear → see drop to 19V

• Add proper branch fusing + separate solenoid supply + PSU capacity → 24V stays 24V → fault disappears

Always create a simple “cause → measurement → fix → measurement” chain.

That’s how you prevent repeat faults.

12) Fast Reference: Common PLC-Reported Faults and True Causes

• “Input not detected” → wrong sensor type, broken wire, wrong common, wrong address

• “Safety not OK” → E-stop chain open, guard misaligned, safety relay fault, reset not satisfied

• “Drive not ready” → VFD trip, enable missing, comms down, cooling failure

• “Length error” → encoder noise, HSC miswired, scaling wrong, mechanical slippage at pinch roll

• “Hydraulic fault” → pressure switch wiring, pump contactor issue, solenoid short, analog scaling drift

• “Random resets” → 24V sag, loose 0V, PSU overload, cabinet vibration damage

Buyer Strategy (30%): How to Specify PLC Diagnostics So Downtime Drops

When buying a roll former, require:

1. I/O map + terminal cross-reference delivered in a spreadsheet

2. HMI page showing:

   • live I/O status

   • permissives (what’s blocking start)

   • fault history with timestamps

3. Proper separation of:

   • power vs signal wiring

   • encoder/analog shielding

4. Drive fault codes shown on HMI (not “Drive Error” only)

5. 24VDC design with:

   • branch fusing

   • documented load calculation

   • PSU headroom

6. Program backup + parameter backup at shipment

Red flag: “Troubleshooting requires calling the manufacturer every time.”
You want a machine your electrician can diagnose in minutes.

6 Frequently Asked Questions

1) Why does a PLC show faults when the PLC isn’t bad?

Because the PLC is the messenger: it reports missing inputs, safety status, and drive feedback—often caused by wiring, power, or sensors.

2) What should I check first when the machine won’t start?

Safety chain status and 24VDC control power at the PLC terminals. These block everything.

3) How do I tell if it’s a wiring fault or a logic fault?

If the device physically changes but the PLC input bit doesn’t change, it’s wiring/device. If inputs are correct but the permissive bit stays false, it’s logic/interlock.

4) Why do faults appear only at high speed?

Because VFD noise, encoder pulse rate, thermal load, and timing sensitivity increase. Many issues are hidden at slow speed.

5) What causes random intermittent faults in roll forming?

Most commonly: 24VDC sag, loose terminals, vibration damage, EMI coupling, overheating, or unstable communications.

6) What’s the best way to prevent repeat PLC-related downtime?

Demand strong diagnostics (permissives screen, fault history), clean I/O mapping, proper EMC separation, and documented 24V power design with headroom.

Final Engineering Summary

A PLC fault diagnosis workflow that works on roll forming lines is:

1. Make safe

2. Define fault precisely

3. Classify domain (Safety / Power / I/O / Drive / Logic)

4. Verify 24V integrity at PLC and field points

5. Confirm safety chain status via relay + PLC monitoring

6. Verify inputs change physically and in PLC

7. Verify outputs command and actuators respond

8. Read drive/servo fault codes directly

9. Identify missing permissive for logic stalls

10. Prove root cause with before/after measurement

If you want the best next page in this troubleshooting sequence, the logical continuation is: