Mastering advanced Function Blocks 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 visual representation of signal flow and good for modular programming.
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 Function Blocks, these capabilities are achieved through process control 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 Function Blocks 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 Function Blocks for Safety Systems
Function Block Diagram (FBD) is a graphical programming language where functions and function blocks are represented as boxes connected by signal lines. Data flows from left to right through the network.
Execution Model:
Blocks execute based on data dependencies - a block executes only when all its inputs are available. Networks execute top to bottom when dependencies allow.
Core Advantages for Safety Systems:
- Visual representation of signal flow: Critical for Safety Systems when handling advanced control logic
- Good for modular programming: Critical for Safety Systems when handling advanced control logic
- Reusable components: Critical for Safety Systems when handling advanced control logic
- Excellent for process control: Critical for Safety Systems when handling advanced control logic
- Good for continuous operations: Critical for Safety Systems when handling advanced control logic
Why Function Blocks 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 Function Blocks:
StandardBlocks:
- logic: AND, OR, XOR, NOT - Boolean logic operations
- comparison: EQ, NE, LT, GT, LE, GE - Compare values
- math: ADD, SUB, MUL, DIV, MOD - Arithmetic operations
TimersCounters:
- ton: Timer On-Delay - Output turns ON after preset time
- tof: Timer Off-Delay - Output turns OFF after preset time
- tp: Pulse Timer - Output pulses for preset time
Connections:
- wires: Connect output pins to input pins to pass data
- branches: One output can connect to multiple inputs
- feedback: Outputs can feed back to inputs for state machines
Best Practices for Function Blocks:
- Arrange blocks for clear left-to-right data flow
- Use consistent spacing and alignment for readability
- Label all inputs and outputs with meaningful names
- Create custom FBs for frequently repeated logic patterns
- Minimize wire crossings by careful block placement
Common Mistakes to Avoid:
- Creating feedback loops without proper initialization
- Connecting incompatible data types
- Not considering execution order dependencies
- Overcrowding networks making them hard to read
Typical Applications:
1. HVAC control: Directly applicable to Safety Systems
2. Temperature control: Related control patterns
3. Flow control: Related control patterns
4. Batch processing: Related control patterns
Understanding these fundamentals prepares you to implement effective Function Blocks solutions for Safety Systems using Unitronics VisiLogic / UniLogic.
Implementing Safety Systems with Function Blocks
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 Function Blocks 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: Function Blocks addresses this through Visual representation of signal flow.
2. Managing nuisance trips while maintaining safety
- Solution: Function Blocks addresses this through Good for modular programming.
3. Integrating safety with production efficiency
- Solution: Function Blocks addresses this through Reusable components.
4. Documenting compliance with multiple standards
- Solution: Function Blocks addresses this through Excellent for process control.
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 Function Blocks Example for Safety Systems
Complete working example demonstrating Function Blocks implementation for Safety Systems using Unitronics VisiLogic / UniLogic. Follows Unitronics naming conventions. Tested on Jazz 2 hardware.
(* Unitronics VisiLogic / UniLogic - Safety Systems Control *)
(* Reusable Function Blocks Implementation *)
(* Function block design in Unitronics uses user-defined FBs in *)
FUNCTION_BLOCK FB_SAFETY_SYSTEMS_Controller
VAR_INPUT
bEnable : BOOL; (* Enable control *)
bReset : BOOL; (* Fault reset *)
rProcessValue : REAL; (* Emergency stop buttons (Category 0 or 1 stop) *)
rSetpoint : REAL := 100.0; (* Target value *)
bEmergencyStop : BOOL; (* Safety input *)
END_VAR
VAR_OUTPUT
rControlOutput : REAL; (* Safety contactors (mirror contact type) *)
bRunning : BOOL; (* Process active *)
bComplete : BOOL; (* Cycle complete *)
bFault : BOOL; (* Fault status *)
nFaultCode : INT; (* Diagnostic code *)
END_VAR
VAR
(* Internal Function Blocks *)
fbSafety : FB_SafetyMonitor; (* Safety logic *)
fbRamp : FB_RampGenerator; (* Soft start/stop *)
fbPID : FB_PIDController; (* Process control *)
fbDiag : FB_Diagnostics; (* 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. *)
(* Internal State *)
eInternalState : E_ControlState;
tonWatchdog : TON;
END_VAR
(* Safety Monitor - Use only certified safety components and PLCs *)
fbSafety(
Enable := bEnable,
EmergencyStop := bEmergencyStop,
ProcessValue := rProcessValue,
HighLimit := rSetpoint * 1.2,
LowLimit := rSetpoint * 0.1
);
(* Main Control Logic *)
IF fbSafety.SafeToRun THEN
(* Ramp Generator - Prevents startup surge *)
fbRamp(
Enable := bEnable,
TargetValue := rSetpoint,
RampRate := 20.0, (* Universal rate *)
CurrentValue => rSetpoint
);
(* PID Controller - Process regulation *)
fbPID(
Enable := fbRamp.InPosition,
ProcessValue := rProcessValue,
Setpoint := fbRamp.CurrentValue,
Kp := 1.0,
Ki := 0.1,
Kd := 0.05,
OutputMin := 0.0,
OutputMax := 100.0
);
rControlOutput := fbPID.Output;
bRunning := TRUE;
bFault := FALSE;
nFaultCode := 0;
ELSE
(* Safe State - Implement dual-channel monitoring per category requirements *)
rControlOutput := 0.0;
bRunning := FALSE;
bFault := NOT bEnable; (* Only fault if not intentional stop *)
nFaultCode := fbSafety.FaultCode;
END_IF;
(* Diagnostics - 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. *)
fbDiag(
ProcessRunning := bRunning,
FaultActive := bFault,
ProcessValue := rProcessValue,
ControlOutput := rControlOutput
);
(* Watchdog - Detects frozen control *)
tonWatchdog(IN := bRunning AND NOT fbPID.OutputChanging, PT := T#10S);
IF tonWatchdog.Q THEN
bFault := TRUE;
nFaultCode := 99; (* Watchdog fault *)
END_IF;
(* Reset Logic *)
IF bReset AND NOT bEmergencyStop THEN
bFault := FALSE;
nFaultCode := 0;
fbDiag.ClearAlarms();
END_IF;
END_FUNCTION_BLOCKCode Explanation:
- 1.Encapsulated function block follows Function block design in Unitronics uses - reusable across Universal projects
- 2.FB_SafetyMonitor provides Use only certified safety components and PLCs including high/low limits
- 3.FB_RampGenerator prevents startup issues common in Safety Systems systems
- 4.FB_PIDController tuned for Universal: Kp=1.0, Ki=0.1
- 5.Watchdog timer detects frozen control - critical for advanced Safety Systems reliability
- 6.Diagnostic function block enables 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. and 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.
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
- βFunction Blocks: Arrange blocks for clear left-to-right data flow
- βFunction Blocks: Use consistent spacing and alignment for readability
- βFunction Blocks: Label all inputs and outputs with meaningful names
- β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
- β Function Blocks: Creating feedback loops without proper initialization
- β Function Blocks: Connecting incompatible data types
- β Function Blocks: Not considering execution order dependencies
- β 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 Function Blocks programs unmaintainable over time
Related Certifications
Mastering Function Blocks 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 Function Blocks 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 Function Blocks features
Function Blocks Foundation:
Function Block Diagram (FBD) is a graphical programming language where functions and function blocks are represented as boxes connected by signal line...
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 Temperature control, Emergency stop systems, and Unitronics platform-specific features for Safety Systems optimization.