Unitronics Structured Text for Safety Systems: Complete Programming Guide

Mastering advanced Structured Text techniques for Safety Systems in Unitronics's VisiLogic / UniLogic unlocks capabilities beyond basic implementations. This guide explores sophisticated programming patterns, optimization strategies, and advanced features that separate expert Unitronics programmers from intermediate practitioners in Universal applications.

Unitronics's VisiLogic / UniLogic contains powerful advanced features that many programmers never fully utilize. With 1% market share and deployment in demanding applications like machine guarding and emergency stop systems, Unitronics has developed advanced capabilities specifically for advanced projects requiring powerful for complex logic and excellent code reusability.

Advanced Safety Systems implementations leverage sophisticated techniques including multi-sensor fusion algorithms, coordinated multi-actuator control, and intelligent handling of safety integrity level (sil) compliance. When implemented using Structured Text, these capabilities are achieved through complex calculations patterns that exploit Unitronics-specific optimizations.

This guide reveals advanced programming techniques used by expert Unitronics programmers, including custom function blocks, optimized data structures, advanced Structured Text patterns, and VisiLogic / UniLogic-specific features that deliver superior performance. You'll learn implementation strategies that go beyond standard documentation, based on years of practical experience with Safety Systems systems in production Universal environments.

Unitronics VisiLogic / UniLogic for Safety Systems

Unitronics takes a distinctive approach to PLC programming: every controller ships with an integrated colour touchscreen HMI, and the development tool handles PLC logic and HMI design in a single workspace. VisiLogic is the legacy tool for the Vision, Samba, and Jazz product families; UniLogic is the current-generation environment for the UniStream line. Both are free to download and include a complete built-in simulator covering PLC logic, HMI screens, alarms, recipes, and data tables — the sim...

Platform Strengths for Safety Systems:

Combined PLC + HMI in one unit reduces panel cost

Free VisiLogic and UniLogic IDEs

Built-in simulator with both PLC and HMI simulation

Strong US small-integrator community

Unique ${brand.software} Features:

Combined PLC + HMI in one unit across Jazz, Samba, Vision, and UniStream

Free VisiLogic (legacy) and UniLogic (current) IDEs

Built-in simulator covering PLC logic, HMI, alarms, data tables, and recipes

Integrated data sampling and trend logging without separate SCADA

Key Capabilities:

The VisiLogic / UniLogic environment excels at Safety Systems applications through its combined plc + hmi in one unit reduces panel cost. 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)

Unitronics's controller families for Safety Systems include:

Jazz 2: Suitable for advanced Safety Systems applications

Samba 7": Suitable for advanced Safety Systems applications

Vision V350: Suitable for advanced Safety Systems applications

Vision V570: Suitable for advanced Safety Systems applications

Hardware Selection Guidance:

CPU selection across Unitronics ranges from the Jazz 2 micro series (tiny applications, basic motor control, simple process monitoring with 10-20 I/O) through Samba 7" (small machine control with touchscreen HMI), Vision V350/V570 (medium machinery with larger HMI), and UniStream 7" / 15.6" (flagship combined PLC+HMI for mid-to-high complexity applications with advanced features like UniCloud, cel...

Industry Recognition:

Moderate - US small-integrator market, OEM machines, building automation. Unitronics' combined PLC+HMI controllers are uncommon in high-volume automotive manufacturing but appear in automotive tier-2 and tier-3 supplier shops, single-machine workcells, and after-market test fixtures. The cost advantage and single-unit PLC+HMI approach makes Unitronics attractive for small...

Investment Considerations:

With $$ pricing, Unitronics 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 Unitronics VisiLogic / UniLogic.

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 Unitronics VisiLogic / UniLogic 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 VisiLogic / UniLogic, perform hazard analysis and risk assessment.

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

In VisiLogic / UniLogic, determine required safety level (sil/pl) for each function.

Step 3: Select certified safety components meeting requirements

In VisiLogic / UniLogic, select certified safety components meeting requirements.

Step 4: Design safety circuit architecture per category requirements

In VisiLogic / UniLogic, design safety circuit architecture per category requirements.

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

In VisiLogic / UniLogic, implement safety logic in certified safety plc/relay.

Step 6: Add diagnostics and proof test provisions

In VisiLogic / UniLogic, add diagnostics and proof test provisions.

Unitronics Function Design:

Function block design in Unitronics uses user-defined FBs in UniLogic (more limited in VisiLogic). Extensive vendor-provided helper FBs cover common tasks (PID, motion, communication, HMI utilities). OEM machine builders typically maintain private FB libraries for their common machine patterns, though code reuse is less mature than in mainstream PLC ecosystems.

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 Jazz 2 capabilities

Response Time: Meeting Universal requirements for Safety Systems

Unitronics Diagnostic Tools:

UniLogic (current) and VisiLogic (legacy) integrated debuggers with breakpoints,Built-in simulator covering PLC logic, HMI screens, alarms, recipes, and data tables,Web visualisation for UniStream — remote HMI viewing without additional software,SD card logging with PC-side export tools for offline trend analysis,Modbus RTU/TCP transaction logging built into the IDE,Controller status monitor — CPU load, scan time, memory usage,HMI event logger capturing operator actions for audit purposes,CAN bus diagnostic tools for CANopen-equipped models,Remote support tool — Unitronics' own screen-sharing for technical support,User community forum with active troubleshooting discussions

Unitronics's VisiLogic / UniLogic provides tools for performance monitoring and optimization, essential for achieving the 4-8 weeks development timeline while maintaining code quality.

Unitronics Structured Text Example for Safety Systems

Complete working example demonstrating Structured Text implementation for Safety Systems using Unitronics VisiLogic / UniLogic. Follows Unitronics naming conventions. Tested on Jazz 2 hardware.

(* Unitronics VisiLogic / UniLogic - Safety Systems Control *)
(* Structured Text Implementation for Universal *)
(* Unitronics projects use IDE-managed tag names rather than raw memory a *)

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 are commonly implemented  *)
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 UniLogic's Data Samplers — configured triggers (time-based or event-based) write structured records to Data Tables or SD card in CSV format. Exported files can be pushed via FTP or email. For cloud integration, UniCloud provides managed data ingestion. Simpler VisiLogic projects use HMI-triggered SD writes via custom ladder code. *)
        eState := IDLE;

    FAULT:
        rSafetyrelays := 0.0;
        (* Alarm handling uses UniLogic's built-in Alarm Manager — configure alarm conditions in tables with severity, message text, and logging behaviour, and the engine handles detection, acknowledgement, history, and HMI display without custom code. VisiLogic uses a simpler alarm approach via HMI event handlers. *)
        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 are commonly implemented in ladder with step-counter registers or in ST using CASE structures with named state constants. UniLogic's HMI graphical bindings make state-to-screen visualisation straightforward — a single state variable drives both logic and operator screen transitions. SFC is not a primary language on Unitronics; state logic is typically CASE or ladder.) 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 - Unitronics best practice for advanced systems

Best Practices

✓Follow Unitronics naming conventions: Unitronics projects use IDE-managed tag names rather than raw memory addressing.
✓Unitronics function design: Function block design in Unitronics uses user-defined FBs in UniLogic (more limi
✓Data organization: Unitronics uses its own tag database concept rather than IEC-standard data block
✓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 VisiLogic / UniLogic: Use the built-in simulator to reproduce issues before hardware visit
✓Safety: Use only certified safety components and PLCs
✓Use VisiLogic / UniLogic 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
⚠Unitronics common error: VisiLogic-to-UniLogic migration issues — not all projects convert cleanly
⚠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

🏆Unitronics Certified Integrator

🏆UniLogic Developer Training

🏆Advanced Unitronics Programming Certification

Mastering Structured Text for Safety Systems applications using Unitronics VisiLogic / UniLogic 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.

Unitronics's 1% market share and moderate - us small-integrator market, oem machines, building automation 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 Unitronics-specific optimizations—you can deliver reliable Safety Systems systems that meet Universal requirements.

Next Steps for Professional Development:

1. Certification: Pursue Unitronics Certified Integrator to validate your Unitronics expertise
2. Advanced Training: Consider UniLogic Developer Training for specialized Universal applications
3. Hands-on Practice: Build Safety Systems projects using Jazz 2 hardware
4. Stay Current: Follow VisiLogic / UniLogic 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 Unitronics platform-specific features for Safety Systems optimization.