Implementing Structured Text for Material Handling using Inovance InoProShop / AutoShop requires translating theory into working code that performs reliably in production. This hands-on guide focuses on practical implementation steps, real code examples, and the pragmatic decisions that make the difference between successful and problematic Material Handling deployments.
Inovance's platform serves High in China across textiles, packaging, lithium battery, EV manufacturing, elevators, robotics; growing in SE Asia and MEA, providing the proven foundation for Material Handling implementations. The InoProShop / AutoShop environment supports 5 programming languages, with Structured Text being particularly effective for Material Handling because complex calculations, data manipulation, advanced control algorithms, and when code reusability is important. Practical implementation requires understanding not just language syntax, but how Inovance's execution model handles 5 sensor inputs and 5 actuator outputs in real-time.
Real Material Handling projects in Logistics & Warehousing face practical challenges including route optimization, traffic management, and integration with existing systems. Success requires balancing powerful for complex logic against steeper learning curve, while meeting 4-12 weeks project timelines typical for Material Handling implementations.
This guide provides step-by-step implementation guidance, complete working examples tested on AM600, practical design patterns, and real-world troubleshooting scenarios. You'll learn the pragmatic approaches that experienced integrators use to deliver reliable Material Handling systems on schedule and within budget.
Inovance InoProShop / AutoShop for Material Handling
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 Material Handling:
- 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 Material Handling 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 Material Handling systems, including Laser scanners, RFID readers, Barcode scanners.
Control Equipment for Material Handling:
- Automated storage and retrieval systems (AS/RS)
- Automated guided vehicles (AGVs/AMRs)
- Vertical lift modules (VLMs)
- Carousel systems (horizontal and vertical)
Inovance's controller families for Material Handling include:
- AM600: Suitable for intermediate to advanced Material Handling applications
- AM610: Suitable for intermediate to advanced Material Handling applications
- H5U: Suitable for intermediate to advanced Material Handling applications
- AC800: Suitable for intermediate to advanced Material Handling 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 Material Handling projects requiring advanced skill levels and 4-12 weeks development time, the total investment includes hardware, software licensing, training, and ongoing support.
Understanding Structured Text for Material Handling
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 Material Handling:
- Powerful for complex logic: Critical for Material Handling when handling intermediate to advanced control logic
- Excellent code reusability: Critical for Material Handling when handling intermediate to advanced control logic
- Compact code representation: Critical for Material Handling when handling intermediate to advanced control logic
- Good for algorithms and calculations: Critical for Material Handling when handling intermediate to advanced control logic
- Familiar to software developers: Critical for Material Handling when handling intermediate to advanced control logic
Why Structured Text Fits Material Handling:
Material Handling systems in Logistics & Warehousing typically involve:
- Sensors: Barcode scanners for product/location identification, RFID readers for pallet and container tracking, Photoelectric sensors for load presence detection
- Actuators: Conveyor motors and drives, Crane bridge, hoist, and trolley drives, Shuttle car drives
- Complexity: Intermediate to Advanced with challenges including Maintaining inventory accuracy in real-time
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 Material Handling
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 Material Handling using Inovance InoProShop / AutoShop.
Implementing Material Handling with Structured Text
Material handling automation uses PLCs to control the movement, storage, and retrieval of materials in warehouses, distribution centers, and manufacturing facilities. These systems optimize storage density, picking efficiency, and inventory accuracy.
This walkthrough demonstrates practical implementation using Inovance InoProShop / AutoShop and Structured Text programming.
System Requirements:
A typical Material Handling implementation includes:
Input Devices (Sensors):
1. Barcode scanners for product/location identification: Critical for monitoring system state
2. RFID readers for pallet and container tracking: Critical for monitoring system state
3. Photoelectric sensors for load presence detection: Critical for monitoring system state
4. Height and dimension sensors for load verification: Critical for monitoring system state
5. Position encoders for crane and shuttle systems: Critical for monitoring system state
Output Devices (Actuators):
1. Conveyor motors and drives: Primary control output
2. Crane bridge, hoist, and trolley drives: Supporting control function
3. Shuttle car drives: Supporting control function
4. Fork positioning and load handling: Supporting control function
5. Vertical lift mechanisms: Supporting control function
Control Equipment:
- Automated storage and retrieval systems (AS/RS)
- Automated guided vehicles (AGVs/AMRs)
- Vertical lift modules (VLMs)
- Carousel systems (horizontal and vertical)
Control Strategies for Material Handling:
1. Primary Control: Automated material movement using PLCs for warehouse automation, AGVs, and logistics systems.
2. Safety Interlocks: Preventing Route optimization
3. Error Recovery: Handling Traffic management
Implementation Steps:
Step 1: Map all storage locations with addressing scheme
In InoProShop / AutoShop, map all storage locations with addressing scheme.
Step 2: Define product characteristics (size, weight, handling requirements)
In InoProShop / AutoShop, define product characteristics (size, weight, handling requirements).
Step 3: Implement location tracking database interface
In InoProShop / AutoShop, implement location tracking database interface.
Step 4: Program crane/shuttle motion control with positioning
In InoProShop / AutoShop, program crane/shuttle motion control with positioning.
Step 5: Add load verification (presence, dimension, weight)
In InoProShop / AutoShop, add load verification (presence, dimension, weight).
Step 6: Implement WMS interface for task assignment
In InoProShop / AutoShop, implement wms interface for task assignment.
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 inventory accuracy in real-time
- Solution: Structured Text addresses this through Powerful for complex logic.
2. Handling damaged or misplaced loads
- Solution: Structured Text addresses this through Excellent code reusability.
3. Coordinating multiple cranes in same aisle
- Solution: Structured Text addresses this through Compact code representation.
4. Optimizing storage assignment dynamically
- Solution: Structured Text addresses this through Good for algorithms and calculations.
Safety Considerations:
- Aisle entry protection with light curtains and interlocks
- Personnel detection in automated zones
- Safe positioning for maintenance access
- Overload protection for cranes and lifts
- Fire suppression system integration
Performance Metrics:
- Scan Time: Optimize for 5 inputs and 5 outputs
- Memory Usage: Efficient data structures for AM600 capabilities
- Response Time: Meeting Logistics & Warehousing requirements for Material Handling
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 4-12 weeks development timeline while maintaining code quality.
Inovance Structured Text Example for Material Handling
Complete working example demonstrating Structured Text implementation for Material Handling using Inovance InoProShop / AutoShop. Follows Inovance naming conventions. Tested on AM600 hardware.
(* Inovance InoProShop / AutoShop - Material Handling Control *)
(* Structured Text Implementation for Logistics & Warehousing *)
(* On InoProShop projects, conventions follow CODESYS / IEC norms β Pasca *)
PROGRAM PRG_MATERIAL_HANDLING_Control
VAR
(* State Machine Variables *)
eState : E_MATERIAL_HANDLING_States := IDLE;
bEnable : BOOL := FALSE;
bFaultActive : BOOL := FALSE;
(* Timers *)
tonDebounce : TON;
tonProcessTimeout : TON;
tonFeedbackCheck : TON;
(* Counters *)
ctuCycleCounter : CTU;
(* Process Variables *)
rLaserscanners : REAL := 0.0;
rAGVmotors : REAL := 0.0;
rSetpoint : REAL := 100.0;
END_VAR
VAR CONSTANT
(* Logistics & Warehousing 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:
rAGVmotors := 0.0;
ctuCycleCounter(RESET := TRUE);
IF bEnable AND rLaserscanners > 0.0 THEN
eState := STARTING;
END_IF;
STARTING:
(* Ramp up output - Gradual start *)
rAGVmotors := MIN(rAGVmotors + 5.0, rSetpoint);
IF rAGVmotors >= rSetpoint THEN
eState := RUNNING;
END_IF;
RUNNING:
(* Material Handling active - Material handling automation uses PLCs to control *)
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:
rAGVmotors := 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:
rAGVmotors := 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
rAGVmotors := 0.0;
eState := FAULT;
bFaultActive := TRUE;
END_IF;
END_PROGRAMCode 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 Material Handling sequence control
- 2.Constants define Logistics & Warehousing-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 intermediate to advanced 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
- βMaterial Handling: Verify load presence before and after each move
- βMaterial Handling: Implement inventory checkpoints for reconciliation
- βMaterial Handling: Use location states to prevent double storage
- βDebug with InoProShop / AutoShop: Use InoProShop's online mode to set breakpoints in POUs and step throu
- βSafety: Aisle entry protection with light curtains and interlocks
- βUse InoProShop / AutoShop simulation tools to test Material Handling 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
- β Material Handling: Maintaining inventory accuracy in real-time
- β Material Handling: Handling damaged or misplaced loads
- β Neglecting to validate Barcode scanners for product/location identification leads to control errors
- β Insufficient comments make Structured Text programs unmaintainable over time
Related Certifications
Mastering Structured Text for Material Handling applications using Inovance InoProShop / AutoShop requires understanding both the platform's capabilities and the specific demands of Logistics & Warehousing. This guide has provided comprehensive coverage of implementation strategies, working code examples, best practices, and common pitfalls to help you succeed with intermediate to advanced Material Handling 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 Logistics & Warehousing applications where Material Handling 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 Material Handling systems that meet Logistics & Warehousing 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 Logistics & Warehousing applications
3. Hands-on Practice: Build Material Handling 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 4-12 weeks typical timeline for Material Handling projects will decrease as you gain experience with these patterns and techniques. Remember: Verify load presence before and after each move
For further learning, explore related topics including Recipe management, AGV systems, and Inovance platform-specific features for Material Handling optimization.