Implementing Structured Text for Temperature Control using Unitronics VisiLogic / UniLogic requires translating theory into working code that performs reliably in production. This hands-on guide focuses on practical implementation steps, real code examples, and the pragmatic decisions that make the difference between successful and problematic Temperature Control deployments.
Unitronics's platform serves Moderate - US small-integrator market, OEM machines, building automation, providing the proven foundation for Temperature Control implementations. The VisiLogic / UniLogic environment supports 3 programming languages, with Structured Text being particularly effective for Temperature Control because complex calculations, data manipulation, advanced control algorithms, and when code reusability is important. Practical implementation requires understanding not just language syntax, but how Unitronics's execution model handles 4 sensor inputs and 5 actuator outputs in real-time.
Real Temperature Control projects in Process Control face practical challenges including pid tuning, temperature stability, and integration with existing systems. Success requires balancing powerful for complex logic against steeper learning curve, while meeting 2-3 weeks project timelines typical for Temperature Control implementations.
This guide provides step-by-step implementation guidance, complete working examples tested on Jazz 2, practical design patterns, and real-world troubleshooting scenarios. You'll learn the pragmatic approaches that experienced integrators use to deliver reliable Temperature Control systems on schedule and within budget.
Unitronics VisiLogic / UniLogic for Temperature Control
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 Temperature Control:
- 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 Temperature Control applications through its combined plc + hmi in one unit reduces panel cost. This is particularly valuable when working with the 4 sensor types typically found in Temperature Control systems, including Thermocouples (K-type, J-type), RTD sensors (PT100, PT1000), Infrared temperature sensors.
Control Equipment for Temperature Control:
- Electric resistance heaters (cartridge, band, strip)
- Steam injection systems
- Thermal fluid (hot oil) systems
- Refrigeration and chiller systems
Unitronics's controller families for Temperature Control include:
- Jazz 2: Suitable for intermediate Temperature Control applications
- Samba 7": Suitable for intermediate Temperature Control applications
- Vision V350: Suitable for intermediate Temperature Control applications
- Vision V570: Suitable for intermediate Temperature Control 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 Temperature Control projects requiring intermediate skill levels and 2-3 weeks development time, the total investment includes hardware, software licensing, training, and ongoing support.
Understanding Structured Text for Temperature Control
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 Temperature Control:
- Powerful for complex logic: Critical for Temperature Control when handling intermediate control logic
- Excellent code reusability: Critical for Temperature Control when handling intermediate control logic
- Compact code representation: Critical for Temperature Control when handling intermediate control logic
- Good for algorithms and calculations: Critical for Temperature Control when handling intermediate control logic
- Familiar to software developers: Critical for Temperature Control when handling intermediate control logic
Why Structured Text Fits Temperature Control:
Temperature Control systems in Process Control typically involve:
- Sensors: RTDs (PT100/PT1000) for high-accuracy measurements, Thermocouples (J, K, T types) for high-temperature applications, Infrared pyrometers for non-contact measurement
- Actuators: SCR (thyristor) power controllers for electric heaters, Solid-state relays for on/off heating control, Proportional control valves for steam or thermal fluid
- Complexity: Intermediate with challenges including Long thermal time constants making tuning difficult
Control Strategies for Temperature Control:
- pid: Standard PID control with proportional, integral, and derivative terms tuned for the thermal process dynamics
- cascade: Master temperature loop outputs to slave heater/cooler control loop for tighter control
- ratio: Maintain temperature ratio between zones for gradient applications
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 Temperature Control
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 Temperature Control using Unitronics VisiLogic / UniLogic.
Implementing Temperature Control with Structured Text
Industrial temperature control systems use PLCs to regulate process temperatures in manufacturing, food processing, chemical processing, and other applications. These systems maintain precise temperature setpoints through heating and cooling control while ensuring product quality and energy efficiency.
This walkthrough demonstrates practical implementation using Unitronics VisiLogic / UniLogic and Structured Text programming.
System Requirements:
A typical Temperature Control implementation includes:
Input Devices (Sensors):
1. RTDs (PT100/PT1000) for high-accuracy measurements: Critical for monitoring system state
2. Thermocouples (J, K, T types) for high-temperature applications: Critical for monitoring system state
3. Infrared pyrometers for non-contact measurement: Critical for monitoring system state
4. Thermistors for fast response applications: Critical for monitoring system state
5. Thermal imaging cameras for surface temperature monitoring: Critical for monitoring system state
Output Devices (Actuators):
1. SCR (thyristor) power controllers for electric heaters: Primary control output
2. Solid-state relays for on/off heating control: Supporting control function
3. Proportional control valves for steam or thermal fluid: Supporting control function
4. Solenoid valves for cooling water or refrigerant: Supporting control function
5. Variable frequency drives for cooling fan control: Supporting control function
Control Equipment:
- Electric resistance heaters (cartridge, band, strip)
- Steam injection systems
- Thermal fluid (hot oil) systems
- Refrigeration and chiller systems
Control Strategies for Temperature Control:
- pid: Standard PID control with proportional, integral, and derivative terms tuned for the thermal process dynamics
- cascade: Master temperature loop outputs to slave heater/cooler control loop for tighter control
- ratio: Maintain temperature ratio between zones for gradient applications
Implementation Steps:
Step 1: Characterize thermal system dynamics (time constants, dead time)
In VisiLogic / UniLogic, characterize thermal system dynamics (time constants, dead time).
Step 2: Select appropriate sensor type and placement for representative measurement
In VisiLogic / UniLogic, select appropriate sensor type and placement for representative measurement.
Step 3: Size heating and cooling capacity for worst-case load conditions
In VisiLogic / UniLogic, size heating and cooling capacity for worst-case load conditions.
Step 4: Implement PID control with appropriate sample time (typically 10x faster than process time constant)
In VisiLogic / UniLogic, implement pid control with appropriate sample time (typically 10x faster than process time constant).
Step 5: Add output limiting and anti-windup for safe operation
In VisiLogic / UniLogic, add output limiting and anti-windup for safe operation.
Step 6: Program ramp/soak profiles if required
In VisiLogic / UniLogic, program ramp/soak profiles if required.
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. Long thermal time constants making tuning difficult
- Solution: Structured Text addresses this through Powerful for complex logic.
2. Transport delay (dead time) causing instability
- Solution: Structured Text addresses this through Excellent code reusability.
3. Non-linear response at different temperature ranges
- Solution: Structured Text addresses this through Compact code representation.
4. Sensor placement affecting measurement accuracy
- Solution: Structured Text addresses this through Good for algorithms and calculations.
Safety Considerations:
- Independent high-limit safety thermostats (redundant to PLC)
- Watchdog timers for heater control validity
- Safe-state definition on controller failure (heaters off)
- Thermal fuse backup for runaway conditions
- Proper ventilation for combustible atmospheres
Performance Metrics:
- Scan Time: Optimize for 4 inputs and 5 outputs
- Memory Usage: Efficient data structures for Jazz 2 capabilities
- Response Time: Meeting Process Control requirements for Temperature Control
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 2-3 weeks development timeline while maintaining code quality.
Unitronics Structured Text Example for Temperature Control
Complete working example demonstrating Structured Text implementation for Temperature Control using Unitronics VisiLogic / UniLogic. Follows Unitronics naming conventions. Tested on Jazz 2 hardware.
(* Unitronics VisiLogic / UniLogic - Temperature Control Control *)
(* Structured Text Implementation for Process Control *)
(* Unitronics projects use IDE-managed tag names rather than raw memory a *)
PROGRAM PRG_TEMPERATURE_CONTROL_Control
VAR
(* State Machine Variables *)
eState : E_TEMPERATURE_CONTROL_States := IDLE;
bEnable : BOOL := FALSE;
bFaultActive : BOOL := FALSE;
(* Timers *)
tonDebounce : TON;
tonProcessTimeout : TON;
tonFeedbackCheck : TON;
(* Counters *)
ctuCycleCounter : CTU;
(* Process Variables *)
rThermocouplesKtypeJtype : REAL := 0.0;
rHeatingelements : REAL := 0.0;
rSetpoint : REAL := 100.0;
END_VAR
VAR CONSTANT
(* Process Control 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:
rHeatingelements := 0.0;
ctuCycleCounter(RESET := TRUE);
IF bEnable AND rThermocouplesKtypeJtype > 10.0 THEN
eState := STARTING;
END_IF;
STARTING:
(* Ramp up output - Gradual start *)
rHeatingelements := MIN(rHeatingelements + 5.0, rSetpoint);
IF rHeatingelements >= rSetpoint THEN
eState := RUNNING;
END_IF;
RUNNING:
(* Temperature Control active - Industrial temperature control systems use PLCs to *)
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:
rHeatingelements := 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:
rHeatingelements := 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
rHeatingelements := 0.0;
eState := FAULT;
bFaultActive := TRUE;
END_IF;
END_PROGRAMCode 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 Temperature Control sequence control
- 2.Constants define Process Control-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 intermediate 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
- ✓Temperature Control: Sample at 1/10 of the process time constant minimum
- ✓Temperature Control: Use derivative on PV, not error, for temperature control
- ✓Temperature Control: Start with conservative tuning and tighten gradually
- ✓Debug with VisiLogic / UniLogic: Use the built-in simulator to reproduce issues before hardware visit
- ✓Safety: Independent high-limit safety thermostats (redundant to PLC)
- ✓Use VisiLogic / UniLogic simulation tools to test Temperature Control 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
- ⚠Temperature Control: Long thermal time constants making tuning difficult
- ⚠Temperature Control: Transport delay (dead time) causing instability
- ⚠Neglecting to validate RTDs (PT100/PT1000) for high-accuracy measurements leads to control errors
- ⚠Insufficient comments make Structured Text programs unmaintainable over time
Related Certifications
Mastering Structured Text for Temperature Control applications using Unitronics VisiLogic / UniLogic requires understanding both the platform's capabilities and the specific demands of Process Control. This guide has provided comprehensive coverage of implementation strategies, working code examples, best practices, and common pitfalls to help you succeed with intermediate Temperature Control 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 Process Control applications where Temperature Control 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 Temperature Control systems that meet Process Control 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 Process Control applications
3. Hands-on Practice: Build Temperature Control 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 2-3 weeks typical timeline for Temperature Control projects will decrease as you gain experience with these patterns and techniques. Remember: Sample at 1/10 of the process time constant minimum
For further learning, explore related topics including Recipe management, Plastic molding machines, and Unitronics platform-specific features for Temperature Control optimization.