HVAC Subnet Controller Memory Recovery via Parameter Backup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional HVAC systems lack advanced data acquisition and processing techniques, leading to limitations in installation, operation, maintenance, and energy efficiency, as well as challenges in diagnosing and self-repairing capabilities.
Innovation Solution
A distributed-architecture HVAC system with a data bus for communication among components, enabling identity, capability, status, and operational data sharing, and allowing for command issuance, which includes a subnet controller for memory recovery and system synchronization, facilitating easier installation, operation, and self-diagnosis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Difficulty of detecting and measuring
If conventional HVAC systems are used without distributed architecture and advanced data acquisition, then system simplicity is maintained, but diagnostic capability and self-repair capability are insufficient
Solution Approach 1:
The HVAC system is divided into multiple subnets, each with its own subnet controller that can independently diagnose and manage devices within its subnet. This segmentation enables localized diagnostic capabilities without requiring a monolithic complex control system, allowing each subnet to operate semi-autonomously while contributing to overall system diagnostics.
Solution Approach 2:
Subnet controllers act as intermediary devices between individual HVAC devices and the central system. These intermediaries collect data from connected devices, perform local diagnostics, and manage data storage/retrieval operations, thereby enhancing diagnostic capability while distributing complexity across multiple manageable nodes rather than concentrating it in a single complex controller.
2Reliability
If subnet controllers implement memory recovery and data retrieval functions, then system reliability during memory corruption is improved, but controller complexity increases
Solution Approach 1:
The subnet controller maintains a stored list of device parameters in memory that serves as a backup or reference copy. When memory corruption is detected, the controller can retrieve this pre-stored parameter list to restore system functionality. This preliminary action of storing backup parameters enables recovery without requiring complex real-time diagnostic algorithms, thus improving reliability while keeping the recovery mechanism relatively simple.
Solution Approach 2:
The system implements a memory recovery mechanism where corrupted or lost device parameters are retrieved from stored backups. The subnet controller compares current memory contents with stored parameter lists, identifies corruption, and recovers lost data by restoring from the stored copies. This approach provides reliable recovery functionality through a straightforward backup-and-restore process rather than complex real-time error correction.
3Adaptability or versatility
If devices report loss of internal memory settings to the subnet controller, then data recovery capability is enhanced, but communication overhead and processing time increase
Solution Approach 1:
Device parameters and configuration data are pre-stored in the subnet controller's memory during system initialization or commissioning. When a device reports memory loss, the recovery process simply involves retrieving these pre-stored parameters rather than performing complex real-time diagnostics or reconfiguration. This preliminary storage of parameter lists enables rapid recovery by eliminating the need for time-consuming data collection during failure scenarios.
Solution Approach 2:
The subnet controller maintains copied versions of device parameter lists in its memory. When memory corruption is detected on a device, the controller retrieves the corresponding parameter copy from its stored list and transfers it back to the device. This copying mechanism enables fast recovery by using pre-existing data replicas, avoiding the need for time-consuming data reconstruction or manual reconfiguration during recovery operations.
Data Source
AI summary
The disclosure provides a system and method of retrieving data for an active subnet controller of a subnet in an HVAC network. In an embodiment, a device on said subnet reports a loss of internal memory settings to said active subnet controller. The device is recognized by the active subnet controller. At least one list of parameters is requested from the device by the active subnet controller. An order of said at least one list of parameters is employed to convey corresponding stored values of these parameters from the active subnet controller to the coupled device.