Methods and systems for identifying and configuring networked devices

• US 8,392,764 B2
• Filed: 11/16/2009
• Issued: 03/05/2013
• Est. Priority Date: 11/16/2009
• Status: Active Grant

• Current Assignee: Eaton Intelligent Power Limited (Eaton Corporation PLC.)
• Original Assignee: Cooper Technologies Company (Eaton Corporation PLC.)
• Inventors: de Buen, Peter
• Primary Examiner(s): MCCARTHY, CHRISTOPHER S
• Application Number:
  US12/619,344
• Publication Number:
  US 20110119556A1
• Time in Patent Office: 1,205 Days
• Field of Search: None
• US Class Current: 714/44
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0809 Plug-and-play configuration
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies

Abstract

Auto-detection and configuring systems and methods for interconnected, position dependent control devices are disclosed. Embedded identification and configuration keys are associated with each of the control devices in a network, such that specific connection nodes for each controller may be determined by electronically reading the identification as the control devices are installed. Hardware and software compatibility issues may be detected and resolved, including self configuring of the control devices with the proper software where possible. Otherwise, error conditions are signaled.

Claims

1. A control system network comprising:

a communication link;

a plurality of interchangeable and replaceable control devices each connected to the communication link and operatively connectable to at least one input/output device of a controlled system; and

an identification key associated with each respective control device, each identification key including configuration data corresponding to the respective control device, each identification key being electronically readable by one of the control devices when introduced to the network;

wherein each identification key includes a first data structure including configuration data and information, each control device including a second data structure including data and information stored in the control device, each control device configured to compare information from the first data structure to information in the second data structure to evaluate a compatibility of the control device with the network; and

wherein if information from the first data structure does not match information in the second data structure when a control device is introduced to the network, the control device is configured to invalidate the information in the second data structure and request correct configuration data and software from another of the control devices on the network.

2. The control system network of claim 1, wherein the plurality of interchangeable and replaceable control devices are electronic control units.

3. The control system network of claim 2, wherein each of the electronic control units is associated with a respective subsystem of input/output devices of the controlled system.

4. The control system network of claim 3, wherein each of the electronic control units is configured to operate all of the respective subsystems of the controlled system.

5. The control system network of claim 1, wherein the communication link comprises a bus.

6. The control system network of claim 1, wherein each identification key is embedded in the network at a fixed location.

7. The control system network of claim 6, wherein the control system includes at least one wiring harness, and at least one of the identification keys is integrated with the wiring harness.

8. The control system network of claim 1, wherein each of the interconnected devices performs at least one specific task, the specific task being dependent on a connection location in the control system.

9. The control system network of claim 1, wherein the first data structure includes a first cyclic redundancy check code (CRC) and the second data structure includes a second cyclic redundancy check (CRC) code, each control device configured to compare the first CRC to the second CRC to determine a compatibility of the control device when introduced to the network.

10. The control system network of claim 1, wherein the first and second data structure includes configuration data for the control devices.

11. The control system network of claim 1, wherein if information from the first data structure matches information in the second data structure when a control device is introduced to the network, the control device is configured to enter a normal operation mode.

12. The control system network of claim 1, wherein each identification key is separately supplied from each respective control device.

13. A method of detecting compatibility of an introduced control device in a control system network including a plurality of connection nodes and the introduced control device operable at each of the plurality of connection nodes, the introduced control device having first configuration data stored therein, the method comprising:

providing an identification key at an embedded location in the network, the identification key including second configuration data for the introduced control device at the embedded location;

reading the second configuration data from the identification key with the introduced control device;

determining, with the introduced control device, a respective one of the nodes to which the control device has been connected based upon the second configuration data from the identification key;

the introduced control device comparing a first parameter from the first configuration data with at least a second parameter from the second configuration data; and

if the first parameter from the first configuration data matches the second parameter from the second configuration data, the introduced control device entering a normal operation mode.

14. The method of claim 13, wherein comparing a first parameter from the first configuration data with at least a second parameter from the second configuration data comprises comparing a first cyclic redundancy check (CRC) value from the first configuration data with a second cyclic redundancy check (CRC) value from the second configuration data.

15. The method of claim 13, further comprising:

comparing, with the introduced control device, hardware and software parameters from the first configuration data to hardware and software parameters from the second configuration data if the first parameter from the first configuration data does not match the second parameter from the second configuration data.

16. The method of claim 15, wherein if one of the hardware and software parameters from the first configuration data matches one of the hardware and software parameters from the second configuration data, the introduced control device invalidating data stored thereon.

17. The method of claim 16, further comprising:

the introduced control device requesting software from another control device on the network.

18. The method of claim 17, further comprising:

the introduced control device entering a normal operation mode.

19. The method of claim 15, further comprising:

if none of the hardware and software parameters from the first configuration data matches the hardware and software parameters from the second configuration data, the introduced control device enters an error mode.

20. The method of claim 13, wherein providing an identification key at an embedded location in the network comprises attaching the identification key to a wiring harness.

21. The method of claim 13, wherein in the normal operation mode the control device functions to control a subsystem of a vehicle.

22. The method of claim 13, wherein the introduced control device includes application software, and the introduced control device executing a portion of the software corresponding to its installed location in the network.

23. A control system comprising:

a plurality of interchangeable and replaceable control devices each operatively connectable to at least one input/output device of a controlled subsystem at one of a plurality of connection nodes, the control devices configured to operate at all of the plurality of connection nodes via different software routines corresponding to at least some of the connected nodes;

a communication link facilitating communication between at least two of the plurality of control devices; and

a plurality of identification keys each associated with a respective one of the control devices, each identification key including configuration data for a respective one of the plurality of connection nodes, and one of the identification keys being electronically readable by each of the control devices when introduced to the network;

wherein each of the plurality of control devices is configured to determine, based on a reading of the associated identification key, hardware and software compatibility with the network, and

if determined to be compatible, each of the control devices further configured to;

determine a respective one of the plurality of connection nodes to which the control device has been connected, and

execute applicable software routines corresponding to the node where the control device has been connected.

24. The system of claim 23, wherein the controlled subsystem comprises a vehicle subsystem, and the plurality of interchangeable and replaceable control devices comprise electronic control units (ECUs).

25. The system of claim 24, wherein each of the ECUs is self configuring with current application software for the respective one of the plurality of connection nodes where it has been connected.

26. The system of claim 24, wherein the plurality of identification keys are each embedded in a plurality of fixed locations proximate the connection nodes.

27. The system of claim 26, wherein the identification keys are attached to respective ones of a plurality of wiring harnesses.

28. The system of claim 24, wherein each ECU includes a data structure having multiple sections, and each of the identification keys include a data structure corresponding to one of the sections of each ECU.