PLC Diagnostics Pattern for Roll Forming Machines — “Why Didn’t It Start?” Bit-by-Bit Trace

Introduction — The Most Common Question in Roll Forming Automation

When a roll forming machine refuses to run, the most common question operators ask is simple:

“Why didn’t the machine start?”

Unfortunately, many PLC programs make this difficult to answer. Operators press the start button and nothing happens, leaving them unsure whether the problem is:

• a safety condition
• a sensor fault
• a hydraulic issue
• a drive fault
• a PLC interlock.

Without proper diagnostics, technicians may spend a long time checking each system manually.

To avoid this, well-designed PLC programs include a diagnostics pattern that traces the machine start logic step by step.

This pattern is often called a bit-by-bit trace.

It allows operators and technicians to see exactly which condition prevented the machine from starting.

Why Roll Forming Machines Need Clear Start Diagnostics

Roll forming lines contain many subsystems that must be ready before production begins.

Typical subsystems include:

• safety systems
• hydraulic power units
• main drive motors
• punch systems
• shear systems
• stackers
• servo systems.

If any of these subsystems reports a fault, the PLC blocks the machine start command.

Without clear diagnostics, identifying the failed condition can be frustrating and time-consuming.

What a Bit-by-Bit Trace Means

A bit-by-bit trace shows the status of every condition required for the machine to start.

Each condition is represented by a PLC signal or bit.

If the bit is TRUE, the condition is satisfied.

If the bit is FALSE, that condition is preventing the machine from starting.

By examining the status of each bit, technicians can immediately identify the problem.

Typical Machine Start Logic

The PLC usually determines whether the machine can start using a group of interlocks.

A simplified start condition might look like this:

MachineStartAllowed =

SafetyOK
AND HydraulicReady
AND DrivesReady
AND ShearHome
AND PunchHome
AND StackerReady
AND NoActiveFaults.

If any one of these conditions is false, the machine will not start.

The Problem with Traditional PLC Programs

In many machines, all these conditions are combined into one large logic rung.

Example:

StartAllowed = A AND B AND C AND D AND E.

If the result is false, operators only see:

Machine not ready.

They cannot see which specific condition failed.

This makes troubleshooting much harder.

The Diagnostic Pattern Solution

Instead of combining conditions immediately, each interlock should be displayed individually.

Example diagnostic signals:

SafetyOK
HydraulicPressureOK
MainDriveReady
ShearHomePosition
PunchHomePosition
StackerReady
ServoReady.

Each signal can be displayed on the HMI.

Operators can then immediately see which condition is blocking machine startup.

Visualizing Interlocks on the HMI

A good HMI screen shows machine start conditions clearly.

Typical displays include:

• green indicator when condition is satisfied
• red indicator when condition is not satisfied.

Example display:

Safety Circuit — OK
Hydraulic Pressure — OK
Shear Position — NOT READY
Punch Position — OK
Stacker Ready — OK

The operator immediately sees that the shear is not in the home position.

Breaking Down the Start Logic

To build a useful diagnostic system, the start logic should be structured in layers.

Layer 1 — Safety Conditions

Safety conditions must always be satisfied first.

Typical safety signals include:

• emergency stop reset
• safety relay healthy
• guard doors closed
• safety light curtain clear.

If any safety condition is false, the machine must not start.

Layer 2 — Machine Readiness

The next layer checks machine subsystem readiness.

Typical checks include:

• hydraulic pressure available
• main drive ready
• servo systems enabled
• encoder signal healthy.

These conditions ensure that the machine can operate correctly.

Layer 3 — Mechanical Position Checks

The PLC verifies that moving components are in safe positions.

Examples include:

• shear blade in home position
• punch head in home position
• stacker platform clear.

Incorrect positions can cause mechanical collisions if the machine starts.

Layer 4 — System Fault Checks

The PLC verifies that no active faults exist.

Typical faults include:

• drive faults
• servo alarms
• hydraulic system errors
• sensor failures.

Active faults must be cleared before startup.

Layer 5 — Operator Commands

Finally, the PLC checks operator commands.

Typical inputs include:

• start button pressed
• correct machine mode selected
• recipe loaded.

Only after these checks pass can the machine start.

Diagnostic Bits Example

A good PLC program may create diagnostic bits such as:

Diag_SafetyOK
Diag_HydraulicReady
Diag_DriveReady
Diag_ShearHome
Diag_PunchHome
Diag_StackerReady
Diag_NoActiveFaults.

These bits represent the status of each subsystem.

Creating a Master Start Signal

After all individual conditions are checked, the PLC combines them to create the final start signal.

Example:

MachineReady =

Diag_SafetyOK
AND Diag_HydraulicReady
AND Diag_DriveReady
AND Diag_ShearHome
AND Diag_PunchHome
AND Diag_StackerReady
AND Diag_NoActiveFaults.

If MachineReady is TRUE, the machine may start.

Adding Failure Reason Diagnostics

To improve troubleshooting further, the PLC can record the first failing condition.

Example diagnostic outputs:

StartBlockedBySafety
StartBlockedByHydraulics
StartBlockedByShearPosition
StartBlockedByPunchPosition.

Displaying this information on the HMI helps operators identify problems instantly.

Example Startup Diagnostic Screen

A typical HMI diagnostic screen might show:

Machine Start Status

Safety System — OK
Hydraulic System — OK
Main Drive — OK
Punch System — OK
Shear Position — NOT READY
Stacker — OK

Machine Start Blocked By: Shear Not Home

This clear message eliminates guesswork.

Why This Pattern Improves Troubleshooting

Using a bit-by-bit trace provides several advantages.

Technicians can:

• identify faults immediately
• avoid unnecessary inspections
• reduce machine downtime.

Operators can also correct simple issues without calling maintenance.

Logging Start Failures

Advanced diagnostic systems may log start failures.

The PLC records:

• time of failure
• condition preventing startup
• operator ID.

This information helps engineers identify recurring machine issues.

Preventing Diagnostic Confusion

To ensure diagnostics remain clear, follow several rules.

Do Not Combine Conditions Too Early

Each condition should remain visible before the final start signal.

Use Clear Naming

Diagnostic bits should use descriptive names.

Example:

Diag_HydraulicPressureOK instead of Bit17.

Provide HMI Visibility

Operators must be able to see diagnostic signals easily.

Commissioning Diagnostic Logic

During machine commissioning, engineers should test diagnostic functions.

Typical tests include:

1 activating each interlock condition
2 verifying correct diagnostic message
3 confirming machine start is blocked.

This ensures the system works correctly.

Preventative Maintenance Using Diagnostics

Diagnostic systems also help with maintenance.

Technicians can review logs to identify:

• frequently failing sensors
• intermittent hydraulic problems
• recurring drive faults.

This information supports predictive maintenance strategies.

Benefits of Bit-by-Bit Diagnostics

Implementing this pattern provides several important benefits.

These include:

• faster troubleshooting
• reduced downtime
• improved operator understanding
• clearer machine status.

For complex roll forming machines, clear diagnostic logic is essential.

FAQ — PLC Startup Diagnostics

What is a bit-by-bit trace in PLC diagnostics?

A bit-by-bit trace displays the status of each interlock condition required for machine startup.

Why is startup diagnostic logic important?

It helps operators quickly identify why a machine cannot start, reducing troubleshooting time.

What conditions usually block roll forming machine startup?

Common causes include safety circuit faults, hydraulic pressure loss, incorrect shear position, or drive faults.

Where are diagnostic signals usually displayed?

Diagnostic signals are typically displayed on the HMI so operators can view machine status.

Can diagnostic systems log machine startup failures?

Yes. Many PLC systems record timestamps and failure reasons to help engineers analyze recurring problems.

How does this pattern improve maintenance?

Technicians can quickly locate faults and identify recurring issues using diagnostic logs.