Implementing Counters for Safety Systems using Delta WPLSoft / ISPSoft / DIADesigner-AX requires a documented design, applicable standards, and project-specific acceptance criteria. This guide organizes practical checks for code structure, diagnostics, testing, and maintenance.
The example references DVP-ES2 / EX2 / SS2 (compact entry)-family terminology, but model capabilities vary. Verify the controller manual, the installed WPLSoft / ISPSoft / DIADesigner-AX version, and any applicable machinery, process, electrical, or functional-safety requirements for the actual project.
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 Counters approach, when properly implemented, provides essential for production tracking and simple to implement, both critical for advanced projects.
This guide presents a reviewable approach to Delta Counters programming for Safety Systems, covering code organization, documentation, test procedures, and maintenance handoff. The sample logic is educational and must be compiled, simulated, peer-reviewed, and tested against the project's acceptance criteria before use on equipment.
Delta WPLSoft / ISPSoft / DIADesigner-AX for Safety Systems
WPLSoft / ISPSoft / DIADesigner-AX is a programming environment associated with Delta controller families such as DVP-ES2 / EX2 / SS2 (compact entry), DVP-SX2 / SA2 / SV2 (motion + analogue), DVP-SE (Ethernet). This guide uses Counters 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 Counters constructs
- The project version matches the installed WPLSoft / ISPSoft / DIADesigner-AX 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:
- DVP-ES2 / EX2 / SS2 (compact entry): Confirm CPU, I/O, memory, communications, and Counters support in the current selection guide
- DVP-SX2 / SA2 / SV2 (motion + analogue): Confirm CPU, I/O, memory, communications, and Counters support in the current selection guide
- DVP-SE (Ethernet): Confirm CPU, I/O, memory, communications, and Counters support in the current selection guide
- DVP-EH3 (legacy high-end): Confirm CPU, I/O, memory, communications, and Counters 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 Delta 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 Counters for Safety Systems
PLC counters track the number of events or items. They increment or decrement on input transitions and compare against preset values.
Execution Model:
For Safety Systems applications, Counters offers significant advantages when counting parts, cycles, events, or maintaining production totals.
Core Advantages for Safety Systems:
- Essential for production tracking: Critical for Safety Systems when handling advanced control logic
- Simple to implement: Critical for Safety Systems when handling advanced control logic
- Reliable and accurate: Critical for Safety Systems when handling advanced control logic
- Easy to understand: Critical for Safety Systems when handling advanced control logic
- Widely used: Critical for Safety Systems when handling advanced control logic
Why Counters 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 Counters:
Counters in WPLSoft / ISPSoft / DIADesigner-AX follows these key principles:
1. Structure: Counters organizes code with simple to implement
2. Execution: Scan-cycle integration defines when the 5 sensor inputs are read and processed; verify the timing on the selected controller
3. Data Handling: Proper data types for 4 actuator control signals
Best Practices for Counters:
- Debounce mechanical switch inputs before counting
- Use high-speed counters for pulses faster than scan time
- Implement overflow detection for long-running counters
- Store counts to retentive memory if needed across power cycles
- Add counter values to HMI for operator visibility
Common Mistakes to Avoid:
- Counting level instead of edge - multiple counts from one event
- Not debouncing noisy inputs causing false counts
- Using standard counters for high-speed applications
- Integer overflow causing count wrap-around
Typical Applications:
1. Bottle counting: Directly applicable to Safety Systems
2. Conveyor tracking: Related control patterns
3. Production totals: Related control patterns
4. Batch counting: Related control patterns
Understanding these fundamentals prepares you to implement effective Counters solutions for Safety Systems using Delta WPLSoft / ISPSoft / DIADesigner-AX.
Implementing Safety Systems with Counters
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 Counters 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: Counters addresses this through Essential for production tracking.
2. Managing nuisance trips while maintaining safety
- Solution: Counters addresses this through Simple to implement.
3. Integrating safety with production efficiency
- Solution: Counters addresses this through Reliable and accurate.
4. Documenting compliance with multiple standards
- Solution: Counters addresses this through Easy to understand.
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
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
Use the monitoring and diagnostic functions available in your WPLSoft / ISPSoft / DIADesigner-AX version, and record the software, firmware, hardware, workload, and test procedure with every result.
Delta Counters Example for Safety Systems
Illustrative Counters example for Safety Systems using Delta terminology. Adapt the syntax to your WPLSoft / ISPSoft / DIADesigner-AX release, compile it, and verify it in an isolated test environment before use on equipment.
// Delta WPLSoft / ISPSoft / DIADesigner-AX - Safety Systems Control
// Counters Implementation for Universal
// WPLSoft / DVP work is dominated by raw soft-element addressi
// ============================================
// 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.Counters 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 DVP-ES2 / EX2 / SS2 (compact entry) task configuration and verify them by measurement
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.
- ✓Counters: Debounce mechanical switch inputs before counting
- ✓Counters: Use high-speed counters for pulses faster than scan time
- ✓Counters: Implement overflow detection for long-running counters
- ✓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 a compatible simulator or isolated test rig to test Safety Systems logic before deployment
Common Pitfalls to Avoid
- ⚠Counters: Counting level instead of edge - multiple counts from one event
- ⚠Counters: Not debouncing noisy inputs causing false counts
- ⚠Counters: Using standard counters for high-speed applications
- ⚠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 Counters programs unmaintainable over time
Related Certifications
Applying Counters to Safety Systems using Delta WPLSoft / ISPSoft / DIADesigner-AX 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 WPLSoft / ISPSoft / DIADesigner-AX 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
Counters Foundation:
PLC counters track the number of events or items. They increment or decrement on input transitions and compare against preset values....
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 Conveyor tracking, Emergency stop systems, and Delta platform-specific features for Safety Systems optimization.