In a roll forming machine, the HMI (Human Machine Interface) is often misunderstood as “just the screen.”
In reality, the HMI determines:
Operator efficiency
Production consistency
Fault response speed
Quality traceability
Changeover accuracy
Training requirements
Warranty disputes
A poorly designed HMI causes:
Wrong recipe selection
Incorrect length entry
Unnoticed alarms
Unsafe overrides
Operator confusion
Production scrap
A professionally engineered HMI becomes:
A control layer
A diagnostic tool
A quality assurance system
A production reporting platform
This guide explains how to structure HMI systems correctly for industrial roll forming machines.
The PLC controls logic.
The HMI controls interaction.
The HMI must:
Display machine state clearly
Allow safe parameter input
Prevent unsafe operation
Record changes
Log faults
Display real-time process variables
The HMI should never directly control outputs.
All commands must pass through PLC interlocks.
A recipe is a structured group of production parameters including:
Panel length
Quantity
Line speed
Shear delay compensation
Punch position offsets
Deceleration ramp
Tension settings
Stacker drop count
Without recipe management:
Operators manually re-enter values
Errors increase
Quality varies
Setup time increases
Recipes should include:
Profile name
Material type
Gauge
Customer reference
Target length
Line speed
Acceleration rate
Deceleration rate
Shear delay
Valve compensation
Punch window offset
Quantity
Batch size
Stacker drop count
Recipes must be structured in data blocks, not loose tags.
Professional systems include:
Recipe revision number
Last modified date
Modified by (operator name)
Change comment
This protects:
Warranty claims
Production traceability
Quality audits
No validation limits
Operators allowed to modify compensation values
No separation between operator and engineer access
No backup storage
Proper design includes permission levels.
Alarms in roll forming machines should:
Identify cause
Provide action guidance
Record timestamp
Record duration
Poor alarm design causes:
Alarm flooding
Operators ignoring warnings
Delayed fault resolution
E-stop activated
Guard open
Emergency circuit fault
Hydraulic pressure low
Encoder mismatch
Length deviation
Stacker jam
Shear timeout
Punch position error
VFD fault
Servo following error
Communication loss
Each alarm must include:
Clear description
Probable cause
Suggested action
Latching alarms:
Require manual reset
Used for safety-critical events
Non-latching alarms:
Clear automatically when condition resolves
Incorrect latching logic causes nuisance resets.
Alarms should be categorized:
Priority 1 — Safety
Priority 2 — Production Stop
Priority 3 — Warning
This ensures operators focus on critical events.
Trend screens are underused in roll forming.
They provide real-time graphs of:
Hydraulic pressure
Line speed
Tension
Encoder speed
Temperature
Trends allow detection of:
Gradual pressure drop
Speed oscillation
Overheating
Slippage events
Without trends, maintenance becomes reactive.
Real-Time:
10–60 second window
Used for tuning
Historical:
Hours or days
Used for maintenance analysis
Both are valuable.
Hydraulic pressure:
Normal: 160 bar
Trend shows drop to 140 bar over weeks
This indicates:
Pump wear
Filter clogging
Internal leakage
Trend analysis prevents unplanned downtime.
Audit logs record:
Recipe changes
Parameter adjustments
Alarm resets
Login activity
Manual overrides
Audit logs are essential for:
Quality disputes
Warranty analysis
ISO compliance
Customer traceability
Old value
New value
Timestamp
User name
Machine state
Without audit logging, responsibility cannot be determined during production issues.
Main screen should show:
Machine state
Current recipe
Length target
Current count
Line speed
Active alarms
Avoid clutter.
Critical operations must be within two screen touches.
Complex navigation slows response time.
Avoid vague messages like:
“Fault 27 Active”
Instead display:
“Hydraulic Pressure Below 120 Bar — Check Pump or Filter”
Professional roll forming HMI should include:
Level 1 — Operator
Level 2 — Supervisor
Level 3 — Maintenance
Level 4 — Engineer
Operators should not modify:
Shear compensation
Encoder scaling
Motion parameters
Security prevents production errors.
Step 1 — Verify tag mapping
Step 2 — Validate recipe save/load
Step 3 — Test alarm triggers
Step 4 — Confirm audit logging
Step 5 — Verify trend data accuracy
Step 6 — Confirm user permissions
Never ship a machine without verifying HMI logging.
Wrong recipe loaded
Shear delay accidentally modified
Alarm not visible on main screen
Trend disabled
No login control
Manual override left active
Most are design flaws, not operator faults.
Use structured recipe storage
Enable audit logs
Provide trend monitoring
Separate operator and engineer access
Display clear machine state
Integrate production reporting
HMI should enhance control, not complicate it.
Recipes ensure consistent production by storing all required parameters for each profile. Without structured recipes, operators must manually enter settings, increasing errors and scrap rates.
An effective alarm should display a clear description, probable cause, suggested action, timestamp, and severity level.
Trend screens allow monitoring of variables such as hydraulic pressure and speed. Gradual changes can be detected before they cause downtime or quality issues.
Audit logs record parameter changes and user actions, protecting against disputes, quality claims, and unauthorized adjustments.
No. Compensation values should be restricted to maintenance or engineering access levels to prevent accidental production errors.
Overcomplicating the interface with excessive screens and unclear alarm messages, leading to slow response and operator confusion.
Copyright 2026 © Machine Matcher.