Unitronics Data Types for HVAC Control: Complete Programming Guide

Learning to implement Data Types for HVAC Control using Unitronics's VisiLogic / UniLogic is a useful skill for PLC programmers working in Building Automation. This guide walks through the fundamentals with clear explanations and an illustrative example that you can adapt to a simulator or test bench.

The example uses Unitronics terminology and references controller families such as Jazz 2 and Samba 7". Confirm the exact instructions, data types, firmware requirements, and licensing in the current vendor documentation before choosing hardware or deploying a project.

The Data Types approach is particularly well-suited for HVAC Control because all programming applications - choosing correct data types is fundamental to efficient plc programming. This combination allows you to leverage memory optimization while managing the typical challenges of HVAC Control, including energy optimization and zone control coordination.

Throughout this guide, you'll find step-by-step implementation guidance, an illustrative code example, and a verification checklist specific to Building Automation. Whether you're programming your first HVAC Control exercise or transitioning from another PLC platform, use the material as a starting point and validate it in your exact VisiLogic / UniLogic version and controller environment.

Unitronics VisiLogic / UniLogic for HVAC Control

VisiLogic / UniLogic is a programming environment associated with Unitronics controller families such as Jazz 2, Samba 7", Vision V350. This guide uses Data Types 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 Data Types constructs

The project version matches the installed VisiLogic / UniLogic 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 HVAC Control exercise, map the required inputs and outputs before writing logic. The example considers 5 sensor types, including Temperature sensors (RTD, Thermocouple), Humidity sensors, Pressure sensors, and 5 actuator types.

Control Equipment for HVAC Control:

Air handling units (AHUs) with supply and return fans

Variable air volume (VAV) boxes with reheat

Chillers and cooling towers for central cooling

Boilers and heat exchangers for heating

Controller-family references used in this guide include:

Jazz 2: Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide

Samba 7": Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide

Vision V350: Confirm CPU, I/O, memory, communications, and Data Types support in the current selection guide

Vision V570: Confirm CPU, I/O, memory, communications, and Data Types 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 Unitronics 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 HVAC Control 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 Data Types for HVAC Control

PLC data types define how values are stored, their valid ranges, and operations that can be performed. Proper type selection ensures accuracy and memory efficiency.

Execution Model:

For HVAC Control applications, Data Types offers significant advantages when all programming applications - choosing correct data types is fundamental to efficient plc programming.

Core Advantages for HVAC Control:

Memory optimization: Critical for HVAC Control when handling intermediate control logic

Type safety: Critical for HVAC Control when handling intermediate control logic

Better organization: Critical for HVAC Control when handling intermediate control logic

Improved performance: Critical for HVAC Control when handling intermediate control logic

Enhanced maintainability: Critical for HVAC Control when handling intermediate control logic

Why Data Types Fits HVAC Control:

HVAC Control systems in Building Automation typically involve:

Sensors: Temperature sensors (RTD, thermistors, thermocouples) for zone and supply/return monitoring, Humidity sensors (capacitive or resistive) for moisture control, CO2 sensors for demand-controlled ventilation

Actuators: Variable frequency drives (VFDs) for fan and pump speed control, Modulating control valves (2-way and 3-way) for heating/cooling coils, Damper actuators (0-10V or 4-20mA) for air flow control

Complexity: Intermediate with challenges including Tuning PID loops for slow thermal processes without causing oscillation

Control Strategies for HVAC Control:

zoneTemperature: Cascaded PID control where zone temperature error calculates supply air temperature setpoint, which then modulates cooling/heating valves or VAV damper position

supplyAirTemperature: PID control of cooling coil valve, heating coil valve, or economizer dampers to maintain supply air temperature setpoint

staticPressure: PID control of supply fan VFD speed to maintain duct static pressure setpoint for proper VAV box operation

Programming Fundamentals in Data Types:

Data Types in VisiLogic / UniLogic follows these key principles:

1. Structure: Data Types organizes code with type safety
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 5 actuator control signals

Best Practices for Data Types:

Use smallest data type that accommodates the value range

Use REAL for analog values that need decimal precision

Create UDTs for frequently repeated data patterns

Use meaningful names for array indices via constants

Document units in comments (e.g., // Temperature in tenths of degrees)

Common Mistakes to Avoid:

Using INT for values that exceed 32767

Losing precision when converting REAL to INT

Array index out of bounds causing memory corruption

Not handling negative numbers correctly with unsigned types

Typical Applications:

1. Recipe management: Directly applicable to HVAC Control
2. Data logging: Related control patterns
3. Complex calculations: Related control patterns
4. System configuration: Related control patterns

Understanding these fundamentals prepares you to implement effective Data Types solutions for HVAC Control using Unitronics VisiLogic / UniLogic.

Implementing HVAC Control with Data Types

HVAC (Heating, Ventilation, and Air Conditioning) control systems use PLCs to regulate temperature, humidity, and air quality in buildings and industrial facilities. These systems balance comfort, energy efficiency, and equipment longevity through sophisticated control algorithms.

This walkthrough demonstrates practical implementation using Unitronics VisiLogic / UniLogic and Data Types programming.

System Requirements:

A typical HVAC Control implementation includes:

Input Devices (Sensors):
1. Temperature sensors (RTD, thermistors, thermocouples) for zone and supply/return monitoring: Critical for monitoring system state
2. Humidity sensors (capacitive or resistive) for moisture control: Critical for monitoring system state
3. CO2 sensors for demand-controlled ventilation: Critical for monitoring system state
4. Pressure sensors for duct static pressure and building pressurization: Critical for monitoring system state
5. Occupancy sensors (PIR, ultrasonic) for demand-based operation: Critical for monitoring system state

Output Devices (Actuators):
1. Variable frequency drives (VFDs) for fan and pump speed control: Primary control output
2. Modulating control valves (2-way and 3-way) for heating/cooling coils: Supporting control function
3. Damper actuators (0-10V or 4-20mA) for air flow control: Supporting control function
4. Compressor contactors and staging relays: Supporting control function
5. Humidifier and dehumidifier control outputs: Supporting control function

Control Equipment:

Air handling units (AHUs) with supply and return fans

Variable air volume (VAV) boxes with reheat

Chillers and cooling towers for central cooling

Boilers and heat exchangers for heating

Control Strategies for HVAC Control:

zoneTemperature: Cascaded PID control where zone temperature error calculates supply air temperature setpoint, which then modulates cooling/heating valves or VAV damper position

supplyAirTemperature: PID control of cooling coil valve, heating coil valve, or economizer dampers to maintain supply air temperature setpoint

staticPressure: PID control of supply fan VFD speed to maintain duct static pressure setpoint for proper VAV box operation

Implementation Steps:

Step 1: Document all zones with temperature requirements and occupancy schedules

In VisiLogic / UniLogic, document all zones with temperature requirements and occupancy schedules.

Step 2: Create I/O list with all sensors, actuators, and their signal types

In VisiLogic / UniLogic, create i/o list with all sensors, actuators, and their signal types.

Step 3: Define setpoints, operating limits, and alarm thresholds

In VisiLogic / UniLogic, define setpoints, operating limits, and alarm thresholds.

Step 4: Implement zone temperature control loops with anti-windup

In VisiLogic / UniLogic, implement zone temperature control loops with anti-windup.

Step 5: Program equipment sequencing with proper lead-lag rotation

In VisiLogic / UniLogic, program equipment sequencing with proper lead-lag rotation.

Step 6: Add economizer logic with lockouts for high humidity conditions

In VisiLogic / UniLogic, add economizer logic with lockouts for high humidity conditions.

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. Tuning PID loops for slow thermal processes without causing oscillation

Solution: Data Types addresses this through Memory optimization.

2. Preventing simultaneous heating and cooling which wastes energy

Solution: Data Types addresses this through Type safety.

3. Managing zone interactions in open-plan spaces

Solution: Data Types addresses this through Better organization.

4. Balancing fresh air requirements with energy efficiency

Solution: Data Types addresses this through Improved performance.

Safety Considerations:

Freeze protection for coils with low-limit thermostats and valve positioning

High-limit safety shutoffs for heating equipment

Smoke detector integration for fan shutdown and damper closure

Fire/smoke damper monitoring and control

Emergency ventilation modes for hazardous conditions

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

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

Use the monitoring and diagnostic functions available in your VisiLogic / UniLogic version, and record the software, firmware, hardware, workload, and test procedure with every result.

Unitronics Data Types Example for HVAC Control

Illustrative Data Types example for HVAC Control using Unitronics terminology. Adapt the syntax to your VisiLogic / UniLogic release, compile it, and verify it in an isolated test environment before use on equipment.

// Unitronics VisiLogic / UniLogic - HVAC Control Control
// Data Types Implementation for Building Automation
// Unitronics projects use IDE-managed tag names rather than ra

// ============================================
// Variable Declarations
// ============================================
VAR
    bEnable : BOOL := FALSE;
    bEmergencyStop : BOOL := FALSE;
    rTemperaturesensorsRTDThermocouple : REAL;
    rVariablefrequencydrivesVFDs : REAL;
END_VAR

// ============================================
// Input Conditioning - Temperature sensors (RTD, thermistors, thermocouples) for zone and supply/return monitoring
// ============================================
// Standard input processing
IF rTemperaturesensorsRTDThermocouple > 0.0 THEN
    bEnable := TRUE;
END_IF;

// ============================================
// Safety Interlock - Freeze protection for coils with low-limit thermostats and valve positioning
// ============================================
IF bEmergencyStop THEN
    rVariablefrequencydrivesVFDs := 0.0;
    bEnable := FALSE;
END_IF;

// ============================================
// Main HVAC Control Control Logic
// ============================================
IF bEnable AND NOT bEmergencyStop THEN
    // HVAC (Heating, Ventilation, and Air Conditioning) control sy
    rVariablefrequencydrivesVFDs := rTemperaturesensorsRTDThermocouple * 1.0; (* Illustrative scaling only *)

    // Process monitoring
    // Add specific control logic here
ELSE
    rVariablefrequencydrivesVFDs := 0.0;
END_IF;

Code Explanation:

1.Data Types structure organized for a HVAC Control training example
2.Input conditioning handles Temperature sensors (RTD, thermistors, thermocouples) for zone and supply/return monitoring signals
3.Safety interlock ensures Freeze protection for coils with low-limit thermostats and valve positioning always takes priority
4.Main control implements HVAC (Heating, Ventilation, and Air Cond
5.Adapt the scan-cycle assumptions to the selected Jazz 2 task configuration and verify them by measurement

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
✓Data Types: Use smallest data type that accommodates the value range
✓Data Types: Use REAL for analog values that need decimal precision
✓Data Types: Create UDTs for frequently repeated data patterns
✓HVAC Control: Use slow integral action for temperature loops to prevent hunting
✓HVAC Control: Implement anti-windup to prevent integral buildup during saturation
✓HVAC Control: Add rate limiting to outputs to prevent actuator wear
✓Debug with VisiLogic / UniLogic: Use the built-in simulator to reproduce issues before hardware visit
✓Safety: Freeze protection for coils with low-limit thermostats and valve positioning
✓Use a compatible simulator or isolated test rig to test HVAC Control logic before deployment

Common Pitfalls to Avoid

⚠Data Types: Using INT for values that exceed 32767
⚠Data Types: Losing precision when converting REAL to INT
⚠Data Types: Array index out of bounds causing memory corruption
⚠Unitronics common error: VisiLogic-to-UniLogic migration issues — not all projects convert cleanly
⚠HVAC Control: Tuning PID loops for slow thermal processes without causing oscillation
⚠HVAC Control: Preventing simultaneous heating and cooling which wastes energy
⚠Neglecting to validate Temperature sensors (RTD, thermistors, thermocouples) for zone and supply/return monitoring leads to control errors
⚠Insufficient comments make Data Types programs unmaintainable over time

Related Certifications

🏆Unitronics Certified Integrator

🏆UniLogic Developer Training

Applying Data Types to HVAC Control using Unitronics VisiLogic / UniLogic 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 intermediate HVAC Control 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 VisiLogic / UniLogic 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

Data Types Foundation:

PLC data types define how values are stored, their valid ranges, and operations that can be performed. Proper type selection ensures accuracy and memo...

Project duration depends on scope, reviews, hardware availability, software and firmware versions, testing, commissioning, and site constraints. Remember: Use slow integral action for temperature loops to prevent hunting

For further learning, explore related topics including Data logging, Hospital environmental systems, and Unitronics platform-specific features for HVAC Control optimization.