Auto Addressing IO Devices in Building Control Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing building management systems (BMS) face challenges in efficiently managing and auto-addressing input/output (IO) devices connected via bus-based topologies, requiring significant manual effort and lacking scalable solutions for unique network address assignment.
Innovation Solution
A method and system where IO devices define a unique device identification code combining engineering data keys (EDKs) with generated numbers, communicated to a controller to auto-assign network addresses, utilizing a repository of available addresses and timestamp information for uniqueness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a configuration tool is used to manually download device data to the controller, then device configuration can be completed, but significant manual effort is required
Solution Approach 1:
The system enables self-service configuration where IO devices automatically provide their own identification codes and the controller automatically assigns network addresses. The configuration tool merely facilitates this automated exchange, eliminating the need for manual configuration steps while maintaining system reliability.
Solution Approach 2:
Device identification codes are pre-defined in the IO devices during manufacturing. This preliminary action ensures that when devices connect to the controller, they already have unique identifiers ready, eliminating the need for manual configuration of device identities and enabling immediate automated address assignment.
2Adaptability or versatility
If IO devices are connected via bus-based topology, then system scalability is improved, but complications arise in assigning unique network addresses
Solution Approach 1:
The controller acts as an intermediary that receives identification codes from multiple IO devices on the bus, maintains a repository of available network addresses, and automatically performs the matching and assignment process. This intermediary function simplifies the addressing complexity by centralizing the assignment logic in the controller rather than requiring complex peer-to-peer addressing protocols.
Solution Approach 2:
The system implements a feedback mechanism where IO devices send requests for network addresses to the controller, the controller assigns addresses from its repository, and the devices confirm receipt. This feedback loop ensures unique address assignment while maintaining bus-based topology flexibility, as each device receives confirmed unique addressing through the controller's centralized management.
3Reliability
If manual configuration is used for each device, then unique device identification can be ensured, but the process requires significant manual effort
Solution Approach 1:
Each IO device serves itself by providing its pre-defined identification code to the controller during the connection process. This self-service approach ensures that each device's unique identity is automatically recognized and recorded by the controller without requiring manual intervention, thereby maintaining reliability while dramatically reducing configuration effort.
Solution Approach 2:
The controller creates a digital copy of the device identification code in its repository, associating it with the assigned network address. This copying mechanism ensures that the unique device identity is preserved and stored centrally, maintaining the reliability of unique identification while eliminating the need for manual configuration of each device's identity.
Data Source
AI summary
Described herein are systems and methods for device management, and more particularly systems and methods for auto addressing in a control network. For example, some embodiments relate to procedures and protocols implemented in the context of a building management system thereby to allow auto addressing of IO devices. In one embodiment, each IO device includes a respective engineering data key (EDK), which is indicative of device data such as the device type and function. This EDK is combined with a generated number thereby to define a device identification code that has significant chances of uniqueness. The device identification code is communicated to a controller to which the IO device connects in a bus-based topology. The controller uses the identification code to assign a network address to the IO device, using a stored repository of network addresses available for such assignment.