Learn PLCs free
Intermediate15 min readBuilding Automation

Inovance Data Types for HVAC Control

Learn Data Types programming for HVAC Control using Inovance InoProShop / AutoShop. Includes code examples, best practices, and step-by-step implementation guide for Building Automation applications.

πŸ’»
Platform
InoProShop / AutoShop
πŸ“Š
Complexity
Intermediate
⏱️
Project Duration
2-4 weeks

Optimizing Data Types performance for HVAC Control applications in Inovance's InoProShop / AutoShop requires understanding both the platform's capabilities and the specific demands of Building Automation. This guide focuses on proven optimization techniques that deliver measurable improvements in cycle time, reliability, and system responsiveness.

Inovance's InoProShop / AutoShop offers powerful tools for Data Types programming, particularly when targeting intermediate applications like HVAC Control. With ~2% global, top-3 in China market share and extensive deployment in industrial automation, Inovance has refined its platform based on real-world performance requirements from thousands of installations.

Performance considerations for HVAC Control systems extend beyond basic functionality. Critical factors include 5 sensor types requiring fast scan times, 5 actuators demanding precise timing, and the need to handle energy optimization. The Data Types approach addresses these requirements through memory optimization, enabling scan times that meet even demanding Building Automation applications.

This guide dives deep into optimization strategies including memory management, execution order optimization, Data Types-specific performance tuning, and Inovance-specific features that accelerate HVAC Control applications. You'll learn techniques used by experienced Inovance programmers to achieve maximum performance while maintaining code clarity and maintainability.

Inovance InoProShop / AutoShop for HVAC Control

Inovance ships InoProShop as its primary programming IDE for the AM600 / AM610 / H5U medium-PLC families and AutoShop for the Easy-series compact PLCs. InoProShop is built on the CODESYS 3.5 platform, which means engineers transferring from Beckhoff TwinCAT, WAGO e!Cockpit, or Schneider EcoStruxure Machine Expert will recognise the project tree, IEC 61131-3 editors, and visualisation tools immediately. AutoShop is a more traditional ladder-and-IL editor closer to compact-PLC tradition. Inovance'...

Platform Strengths for HVAC Control:

  • CODESYS-based InoProShop for IEC 61131-3 compliance

  • Tight integration with Inovance servo drives and inverters

  • Strong motion, robotics, and elevator-control product lines

  • EtherCAT support across mid-tier and high-end CPUs


Unique ${brand.software} Features:

  • InoProShop built on CODESYS 3.5 β€” full IEC 61131-3 compliance

  • Native EtherCAT motion across mid-tier and high-end CPUs

  • Tight integration with Inovance servo drives, inverters, and HMIs

  • AutoShop for compact AC800 / Easy-series CPUs (lighter IDE)


Key Capabilities:

The InoProShop / AutoShop environment excels at HVAC Control applications through its codesys-based inoproshop for iec 61131-3 compliance. This is particularly valuable when working with the 5 sensor types typically found in HVAC Control systems, including Temperature sensors (RTD, Thermocouple), Humidity sensors, Pressure sensors.

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


Inovance's controller families for HVAC Control include:

  • AM600: Suitable for intermediate HVAC Control applications

  • AM610: Suitable for intermediate HVAC Control applications

  • H5U: Suitable for intermediate HVAC Control applications

  • AC800: Suitable for intermediate HVAC Control applications

Hardware Selection Guidance:

Inovance CPU choice ranges from Easy320 / Easy510 (compact, AutoShop-programmed, FX-style memory model) through AC800 (mid-range compact) to AM600 / AM610 / H5U (medium PLC with EtherCAT, OPC UA, redundant networking on H5U). AM600 is the volume product for OEM machinery; H5U is the choice for higher-axis-count motion applications and lithium-battery / EV manufacturing lines where EtherCAT and tig...

Industry Recognition:

High in China across textiles, packaging, lithium battery, EV manufacturing, elevators, robotics; growing in SE Asia and MEA. High in Chinese EV manufacturing β€” Inovance is a major automation supplier to BYD, NIO, and Tier 2/3 EV-component plants. AM600 + H5U with EtherCAT motion controls battery-cell assembly, module welding, pack assembly, and end-of-line test stations. Less common in Western Tier 1 automotive but appear...

Investment Considerations:

With $$ pricing, Inovance positions itself in the mid-range segment. For HVAC Control projects requiring intermediate skill levels and 2-4 weeks development time, the total investment includes hardware, software licensing, training, and ongoing support.

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 InoProShop / AutoShop follows these key principles:

1. Structure: Data Types organizes code with type safety
2. Execution: Scan cycle integration ensures 5 sensor inputs are processed reliably
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 Inovance InoProShop / AutoShop.

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 Inovance InoProShop / AutoShop 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 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: 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:

  • Scan Time: Optimize for 5 inputs and 5 outputs

  • Memory Usage: Efficient data structures for AM600 capabilities

  • Response Time: Meeting Building Automation requirements for HVAC Control

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

Inovance's InoProShop / AutoShop provides tools for performance monitoring and optimization, essential for achieving the 2-4 weeks development timeline while maintaining code quality.

Inovance Data Types Example for HVAC Control

Complete working example demonstrating Data Types implementation for HVAC Control using Inovance InoProShop / AutoShop. Follows Inovance naming conventions. Tested on AM600 hardware.

// Inovance InoProShop / AutoShop - HVAC Control Control
// Data Types Implementation for Building Automation
// On InoProShop projects, conventions follow CODESYS / IEC nor

// ============================================
// 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;

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

Code Explanation:

  • 1.Data Types structure optimized for HVAC Control in Building Automation applications
  • 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.Code runs every scan cycle on AM600 (typically 5-20ms)

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 /
  • βœ“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 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 InoProShop / AutoShop simulation tools 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
  • ⚠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 Data Types programs unmaintainable over time

Related Certifications

πŸ†Inovance Certified Engineer
πŸ†InoProShop / AutoShop training certificates
πŸ†EV / Lithium Battery automation specialist tracks

Mastering Data Types for HVAC Control applications using Inovance InoProShop / AutoShop requires understanding both the platform's capabilities and the specific demands of Building Automation. This guide has provided comprehensive coverage of implementation strategies, working code examples, best practices, and common pitfalls to help you succeed with intermediate HVAC Control projects.

Inovance's ~2% global, top-3 in China market share and high in china across textiles, packaging, lithium battery, ev manufacturing, elevators, robotics; growing in se asia and mea demonstrate the platform's capability for demanding applications. The platform excels in Building Automation applications where HVAC Control reliability is critical.

By following the practices outlined in this guideβ€”from proper program structure and Data Types best practices to Inovance-specific optimizationsβ€”you can deliver reliable HVAC Control systems that meet Building Automation requirements.

Next Steps for Professional Development:

1. Certification: Pursue Inovance Certified Engineer to validate your Inovance expertise
2. Advanced Training: Consider InoProShop / AutoShop training certificates for specialized Building Automation applications
3. Hands-on Practice: Build HVAC Control projects using AM600 hardware
4. Stay Current: Follow InoProShop / AutoShop updates and new Data Types features

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

The 2-4 weeks typical timeline for HVAC Control projects will decrease as you gain experience with these patterns and techniques. Remember: Use slow integral action for temperature loops to prevent hunting

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