HVAC Device Abstraction via Subnet Controllers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional HVAC systems lack advanced control and data acquisition techniques, making them inflexible, difficult to install and maintain, and inefficient in temperature and humidity management.

Innovation Solution

A networked HVAC system with a data bus that allows components to communicate and share identity, capability, status, and operational data, enabling more sophisticated control and diagnostics, and allowing for remote configuration and monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a networked HVAC system with data bus and multiple controllers is implemented, then flexibility and control sophistication are improved, but device complexity increases

Engineering Contradiction:
ImproveflexibilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The HVAC system is divided into multiple independent controllers (subnet controllers) that can operate autonomously. Each controller manages specific zones or equipment, allowing the system to be scaled and configured flexibly without requiring complete system redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The subnet controllers are designed with universal functionality to handle multiple tasks including temperature control, data acquisition, communication protocol management, and device abstraction. This multi-functionality reduces the need for specialized components while maintaining system flexibility.

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

2Ease of operation

If device abstraction and parameter update mechanisms are implemented, then ease of operation and maintenance are improved, but device complexity increases

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A device abstraction layer is introduced as an intermediary between the physical HVAC equipment and the control software. This abstraction layer provides standardized interfaces and parameter management, simplifying operation and maintenance while isolating the complexity within the abstraction layer itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements automatic parameter update mechanisms where subnet controllers monitor and detect parameter changes, then automatically update affected devices. This feedback loop reduces manual intervention requirements while maintaining system complexity within manageable bounds.

Inventive Principle:
Principle #23Feedback

3Productivity

If automatic parameter update and change detection are implemented, then productivity and energy efficiency are improved, but use of energy for data processing increases

Engineering Contradiction:
ImproveproductivityVSAvoiduse of energy by moving object
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The parameter update mechanism operates periodically rather than continuously, with subnet controllers checking for changes at scheduled intervals. This approach maintains system responsiveness and productivity while significantly reducing the energy consumption associated with constant monitoring and data processing.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9432208B2Device abstraction system and method for a distributed architecture heating, ventilation and air conditioning system
Publication Date: 2016.08.30 LENNOX IND INC
  • US9432208B2 patent drawing
  • US9432208B2 patent drawing
  • US9432208B2 patent drawing

AI summary

The disclosure provides an HVAC data processing and communication network and a method of manufacturing the same. In an embodiment, the network includes configuring a first system device and a subnet controller. The first system device is configured to receive an initial value of a specified dependent parameter. The subnet controller is configured to determine that a value of said specified parameter has been changed to a modified value after said first system device receives said initial value. The subnet controller is further configured to send to said first system device, in response to said determining, a message updating said specified parameter with said modified value.