Implementing Structured Text for Safety Systems using Red Lion Controls Crimson 3.2 requires adherence to industry standards and proven best practices from Universal. This guide compiles best practices from successful Safety Systems deployments, Red Lion Controls programming standards, and Universal requirements to help you deliver professional-grade automation solutions.
Red Lion Controls's position as Niche - Panel builders, OEM machines, remote monitoring, rail and transport means their platforms must meet rigorous industry requirements. Companies like FlexEdge DA10D users in machine guarding and emergency stop systems have established proven patterns for Structured Text implementation that balance functionality, maintainability, and safety.
Best practices for Safety Systems encompass multiple dimensions: proper handling of 5 sensor types, safe control of 4 different actuators, managing safety integrity level (sil) compliance, and ensuring compliance with relevant industry standards. The Structured Text approach, when properly implemented, provides powerful for complex logic and excellent code reusability, both critical for advanced projects.
This guide presents industry-validated approaches to Red Lion Controls Structured Text programming for Safety Systems, covering code organization standards, documentation requirements, testing procedures, and maintenance best practices. You'll learn how leading companies structure their Safety Systems programs, handle error conditions, and ensure long-term reliability in production environments.
Red Lion Controls Crimson 3.2 for Safety 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 Safety 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 Safety 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 Safety Systems systems, including Safety light curtains, Emergency stop buttons, Safety door switches.
Control Equipment for Safety Systems:
- Safety PLCs (fail-safe controllers)
- Safety relays (configurable or fixed)
- Safety I/O modules with diagnostics
- Safety network protocols (PROFIsafe, CIP Safety)
Red Lion Controls's controller families for Safety Systems include:
- FlexEdge DA10D: Suitable for advanced Safety Systems applications
- FlexEdge DA30D: Suitable for advanced Safety Systems applications
- FlexEdge DA50D: Suitable for advanced Safety Systems applications
- Graphite HMI: Suitable for advanced Safety 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 Safety Systems projects requiring advanced skill levels and 4-8 weeks development time, the total investment includes hardware, software licensing, training, and ongoing support.
Understanding Structured Text for Safety 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 Safety Systems:
- Powerful for complex logic: Critical for Safety Systems when handling advanced control logic
- Excellent code reusability: Critical for Safety Systems when handling advanced control logic
- Compact code representation: Critical for Safety Systems when handling advanced control logic
- Good for algorithms and calculations: Critical for Safety Systems when handling advanced control logic
- Familiar to software developers: Critical for Safety Systems when handling advanced control logic
Why Structured Text Fits Safety Systems:
Safety Systems systems in Universal typically involve:
- Sensors: Emergency stop buttons (Category 0 or 1 stop), Safety light curtains (Type 2 or Type 4), Safety laser scanners for zone detection
- Actuators: Safety contactors (mirror contact type), Safe torque off (STO) drives, Safety brake modules
- Complexity: Advanced with challenges including Achieving required safety level with practical architecture
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 Safety 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 Safety Systems using Red Lion Controls Crimson 3.2.
Implementing Safety Systems with Structured Text
Safety system control uses safety-rated PLCs and components to protect personnel and equipment from hazardous conditions. These systems implement safety functions per IEC 62443 and ISO 13849 standards with redundancy and diagnostics.
This walkthrough demonstrates practical implementation using Red Lion Controls Crimson 3.2 and Structured Text programming.
System Requirements:
A typical Safety Systems implementation includes:
Input Devices (Sensors):
1. Emergency stop buttons (Category 0 or 1 stop): Critical for monitoring system state
2. Safety light curtains (Type 2 or Type 4): Critical for monitoring system state
3. Safety laser scanners for zone detection: Critical for monitoring system state
4. Safety interlock switches (tongue, hinged, trapped key): Critical for monitoring system state
5. Safety mats and edges: Critical for monitoring system state
Output Devices (Actuators):
1. Safety contactors (mirror contact type): Primary control output
2. Safe torque off (STO) drives: Supporting control function
3. Safety brake modules: Supporting control function
4. Lock-out valve manifolds: Supporting control function
5. Safety relay outputs: Supporting control function
Control Equipment:
- Safety PLCs (fail-safe controllers)
- Safety relays (configurable or fixed)
- Safety I/O modules with diagnostics
- Safety network protocols (PROFIsafe, CIP Safety)
Control Strategies for Safety Systems:
1. Primary Control: Safety-rated PLC programming for personnel protection, emergency stops, and safety interlocks per IEC 61508/61511.
2. Safety Interlocks: Preventing Safety integrity level (SIL) compliance
3. Error Recovery: Handling Redundancy requirements
Implementation Steps:
Step 1: Perform hazard analysis and risk assessment
In Crimson 3.2, perform hazard analysis and risk assessment.
Step 2: Determine required safety level (SIL/PL) for each function
In Crimson 3.2, determine required safety level (sil/pl) for each function.
Step 3: Select certified safety components meeting requirements
In Crimson 3.2, select certified safety components meeting requirements.
Step 4: Design safety circuit architecture per category requirements
In Crimson 3.2, design safety circuit architecture per category requirements.
Step 5: Implement safety logic in certified safety PLC/relay
In Crimson 3.2, implement safety logic in certified safety plc/relay.
Step 6: Add diagnostics and proof test provisions
In Crimson 3.2, add diagnostics and proof test provisions.
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. Achieving required safety level with practical architecture
- Solution: Structured Text addresses this through Powerful for complex logic.
2. Managing nuisance trips while maintaining safety
- Solution: Structured Text addresses this through Excellent code reusability.
3. Integrating safety with production efficiency
- Solution: Structured Text addresses this through Compact code representation.
4. Documenting compliance with multiple standards
- Solution: Structured Text addresses this through Good for algorithms and calculations.
Safety Considerations:
- Use only certified safety components and PLCs
- Implement dual-channel monitoring per category requirements
- Add diagnostic coverage to detect latent faults
- Design for fail-safe operation (de-energize to trip)
- Provide regular proof testing of safety functions
Performance Metrics:
- Scan Time: Optimize for 5 inputs and 4 outputs
- Memory Usage: Efficient data structures for FlexEdge DA10D capabilities
- Response Time: Meeting Universal requirements for Safety 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 4-8 weeks development timeline while maintaining code quality.
Red Lion Controls Structured Text Example for Safety Systems
Complete working example demonstrating Structured Text implementation for Safety 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 - Safety Systems Control *)
(* Structured Text Implementation for Universal *)
(* Red Lion projects use Crimson's tag database with typed tags and descr *)
PROGRAM PRG_SAFETY_SYSTEMS_Control
VAR
(* State Machine Variables *)
eState : E_SAFETY_SYSTEMS_States := IDLE;
bEnable : BOOL := FALSE;
bFaultActive : BOOL := FALSE;
(* Timers *)
tonDebounce : TON;
tonProcessTimeout : TON;
tonFeedbackCheck : TON;
(* Counters *)
ctuCycleCounter : CTU;
(* Process Variables *)
rSafetylightcurtains : REAL := 0.0;
rSafetyrelays : REAL := 0.0;
rSetpoint : REAL := 100.0;
END_VAR
VAR CONSTANT
(* Universal 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:
rSafetyrelays := 0.0;
ctuCycleCounter(RESET := TRUE);
IF bEnable AND rSafetylightcurtains > 0.0 THEN
eState := STARTING;
END_IF;
STARTING:
(* Ramp up output - Gradual start *)
rSafetyrelays := MIN(rSafetyrelays + 5.0, rSetpoint);
IF rSafetyrelays >= rSetpoint THEN
eState := RUNNING;
END_IF;
RUNNING:
(* Safety Systems active - Safety system control uses safety-rated PLCs and c *)
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:
rSafetyrelays := 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:
rSafetyrelays := 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
rSafetyrelays := 0.0;
eState := FAULT;
bFaultActive := TRUE;
END_IF;
END_PROGRAMCode 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 Safety Systems sequence control
- 2.Constants define Universal-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 advanced 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
- ✓Safety Systems: Keep safety logic simple and auditable
- ✓Safety Systems: Use certified function blocks from safety PLC vendor
- ✓Safety Systems: Implement cross-monitoring between channels
- ✓Debug with Crimson 3.2: Use Crimson 3.2's simulation mode to test HMI and logic before deployi
- ✓Safety: Use only certified safety components and PLCs
- ✓Use Crimson 3.2 simulation tools to test Safety 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
- ⚠Safety Systems: Achieving required safety level with practical architecture
- ⚠Safety Systems: Managing nuisance trips while maintaining safety
- ⚠Neglecting to validate Emergency stop buttons (Category 0 or 1 stop) leads to control errors
- ⚠Insufficient comments make Structured Text programs unmaintainable over time
Related Certifications
Mastering Structured Text for Safety Systems applications using Red Lion Controls Crimson 3.2 requires understanding both the platform's capabilities and the specific demands of Universal. This guide has provided comprehensive coverage of implementation strategies, working code examples, best practices, and common pitfalls to help you succeed with advanced Safety 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 Universal applications where Safety 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 Safety Systems systems that meet Universal 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 Universal applications
3. Hands-on Practice: Build Safety 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 4-8 weeks typical timeline for Safety Systems projects will decrease as you gain experience with these patterns and techniques. Remember: Keep safety logic simple and auditable
For further learning, explore related topics including Recipe management, Emergency stop systems, and Red Lion Controls platform-specific features for Safety Systems optimization.