SYSTEMS AND METHODS FOR AUTO ADDRESSING IN A CONTROL NETWORK

• US 20110196990A1
• Filed: 02/08/2011
• Published: 08/11/2011
• Est. Priority Date: 02/09/2010
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Chandrasekaran, Geetha, Sundharam, Muthu Lakshmi, Seetharaman, Harini S., Govindaraju, Sangeetha, Kannan, Karthika K., Natesan, VigneshKumar M.R.N., Sankarapandian, Rajesh Kulandaivel KS
• Granted Patent: US 8,489,779 B2
• Time in Patent Office: Days
• US Class Current: 710/9
• CPC Class Codes: G06F 13/42 Bus transfer protocol, e.g. handshake; Synchronisation
• CPC Class Codes: G06F 2213/0052 Assignment of addresses or identifiers to the modules of a bus system
• CPC Class Codes: H04L 12/12 Arrangements for remote connection or disconnection of substations or of equipment thereof
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

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.

Claims

1. A method for assigning network addresses to a plurality of IO devices in a control network, wherein the plurality of IO devices are connected to the controller through a common bus, the method including:

at the controller, maintaining data indicative of a plurality of assignable network addresses;

at a given IO device;

defining a device identification code;

storing the device identification code in local memory; and

providing to the controller data indicative of a request for a network address, wherein the request includes the device identification code;

at the controller;

receiving from the given IO device the data indicative of the request for a network address;

identifying, from the data indicative of a plurality of assignable network addresses, a network address for assignment to the given IO device;

providing to the given IO device data indicative of the identified network address and the device identification code;

maintaining data indicative of the assignment of the identified network address to the given IO device; and

at the given IO device;

receiving from the controller the data indicative of the identified network address and the device identification code;

verifying the received device identification code matches the device identification code stored in local memory; and

in the case that the verification is successful, applying the identified network address.

2. A method according to claim 1 wherein the device identification code includes device data, wherein the device data is locally stored at the given one of the IO devices for communication to the controller, wherein the device data is indicative of at least one of the device type and the device functionality.

3. , A method according to claim 1 wherein the identification code includes a generated identifier.

4. A method according to claim 3 wherein the generated identifier is generated based on a timestamp.

5. A method according to claim 3 wherein the generated identifier is generated based on a network event.

6. A method according to claim 1 wherein the device identification code includes a generated identifier combined with device data, wherein the device data is locally stored at the given one of the IO devices for communication to the controller, wherein the device data is indicative of at least one of the device type and the device functionality.

7. A method according to claim 3 wherein the generated identifier is generated based on a timestamp.

8. A method according to claim 5 wherein the generated identifier is generated based on a network event.

9. A method according to claim 2 wherein the controller uses the device data to facilitate control of the given IO device.

10. A method according to claim 1 wherein the control network is part of a building management system.

11. A control network including:

a controller configured to maintain data indicative of a plurality of assignable network addresses; and

a plurality of IO devices are connected to the controller through a common bus, each IO device being configured to define a device identification code, store the device identification code in local memory, and provide to the controller data indicative of a request for a network address, wherein the request includes the device identification code;

wherein the controller is additionally configured to receive from each IO device the respective data indicative of a request for a network address, identify, from the data indicative of a plurality of assignable network addresses, respective network addresses for assignment to IO devices, respectively provide to the IO devices data indicative of the identified network addresses and the device identification code, and maintain data indicative of the respective assignment of the identified network address to the IO devices; and

wherein the IO devices are additionally configured to receive from the controller the data indicative of the network addresses and associated device identification codes and, in the case that the associated device identification code that stored in local memory, apply the network address.

12. A control network according to claim 11 wherein the device identification code includes device data, wherein the device data is locally stored at the given one of the IO devices for communication to the controller, wherein the device data is indicative of at least one of the device type and the device functionality.

13. A control network according to claim 11 wherein the identification code includes a generated identifier.

14. A control network according to claim 13 wherein the generated identifier is generated based on a timestamp.

15. A control network according to claim 13 wherein the generated identifier is generated based on a network event.

16. A control network according to claim 11 wherein the device identification code includes a generated identifier combined with device data, wherein the device data is locally stored at the given one of the IO devices for communication to the controller, wherein the device data is indicative of at least one of the device type and the device functionality.

17. A control network according to claim 13 wherein the generated identifier is generated based on a timestamp.

18. A control network according to claim 15 wherein the generated identifier is generated based on a network event.

19. A control network according to claim 12 wherein the controller uses the device data to facilitate control of the given IO device.

20. A method for assigning network addresses to a plurality of IO devices in a control network, wherein the plurality of IO devices are connected to the controller through a common bus, the method including operating the controller to auto assign network addresses to the IO devices based on respective messages received from the IO devices, wherein each message includes device data for the respective device, the device data including data indicative of at least one of the device type and the device functionality.