Learning to implement Structured Text for Safety Systems using Delta's WPLSoft / ISPSoft / DIADesigner-AX is an essential skill for PLC programmers working in Universal. This comprehensive guide walks you through the fundamentals, providing clear explanations and practical examples that you can apply immediately to real-world projects.
Delta has established itself as Strong in Asian, Indian, and SE Asian OEM machinery — packaging, plastics, textiles, HVAC, food processing — and in cost-sensitive water-treatment, irrigation, and small-plant work across Latin America and EMEA, making it a strategic choice for Safety Systems applications. With ~3–4% global, growing global market share and 7 popular PLC families including the DVP-ES2 / EX2 / SS2 (compact entry) and DVP-SX2 / SA2 / SV2 (motion + analogue), Delta provides the robust platform needed for advanced complexity projects like Safety Systems.
The Structured Text approach is particularly well-suited for Safety Systems because complex calculations, data manipulation, advanced control algorithms, and when code reusability is important. This combination allows you to leverage powerful for complex logic while managing the typical challenges of Safety Systems, including safety integrity level (sil) compliance and redundancy requirements.
Throughout this guide, you'll discover step-by-step implementation strategies, working code examples tested on WPLSoft / ISPSoft / DIADesigner-AX, and industry best practices specific to Universal. Whether you're programming your first Safety Systems system or transitioning from another PLC platform, this guide provides the practical knowledge you need to succeed with Delta Structured Text programming.
Delta WPLSoft / ISPSoft / DIADesigner-AX for Safety Systems
Delta's PLC programming ecosystem is split between two free Windows IDEs: WPLSoft for the legacy DVP-ES2 / EX2 / SS2 / SX2 / SA2 / SV2 / EH3 family, and ISPSoft for newer DVP-SE / SV2 / SX3 models and the AH and AS mid-range series. WPLSoft is a focused ladder-and-IL editor with an offline simulator, online monitoring with rung-state colour, and built-in Modbus RTU / TCP wizards. ISPSoft is IEC 61131-3 oriented — ladder, structured text, function block diagram and SFC — with project-tree organis...
Platform Strengths for Safety Systems:
- Free WPLSoft and ISPSoft IDEs with built-in offline simulator
- Full IEC 61131-3 language coverage on AH / AS / AX series via ISPSoft
- Mitsubishi-FX-style instruction set easing migration on DVP
- Aggressive pricing typically 30–50% below Siemens or Allen-Bradley
Unique ${brand.software} Features:
- Free WPLSoft IDE for DVP series with built-in offline simulator
- Free ISPSoft IDE for AH / AS / DVP-SE with full IEC 61131-3 language coverage
- Mitsubishi-FX-style instruction set easing migration for FX-trained engineers
- Built-in Modbus RTU and Modbus TCP master / slave on most CPUs
Key Capabilities:
The WPLSoft / ISPSoft / DIADesigner-AX environment excels at Safety Systems applications through its free wplsoft and ispsoft ides with built-in offline simulator. 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)
Delta's controller families for Safety Systems include:
- DVP-ES2 / EX2 / SS2 (compact entry): Suitable for advanced Safety Systems applications
- DVP-SX2 / SA2 / SV2 (motion + analogue): Suitable for advanced Safety Systems applications
- DVP-SE (Ethernet): Suitable for advanced Safety Systems applications
- DVP-EH3 (legacy high-end): Suitable for advanced Safety Systems applications
Hardware Selection Guidance:
DVP-ES2 / EX2 / SS2 cover compact entry-level for small machines; DVP-SX2 adds analogue I/O; DVP-SA2 / SV2 step up for motion-heavy applications; DVP-SE adds Ethernet; DVP-EH3 is the legacy high-end. For mid-range process and machine control, AS-series (AS218 / AS228 / AS318 / AS332) and AH-series (AH500 modular rack) are preferred. AX-series motion controllers handle EtherCAT-based multi-axis. Se...
Industry Recognition:
Strong in Asian, Indian, and SE Asian OEM machinery — packaging, plastics, textiles, HVAC, food processing — and in cost-sensitive water-treatment, irrigation, and small-plant work across Latin America and EMEA. Tier 2 / Tier 3 component fixturing and ancillary equipment in Asian and Indian automotive supply chains. Limited Tier 1 line-control presence — OEMs typically specify Siemens or Mitsubishi at that tier....
Investment Considerations:
With $ pricing, Delta positions itself in the value 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 Delta WPLSoft / ISPSoft / DIADesigner-AX.
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 Delta WPLSoft / ISPSoft / DIADesigner-AX 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 WPLSoft / ISPSoft / DIADesigner-AX, perform hazard analysis and risk assessment.
Step 2: Determine required safety level (SIL/PL) for each function
In WPLSoft / ISPSoft / DIADesigner-AX, determine required safety level (sil/pl) for each function.
Step 3: Select certified safety components meeting requirements
In WPLSoft / ISPSoft / DIADesigner-AX, select certified safety components meeting requirements.
Step 4: Design safety circuit architecture per category requirements
In WPLSoft / ISPSoft / DIADesigner-AX, design safety circuit architecture per category requirements.
Step 5: Implement safety logic in certified safety PLC/relay
In WPLSoft / ISPSoft / DIADesigner-AX, implement safety logic in certified safety plc/relay.
Step 6: Add diagnostics and proof test provisions
In WPLSoft / ISPSoft / DIADesigner-AX, add diagnostics and proof test provisions.
Delta Function Design:
WPLSoft P-labels are the primary reuse mechanism on DVP. ISPSoft instance-based function blocks enable proper IEC-style reuse on AH / AS, with library import / export. Delta-supplied motion, communication, and PID FBs ship with the IDE.
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 DVP-ES2 / EX2 / SS2 (compact entry) capabilities
- Response Time: Meeting Universal requirements for Safety Systems
Delta Diagnostic Tools:
WPLSoft / ISPSoft online monitor with rung-state colour,Soft-element watch table and tag watch lists,Built-in offline simulator (WPLSoft and ISPSoft),Modbus RTU / TCP communication wizard with diagnostic counters,DIADesigner-AX integrated diagnostics for AX motion projects,M1000-range system flags for CPU and comms diagnostics,Delta distributor support and loaner CPUs in major markets,Delta IA forum and DeltaPLC community for application questions
Delta's WPLSoft / ISPSoft / DIADesigner-AX provides tools for performance monitoring and optimization, essential for achieving the 4-8 weeks development timeline while maintaining code quality.
Delta Structured Text Example for Safety Systems
Complete working example demonstrating Structured Text implementation for Safety Systems using Delta WPLSoft / ISPSoft / DIADesigner-AX. Follows Delta naming conventions. Tested on DVP-ES2 / EX2 / SS2 (compact entry) hardware.
(* Delta WPLSoft / ISPSoft / DIADesigner-AX - Safety Systems Control *)
(* Structured Text Implementation for Universal *)
(* WPLSoft / DVP work is dominated by raw soft-element addressing (X0, Y0 *)
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: FX-style SFC steps (S0..S1023) for clean *)
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 - PLC-tier logging is uncommon on DVP — logging happens at the HMI tier (DOPSoft, Delta DIAView SCADA) or via Modbus pull from a higher-level historian. AH / AS supports SD-card data logging and on-board CSV export. *)
eState := IDLE;
FAULT:
rSafetyrelays := 0.0;
(* M-flag banks latched on fault detection on DVP; ISPSoft on AH / AS allows alarm structures and HMI alarm-banner integration via Delta DOPSoft or third-party HMIs over Modbus TCP. *)
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 (FX-style SFC steps (S0..S1023) for clean sequencer logic on DVP; integer state in D-registers for fault-recovery branching. ISPSoft on AH / AS supports IEC-style state-machine function blocks with structured-text guards.) 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 - Delta best practice for advanced systems
Best Practices
- ✓Follow Delta naming conventions: WPLSoft / DVP work is dominated by raw soft-element addressing (X0, Y0, M100, D1
- ✓Delta function design: WPLSoft P-labels are the primary reuse mechanism on DVP. ISPSoft instance-based
- ✓Data organization: DVP has no structured data blocks — D / register banks are documented by range.
- ✓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 WPLSoft / ISPSoft / DIADesigner-AX: Run the offline simulator with forced inputs before live download
- ✓Safety: Use only certified safety components and PLCs
- ✓Use WPLSoft / ISPSoft / DIADesigner-AX 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
- ⚠Delta common error: Battery-low alarm on legacy DVP-EH causing D-range data loss
- ⚠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 Delta WPLSoft / ISPSoft / DIADesigner-AX 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.
Delta's ~3–4% global, growing market share and strong in asian, indian, and se asian oem machinery — packaging, plastics, textiles, hvac, food processing — and in cost-sensitive water-treatment, irrigation, and small-plant work across latin america and emea 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 Delta-specific optimizations—you can deliver reliable Safety Systems systems that meet Universal requirements.
Next Steps for Professional Development:
1. Certification: Pursue Delta IA Academy distributor-led engineer training to validate your Delta expertise
2. Advanced Training: Consider WPLSoft / ISPSoft course completions for specialized Universal applications
3. Hands-on Practice: Build Safety Systems projects using DVP-ES2 / EX2 / SS2 (compact entry) hardware
4. Stay Current: Follow WPLSoft / ISPSoft / DIADesigner-AX 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 Delta platform-specific features for Safety Systems optimization.