Inovance Structured Text for HVAC Control: Complete Programming Guide

Learning to implement Structured Text for HVAC Control using Inovance's InoProShop / AutoShop 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 Inovance terminology and references controller families such as AM600 and AM610. Confirm the exact instructions, data types, firmware requirements, and licensing in the current vendor documentation before choosing hardware or deploying a project.

The Structured Text approach is particularly well-suited for HVAC Control 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 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 InoProShop / AutoShop version and controller environment.

Inovance InoProShop / AutoShop for HVAC Control

InoProShop / AutoShop is a programming environment associated with Inovance controller families such as AM600, AM610, H5U. This guide uses Structured Text 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 Structured Text constructs

The project version matches the installed InoProShop / AutoShop 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:

AM600: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

AM610: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

H5U: Confirm CPU, I/O, memory, communications, and Structured Text support in the current selection guide

AC800: Confirm CPU, I/O, memory, communications, and Structured Text 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 Inovance 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 Structured Text for HVAC 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 HVAC Control:

Powerful for complex logic: Critical for HVAC Control when handling intermediate control logic

Excellent code reusability: Critical for HVAC Control when handling intermediate control logic

Compact code representation: Critical for HVAC Control when handling intermediate control logic

Good for algorithms and calculations: Critical for HVAC Control when handling intermediate control logic

Familiar to software developers: Critical for HVAC Control when handling intermediate control logic

Why Structured Text 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 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 HVAC 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 HVAC Control using Inovance InoProShop / AutoShop.

Implementing HVAC Control with Structured Text

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 Inovance InoProShop / AutoShop and Structured Text 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 InoProShop / AutoShop, document all zones with temperature requirements and occupancy schedules.

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

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

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

In InoProShop / AutoShop, define setpoints, operating limits, and alarm thresholds.

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

In InoProShop / AutoShop, implement zone temperature control loops with anti-windup.

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

In InoProShop / AutoShop, program equipment sequencing with proper lead-lag rotation.

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

In InoProShop / AutoShop, add economizer logic with lockouts for high humidity conditions.

Inovance Function Design:

InoProShop strongly favours function-block reuse via the Library Manager — Inovance ships standard libraries for motion, drives, HMI, OPC UA, and industry-specific applications (lithium-battery, EV, elevator). AutoShop reuse is open-coded via P-label subroutines. OEM machine-builders increasingly default to InoProShop / AM600 to access the FB libraries.

Common Challenges and Solutions:

1. Tuning PID loops for slow thermal processes without causing oscillation

Solution: Structured Text addresses this through Powerful for complex logic.

2. Preventing simultaneous heating and cooling which wastes energy

Solution: Structured Text addresses this through Excellent code reusability.

3. Managing zone interactions in open-plan spaces

Solution: Structured Text addresses this through Compact code representation.

4. Balancing fresh air requirements with energy efficiency

Solution: Structured Text addresses this through Good for algorithms and calculations.

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

Inovance Diagnostic Tools:

InoProShop online mode with full POU monitoring and breakpoint debug,EtherCAT diagnostics page with topology and slave status,Trace tool for analogue / motion signal capture,OPC UA server diagnostics page,Modbus communication trace utility,AutoShop online mode for legacy AC800 / Easy series,Inovance HMI integrated diagnostics for HMI-PLC binding faults,Servo-drive panel diagnostics with InoProShop drive-monitor view,EtherCAT slave-firmware update tool,Project compare tool for change tracking

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

Inovance Structured Text Example for HVAC Control

Illustrative Structured Text example for HVAC Control using Inovance terminology. Adapt the syntax to your InoProShop / AutoShop release, compile it, and verify it in an isolated test environment before use on equipment.

(* Inovance InoProShop / AutoShop - HVAC Control Control *)
(* Structured Text Implementation for Building Automation *)
(* On InoProShop projects, conventions follow CODESYS / IEC norms — Pasca *)

PROGRAM PRG_HVAC_CONTROL_Control

VAR
    (* State Machine Variables *)
    eState : E_HVAC_CONTROL_States := IDLE;
    bEnable : BOOL := FALSE;
    bFaultActive : BOOL := FALSE;

    (* Timers *)
    tonDebounce : TON;
    tonProcessTimeout : TON;
    tonFeedbackCheck : TON;

    (* Counters *)
    ctuCycleCounter : CTU;

    (* Process Variables *)
    rTemperaturesensorsRTDThermocouple : REAL := 0.0;
    rVariablefrequencydrivesVFDs : REAL := 0.0;
    rSetpoint : REAL := 100.0; (* Illustrative value; replace with a reviewed requirement *)
END_VAR

VAR CONSTANT
    (* Building Automation Process Parameters *)
    C_DEBOUNCE_TIME : TIME := T#500MS;
    C_PROCESS_TIMEOUT : TIME := T#30S; (* Illustrative value; verify for the process *)
    C_BATCH_SIZE : INT := 50; (* Illustrative value; replace with a reviewed requirement *)
END_VAR

(* Input Conditioning *)
tonDebounce(IN := bStartButton, PT := C_DEBOUNCE_TIME);
bEnable := tonDebounce.Q AND NOT bEmergencyStop AND bSafetyOK;

(* Main State Machine - Pattern: InoProShop state machines typically use  *)
CASE eState OF
    IDLE:
        rVariablefrequencydrivesVFDs := 0.0;
        ctuCycleCounter(RESET := TRUE);
        IF bEnable AND rTemperaturesensorsRTDThermocouple > 10.0 THEN
            eState := STARTING;
        END_IF;

    STARTING:
        (* Ramp up output - Gradual start *)
        rVariablefrequencydrivesVFDs := MIN(rVariablefrequencydrivesVFDs + 5.0, rSetpoint);
        IF rVariablefrequencydrivesVFDs >= rSetpoint THEN
            eState := RUNNING;
        END_IF;

    RUNNING:
        (* HVAC Control active - HVAC (Heating, Ventilation, and Air Conditioning)  *)
        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:
        rVariablefrequencydrivesVFDs := 0.0;
        (* Log production data - InoProShop on AM600 / H5U supports SD-card logging via library FBs, plus OPC UA streaming for cloud / on-premises historians. Inovance HMIs add CSV logging at HMI tier. AutoShop projects rely on HMI-tier logging exclusively. *)
        eState := IDLE;

    FAULT:
        rVariablefrequencydrivesVFDs := 0.0;
        (* InoProShop alarms are typically defined in the visualisation alarm-configuration page with severity, latching, and acknowledgement behaviour configured per alarm. The runtime maintains active and historical alarm lists. AutoShop projects fall back to M-flag banks with HMI-side alarm logging. *)
        IF bFaultReset AND NOT bEmergencyStop THEN
            bFaultActive := FALSE;
            eState := IDLE;
        END_IF;
END_CASE;

(* Safety Override - Always executes *)
IF bEmergencyStop OR NOT bSafetyOK THEN
    rVariablefrequencydrivesVFDs := 0.0;
    eState := FAULT;
    bFaultActive := TRUE;
END_IF;

END_PROGRAM

Code Explanation:

1.Enumerated state machine (InoProShop state machines typically use IEC SFC steps with action blocks per step, or a state-enum-and-CASE pattern in Structured Text. SFC dominates production-line sequencers; CASE patterns dominate axis-control state and recipe-routing logic. AutoShop projects fall back to FX-style SFC step memory (S0..S511) or D-register integer state.) for clear HVAC Control sequence control
2.Constants use clearly marked illustrative values that must be replaced with reviewed project requirements
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 flags a possible stuck condition for investigation
6.The final override illustrates a software permissive only; it is not a safety-rated function and must not replace a validated safety system

Best Practices

✓Follow Inovance naming conventions: On InoProShop projects, conventions follow CODESYS / IEC norms — PascalCase for
✓Inovance function design: InoProShop strongly favours function-block reuse via the Library Manager — Inova
✓Data organization: InoProShop uses GVLs and persistent variables for shared data. AutoShop uses D /
✓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
✓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 InoProShop / AutoShop: Use InoProShop's online mode to set breakpoints in POUs and step throu
✓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

⚠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
⚠Inovance common error: EtherCAT slave order mismatch after physical re-cabling — slave addressing break
⚠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 Structured Text programs unmaintainable over time

Related Certifications

🏆Inovance Certified Engineer

🏆InoProShop / AutoShop training certificates

🏆EV / Lithium Battery automation specialist tracks

🏆Advanced Inovance Programming Certification

Applying Structured Text to HVAC Control using Inovance InoProShop / AutoShop 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 InoProShop / AutoShop 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

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...

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 Recipe management, Hospital environmental systems, and Inovance platform-specific features for HVAC Control optimization.