Distributed HVAC Device Abstraction for Auto Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional HVAC systems lack advanced control and data acquisition techniques, leading to limitations in flexibility, installation ease, user operation, energy efficiency, diagnostic capabilities, and maintenance, requiring more sophisticated system management solutions for improved performance.

Innovation Solution

The implementation of a data processing and communication network within HVAC systems using a subnet controller that assigns equipment type numbers based on device ID numbers and offsets, enabling communication and coordination among components via a data bus, allowing for advanced control algorithms, flexible installation, and intuitive user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional HVAC systems are used with basic thermostat control, then the system structure is simple, but the flexibility, energy efficiency, and diagnostic capabilities are limited

Engineering Contradiction:
Improvesystem flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into multiple independent devices, each with its own microprocessor controller. These devices communicate through a data bus network, allowing modular expansion and configuration. Each device can be independently configured and diagnosed, providing flexibility without requiring complete system redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal communication protocol and data bus structure that can accommodate various HVAC devices (thermostats, sensors, actuators, controllers) with different functions. The system can be configured for different applications (residential, commercial, industrial) using the same basic architecture, enhancing adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of operation

If manual configuration methods are used in conventional HVAC systems, then the device complexity is low, but the installation ease and operation convenience are poor

Engineering Contradiction:
Improveinstallation easeVSAvoidconfiguration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system automatically configures devices and assigns addresses through self-diagnostic routines. When devices are connected to the data bus, they automatically register themselves and receive unique identifiers. The microprocessor controllers perform self-tests and configure communication parameters without manual intervention, significantly easing installation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Devices are pre-programmed with communication protocols and identification data before installation. The system performs preliminary configuration steps automatically upon power-up, including address assignment, capability detection, and communication parameter setup, reducing on-site configuration time and complexity.

Inventive Principle:
Principle #10Preliminary action

3Use of energy by moving object

If basic thermostat control is used, then the system is easy to operate, but the energy efficiency and temperature control precision are limited

Engineering Contradiction:
Improveenergy efficiencyVSAvoidoperation complexity
Core Design Contradiction:
Use of energy by moving objectVSEase of operation

Solution Approach 1:

The system implements continuous feedback loops where sensors monitor temperature, humidity, and system status, and this data is transmitted through the data bus to controllers that adjust operating parameters in real-time. Multiple sensors provide feedback on system performance, enabling optimized energy consumption while maintaining comfort parameters.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically adjusts operating parameters based on real-time conditions. Controllers can modify setpoints, adjust equipment operation modes, and optimize energy consumption patterns according to environmental conditions, occupancy patterns, and system status, moving beyond static on/off control to dynamic optimization.

Inventive Principle:
Principle #15Dynamics

4Ease of repair

If distributed architecture with data bus is implemented, then the diagnostic capabilities and maintenance are improved, but the device complexity increases

Engineering Contradiction:
Improvediagnostic capabilityVSAvoidnetwork complexity
Core Design Contradiction:
Ease of repairVSDevice complexity

Solution Approach 1:

The data bus acts as an intermediary communication medium that connects all devices and enables centralized or distributed diagnostic capabilities. The communication protocol includes diagnostic data transmission, allowing controllers to query device status, retrieve error codes, and monitor system health through the standardized data bus interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces manual diagnostic procedures with electronic self-diagnostic routines executed by microprocessor controllers. Devices automatically test their own components, communicate status through the data bus, and provide digital diagnostic information, eliminating the need for manual inspection and simplifying maintenance despite increased electronic complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentEP2241835B1Device abstraction system and method for a distributed-architecture heating, ventilation and air conditioning system
Publication Date: 2015.06.03 LENNOX IND INC
  • EP2241835B1 patent drawingFigure 1~2
  • EP2241835B1 patent drawingFigure 3~4
  • EP2241835B1 patent drawingFigure 5

AI summary

The disclosure provides an HVAC data processing and communication network and a method of manufacturing the same. In an embodiment, the method includes configuring a subnet controller. The subnet controller is configured to assign to a first device associated with the network a first equipment type number based on a first device ID number and a first offset. The subnet controller is configured, in the event that the first device shares a same enclosure with a second device associated with the network, to assign to the second device a second equipment type number based on the first device ID number and a second offset. The subnet controller is configured, in the event that the first device does not share a same enclosure with the second device, to assign to the second device the second equipment type number based on a second device ID number and the second offset.