PLC Programming.io
Learn PLCs free
Advanced25 min readUniversal

Eaton Structured Text for Safety Systems

Learn Structured Text programming for Safety Systems using Eaton XSoft-CoDeSys-3 / easySoft. Includes code examples, best practices, and step-by-step implementation guide for Universal applications.

💻
Platform
XSoft-CoDeSys-3 / easySoft
📊
Complexity
Advanced
⏱️
Project Duration
4-8 weeks

Optimizing Structured Text for Safety Systems applications in Eaton's XSoft-CoDeSys-3 / easySoft requires measuring the baseline and understanding the demands of Universal. This guide focuses on techniques you can evaluate with task timing, scan-time traces, memory use, and controlled fault tests.

For advanced applications like Safety Systems, check which diagnostics and profiling tools are available in your installed XSoft-CoDeSys-3 / easySoft version. Controller model, firmware, task configuration, communications, and I/O update behavior can all affect the result.

Performance considerations for Safety Systems systems extend beyond basic functionality. Critical factors include 5 sensor types, 4 actuators, communications load, and the need to handle safety integrity level (sil) compliance. Evaluate whether powerful for complex logic helps the design, then measure the actual task and I/O timing on the selected configuration.

This guide covers memory management, execution order, Structured Text-specific tuning, and a repeatable measurement plan for Safety Systems applications. Treat every optimization as a hypothesis: record the baseline, change one variable, retest the same workload, and keep the change only when the measured result and code maintainability both improve.

Eaton XSoft-CoDeSys-3 / easySoft for Safety Systems

XSoft-CoDeSys-3 / easySoft is a programming environment associated with Eaton controller families such as easyE4, XC-100, XC-152. This guide uses Structured Text 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 Structured Text constructs

  • The project version matches the installed XSoft-CoDeSys-3 / easySoft 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:

  • easyE4: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

  • XC-100: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

  • XC-152: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

  • XC-202: Confirm CPU, I/O, memory, communications, and Structured Text 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 Eaton 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 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 Eaton XSoft-CoDeSys-3 / easySoft.

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 Eaton XSoft-CoDeSys-3 / easySoft 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 XSoft-CoDeSys-3 / easySoft, perform hazard analysis and risk assessment.

Step 2: Determine required safety level (SIL/PL) for each function

In XSoft-CoDeSys-3 / easySoft, determine required safety level (sil/pl) for each function.

Step 3: Select certified safety components meeting requirements

In XSoft-CoDeSys-3 / easySoft, select certified safety components meeting requirements.

Step 4: Design safety circuit architecture per category requirements

In XSoft-CoDeSys-3 / easySoft, design safety circuit architecture per category requirements.

Step 5: Implement safety logic in certified safety PLC/relay

In XSoft-CoDeSys-3 / easySoft, implement safety logic in certified safety plc/relay.

Step 6: Add diagnostics and proof test provisions

In XSoft-CoDeSys-3 / easySoft, add diagnostics and proof test provisions.


Eaton Function Design:

Eaton projects typically build atop Codesys's standard FB libraries (timers, counters, PID, motion) plus Eaton-specific libraries for SmartWire-DT device control and easyE4 smart-relay integration. OEMs often maintain private function-block libraries for their machine families. Code reuse practices mirror mainstream Codesys conventions; OOP extensions are available but not heavily adopted.

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:

  • 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

Eaton Diagnostic Tools:

XSoft-CoDeSys-3 integrated debugger with breakpoints, watch, and trace,easySoft project simulator for easyE4 logic development without hardware,CoDeSys trace buffer — capture variable histories during live operation,XSoft-CoDeSys-3 network analyzer for EtherCAT and PROFINET fieldbus diagnostics,Online parameter comparison between development PC and running controller,easyE4 webserver interface — remote status view from any browser,SmartWire-DT diagnostics for Eaton's own device-level network,Modbus TCP protocol analyzer built into XSoft-CoDeSys-3,Controller self-diagnostics via LED codes (standard Codesys behaviour),Eaton Automation Portal online documentation and firmware archive

Use the monitoring and diagnostic functions available in your XSoft-CoDeSys-3 / easySoft version, and record the software, firmware, hardware, workload, and test procedure with every result.

Eaton Structured Text Example for Safety Systems

Illustrative Structured Text example for Safety Systems using Eaton terminology. Adapt the syntax to your XSoft-CoDeSys-3 / easySoft release, compile it, and verify it in an isolated test environment before use on equipment.

(* Eaton XSoft-CoDeSys-3 / easySoft - Safety Systems Control *)
(* Structured Text Implementation for Universal *)
(* Eaton Codesys projects follow IEC 61131-3 conventions — camelCase for  *)

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; (* Illustrative value; replace with a reviewed requirement *)
END_VAR

VAR CONSTANT
    (* Universal Process Parameters *)
    C_DEBOUNCE_TIME : TIME := T#500MS;
    C_PROCESS_TIMEOUT : TIME := T#30S; (* Illustrative value; verify for the process *)
    C_BATCH_SIZE : INT := 50; (* Illustrative value; replace with a reviewed requirement *)
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 on Eaton controllers are  *)
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 patterns range from simple CSV append via Codesys file-IO FBs to networked SQL writes via OPC UA or MQTT. The easyE4 webserver provides basic data-export functionality for small-scale monitoring. For serious logging, XC-303 controllers with SD-card storage and SCADA integration are typical. *)
        eState := IDLE;

    FAULT:
        rSafetyrelays := 0.0;
        (* Alarm handling on XC-series controllers typically uses custom FB-based alarm managers that write timestamped events to a buffer, with optional logging to SD card or networked databases. For easyE4, alarm-like behaviour is implemented by setting output bits tied to HMI indicators or SMS-notification via the optional WiFi/cellular module. Engineers wanting richer alarm handling typically move to XC. *)
        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_PROGRAM

Code Explanation:

  • 1.Enumerated state machine (State machines on Eaton controllers are most commonly implemented as CASE-of-INT in ST with named state constants, or via CFC (Continuous Function Chart) for visual representation. For complex sequencing, IEC SFC is supported. easyE4 applications rarely implement full state machines; they use block-level logic for simpler sequencing patterns.) for clear Safety Systems sequence control
  • 2.Constants use clearly marked illustrative values that must be replaced with reviewed project requirements
  • 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 flags a possible stuck condition for investigation
  • 6.The final override illustrates a software permissive only; it is not a safety-rated function and must not replace a validated safety system

Best Practices

  • ✓Follow Eaton naming conventions: Eaton Codesys projects follow IEC 61131-3 conventions — camelCase for variables,
  • ✓Eaton function design: Eaton projects typically build atop Codesys's standard FB libraries (timers, cou
  • ✓Data organization: Codesys-based Eaton projects use IEC 61131-3 global variable lists and PROGRAM V
  • ✓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 XSoft-CoDeSys-3 / easySoft: Use XSoft-CoDeSys-3 online monitoring with trace buffers rather than p
  • ✓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

  • ⚠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
  • ⚠Eaton common error: Codesys V3 vs V2 project incompatibility for engineers migrating from legacy Moe
  • ⚠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

🏆Eaton Automation Certified Specialist
🏆Codesys-based programming certifications
🏆Advanced Eaton Programming Certification

Applying Structured Text to Safety Systems using Eaton XSoft-CoDeSys-3 / easySoft 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 XSoft-CoDeSys-3 / easySoft 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

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...

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 Recipe management, Emergency stop systems, and Eaton platform-specific features for Safety Systems optimization.