Red Lion Controls Sequential Function Charts (SFC) for Safety Systems: Complete Programming Guide

Troubleshooting Sequential Function Charts (SFC) programs for Safety Systems in Red Lion Controls's Crimson 3.2 benefits from a systematic diagnostic process and a clear understanding of likely failure modes. This guide provides a repeatable path from observed symptom to evidence, hypothesis, controlled test, and documented correction.

Start by recording the controller model, firmware, Crimson 3.2 version, task state, active faults, I/O status, and the exact conditions that reproduce the problem. Preserve the original project and collect diagnostic evidence before changing logic.

Common challenges in Safety Systems systems include safety integrity level (sil) compliance, redundancy requirements, and safety circuit design. When implemented with Sequential Function Charts (SFC), additional considerations include limited to sequential operations, requiring specific diagnostic approaches. Red Lion Controls's diagnostic tools in Crimson 3.2 provide powerful capabilities, but knowing exactly which tools to use for specific symptoms dramatically improves troubleshooting efficiency.

This guide walks through systematic troubleshooting procedures, from initial symptom analysis through root-cause verification and corrective-action testing. It explains how to use relevant Crimson 3.2 diagnostic features and interpret system behavior in a Safety Systems context without assuming that one symptom always has the same cause.

Red Lion Controls Crimson 3.2 for Safety Systems

Crimson 3.2 is a programming environment associated with Red Lion Controls controller families such as FlexEdge DA10D, FlexEdge DA30D, FlexEdge DA50D. This guide uses Sequential Function Charts (SFC) terminology from the supplied guide dataset, but controller capabilities and language support can change by model, firmware, software edition, and license.

Verify Before You Start:

The selected controller supports the required Sequential Function Charts (SFC) constructs

The project version matches the installed Crimson 3.2 release

Required communications, motion, safety, and simulation options are licensed

Firmware and device-description files are compatible with the project

The vendor manuals used for the design match the exact hardware revision

Application Planning:

For a Safety Systems exercise, map the required inputs and outputs before writing logic. The example considers 5 sensor types, including Safety light curtains, Emergency stop buttons, Safety door switches, and 4 actuator types.

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)

Controller-family references used in this guide include:

FlexEdge DA10D: Confirm CPU, I/O, memory, communications, and Sequential Function Charts (SFC) support in the current selection guide

FlexEdge DA30D: Confirm CPU, I/O, memory, communications, and Sequential Function Charts (SFC) support in the current selection guide

FlexEdge DA50D: Confirm CPU, I/O, memory, communications, and Sequential Function Charts (SFC) support in the current selection guide

Graphite HMI: Confirm CPU, I/O, memory, communications, and Sequential Function Charts (SFC) support in the current selection guide

Hardware Selection Checklist:

Count local and remote I/O, including planned expansion

Measure the required task and communications update rates

Identify memory, data-retention, diagnostics, and cybersecurity requirements

Treat safety functions as a separate, standards-led design activity

Confirm lifecycle status, regional availability, licensing, and support

Source and Validation Note:

This page does not represent a vendor certification or a hardware acceptance test. Use current Red Lion Controls manuals, release notes, and safety documentation as the authority for product-specific behavior. Validate adapted logic in a simulator or isolated test setup before connecting it to equipment.

Investment Considerations:

For Safety Systems projects, compare hardware, software licensing, training, engineering, test equipment, commissioning, spares, and ongoing support. Obtain current pricing and lifecycle information directly from the vendor or an authorized regional supplier.

Understanding Sequential Function Charts (SFC) for Safety Systems

Sequential Function Chart (SFC) is a graphical language for programming sequential processes. It models systems as a series of steps connected by transitions, ideal for batch processes and machine sequences.

Execution Model:

Only active steps execute their actions. Transitions define conditions for moving between steps. Multiple steps can be active simultaneously in parallel branches.

Core Advantages for Safety Systems:

Perfect for sequential processes: Critical for Safety Systems when handling advanced control logic

Clear visualization of process flow: Critical for Safety Systems when handling advanced control logic

Easy to understand process steps: Critical for Safety Systems when handling advanced control logic

Good for batch operations: Critical for Safety Systems when handling advanced control logic

Simplifies complex sequences: Critical for Safety Systems when handling advanced control logic

Why Sequential Function Charts (SFC) 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 Sequential Function Charts (SFC):

Steps:
- initialStep: Double-bordered box - starting point of sequence, active on program start
- normalStep: Single-bordered box - becomes active when preceding transition fires
- actions: Associated code that executes while step is active

Transitions:
- condition: Boolean expression that must be TRUE to advance
- firing: Transition fires when preceding step is active AND condition is TRUE
- priority: In selective branches, transitions are evaluated in defined order

ActionQualifiers:
- N: Non-stored - executes while step is active
- S: Set - sets output TRUE on step entry, remains TRUE
- R: Reset - sets output FALSE on step entry

Best Practices for Sequential Function Charts (SFC):

Start with a clear process flow diagram before implementing SFC

Use descriptive step names indicating what happens (e.g., Filling, Heating)

Keep transition conditions simple - complex logic goes in action code

Implement timeout transitions to prevent stuck sequences

Always provide a path back to initial step for reset/restart

Common Mistakes to Avoid:

Forgetting to include stop/abort transitions for emergency handling

Creating deadlocks where no transition can fire

Not handling the case where transition conditions never become TRUE

Using S (Set) actions without corresponding R (Reset) actions

Typical Applications:

1. Bottle filling: Directly applicable to Safety Systems
2. Assembly sequences: Related control patterns
3. Material handling: Related control patterns
4. Batch mixing: Related control patterns

Understanding these fundamentals prepares you to implement effective Sequential Function Charts (SFC) solutions for Safety Systems using Red Lion Controls Crimson 3.2.

Implementing Safety Systems with Sequential Function Charts (SFC)

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 Sequential Function Charts (SFC) 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: Sequential Function Charts (SFC) addresses this through Perfect for sequential processes.

2. Managing nuisance trips while maintaining safety

Solution: Sequential Function Charts (SFC) addresses this through Clear visualization of process flow.

3. Integrating safety with production efficiency

Solution: Sequential Function Charts (SFC) addresses this through Easy to understand process steps.

4. Documenting compliance with multiple standards

Solution: Sequential Function Charts (SFC) addresses this through Good for batch operations.

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:

Task and I/O timing: Record minimum, average, and maximum values under a defined test load

Accuracy: Define an acceptable tolerance and compare it with calibrated reference measurements

Throughput: Count completed cycles over a fixed interval and record rejected or incomplete cycles

Fault response: Measure detection, safe-state, alarm, and recovery behavior for each test case

Resource use: Record memory, communications load, and diagnostic-buffer behavior

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

Use the monitoring and diagnostic functions available in your Crimson 3.2 version, and record the software, firmware, hardware, workload, and test procedure with every result.

Red Lion Controls Sequential Function Charts (SFC) Example for Safety Systems

Illustrative Sequential Function Charts (SFC) example for Safety Systems using Red Lion Controls terminology. Adapt the syntax to your Crimson 3.2 release, compile it, and verify it in an isolated test environment before use on equipment.

// Red Lion Controls Crimson 3.2 - Safety Systems Control
// Sequential Function Charts (SFC) Implementation for Universal
// Red Lion projects use Crimson's tag database with typed tags

// ============================================
// Variable Declarations
// ============================================
VAR
    bEnable : BOOL := FALSE;
    bEmergencyStop : BOOL := FALSE;
    rSafetylightcurtains : REAL;
    rSafetyrelays : REAL;
END_VAR

// ============================================
// Input Conditioning - Emergency stop buttons (Category 0 or 1 stop)
// ============================================
// Standard input processing
IF rSafetylightcurtains > 0.0 THEN
    bEnable := TRUE;
END_IF;

// ============================================
// Safety Interlock - Use only certified safety components and PLCs
// ============================================
IF bEmergencyStop THEN
    rSafetyrelays := 0.0;
    bEnable := FALSE;
END_IF;

// ============================================
// Main Safety Systems Control Logic
// ============================================
IF bEnable AND NOT bEmergencyStop THEN
    // Safety system control uses safety-rated PLCs and components 
    rSafetyrelays := rSafetylightcurtains * 1.0; (* Illustrative scaling only *)

    // Process monitoring
    // Add specific control logic here
ELSE
    rSafetyrelays := 0.0;
END_IF;

Code Explanation:

1.Sequential Function Charts (SFC) structure organized for a Safety Systems training example
2.Input conditioning handles Emergency stop buttons (Category 0 or 1 stop) signals
3.Safety interlock ensures Use only certified safety components and PLCs always takes priority
4.Main control implements Safety system control uses safety-rated
5.Adapt the scan-cycle assumptions to the selected FlexEdge DA10D task configuration and verify them by measurement

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
✓Sequential Function Charts (SFC): Start with a clear process flow diagram before implementing SFC
✓Sequential Function Charts (SFC): Use descriptive step names indicating what happens (e.g., Filling, Heating)
✓Sequential Function Charts (SFC): Keep transition conditions simple - complex logic goes in action code
✓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 a compatible simulator or isolated test rig to test Safety Systems logic before deployment

Common Pitfalls to Avoid

⚠Sequential Function Charts (SFC): Forgetting to include stop/abort transitions for emergency handling
⚠Sequential Function Charts (SFC): Creating deadlocks where no transition can fire
⚠Sequential Function Charts (SFC): Not handling the case where transition conditions never become TRUE
⚠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 Sequential Function Charts (SFC) programs unmaintainable over time

Related Certifications

🏆Red Lion Crimson Certified Engineer

🏆Red Lion Specialist Training

Applying Sequential Function Charts (SFC) to Safety Systems using Red Lion Controls Crimson 3.2 requires understanding the platform, the process, and the project's acceptance criteria. This guide has covered implementation structure, an illustrative code example, verification practices, and common pitfalls for a advanced Safety Systems exercise.

Use the practices outlined here to create a design that can be reviewed and tested. Define performance targets in the project requirements and confirm them with repeatable measurements.

Next Steps:

1. Check Sources: Read the current Crimson 3.2 help, controller manual, release notes, and relevant standards
2. Practice Safely: Adapt the example in a simulator or isolated training setup
3. Review: Have the I/O map, state behavior, faults, and recovery steps reviewed
4. Test: Record normal, boundary, fault, restart, and communications test results

Sequential Function Charts (SFC) Foundation:

Sequential Function Chart (SFC) is a graphical language for programming sequential processes. It models systems as a series of steps connected by tran...

Project duration depends on scope, reviews, hardware availability, software and firmware versions, testing, commissioning, and site constraints. Remember: Keep safety logic simple and auditable

For further learning, explore related topics including Assembly sequences, Emergency stop systems, and Red Lion Controls platform-specific features for Safety Systems optimization.