SYSTEM FOR INTEGRATING A PLURALITY OF MODULES USING A POWER/DATA BACKBONE NETWORK

• US 20090016216A1
• Filed: 06/06/2008
• Published: 01/15/2009
• Est. Priority Date: 06/06/2007
• Status: Active Grant

• Current Assignee: Veedims, LLC
• Original Assignee: Claudio Ballard
• Inventors: BALLARD, CLAUDIO R., SARGENT, ANDREW P., SEWARD, JEFFREY N.
• Granted Patent: US 7,940,673 B2
• Time in Patent Office: Days
• US Class Current: 370/230
• CPC Class Codes: B60R 16/03 for supply of electrical power to vehicle subsystems or for circuit arrangements for charging batteries H02J7/00
• CPC Class Codes: G06F 1/266 Arrangements to supply power to external peripherals either directly from the computer or under computer control, e.g. supply of power through the communication port, computer controlled power-strips
• CPC Class Codes: G06F 11/3013 where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems testing or monitoring of control systems or parts thereof G05B23/02
• CPC Class Codes: H04L 41/0253 using browsers or web-pages for accessing management information
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) is provided. In one example, the VEEDIMS includes a backbone network formed by cables that are configured to simultaneously carry digital data and power. A controller is coupled to the backbone network and configured to execute control instructions. A plurality of modules are coupled to the controller via the backbone network and receive data and power via the backbone network. The modules receive control signals from the controller based on the control instructions. At least one device is coupled to one of the modules via a direct input/output (I/O) interface positioned in the module. A device specific driver contained in the module provides a communications interface between the device and a generic VEEDIMS controller driver in the controller.

Claims

1. A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) for a vehicle comprising:

a backbone network formed by a plurality of cables, wherein each cable is configured to simultaneously carry digital data and power;

a controller coupled to the backbone network and configured to execute a plurality of control instructions;

a plurality of modules coupled to the controller via the backbone network and configured to receive data and all power needed by the modules via the backbone network, wherein the modules are configured to receive control signals from the controller based on the plurality of control instructions; and

at least one device coupled to a first module of the plurality of modules via a direct input/output (I/O) interface positioned in the first module, wherein a device specific driver contained in the first module provides a communications interface between the device and a generic VEEDIMS controller driver in the controller.

2. The VEEDIMS of claim 1 further comprising a switch positioned in the backbone network between the controller and the first module, wherein the switch is configured to pass the needed power from a power source to the first module and to transfer communications between the first module and the controller.

3. The VEEDIMS of claim 2 wherein the backbone network is Ethernet based and wherein the controller and first module each include a transmission control protocol (TCP) driver for communications between the first module and the controller.

4. The VEEDIMS of claim 2 wherein the switch includes an Ethernet switch.

5. The VEEDIMS of claim 1 wherein the first module further comprises a HyperText Transfer Protocol (HTTP) server.

6. The VEEDIMS of claim 5 wherein the first module further comprises a diagnostics component adapted to obtain diagnostics data about the first module and the device and to make the diagnostics data accessible via the HTTP server.

7. The VEEDIMS of claim 5 wherein the first module further includes a documentation set containing a service history of the first module, and wherein the documentation set is configured to be accessible via the HTTP server.

8. The VEEDIMS of claim 1 wherein the first module further comprises a configuration component adapted to set operational parameters for at least one of the first module and the device.

9. The VEEDIMS of claim 1 wherein the first module further comprises a data acquisition component adapted to acquire data about at least one of the first module and the device.

10. The VEEDIMS of claim 9 wherein the data acquisition component includes an Embedded Component Historian Object (ECHO) coupled to an ECHO driver for sending the acquired data from the first module to the controller.

11. The VEEDIMS of claim 9 wherein the acquired data is stored in a register map in the first module prior to being transferred to a database in the controller.

12. The VEEDIMS of claim 1 wherein the first module is integrated with the device.

13. A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) comprising:

a first controller having a first power interface, a first network/power interface, a first processor coupled to the first power and first network/power interfaces, and a first memory containing a plurality of instructions executable by the first processor, the instructions including controller instructions adapted to control a plurality of modules;

an energy source coupled directly to the first power interface via a first cable adapted to carry only power;

a first switch having a second power interface coupled directly to the energy source via a second cable adapted to carry only power, and a second network/power interface coupled directly to the first network/power interface via a third cable adapted to simultaneously carry both power and data;

a first module of the plurality of modules having a third network/power interface coupled directly to the second network/power interface via a fourth cable adapted to simultaneously carry both power and data, a device input/output (I/O) port, a second processor coupled to the third network/power interface and the device I/O port, and a second memory containing a plurality of instructions executable by the second processor, the instructions including driver instructions adapted to enable communications between the first module and a device coupled to the first module via the device I/O port, wherein the first module is adapted to provide a communication interface between the device and the first controller.

14. The VEEDIMS of claim 13 further comprising a second controller coupled to the first controller via a fifth cable adapted to simultaneously carry both power and data, wherein the first memory contains a plurality of instructions executable by the first processor for balancing a load caused by the plurality of modules between the first and second controllers.

15. The VEEDIMS of claim 13 further comprising a second switch having a third power interface and a fourth network/power interface coupled directly to the second network/power interface via a fifth cable adapted to simultaneously carry both power and data, wherein the second switch is configured to obtain its power from the first switch rather than the power source.

16. The VEEDIMS of claim 15 wherein the first and second switches are configured to pass power from the first switch to the second switch via the fifth cable and to simultaneously pass data from the second switch to the first switch via the fifth cable.

17. The VEEDIMS of claim 13 further comprising a second module having a fourth network/power interface coupled directly to the third network/power interface via a fifth cable adapted to simultaneously carry both power and data, wherein the second module is configured to obtain its power from the first module.

18. The VEEDIMS of claim 13 wherein the second memory further includes instructions for sending a query to the device when the device is first coupled to the first module and sending data resulting from the query to the first controller.

19. The VEEDIMS of claim 13 wherein at least one of the first module and device includes an optical indicator configured to indicate whether the first module or device is operational after being coupled to the first switch or first module, respectively.

20. The VEEDIMS of claim 13 wherein the second memory further includes instructions for sending data describing functionality of the first module to the first controller when the first module is first coupled to the first switch.

21. The VEEDIMS of claim 13 wherein the first switch includes a third processor coupled to the second network/power interface and a third memory containing a plurality of instructions executable by the third processor, the instructions including instructions for determining a power requirement of the device when the device is first coupled to the first module and for determining whether enough power is available to the first switch to meet the power requirement of the device.

22. The VEEDIMS of claim 13 wherein the first module and the device are integrated into a single unit.

23. The VEEDIMS of claim 13 wherein a plurality of devices are coupled to the first module.

24. A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture comprising:

a module positioned in a vehicle and configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to a controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module, wherein the module has a first processor and a first memory containing a first instruction set executable by the first processor, the first instruction set including instructions for providing a HyperText Transfer Protocol (HTTP) server, and wherein the first memory further contains a documentation set containing a service history of the module and a bill of materials for at least one of the module and the device that is accessible via the HTTP server; and

the controller positioned in the vehicle and having a second processor and a second memory containing a second instruction set executable by the second processor, the second instruction set including instructions for receiving data from the module and storing the data in the second memory.

25. The VEEDIMS support architecture of claim 24 wherein the first instruction set further comprises instructions for a diagnostics component configured to obtain diagnostics data about the module and the device and to transfer the diagnostics data via at least one of the HTTP server and the cable.

26. The VEEDIMS support architecture of claim 24 wherein the first instruction set further comprises instructions for a configuration component configured to set operational parameters for at least one of the module and the device.

27. The VEEDIMS support architecture of claim 24 wherein the first instruction set further comprises instructions for a data acquisition component configured to acquire data about at least one of the module and the device.

28. The VEEDIMS support architecture of claim 27 wherein the data acquisition component includes an Embedded Component Historian Object (ECHO) coupled to an ECHO driver for sending the acquired data from the module to the controller via the cable.

29. The VEEDIMS support architecture of claim 24 wherein the first instruction set further comprises instructions for monitoring the device to create a device profile and sending the device profile to the controller.