Changeable BACnet Interface via Downloadable Configuration Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing BACnet controllers require resource-intensive run-time object creation, leading to high costs due to the need for processor-intensive resources and extensive overhead, making them expensive to implement.
Innovation Solution
A changeable BACnet interface system that allows a controller object interface to be engineered and downloaded via configuration files, eliminating the need for run-time object creation by using downloadable configuration files that specify supported objects, properties, and storage locations, which can be stored in flash or RAM memory.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If run-time object creation is implemented in BACnet controllers, then the controller can dynamically create and manage BACnet objects during operation, but the resource requirements and implementation costs increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-defining BACnet objects in configuration files before the controller operates. Objects are created during the configuration phase rather than at run-time, which eliminates the need for complex run-time object creation mechanisms while maintaining the ability to have a configurable set of objects.
Solution Approach 2:
The patent uses copying by transferring object definitions from configuration files to the controller's memory during initialization. Instead of creating objects dynamically during operation, the system copies pre-defined object templates from external configuration data, reducing run-time processing requirements.
2Adaptability or versatility
If BACnet objects are created at run-time, then the controller can flexibly adapt to different configurations, but the implementation becomes expensive due to resource requirements
Solution Approach 1:
Configuration flexibility is achieved through pre-defining objects in configuration files during the design phase. The controller loads these pre-configured objects during initialization, maintaining adaptability without requiring expensive run-time object creation capabilities.
Solution Approach 2:
The patent uses simple, lightweight object representations defined in configuration files rather than complex run-time object structures. This approach uses cheaper, simpler data structures that require less processing power and memory, reducing implementation costs while maintaining configurability.
3Adaptability or versatility
If configuration is done at run-time through object creation, then the system can adapt to changes, but the configuration burden falls on the run-time environment
Solution Approach 1:
The patent moves configuration activities to the pre-runtime phase by defining all BACnet objects in configuration files before the controller starts operating. This eliminates the need for time-consuming run-time configuration processing, as objects are already defined and ready for immediate use.
Solution Approach 2:
The patent replaces the mechanical process of run-time object creation with a file-based configuration system. Configuration data is stored in external files and loaded during initialization, substituting the complex run-time object creation mechanism with a simpler file I/O and parsing approach.
Data Source
AI summary
A changeable BACnet interface system having a workstation and a controller. The system may allow a controller object interface to be engineered and downloaded to the controller via configuration files, rather than as individual objects created at run time. A BACnet network may be connected to the workstation and controller. BACnet objects may be designed to constitute an interface to the control application, and be stored in the controller. The BACnet interface may be presented to the BACnet network.