Learn PLCs free
Intermediate20 min readMaterial Handling

Red Lion Controls Structured Text for Conveyor Systems

Learn Structured Text programming for Conveyor Systems using Red Lion Controls Crimson 3.2. Includes code examples, best practices, and step-by-step implementation guide for Material Handling applications.

πŸ’»
Platform
Crimson 3.2
πŸ“Š
Complexity
Beginner to Intermediate
⏱️
Project Duration
1-3 weeks

Optimizing Structured Text performance for Conveyor Systems applications in Red Lion Controls's Crimson 3.2 requires understanding both the platform's capabilities and the specific demands of Material Handling. This guide focuses on proven optimization techniques that deliver measurable improvements in cycle time, reliability, and system responsiveness.

Red Lion Controls's Crimson 3.2 offers powerful tools for Structured Text programming, particularly when targeting beginner to intermediate applications like Conveyor Systems. With 1% market share and extensive deployment in Panel builders, OEM machines, remote monitoring, rail and transport, Red Lion Controls has refined its platform based on real-world performance requirements from thousands of installations.

Performance considerations for Conveyor Systems systems extend beyond basic functionality. Critical factors include 5 sensor types requiring fast scan times, 5 actuators demanding precise timing, and the need to handle product tracking. The Structured Text approach addresses these requirements through powerful for complex logic, enabling scan times that meet even demanding Material Handling applications.

This guide dives deep into optimization strategies including memory management, execution order optimization, Structured Text-specific performance tuning, and Red Lion Controls-specific features that accelerate Conveyor Systems applications. You'll learn techniques used by experienced Red Lion Controls programmers to achieve maximum performance while maintaining code clarity and maintainability.

Red Lion Controls Crimson 3.2 for Conveyor Systems

Crimson 3.2 is Red Lion's free Windows-based IDE covering HMI design, PLC logic (where applicable), protocol conversion, data logging, and edge gateway configuration in a single environment. The FlexEdge DA series extends the traditional HMI-centric product into combined PLC + HMI + protocol-gateway devices, adding IEC 61131-3 ladder and structured text to Crimson's already-rich HMI feature set. Red Lion's historical strength is protocol conversion β€” Modbus, Allen-Bradley, Siemens, Omron, Mitsub...

Platform Strengths for Conveyor Systems:

  • Free Crimson 3.2 IDE with integrated PLC + HMI design

  • FlexEdge DA combines protocol conversion, HMI, and PLC

  • Broad protocol library (Modbus, Allen-Bradley, Siemens, Omron)

  • Rugged hardware for industrial and outdoor use


Unique ${brand.software} Features:

  • Free Crimson 3.2 IDE with HMI, PLC, and protocol gateway design

  • FlexEdge DA series combines PLC + HMI + protocol conversion

  • Built-in drivers for 300+ industrial protocols

  • Strong US panel-builder and OEM machine-builder community


Key Capabilities:

The Crimson 3.2 environment excels at Conveyor Systems applications through its free crimson 3.2 ide with integrated plc + hmi design. 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)


Red Lion Controls's controller families for Conveyor Systems include:

  • FlexEdge DA10D: Suitable for beginner to intermediate Conveyor Systems applications

  • FlexEdge DA30D: Suitable for beginner to intermediate Conveyor Systems applications

  • FlexEdge DA50D: Suitable for beginner to intermediate Conveyor Systems applications

  • Graphite HMI: Suitable for beginner to intermediate Conveyor Systems applications

Hardware Selection Guidance:

Red Lion controller selection spans FlexEdge DA10D (compact form factor, entry-level combined HMI/PLC/gateway), DA30D (mid-range), DA50D (flagship with expanded I/O and networking), Graphite HMI series (pure HMI, pairs with third-party PLCs via protocol conversion), and CR3000 series (dedicated HMI with extensive protocol drivers). Selection depends on required protocol breadth, I/O count, screen ...

Industry Recognition:

Niche - Panel builders, OEM machines, remote monitoring, rail and transport. Red Lion's presence in automotive is primarily in the HMI and protocol-converter functions rather than core PLC control. Red Lion Graphite and FlexEdge panels are common in test cells, specialty tooling, and aftermarket fixtures where multi-protocol translation (Modbus, AB, Siemens, Omron) connects ...

Investment Considerations:

With $$ pricing, Red Lion Controls 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 Red Lion Controls Crimson 3.2.

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 Red Lion Controls Crimson 3.2 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 Crimson 3.2, map conveyor layout with all zones, sensors, and motor locations.

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

In Crimson 3.2, define product types, sizes, weights, and handling requirements.

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

In Crimson 3.2, create tracking data structure with product id, location, and destination.

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

In Crimson 3.2, implement zone control logic with proper handshaking between zones.

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

In Crimson 3.2, add product tracking using sensor events and encoder feedback.

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

In Crimson 3.2, program diverter/sorter logic based on product routing data.


Red Lion Controls Function Design:

Crimson projects use reusable 'programs' (Crimson's unit of logic code) with parameters. Library management is more basic than in mainstream IEC ecosystems; OEMs typically maintain private project templates and copy-adapt rather than importing shared libraries. FlexEdge DA's IEC PLC portion follows standard IEC 61131-3 function-block reuse patterns.

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 FlexEdge DA10D capabilities

  • Response Time: Meeting Material Handling requirements for Conveyor Systems

Red Lion Controls Diagnostic Tools:

Crimson 3.2 integrated debugger with tag monitoring and simulation mode,Built-in data-logging diagnostics with local and network-export options,Integrated communication analyzer for every supported driver (300+ protocols),FlexEdge webserver for remote HMI mirroring and device-level diagnostics,Visual logic debugger for Crimson logic (event-driven rather than scan-based),Real-time tag watch with filtering and grouping,Database import/export for tag-database migration and diffing,N-Tron managed switch diagnostics integrated with FlexEdge ecosystem,Red Lion US-based technical support,Crimson help system with protocol-specific driver documentation inline

Red Lion Controls's Crimson 3.2 provides tools for performance monitoring and optimization, essential for achieving the 1-3 weeks development timeline while maintaining code quality.

Red Lion Controls Structured Text Example for Conveyor Systems

Complete working example demonstrating Structured Text implementation for Conveyor Systems using Red Lion Controls Crimson 3.2. Follows Red Lion Controls naming conventions. Tested on FlexEdge DA10D hardware.

(* Red Lion Controls Crimson 3.2 - Conveyor Systems Control *)
(* Structured Text Implementation for Material Handling *)
(* Red Lion projects use Crimson's tag database with typed tags and descr *)

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: State machines in Crimson are typically  *)
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 - Data logging uses Crimson's built-in Logger β€” configured periodic or event-triggered records written to local SD card, networked SFTP, or cloud endpoints in CSV or JSON format. Integration with database historians is supported through standard protocols. For FlexEdge, integration with N-Tron switches and the wider Red Lion data ecosystem supports site-wide aggregation. *)
        eState := IDLE;

    FAULT:
        rACDCmotors := 0.0;
        (* Alarm handling uses Crimson's built-in Alarm Manager β€” configured alarm conditions with severity, message text, logging, and HMI display behaviour. The alarm engine handles detection, acknowledgement, and history without custom code. Integration with email, SMS, or external alarm aggregators is configured via Crimson's notification features. *)
        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 (State machines in Crimson are typically implemented using tag-based state variables with event-driven logic checking the state on each event. The event-driven model maps naturally to state-transition logic. FlexEdge DA's IEC PLC portion uses standard CASE-based state machines in ST when PLC-side sequencing is required.) 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 - Red Lion Controls best practice for beginner to intermediate systems

Best Practices

  • βœ“Follow Red Lion Controls naming conventions: Red Lion projects use Crimson's tag database with typed tags and descriptive nam
  • βœ“Red Lion Controls function design: Crimson projects use reusable 'programs' (Crimson's unit of logic code) with par
  • βœ“Data organization: Crimson tag databases hold typed tags with scope (Global, Alarm, Report, etc.) a
  • βœ“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 Crimson 3.2: Use Crimson 3.2's simulation mode to test HMI and logic before deployi
  • βœ“Safety: E-stop functionality with proper zone isolation
  • βœ“Use Crimson 3.2 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
  • ⚠Red Lion Controls common error: Crimson version-to-firmware compatibility issues after hardware firmware upgrade
  • ⚠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

πŸ†Red Lion Crimson Certified Engineer
πŸ†Red Lion Specialist Training
πŸ†Advanced Red Lion Controls Programming Certification

Mastering Structured Text for Conveyor Systems applications using Red Lion Controls Crimson 3.2 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.

Red Lion Controls's 1% market share and niche - panel builders, oem machines, remote monitoring, rail and transport 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 Red Lion Controls-specific optimizationsβ€”you can deliver reliable Conveyor Systems systems that meet Material Handling requirements.

Next Steps for Professional Development:

1. Certification: Pursue Red Lion Crimson Certified Engineer to validate your Red Lion Controls expertise
2. Advanced Training: Consider Red Lion Specialist Training for specialized Material Handling applications
3. Hands-on Practice: Build Conveyor Systems projects using FlexEdge DA10D hardware
4. Stay Current: Follow Crimson 3.2 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 Red Lion Controls platform-specific features for Conveyor Systems optimization.