State Machine Diagram Tool for Swarf Conveyor Logic

The Swarf Tangle Problem: Why Standard Ladder Logic Fails

When machining stringy, work-hardening materials like Inconel 718 or 304 stainless steel, traditional hinge-belt chip conveyors frequently suffer from 'bird-nesting.' Long, unbroken chips wrap around the conveyor's internal sprockets or jam the hinge plates, leading to catastrophic mechanical binding. Standard PLC ladder logic—which typically relies on simple start/stop relays and thermal overloads—is fundamentally reactive. By the time a thermal overload trips on a 3HP conveyor motor, the hinge belt is already stretched, and the gearbox is damaged.

⚠️ Cost Warning: A burned-out motor and torn hinge belt on a Mazak INTEGREX i-400 can cost upwards of $4,500 in replacement parts and 8 hours of spindle downtime. Relying on simple thermal overloads is a reactive, expensive strategy that modern job shops cannot afford.

To solve this, control engineers are shifting to Finite State Machine (FSM) architectures. By utilizing a robust state machine diagram tool, engineers can visually map and simulate complex, asynchronous conveyor behaviors—such as automated reverse-purging and torque-spike detection—before writing a single line of Structured Text (ST) or ladder logic.

Defining Conveyor States for Smart Swarf Management

Before selecting a software tool, you must define the operational states required for intelligent swarf extraction. A modern Hennig Titan series or Mayfran hinge-belt conveyor integrated with a Variable Frequency Drive (VFD) requires at least five distinct states to handle aerospace-grade stringy swarf:

• IDLE: Coolant pump off, belt stopped, VFD at 0Hz.
• FWD_RUN: Normal extraction. Belt runs forward at 30Hz.
• TORQUE_SPIKE: VFD detects >120% rated torque current for >1.5 seconds. Indicates initial bird-nesting.
• REVERSE_PURGE: Belt runs backward at 15Hz for 3.0 seconds to untangle chips from the sprockets, then returns to FWD_RUN.
• FAULT_LOCKOUT: Three consecutive TORQUE_SPIKE events without successful clearing. Triggers machine alarm and halts the CNC cycle.

Mapping the transitions between these states—especially the timers and interlocks required to prevent the VFD from faulting during rapid direction changes—requires dedicated visualization software.

Comparing the Top State Machine Diagram Tool Options

Choosing the right state machine diagram tool depends on your shop's PLC ecosystem, budget, and whether you require automatic code generation. Below is a comparison of the three dominant tools used in industrial machine tool automation as of 2026.

Tool	Standard / Architecture	Code Generation	Approx. Cost (2026)	Best Use Case
MathWorks Stateflow	Model-Based Design (MBD)	Auto-generates IEC 61131-3 ST / C	~$3,500 / year	OEMs building proprietary smart conveyors
Siemens S7-Graph	GRAFCET (IEC 60848)	Native compilation to S7-1500	Included in TIA Portal Pro	Shops standardized on Siemens PLCs
PlantUML	UML State Machine	None (Manual coding required)	Free / Open Source	Agile documentation & Allen-Bradley shops

MathWorks Stateflow (Model-Based Design)

Stateflow is a premium state machine diagram tool integrated into the Simulink environment. It allows engineers to draw state transitions visually and then use the PLC Coder add-on to automatically generate IEC 61131-3 Structured Text. This eliminates syntax errors during the coding phase. If your engineering team is designing a completely new conveyor control algorithm that utilizes edge-computing IoT gateways to predict motor wear based on torque histograms, Stateflow is the industry standard.

Siemens S7-Graph (GRAFCET Standard)

For machine shops running Siemens SIMATIC S7-1500 PLCs, S7-Graph is the native sequential control language based on the GRAFCET standard. Instead of drawing a generic UML diagram and translating it, you build the state machine directly inside TIA Portal. The interlocks (e.g., 'Transition to REVERSE_PURGE only if VFD Ready bit is TRUE') are programmed as transition conditions between steps. It is highly efficient but locks you into the Siemens ecosystem.

PlantUML (Agile Documentation)

PlantUML is a text-based, open-source tool. You write simple code to render state diagrams. While it does not generate PLC code, it is invaluable for shops using Allen-Bradley ControlLogix or CompactLogix systems where programmers prefer writing Structured Text manually but need rigorous, version-controlled documentation stored in Git repositories alongside the PLC project.

Real-World Implementation: VFD Integration & Wiring

A state machine diagram is only as effective as the hardware feedback it receives. To execute the TORQUE_SPIKE state reliably, you cannot rely on the PLC's analog inputs alone due to scan-time latency. You must utilize the VFD's internal logic.

'When programming the reverse-purge state, always ensure the VFD's deceleration time (Parameter P039 on a PowerFlex 525) is set to match the mechanical inertia of the loaded belt. If the PLC commands a reverse while the belt is still coasting forward, you will trip the VFD's overvoltage fault and lock out the conveyor entirely.'

Step-by-Step Hardware Configuration

1. VFD Parameter Setup: On an Allen-Bradley PowerFlex 525, configure the Relay Output to trigger when 'Torque Current' exceeds 120% of the motor's FLA (Full Load Amps).
2. PLC Wiring: Wire the VFD relay output to a high-speed digital input on the PLC (e.g., Siemens DI 16x24VDC HF module).
3. Timer Logic: In your state machine tool, map a TON (Timer On Delay) block. The transition from FWD_RUN to TORQUE_SPIKE only occurs if the digital input remains HIGH for 1500ms. This filters out harmless, momentary torque spikes caused by heavy cast iron chips dropping onto the belt.
4. Direction Interlock: Before transitioning to REVERSE_PURGE, the state machine must verify the VFD's 'At Zero Speed' bit is TRUE to prevent mechanical shock to the gearbox.

Decision Framework: Which Tool Should Your Shop Use?

Selecting the correct state machine diagram tool requires aligning the software with your shop's specific maintenance capabilities and PLC hardware.

Choose MathWorks Stateflow if:

• You are an OEM building custom swarf management systems.
• You require automated C-code generation for embedded IoT edge sensors on the conveyor.
• Your team has a dedicated controls engineering department.

Choose Siemens S7-Graph if:

• Your CNC cells are integrated via Siemens S7-1500 or S7-1200 PLCs.
• You want to keep the visual diagram and the executable code in a single TIA Portal environment.
• You need to comply strictly with IEC 60848 GRAFCET standards for European machine exports.

Ultimately, migrating from reactive thermal-overload logic to a predictive, state-machine-driven swarf management architecture reduces conveyor-related CNC downtime by up to 80%. By mapping your states visually before programming, you ensure that edge cases—like a jam occurring exactly during a coolant flush cycle—are handled gracefully, protecting both your machine tool and your bottom line.