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.
Before diagnosis:
Lockout/Tagout main power when opening cabinets or moving wiring
Confirm stored energy is safe:
VFD DC bus discharged
Hydraulic pressure relieved
Pneumatic air isolated if relevant
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.
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.
Use this quick sorting:
Machine won’t start
“Safety Not OK”
Safety relay LEDs show fault
Contactors won’t pull in
PLC resets, HMI flickers
Random I/O drops
Multiple unrelated alarms
24V undervoltage events
One sensor “never turns on”
Solenoid doesn’t actuate
A limit switch always “stuck”
Inputs chatter
VFD trip code
Servo alarm
“Drive not ready”
Motor won’t enable
No hardware fault visible
One permissive missing
State machine stuck
Sequence halts at same step
This classification decides your next test.
Do this before deep PLC work—control power issues create fake “logic problems.”
Measure 24VDC at the PLC power terminals (not only at PSU output)
Measure 24VDC at the farthest field I/O terminals (worst-case drop)
Look for voltage sag when:
hydraulic pump starts
shear fires
stacker engages
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.
Even if the PLC is fine, safety not OK will prevent outputs.
24VDC → E-STOP loop (dual channel) → Safety relay → Safety outputs → Main contactor / drive enable
Safety relay AUX → PLC input “Safety_OK”
Check safety relay status LEDs / fault code (if present)
Confirm Safety_OK input changes in PLC monitoring
Verify each device in chain:
E-stop buttons (all stations)
guard switches
light curtain OSSD if fitted
reset button logic (no auto restart)
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.
Open your PLC monitoring screen / online view and verify:
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
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?”
Confirm supply at sensor: +24V and 0V
Confirm signal line changes state at terminal block
Confirm PLC input LED / bit changes
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)
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.
If motor won’t run or trips:
Read VFD fault code on keypad / HMI
Confirm enable chain:
Safety relay output
PLC “Run/Enable” output
VFD “Ready” input back to PLC (if used)
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.
When hardware looks fine but the line won’t proceed, you likely have a permissive missing.
Safety_OK AND No_Fault AND Drive_Ready AND Hydraulic_OK AND Shear_Home AND Guard_Closed → Allow_Run
Diagnosis method:
Identify the “Allow_Run” coil/bit in PLC
Look at each permissive input bit
Find the one that is FALSE
Trace it back to:
sensor state
wiring
PLC mapping
interlock logic design
This turns “mystery stops” into a checklist.
Usually:
interlock logic
sensor alignment
mechanical timing (shear home switch)
parameter limit reached
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
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.
“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
When buying a roll former, require:
I/O map + terminal cross-reference delivered in a spreadsheet
HMI page showing:
live I/O status
permissives (what’s blocking start)
fault history with timestamps
Proper separation of:
power vs signal wiring
encoder/analog shielding
Drive fault codes shown on HMI (not “Drive Error” only)
24VDC design with:
branch fusing
documented load calculation
PSU headroom
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.
Because the PLC is the messenger: it reports missing inputs, safety status, and drive feedback—often caused by wiring, power, or sensors.
Safety chain status and 24VDC control power at the PLC terminals. These block everything.
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.
Because VFD noise, encoder pulse rate, thermal load, and timing sensitivity increase. Many issues are hidden at slow speed.
Most commonly: 24VDC sag, loose terminals, vibration damage, EMI coupling, overheating, or unstable communications.
Demand strong diagnostics (permissives screen, fault history), clean I/O mapping, proper EMC separation, and documented 24V power design with headroom.
A PLC fault diagnosis workflow that works on roll forming lines is:
Make safe
Define fault precisely
Classify domain (Safety / Power / I/O / Drive / Logic)
Verify 24V integrity at PLC and field points
Confirm safety chain status via relay + PLC monitoring
Verify inputs change physically and in PLC
Verify outputs command and actuators respond
Read drive/servo fault codes directly
Identify missing permissive for logic stalls
Prove root cause with before/after measurement
If you want the best next page in this troubleshooting sequence, the logical continuation is:
Copyright 2026 © Machine Matcher.