Inovance Structured Text for Conveyor Systems: Complete Programming Guide

Mastering advanced Structured Text techniques for Conveyor Systems in Inovance's InoProShop / AutoShop unlocks capabilities beyond basic implementations. This guide explores sophisticated programming patterns, optimization strategies, and advanced features that separate expert Inovance programmers from intermediate practitioners in Material Handling applications.

Inovance's InoProShop / AutoShop contains powerful advanced features that many programmers never fully utilize. With ~2% global, top-3 in China market share and deployment in demanding applications like airport baggage handling and warehouse distribution, Inovance has developed advanced capabilities specifically for beginner to intermediate projects requiring powerful for complex logic and excellent code reusability.

Advanced Conveyor Systems implementations leverage sophisticated techniques including multi-sensor fusion algorithms, coordinated multi-actuator control, and intelligent handling of product tracking. When implemented using Structured Text, these capabilities are achieved through complex calculations patterns that exploit Inovance-specific optimizations.

This guide reveals advanced programming techniques used by expert Inovance programmers, including custom function blocks, optimized data structures, advanced Structured Text patterns, and InoProShop / AutoShop-specific features that deliver superior performance. You'll learn implementation strategies that go beyond standard documentation, based on years of practical experience with Conveyor Systems systems in production Material Handling environments.

Inovance InoProShop / AutoShop for Conveyor Systems

Inovance ships InoProShop as its primary programming IDE for the AM600 / AM610 / H5U medium-PLC families and AutoShop for the Easy-series compact PLCs. InoProShop is built on the CODESYS 3.5 platform, which means engineers transferring from Beckhoff TwinCAT, WAGO e!Cockpit, or Schneider EcoStruxure Machine Expert will recognise the project tree, IEC 61131-3 editors, and visualisation tools immediately. AutoShop is a more traditional ladder-and-IL editor closer to compact-PLC tradition. Inovance'...

Platform Strengths for Conveyor Systems:

CODESYS-based InoProShop for IEC 61131-3 compliance

Tight integration with Inovance servo drives and inverters

Strong motion, robotics, and elevator-control product lines

EtherCAT support across mid-tier and high-end CPUs

Unique ${brand.software} Features:

InoProShop built on CODESYS 3.5 — full IEC 61131-3 compliance

Native EtherCAT motion across mid-tier and high-end CPUs

Tight integration with Inovance servo drives, inverters, and HMIs

AutoShop for compact AC800 / Easy-series CPUs (lighter IDE)

Key Capabilities:

The InoProShop / AutoShop environment excels at Conveyor Systems applications through its codesys-based inoproshop for iec 61131-3 compliance. This is particularly valuable when working with the 5 sensor types typically found in Conveyor Systems systems, including Photoelectric sensors, Proximity sensors, Encoders.

Control Equipment for Conveyor Systems:

Belt conveyors with motor-driven pulleys

Roller conveyors (powered and gravity)

Modular plastic belt conveyors

Accumulation conveyors (zero-pressure, minimum-pressure)

Inovance's controller families for Conveyor Systems include:

AM600: Suitable for beginner to intermediate Conveyor Systems applications

AM610: Suitable for beginner to intermediate Conveyor Systems applications

H5U: Suitable for beginner to intermediate Conveyor Systems applications

AC800: Suitable for beginner to intermediate Conveyor Systems applications

Hardware Selection Guidance:

Inovance CPU choice ranges from Easy320 / Easy510 (compact, AutoShop-programmed, FX-style memory model) through AC800 (mid-range compact) to AM600 / AM610 / H5U (medium PLC with EtherCAT, OPC UA, redundant networking on H5U). AM600 is the volume product for OEM machinery; H5U is the choice for higher-axis-count motion applications and lithium-battery / EV manufacturing lines where EtherCAT and tig...

Industry Recognition:

High in China across textiles, packaging, lithium battery, EV manufacturing, elevators, robotics; growing in SE Asia and MEA. High in Chinese EV manufacturing — Inovance is a major automation supplier to BYD, NIO, and Tier 2/3 EV-component plants. AM600 + H5U with EtherCAT motion controls battery-cell assembly, module welding, pack assembly, and end-of-line test stations. Less common in Western Tier 1 automotive but appear...

Investment Considerations:

With $$ pricing, Inovance positions itself in the mid-range segment. For Conveyor Systems projects requiring beginner skill levels and 1-3 weeks development time, the total investment includes hardware, software licensing, training, and ongoing support.

Understanding Structured Text for Conveyor Systems

Structured Text (ST) is a high-level, text-based programming language defined in IEC 61131-3. It resembles Pascal and provides powerful constructs for complex algorithms, calculations, and data manipulation.

Execution Model:

Code executes sequentially from top to bottom within each program unit. Variables maintain state between scan cycles unless explicitly reset.

Core Advantages for Conveyor Systems:

Powerful for complex logic: Critical for Conveyor Systems when handling beginner to intermediate control logic

Excellent code reusability: Critical for Conveyor Systems when handling beginner to intermediate control logic

Compact code representation: Critical for Conveyor Systems when handling beginner to intermediate control logic

Good for algorithms and calculations: Critical for Conveyor Systems when handling beginner to intermediate control logic

Familiar to software developers: Critical for Conveyor Systems when handling beginner to intermediate control logic

Why Structured Text Fits Conveyor Systems:

Conveyor Systems systems in Material Handling typically involve:

Sensors: Photoelectric sensors for product detection and zone occupancy, Proximity sensors for metal product detection, Encoders for speed feedback and position tracking

Actuators: AC motors with VFDs for variable speed control, Motor starters for fixed-speed sections, Pneumatic diverters and pushers for sorting

Complexity: Beginner to Intermediate with challenges including Maintaining product tracking through merges and diverters

Programming Fundamentals in Structured Text:

Variables:
- declaration: VAR / VAR_INPUT / VAR_OUTPUT / VAR_IN_OUT / VAR_GLOBAL sections
- initialization: Variables can be initialized at declaration: Counter : INT := 0;
- constants: VAR CONSTANT section for read-only values

Operators:
- arithmetic: + - * / MOD (modulo)
- comparison: = <> < > <= >=
- logical: AND OR XOR NOT

ControlStructures:
- if: IF condition THEN statements; ELSIF condition THEN statements; ELSE statements; END_IF;
- case: CASE selector OF value1: statements; value2: statements; ELSE statements; END_CASE;
- for: FOR index := start TO end BY step DO statements; END_FOR;

Best Practices for Structured Text:

Use meaningful variable names with consistent naming conventions

Initialize all variables at declaration to prevent undefined behavior

Use enumerated types for state machines instead of magic numbers

Break complex expressions into intermediate variables for readability

Use functions for reusable calculations and function blocks for stateful operations

Common Mistakes to Avoid:

Using = instead of := for assignment (= is comparison)

Forgetting semicolons at end of statements

Integer division truncation - use REAL for decimal results

Infinite loops from incorrect WHILE/REPEAT conditions

Typical Applications:

1. PID control: Directly applicable to Conveyor Systems
2. Recipe management: Related control patterns
3. Statistical calculations: Related control patterns
4. Data logging: Related control patterns

Understanding these fundamentals prepares you to implement effective Structured Text solutions for Conveyor Systems using Inovance InoProShop / AutoShop.

Implementing Conveyor Systems with Structured Text

Conveyor control systems manage the movement of materials through manufacturing and distribution facilities. PLCs coordinate multiple conveyor sections, handle product tracking, manage zones and accumulation, and interface with other automated equipment.

This walkthrough demonstrates practical implementation using Inovance InoProShop / AutoShop and Structured Text programming.

System Requirements:

A typical Conveyor Systems implementation includes:

Input Devices (Sensors):
1. Photoelectric sensors for product detection and zone occupancy: Critical for monitoring system state
2. Proximity sensors for metal product detection: Critical for monitoring system state
3. Encoders for speed feedback and position tracking: Critical for monitoring system state
4. Barcode readers and RFID scanners for product identification: Critical for monitoring system state
5. Weight scales for product verification: Critical for monitoring system state

Output Devices (Actuators):
1. AC motors with VFDs for variable speed control: Primary control output
2. Motor starters for fixed-speed sections: Supporting control function
3. Pneumatic diverters and pushers for sorting: Supporting control function
4. Servo drives for precision positioning: Supporting control function
5. Brake modules for controlled stops: Supporting control function

Control Equipment:

Belt conveyors with motor-driven pulleys

Roller conveyors (powered and gravity)

Modular plastic belt conveyors

Accumulation conveyors (zero-pressure, minimum-pressure)

Control Strategies for Conveyor Systems:

1. Primary Control: Automated material handling using conveyor belts with PLC control for sorting, routing, and tracking products.
2. Safety Interlocks: Preventing Product tracking
3. Error Recovery: Handling Speed synchronization

Implementation Steps:

Step 1: Map conveyor layout with all zones, sensors, and motor locations

In InoProShop / AutoShop, map conveyor layout with all zones, sensors, and motor locations.

Step 2: Define product types, sizes, weights, and handling requirements

In InoProShop / AutoShop, define product types, sizes, weights, and handling requirements.

Step 3: Create tracking data structure with product ID, location, and destination

In InoProShop / AutoShop, create tracking data structure with product id, location, and destination.

Step 4: Implement zone control logic with proper handshaking between zones

In InoProShop / AutoShop, implement zone control logic with proper handshaking between zones.

Step 5: Add product tracking using sensor events and encoder feedback

In InoProShop / AutoShop, add product tracking using sensor events and encoder feedback.

Step 6: Program diverter/sorter logic based on product routing data

In InoProShop / AutoShop, program diverter/sorter logic based on product routing data.

Inovance Function Design:

InoProShop strongly favours function-block reuse via the Library Manager — Inovance ships standard libraries for motion, drives, HMI, OPC UA, and industry-specific applications (lithium-battery, EV, elevator). AutoShop reuse is open-coded via P-label subroutines. OEM machine-builders increasingly default to InoProShop / AM600 to access the FB libraries.

Common Challenges and Solutions:

1. Maintaining product tracking through merges and diverters

Solution: Structured Text addresses this through Powerful for complex logic.

2. Handling products of varying sizes and weights

Solution: Structured Text addresses this through Excellent code reusability.

3. Preventing jams at transitions and merge points

Solution: Structured Text addresses this through Compact code representation.

4. Coordinating speeds between connected conveyors

Solution: Structured Text addresses this through Good for algorithms and calculations.

Safety Considerations:

E-stop functionality with proper zone isolation

Pull-cord emergency stops along conveyor length

Guard interlocking at all pinch points

Speed monitoring to prevent runaway conditions

Light curtains at operator access points

Performance Metrics:

Scan Time: Optimize for 5 inputs and 5 outputs

Memory Usage: Efficient data structures for AM600 capabilities

Response Time: Meeting Material Handling requirements for Conveyor Systems

Inovance Diagnostic Tools:

InoProShop online mode with full POU monitoring and breakpoint debug,EtherCAT diagnostics page with topology and slave status,Trace tool for analogue / motion signal capture,OPC UA server diagnostics page,Modbus communication trace utility,AutoShop online mode for legacy AC800 / Easy series,Inovance HMI integrated diagnostics for HMI-PLC binding faults,Servo-drive panel diagnostics with InoProShop drive-monitor view,EtherCAT slave-firmware update tool,Project compare tool for change tracking

Inovance's InoProShop / AutoShop provides tools for performance monitoring and optimization, essential for achieving the 1-3 weeks development timeline while maintaining code quality.

Inovance Structured Text Example for Conveyor Systems

Complete working example demonstrating Structured Text implementation for Conveyor Systems using Inovance InoProShop / AutoShop. Follows Inovance naming conventions. Tested on AM600 hardware.

(* Inovance InoProShop / AutoShop - Conveyor Systems Control *)
(* Structured Text Implementation for Material Handling *)
(* On InoProShop projects, conventions follow CODESYS / IEC norms — Pasca *)

PROGRAM PRG_CONVEYOR_SYSTEMS_Control

VAR
    (* State Machine Variables *)
    eState : E_CONVEYOR_SYSTEMS_States := IDLE;
    bEnable : BOOL := FALSE;
    bFaultActive : BOOL := FALSE;

    (* Timers *)
    tonDebounce : TON;
    tonProcessTimeout : TON;
    tonFeedbackCheck : TON;

    (* Counters *)
    ctuCycleCounter : CTU;

    (* Process Variables *)
    rPhotoelectricsensors : REAL := 0.0;
    rACDCmotors : REAL := 0.0;
    rSetpoint : REAL := 100.0;
END_VAR

VAR CONSTANT
    (* Material Handling Process Parameters *)
    C_DEBOUNCE_TIME : TIME := T#500MS;
    C_PROCESS_TIMEOUT : TIME := T#30S;
    C_BATCH_SIZE : INT := 50;
END_VAR

(* Input Conditioning *)
tonDebounce(IN := bStartButton, PT := C_DEBOUNCE_TIME);
bEnable := tonDebounce.Q AND NOT bEmergencyStop AND bSafetyOK;

(* Main State Machine - Pattern: InoProShop state machines typically use  *)
CASE eState OF
    IDLE:
        rACDCmotors := 0.0;
        ctuCycleCounter(RESET := TRUE);
        IF bEnable AND rPhotoelectricsensors > 0.0 THEN
            eState := STARTING;
        END_IF;

    STARTING:
        (* Ramp up output - Gradual start *)
        rACDCmotors := MIN(rACDCmotors + 5.0, rSetpoint);
        IF rACDCmotors >= rSetpoint THEN
            eState := RUNNING;
        END_IF;

    RUNNING:
        (* Conveyor Systems active - Conveyor control systems manage the movement of ma *)
        tonProcessTimeout(IN := TRUE, PT := C_PROCESS_TIMEOUT);
        ctuCycleCounter(CU := bCyclePulse, PV := C_BATCH_SIZE);

        IF ctuCycleCounter.Q THEN
            eState := COMPLETE;
        ELSIF tonProcessTimeout.Q THEN
            bFaultActive := TRUE;
            eState := FAULT;
        END_IF;

    COMPLETE:
        rACDCmotors := 0.0;
        (* Log production data - InoProShop on AM600 / H5U supports SD-card logging via library FBs, plus OPC UA streaming for cloud / on-premises historians. Inovance HMIs add CSV logging at HMI tier. AutoShop projects rely on HMI-tier logging exclusively. *)
        eState := IDLE;

    FAULT:
        rACDCmotors := 0.0;
        (* InoProShop alarms are typically defined in the visualisation alarm-configuration page with severity, latching, and acknowledgement behaviour configured per alarm. The runtime maintains active and historical alarm lists. AutoShop projects fall back to M-flag banks with HMI-side alarm logging. *)
        IF bFaultReset AND NOT bEmergencyStop THEN
            bFaultActive := FALSE;
            eState := IDLE;
        END_IF;
END_CASE;

(* Safety Override - Always executes *)
IF bEmergencyStop OR NOT bSafetyOK THEN
    rACDCmotors := 0.0;
    eState := FAULT;
    bFaultActive := TRUE;
END_IF;

END_PROGRAM

Code Explanation:

1.Enumerated state machine (InoProShop state machines typically use IEC SFC steps with action blocks per step, or a state-enum-and-CASE pattern in Structured Text. SFC dominates production-line sequencers; CASE patterns dominate axis-control state and recipe-routing logic. AutoShop projects fall back to FX-style SFC step memory (S0..S511) or D-register integer state.) for clear Conveyor Systems sequence control
2.Constants define Material Handling-specific parameters: cycle time 30s, batch size
3.Input conditioning with debounce timer prevents false triggers in industrial environment
4.STARTING state implements soft-start ramp - prevents mechanical shock
5.Process timeout detection identifies stuck conditions - critical for reliability
6.Safety override section executes regardless of state - Inovance best practice for beginner to intermediate systems

Best Practices

✓Follow Inovance naming conventions: On InoProShop projects, conventions follow CODESYS / IEC norms — PascalCase for
✓Inovance function design: InoProShop strongly favours function-block reuse via the Library Manager — Inova
✓Data organization: InoProShop uses GVLs and persistent variables for shared data. AutoShop uses D /
✓Structured Text: Use meaningful variable names with consistent naming conventions
✓Structured Text: Initialize all variables at declaration to prevent undefined behavior
✓Structured Text: Use enumerated types for state machines instead of magic numbers
✓Conveyor Systems: Use rising edge detection for sensor events, not level
✓Conveyor Systems: Implement proper debouncing for mechanical sensors
✓Conveyor Systems: Add gap checking before merges to prevent collisions
✓Debug with InoProShop / AutoShop: Use InoProShop's online mode to set breakpoints in POUs and step throu
✓Safety: E-stop functionality with proper zone isolation
✓Use InoProShop / AutoShop simulation tools to test Conveyor Systems logic before deployment

Common Pitfalls to Avoid

⚠Structured Text: Using = instead of := for assignment (= is comparison)
⚠Structured Text: Forgetting semicolons at end of statements
⚠Structured Text: Integer division truncation - use REAL for decimal results
⚠Inovance common error: EtherCAT slave order mismatch after physical re-cabling — slave addressing break
⚠Conveyor Systems: Maintaining product tracking through merges and diverters
⚠Conveyor Systems: Handling products of varying sizes and weights
⚠Neglecting to validate Photoelectric sensors for product detection and zone occupancy leads to control errors
⚠Insufficient comments make Structured Text programs unmaintainable over time

Related Certifications

🏆Inovance Certified Engineer

🏆InoProShop / AutoShop training certificates

🏆EV / Lithium Battery automation specialist tracks

🏆Advanced Inovance Programming Certification

Mastering Structured Text for Conveyor Systems applications using Inovance InoProShop / AutoShop requires understanding both the platform's capabilities and the specific demands of Material Handling. This guide has provided comprehensive coverage of implementation strategies, working code examples, best practices, and common pitfalls to help you succeed with beginner to intermediate Conveyor Systems projects.

Inovance's ~2% global, top-3 in China market share and high in china across textiles, packaging, lithium battery, ev manufacturing, elevators, robotics; growing in se asia and mea demonstrate the platform's capability for demanding applications. The platform excels in Material Handling applications where Conveyor Systems reliability is critical.

By following the practices outlined in this guide—from proper program structure and Structured Text best practices to Inovance-specific optimizations—you can deliver reliable Conveyor Systems systems that meet Material Handling requirements.

Next Steps for Professional Development:

1. Certification: Pursue Inovance Certified Engineer to validate your Inovance expertise
2. Advanced Training: Consider InoProShop / AutoShop training certificates for specialized Material Handling applications
3. Hands-on Practice: Build Conveyor Systems projects using AM600 hardware
4. Stay Current: Follow InoProShop / AutoShop updates and new Structured Text features

Structured Text Foundation:

Structured Text (ST) is a high-level, text-based programming language defined in IEC 61131-3. It resembles Pascal and provides powerful constructs for...

The 1-3 weeks typical timeline for Conveyor Systems projects will decrease as you gain experience with these patterns and techniques. Remember: Use rising edge detection for sensor events, not level

For further learning, explore related topics including Recipe management, Warehouse distribution, and Inovance platform-specific features for Conveyor Systems optimization.