JP2011522443A - System for integrating multiple modules using a power / data backbone network - Google Patents

Abstract

  A virtual electrical / electronic device interface and management system (VEEDIMS) is provided. In one embodiment, VEEDIMS comprises a backbone network formed by a plurality of cables configured to carry digital data and power simultaneously. A controller is connected to the backbone network and configured to execute a plurality of control instructions. A plurality of modules are connected to the controller via the backbone network and receive data and power via the backbone network. The module receives a control signal from the controller based on the control command. At least one device is connected to one of the modules via a direct input / output (I / O) interface located within the module. A device specific driver housed in the module provides a communication interface between the device and the generic VEEDIMS controller driver in the controller.

Description

[Cross-reference of related applications]
This application is filed on June 6, 2007, US Patent Application No. 60 / 933,358 entitled “VIRTUAL ELECTRICAL AND ELECTRONIC DEVICE INTERFACE AND MANAGEMENT SYSTEM”, and “July 6, 2008”. Claims priority to US patent application Ser. No. 12 / 134,424 entitled “SYSTEM FOR INTEGRATING A PLURALITY OF MODULES USING A POWER / DATA BACKBONE NETWORK”, which is hereby incorporated by reference.

  The following disclosure relates to control systems, and more particularly to providing and controlling modular functionality over a power / data backbone.

Background As is well known, it is not uncommon for power and communication components to be formed as automation islands, especially in vehicles, in which case Communication and power distribution is limited or not performed at all. For example, vehicle electrical systems are typically limited to unbent wire harnesses and isolated components, which makes problem solving and repair difficult. Therefore, there is a need for a system that can provide and control a network integrating power and data and the corresponding modular components.

SUMMARY OF THE INVENTION In one embodiment, a Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) for a vehicle is provided. VEEDIMS comprises a backbone network, a controller, a plurality of modules, and at least one device. The backbone network is formed by a plurality of cables, each cable configured to carry digital data and power simultaneously. The controller is connected to the backbone network and is configured to execute a plurality of control instructions. The plurality of modules are connected to the controller via a backbone network and configured to receive data and total power required by the module via the backbone network. The module is configured to receive a control signal from a controller based on a plurality of control instructions. The device is connected to the first module via a direct input / output (I / O) interface disposed within the first module of the plurality of modules. A device specific driver housed in the first module provides a communication interface between the device and the generic VEEDIMS controller driver in the controller.

  In another embodiment, a virtual electrical / electronic device interface and management system (VEEDIMS) is provided. The VEEDIMS includes a first controller, an energy source, a first switch, and a first module. The first controller includes a first power interface, a first network / power interface, a first processor connected to the first power interface and the first network / power interface, and a first processor. And a first memory containing a plurality of instructions executable by the controller, the instructions including controller instructions adapted to control the plurality of modules. The energy source is directly connected to the first power interface via a first cable adapted to carry only power. The first switch is adapted to carry both power and data simultaneously with a second power interface connected directly to the energy source via a second cable that is intended to carry only power. And a second network / power interface connected directly to the first network / power interface via a third cable. A first module of the plurality of modules is a third network directly connected to the second network / power interface via a fourth cable adapted to carry both power and data simultaneously. Executable by the second processor / power interface, a device input / output (I / O) port, a second processor connected to the third network / power interface and the device I / O port A second memory containing a plurality of instructions, wherein the instructions enable communication between the first module and a device connected to the first module via a device I / O port Contains driver instructions that are supposed to be The first module is configured to provide a communication interface between the device and the first controller.

  In yet another embodiment, a virtual electrical / electronic device interface and management system (VEEDIMS) support architecture is provided. The VEEDIMS support architecture includes a module and a controller. The module is located in the vehicle and is configured to connect to the device via an input / output (I / O) interface that is compatible with the device so as to simultaneously carry bidirectional data and unidirectional power to the module. It is configured to connect to the controller via a cable. The module includes a first processor and a first memory including a first instruction set executable by the first processor, the first instruction set providing a hypertext transfer protocol (HTTP) server. The first memory further includes a documentation set including a service history of the module and a bill of materials for at least one of the module and the device accessible via an HTTP server. Including. The controller is disposed in the vehicle and includes a second processor and a second memory including a second instruction set executable by the second processor, wherein the second instruction set includes the module And instructions for storing the data in the second memory.

  For a more complete understanding, reference is now made to the following description, taken in conjunction with the accompanying drawings.

FIG. 2 illustrates software and hardware layers that may be present in one embodiment of a virtual electrical / electronic device interface and management system (VEEDIMS) control environment (VCE). FIG. 2 is a diagram illustrating one possible configuration of hardware layers in one embodiment of the VCE of FIG. FIG. 3 is a diagram illustrating another possible configuration of hardware layers in one embodiment of the VCE of FIG. 1. FIG. 2 is a block diagram illustrating one embodiment of a VEEDIMS controller that can be used in the VCE of FIG. FIG. 2 is a block diagram illustrating one embodiment of a VEEDIMS switch that can be used in the VCE of FIG. FIG. 2 is a block diagram illustrating one embodiment of a VEEDIMS module that can be used in the VCE of FIG. FIG. 2 illustrates one embodiment of a system architecture that may incorporate aspects of the VCE of FIG. FIG. 2 illustrates one embodiment of a vehicle that can use the VCE of FIG. FIG. 9 illustrates one embodiment of the VCE of FIG. 1 disposed within the vehicle of FIG. FIG. 2 is a diagram illustrating one embodiment of a structure that can use the VCE of FIG. 1.

  Referring now to the drawings, wherein like reference numerals are used to refer to like components throughout, a system for integrating multiple modules using a power / data backbone network Various figures and embodiments of methods and methods are illustrated and described, and other possible embodiments are described. The drawings are not necessarily drawn to scale, in some cases the drawings are exaggerated and / or simplified for illustrative purposes only. Those skilled in the art will appreciate the many possible applications and variations based on the following example embodiments that can be implemented.

  The following disclosure describes providing and controlling an integrated power and data network and corresponding modular components for all or part of a vehicle or structure. The term “vehicle” may include any man-made mechanical or electromechanical system (eg, motorcycle, automobile, truck, boat and aircraft) that can move, while the term A “structure” may include any artificial system that cannot move. In the present disclosure, both vehicles and structures are used for illustrative purposes, but it is to be understood that the teachings of the present disclosure can be applied to many different environments and various conditions within a particular environment. Accordingly, the present disclosure can be applied to vehicles and structures in the terrestrial environment, including manned and remotely controlled land vehicles, and ground and underground structures. The present disclosure also includes ships and other manned and remotely controlled vehicles and stationary structures (eg, oil platforms and submersible survey facilities) designed for use on or under water. It can also be applied to vehicles and structures. The present disclosure can also be applied to vehicles and structures in the aerospace environment, including manned and remotely controlled aircraft, spacecraft and satellites.

  Referring to FIG. 1, in one embodiment, a virtual electrical / electronic device interface and management system (VEEDIMS, or represented herein simply by prefixing it with the letter “V”) Control Environment (VCE) 100. Is exemplified. VCE 100 may include software components and hardware components arranged within software layer 102 and hardware layer 104 to provide distributed local-level intelligence. The software layer 102 may include a VEEDIMS controller (V controller) layer 106, a VEEDIMS network (V net) transport layer 108, and a VEEDIMS module (V module) driver layer 110. The hardware layer 104 may include one or more V controllers 112, a VCE power supply 114, a VEEDIMS switch (V switch) 116, and a V module 118, with connections between various hardware components. Provided by V net cable 120 and / or VEEDIMS power (V power) cable 122.

  The software layer 102 provides control instructions to the hardware layer 104, which is required to operate, collect data, monitor and report events, and provide a VEEDIMS operating environment (VOE). Allow other functions to be performed. The actual physical location of the functions provided by the software layer 102 may vary depending on the configuration of the VCE 100. For example, certain software functions may be located in the V controller 112 or in the V module 118 depending on the configuration.

  The V controller layer 106 includes a VEEDIMS controller kernel that executes a VEEDIMS controller driver (not shown), among other functions. The VEEDIMS controller driver is a software module that is configured to interact with the V module 118, as described below, to directly move and manage the electrical / electronic system operating within the VCE 100, Further monitoring. The VEEDIMS controller driver is a high level driver that can be relatively general purpose, and more specialized drivers (eg, in the V module driver layer 110) are physical and high level drivers. Is provided in a lower software layer that interprets communications to and from the various component interfaces.

  The V-net transport layer 108 can be based on an open protocol, such as an optimized version of the Ethernet protocol, carries broadcast and / or addressable V-net traffic, and is a high-speed VCE 100. Support real-time operation ability. V net traffic is in packet form, and the term “packet” as used in this disclosure may include any type of encapsulated data, including datagrams, frames, packets, etc. Information may include audio, video, data and / or other information. Some or all of the V net traffic may be encrypted.

  The V-net transport layer 108, along with the V-net backbone (discussed later), allows high-bandwidth networks to be used to integrate network communications down to individual input / output (I / O) levels. This is in contrast to conventional vehicle networking techniques that apply networking globally to serve a very specific purpose for a given subsystem in the vehicle. In addition to Ethernet, other protocols that may be used by the V-net transport layer 108 are Transmission Control Protocol / Internet Protocol (TCP / IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Modbus (serial communication protocol published by Modicon), Bluetooth, Firewire, Controller Area Network (CAN) and FlexRay. For example, VEEDIMS can use Modbus TCP as the de facto standard for Ethernet communication, and can use Modbus as the de facto standard for serial communication, and other application-specific lower level protocols use Modbus TCP as a gateway. Can be accessed.

  The V module driver layer 110 is configured to interact with the internal hardware of the V module 118 and devices physically connected to the V module internal hardware, as will be described in further detail below. These can be device specific drivers written to allow a particular subsystem (eg, V module 118 and device / component) or device to function within VCE 100.

  The hardware layer 104 provides a hardware platform on which the software layer 102 can run and also provides communication and power links between the various subsystems and components. The V controller 112 executes the VEEDIMS controller kernel, which is part of the V controller layer 106 and is responsible for managing the VOE. V-controller 112 has overall responsibility for mission-critical tasks and has functionally common parts to minimize problems that can be caused when one V-controller becomes inoperative Can do.

  One or more VCE power supplies 114 can provide electrical energy to all components in VCE 100, either directly or indirectly. The VCE power supply 114 may be connected to a power distribution network formed by a V net cable 120 and a V power cable 122, which will be described later. The power distribution network may be a high quality (eg, aerospace level) power distribution network. This high quality power distribution network protects components and wiring using supervised magnetic hydraulic circuit breakers and cycle-by-cycle or foldback current limiting electronics. And promote diagnosis and failure recovery. Surveillance may include steps to be taken to immediately instruct the vehicle operator why the electrical system has failed and to solve the problem. Current foldback can be used to limit electrical failures to the subsystem, thereby suppressing the failure and providing the vehicle with the maximum possible functionality even in the event of a failure. it can.

  The V switch 116 includes a physical enclosure that allows the V switch to serve as a conduit for V net traffic between the V controller 112 and the V module 118. The electronic circuits and connectors required for the purpose are accommodated. The V switch also distributes the power received from the VCE power supply 114 (ie, V power current) to the V module.

  The V module 118 allows any electrical / electronic device to connect to the VCE 100 via a V net backbone (ie, network or multi-drop communication bus) formed by the V switch 116 and the V net cable 120, and to connect to the VCE 100 for digital data and power connections. It is an individual electric / electronic equipment interface module designed to be able to have In some embodiments, the V module 118 may include at least limited control functions.

  The interconnection within VCE 100 is provided by V net cable 120 and V power cable 122. V net cable 120 is a physical V net distribution wiring medium that can provide a digital signal path and direct current (DC) voltage interconnection between V controller 112, V switch 116 and V module 118. The V power cable 122 is a physical power distribution wiring medium dedicated to supplying a high amperage DC voltage from the VCE power supply 114 to the V controller 112 and the V switch 116.

  The functions provided by the V net cable 120 and the V power cable 122 may vary depending on the particular VCE 100. For example, some VCE implementations require only 12 volt DC power to be applied, while higher voltages (e.g., 110/220 VAC at 24 volts DC, 48 volts DC or 50/60 Hz) can be applied. Some are needed. In VCE implementations with high power requirements (required power), dedicated V switches 116, V modules 118, V net cables 120 and V power cables 122 may be provided. The dedicated one is identified by using a color-coded cable and a key connector having a different configuration, and the risk of connecting the V switch 116 and the V module 118 that are not compatible with each other can be avoided.

  One embodiment of the V-net cable 120 is formed as an integrated single cable connector assembly that combines power distribution and data networking capabilities. The assembly meets certain waterproof and dustproof protection standards (e.g., qualifies as an IP-67 or similar level of protective seal) and provides a durable interface to the V module 118 or subsystem within the VCE 100. May include water-resistant connectors. The connector can have a specific power distribution level as described above (eg, 12, 24 or 48 volts DC or 110/220 VAC 50/60) and a non-polar contact capable of carrying the required current; And network connectors designed for use with multiple high performance protocols. The V net cable connector can accommodate various levels of Ethernet (eg, 10baseT, 100baseT, and 1000baseT). Other embodiments may also support protocols such as Universal Serial Bus (USE) protocol, Firewire, CAN and FlexRay in addition to or instead of Ethernet. The connector shell of the V net cable assembly can be manufactured to aerospace standards from a corrosion resistant material having a temperature rating suitable for harsh application environments. Matched jacketed cable assemblies can be used that have a sufficient shielding effect to maintain crosstalk or other noise at a level that does not interfere with V-net data traffic.

  The V net cable 120 integrates neutral wiring into a single cable concept to prevent ground loops, reduce noise and increase reliability. To date, cars, ships, aircraft and similar environments have used vehicle metal chassis as a return path for DC operating voltages. This is mainly done as a cost-saving measure, but can lead to downstream failures. For example, electrical connections to ground can have different potentials depending on the finish and composition of the material used, which can still further corrode even in harsh operating environments. The electrical resistance of a circuit can fluctuate over time, resulting in a fluctuating voltage flowing through the same common ground, which often causes electrical noise between circuit paths. Thus, by using the V-net cable 120, an airtight and reliable connection designed to isolate the electrical circuit return path and minimize or eliminate the induced electrical crosstalk VEEDIMS minimizes or eliminates these problems by configuring the V net cable as a protective ground wire having

  It should be understood that many different types of communication media may be used, including copper wire and optical fiber, in addition to or as an alternative to V-net cable 120. If optical fibers are used, the VCE 100 V module 118 or another component can perform fiber / copper conversion and copper / fiber conversion.

  Still referring to FIG. 2, in another embodiment, another possible configuration of the hardware layer 104 of FIG. 1 is shown. In this example, the V controller 112 is connected to the VCE power supply 114 via the V power cable 112 and is connected to the V switch 116 via the V net cable 120. The VCE power supply 114 is also connected to the V switch 116. This is because the V net cable 120 may not carry power and / or components such as the V module 118 where the V net cable 120 depends on the V switch and the V switch to obtain power. This is because the required amount of power may not be supplied. The V module 118 is connected only to the V switch 116, but may be connected to other V modules as described below. Although not shown in the figure, in some embodiments, the V controller 112 may be connected directly to the V module 118 (ie, without the intervening V switch 116). One or both of the V controller 112 and the V switch 116 can communicate with the VCE power supply 114 to determine how much power is available, return power demand to the VCE power supply, and control the power level. it can.

  In addition to being connected to the V switch 116, the V module 118 may be connected to the subsystem / device 200 via an input / output (I / O) interface 202, which interface is connected to a V net cable. 120, or another bus-based I / O interface, an analog I / O interface, and / or a digital I / O interface. Subsystem / device 200 is shown as being external to VCE 100 in this example, but can also be part of VCE. V-module 118 can be integrated with subsystem / device 200 to form a single subsystem, or can be separate as shown in the figure.

  By automatically integrating the V module or subsystem / device with the VCE after the V module 118 or subsystem / device 200 is plugged into the V net backbone, the VCE 100 is put into a “plug and run” function. Can respond. The integration status of the V module 118 or subsystem / device 200 and the VCE 100 may be indicated by a light emitting diode (LED) or another indicator. For example, when subsystem 200 is connected to a V net backbone, a certain LED color of the subsystem can indicate the integration status of that subsystem. The red LED indicates that the subsystem 200 is not integrated with the VCE 100 (eg, due to lack of available power), and the green LED indicates that the subsystem can be integrated and used. Instruct. If it is not integrated when it is first plugged in, for example, if the subsystem 200 becomes available for power, the LED color may change from red to green.

  The VCE 100 can also support self-publishing. In self-publishing, new components such as V-module 118 or VEEDIMS-enabled subsystems or devices (eg, subsystems or devices that incorporate at least basic V-module functionality therein) are added to the V-net backbone. When connected, the new component can publish its “personality” (eg, power demand, capacity and other information). Alternatively, the V-controller 112 or another component can query the new component to determine its personality. If the new component is a member of a class (described later), the VCE 100 may already have certain information about the new component (eg, maximum power consumption). Thus, until now, in order to add a new component as a part to the VCE 100, it has often been necessary to input information about the new component into the VCE. For example, a new component can simply be plugged into the V net backbone, after which the VCE identifies relevant information about the new component.

  The VCE 100 can support automatic updating. Auto-update allows new components such as V module 118, or VEEDIMS-enabled subsystems or devices (eg, subsystems or devices that incorporate at least basic V module functionality) into the V net backbone. When connected, the new component can send information to update the higher control level of the VOE for the new component. This avoids human error in entering information about new components.

  The VCE 100 can support efficient power usage by power distribution. In power distribution, new components such as V module 118 or VEEDIMS-enabled subsystems or devices (eg, subsystems or devices that incorporate at least basic V module functionality therein) are added to the V net backbone. When connected, another component such as V controller 112 or V switch 116 can determine whether there is sufficient power to operate the new component. This determination can be based on the operating specifications of the new component, which may be published by the new component when the new component is connected, or new May be obtained by querying the component. If sufficient power is available, the amount of available power is reduced and new components are accepted into the VCE 100 as active. The available power is either because the required power of the new component is greater than the available power or because a certain amount of power is reserved and not available for use by the new component If not, the new component is deactivated until access to the VCE 100 is denied or sufficient power is available.

  If the new component is not VEEDIMS compliant, the V module 118 into which the component is plugged in can perform a test to determine the power usage of the new component, or power is available Can be simply assigned a certain level of power. For example, if a non-VEEDIMS capable fan is plugged into the V module 118, the fan cannot publish information about its personality and cannot be queried to find such information. . Thus, V-module 118 monitors fan operation to identify power requirements and current, temperature, and other similar information, create a profile for the fan, and prevent short circuits and other problems. Can do. The V module 118 can then update the VOE with its profile information, thereby acting as a VEEDIMS proxy and providing at least basic VEEDIMS functionality to non-VEEDIMS capable fans.

  Power distribution can also make the VCE 100 more environmentally friendly because power consumption can be monitored and controlled at various levels of the VCE to ensure that the VCE is being used efficiently. This control can be used to identify components with high power requirements for replacement and adjust overall power consumption within the VCE 100.

  The VCE 100 can support software and hardware redundancy. For example, hardware redundancy is achieved by using multiple hardware components (eg, V controller 112) for mission critical operations and dual ports and other for V controller 112, V switch 116 and V module 118. Can be provided by providing a safety means. Some or all of V-controller 112, V-switch 116 and V-module 118 may have a heartbeat or other to allow VCE 100 to detect software, hardware and link failures and adjust accordingly. This notification method can also be used.

  Still referring to FIG. 3, in yet another embodiment, one possible configuration of the VCE 100 of FIG. 1 illustrates that multiple V switches 116 and V modules 118 can be connected together (ie, daisy chain). The ability to daisy chain V switches 116 eliminates the need for separate V net cables 120 and V power cables 122 from each V switch to V controller 112 and VCE power supply 114 in VCE 100, respectively. Similarly, the ability to daisy chain V modules 118 eliminates the need for a separate V net cable 120 from each V module to V switch 116. As a result, the cable can be wired more efficiently. This is because the VCE 100 can be configured with multiple V switches 116 and V modules 118 that are distributed throughout the vehicle or other environment.

  A daisy chain connection may include power, data, or both power and data. One or more of V-switch 116 and V-module 118 are configured to pass data to other V-switches and V-modules so that V-net traffic can be daisy chained. ) A switch may be provided. Further, power may be transmitted in one direction of one daisy chain, and data may be transmitted in the other direction. Thus, any given configuration of VCE 100 can be configured with a high degree of freedom while providing a distributed and isolated (ie, modular) system.

  In this example, the V controller 112 is connected to the VCE power supply 114 to obtain power (dashed line), and is connected to the V switches 116a and 116b (solid line) for V net data communication. The V switch 116a supplies V net data and power to the V module 118a, and the V module 118a similarly supplies V net data and power to the daisy chained V module 118b. The V switch 116b is connected to the V switch 116c and the V module 118c, supplies V net data to the V switch 116c, and supplies both V net data and power to the V module 118c. Note that V switch 116b is not directly connected to VCE power supply 114. The V switch 116c is connected to the V modules 118d and 118e and the V switch 116b. The V switch 116c supplies power to the V switch 116b, and supplies both V net data and power to the V modules 118d and 118e. Although not shown in the figure, the V controller 112 and / or the V switch 116 communicates with the VCE power supply 114 to determine how much power is available, return the power demand to the VCE power supply, and set the power level. Can be controlled.

  An additional V switch 116 (not shown) may be connected to V controller 112 and / or daisy chained from V switches 116a-116c, and an additional V module 118 (not shown) may be connected to V switch 116a. May be connected to one of ˜116c or daisy chained from V modules 118a to 118e. Further, multiple V switches 116 may be connected to a single V switch, and multiple V modules 118 may be connected to a single V module. The restrictions on the number of V switches 116 and V modules 118 that can be connected are the number of available ports and the amount of power required by the connected components vs. the power available to that set of components. May include quantity. It may be difficult to replace cables and components because the number of connections required increases as the connected components become relatively long.

  Although not shown in the figure, it should be understood that many different network topographies may be used. For example, both a ring network configuration and a star network configuration can be used in the VCE 100.

  Referring to FIG. 4, one embodiment of the V controller 112 of FIG. 1 is shown. The V controller 112 includes a VEEDIMS central processing unit (VCPU) 400, a memory 402, a communication / power interface 404, and one or more internal communication links 406. It should be understood that the configuration of V controller 112 and the types of its components may vary depending on the particular VCE 100 for which the V controller is to be used. For example, in a vehicle environment, the V controller 112 may be designed as a relatively compact integrated circuit board with the minimum number of ports required to provide the desired functionality. In contrast, in environments such as structures (eg, homes or office buildings), non-compact V-controllers 112 may be used because space is generally less important. Further, the V controller 112 may be relatively general for use in many different VCEs or customized for use in a particular VCE 100 that has very specific requirements (eg, aerospace environment). There is a case.

  VCPU 400 may actually represent a multiprocessor or distributed processing system, memory 402 may include various levels of cache memory, main memory, hard disk, and remote storage locations, and communication / power interface 404 may be It may represent multiple interfaces dedicated to reception, dedicated to data / power distribution / combination, and dedicated to transmission. For example, the communication / power interface 404 includes a first interface (not shown) that receives power from the VCE power supply 114 via the V power cable 122 and one or more V switches 116 via the V net cable 120. And a second interface (not shown) that communicates with the. In some embodiments, the V controller 112 may transmit power to the V switch 116 via the V net cable 120. The data transmission capability of the communication / power interface 404 can provide both wired (eg, V-net cable 120) and wireless functions.

  Instructions for V controller layer 106 (eg, VEEDIMS controller kernel and VEEDIMS controller driver) and V net transport layer 108 may be stored in memory 402 and executed by VCPU 400. The functions of the V controller layer 106 may be fully processed by the V controller 112, or some or all of the V controller layer functions may be pushed down to a level below the V switch 116. As will be discussed later, additional functionality may be provided by the V controller 112 to allow the user to interact with the V controller to control the parameters of the VCE 100 and to obtain data about the VCE. When there are a plurality of V controllers 112 in the VCE 100, the V controllers provide a load balancing function and include software for ensuring redundancy when one of the V controllers does not operate. There is.

  Referring to FIG. 5, one embodiment of the V switch 116 of FIG. 1 is shown. The V switch 116 includes a processing unit (PU) 500, a memory 502, a communication / power interface 504, and one or more internal communication links 506. It should be understood that the configuration of the V switch 116 and its component types may vary depending on the particular VCE 100 for which the V controller is to be used. For example, in a vehicle environment, the V-switch 116 may be designed as a relatively compact integrated circuit board with the minimum number of ports required to provide the desired functionality. In contrast, in environments such as structures (eg, homes or office buildings), non-compact V-switches 116 may be used because space is generally less important. In addition, the V switch 116 may be relatively generic for use in many different VCEs, or customized for use in a particular VCE 100 that has very specific requirements (eg, aerospace environment). There is a case.

  The PU 500 may actually represent a multiprocessor or distributed processing system, and the memory 502 may include various levels of cache memory, main memory, hard disk, and remote storage locations. In this example, PU 500 and memory 502 may be formed on a circuit board having an embedded system such as that manufactured by Netburner (San Diego, Calif.). The circuit board may include multiple ports for power, communication, and other connections.

  Communication / power interface 504 may represent multiple interfaces dedicated to receiving V-net data traffic and power, dedicated to distributing / combining V-net data traffic and power, and dedicated to transmitting V-net data traffic and power. For example, the communication / power interface 504 includes a first interface (not shown) that receives power from the VCE power supply 114 via the V power cable 122 and transmits power to the PU 500 and the memory 502, and the V net cable 120. A second interface (not shown) that communicates with the V controller 112, the V switch 116, and the V module 118.

  The second interface is that the V net cable 120 that links the V switch 116 to the V controller 112 has no power component, or that the V net cable that links the two does not support power. It can be configured to recognize that it may be inserted into a designated slot. The communication / power interface 504 includes a first interface and a second interface for passing power received via the V power cable 122 to the V net cable 120 connected to the other V switch 116 and the V module 118. May include a connection between. If the V net cable 120 has two separate channels for data and power, the first and second interfaces may be individually connected to the appropriate channels. When data and power are carried in one signal (eg, at separate frequencies), the first and second interfaces combine the V net data traffic signal and the power signal into a single A transmission signal can be generated.

  The first and second interfaces of the communication / power interface 504 can also be configured to allow some or all of the V net data traffic and power to pass through the V switch 116. For example, if another V switch 116 is connected to the input / output port of the communication / power interface 504 via the V net cable 120, the communication / power interface may receive a certain amount of received power, and Some or all of the received V net data traffic can be passed through to other V switches. The communication / power interface 504 may include a filter or other control circuit that allows the V switch 116 to control power delivery via the V net cable 120. The data transmission capability of the communication / power interface 504 can provide both wired (eg, V-net cable 120) and wireless functions.

  Instructions for V net transport layer 180 and instructions for interacting with V controller layer 106 are stored in memory 502 to establish V switch 116 as a multiple application execution interface (MAXI) in VCE 100. It may be executed by the PU 500. In some embodiments, the V switch 116 may include instructions for at least a portion of the V controller layer 106. In other embodiments, the V-switch 116 can provide only basic V-net data traffic switching (eg, in a VCE 100 having individually addressable V-modules 118) and has its own power consumption demand. Once filled, any remaining power can simply be passed and passed to the connected V-switch and V-module.

  Referring to FIG. 6, one embodiment of the V module 118 of FIG. 1 is shown. As described above, the V module 118 is a discrete electrical / electronic equipment interface module, in which any electrical / electronic device is connected to the VCE 100 via a V net backbone formed by a V switch 116 and a V net cable 120. It is designed to be able to have data and power connections to. In general, the V module 118 is a low-level instrument panel instrument that may be found in a vehicle with an engine, for example, a general-purpose software control driver operating in the V controller layer 106 residing in the V controller 112. It is designed to provide a VOE with a hardware (in some applications, software) abstraction layer so that the device can be controlled.

  The V module 118 includes a VEEDIMS remote processing unit (VRPU) 600, a memory 602, a communication / power interface 604, and one or more internal communication links 606. It should be understood that the configuration and component types of the V module 118 may vary depending on the particular VCE 100 in which the V module is to be used. For example, in a vehicle environment, the V module 118 may be designed as a relatively compact integrated circuit board having the minimum number of ports required to provide the desired functionality. In contrast, in environments such as structures (eg, homes or office buildings), non-compact V modules 118 may be used because space is generally not important. Further, the V module 118 may be relatively generic for use in many different VCEs or customized for use in a particular VCE 100 having very specific requirements (eg, aerospace environment). There is a case.

  VRPU 600 may actually represent a multiprocessor or distributed processing system, and memory 602 may include various levels of cache memory, main memory, hard disk, and remote storage locations. In this example, VRPU 600 and memory 602 may be formed on a circuit board having an embedded system such as that manufactured by Netburner (San Diego, Calif.). The circuit board can include multiple ports for power, communication and other connections.

  Communication / power interface 604 may represent multiple interfaces dedicated to receiving V-net data traffic and power, dedicated to V-net data traffic and power distribution / combining, and dedicated to transmitting V-net data traffic and power. For example, the communication / power interface 604 transmits / receives V net data via the same V net cable to a first interface (not shown) that receives power from the V net cable 120 connected to the V switch 116. 2 interfaces (not shown). If the V net cable has two separate channels for data and power, the first and second interfaces may be individually connected to the appropriate channels. If data and power are combined into a single signal (eg, at separate frequencies), the first and second interfaces can filter the incoming signal to separate the data and power. .

  The first and second interfaces of the communication / power interface 604 can also be configured to allow some or all of the V net data traffic and power to pass through the V module 118. For example, if another V module 118 is connected to the input / output port of the communication / power interface 604 via the V net cable 120, the communication / power interface 604 may have a certain amount of received power, And some or all of the received V net data traffic can be passed through to other V modules. The data transmission capability of the communication / power interface 604 can provide both wired (eg, V-net cable 120) and wireless functions.

  The first and second interfaces of the communication / power interface 604 can connect the V module 118 to one or more subsystems / devices 200. For example, one or both of the first and second interfaces may form the I / O interface 202 of FIG. 2, or the communication / power interface 604 may communicate and distribute power to the subsystem / device 200. One or more other bus-based I / O interfaces, analog I / O interfaces and / or digital I / O interfaces may be provided. The V module 118 can, for example, exercise an I / O scan via the I / O interface 202 to perform exception reporting on the failure of the attached subsystem / device 200. In some embodiments, the communication / power interface 604 of the V module 118 serves as a gateway and allows the attached subsystem / device 200 to access an external wireless device (not shown).

  Instructions for the V net transport layer 108, instructions for the V module driver layer 110, and instructions for interacting with the V controller layer 106 are stored in the memory unit 602, and the V module 118 is designated as MAXI in the VCE 100. May be executed by VRPU 600 to configure. In some embodiments, the V module 118 may include instructions for at least a portion of the V controller layer 106.

  The V module driver layer 110 includes driver software specific to the dedicated device interface, which provides the interface between the VOE and the subsystem / device 200 connected to the V module 118. For example, in a VCE 100 such as a vehicle (vehicle), signal data from individual sensors such as oil temperature, pressure, and water temperature are captured from the subsystem / device 200 via a specific driver of the V module driver layer 110, and the V module Collected and processed by 118. The V module 118 captures the sensor data and sends the data as V net traffic (eg, as a VEEDIMS data stream) to the V controller 112 via the V net backbone. It should be understood that sensor data that is not VEEDIMS compliant may be converted by the V module 118 before being sent to the V controller 112. In a more specific example, a V controller layer driver in V controller layer 106 has been developed to drive a tachometer, speedometer, and a series of other instruments for the purpose of notifying the operator of the current state of the vehicle. May be. To accomplish this, individual sensors connected to the V module 118 generate digital or analog signal data that is collected and processed by the V module based on the corresponding V module driver layer 110. . The V module 118 transmits the processed signal data to the V controller 112 via the V net backbone for processing by the VCPU 400. At that time, the V controller 112 can give the information to the driver of the vehicle.

  The V module 118 allows new subsystems and components to be integrated with the VOE without requiring a high level of change. For example, a driver for the V module 118 can be written to accommodate new physical electrical / electronic devices and any corresponding software. The driver will reside in the V module driver layer 110 and will be written to comply with the VEEDIMS standard interface protocol used by the V controller layer 106. The standard interface protocol is available via the VEEDIMS Development Kit (VDK) or may be otherwise published for use by developers. This approach is conceptually similar to the concept of a general purpose disk drive controller driver written in the UNIX operating system environment to control the disk drive. When a new disk drive is developed, the generic disk drive controller driver can interact with the new drive, despite the ability to use any newly available hardware at that hardware level. Because any unique aspect of the new drive is transparent to the generic device driver as long as the new drive's low-level driver is designed to match the higher-level generic disk drive controller driver. This is because. Thus, new subsystems and components can be integrated with VCE 100 without requiring high level VCE changes as long as their drivers comply with the VEEDIMS standard interface protocol.

  V module 118 may have a unique identifier that can be used within VCE 100 to distinguish it from other V modules. The unique identifier can be a medium access control (MAC) address, an IP address, or any other unique identification code (eg, a serial number).

  As will be described in more detail later, the V module 118 may store its internal website, protected by a fully encrypted password, in non-volatile memory (eg, memory 602). it can. That information may include product documentation and revision levels, complete bill of materials (BOM), and repair and manufacturing history. The V module 118 can broadcast or transmit this data to the same level V module in the VCE 100 and higher level components (eg, the V switch 116 and the V controller 112). The V module 118 may maintain a cached data snapshot of events preceding the failure in non-volatile memory for failure analysis, and may also store execution time and other target parameters. Such information can be used to replace a failed V module 118 without having to reconfigure the VCE software upon replacement. The V module 118 can be configured to perform diagnostics at startup and report its status as needed. In addition, the V module 118, and the V switch 116 and V controller 112 may all generate a heartbeat signal, and the V controller 112 monitors the heartbeat signal to determine the state of various VCE components. be able to.

  Turning to FIG. 7, one embodiment 700 of a system architecture is shown. The system architecture 700 considers the VCE 100 to have an information upper layer that is widely accessible and may be manipulated, a central control layer that is mission critical, and a device layer. The system architecture 700 focuses on the information upper layer, and the lower layer is mainly used for data collection and diagnosis. For illustrative purposes, the system architecture 700 is described with respect to a vehicle layer, a store (eg, vehicle repair shop) shop layer, and an enterprise layer. The VCE 100 in the present embodiment includes the V controller 112 and the V module 118 of FIG. 1 in the vehicle layer, the VEEDIMS fleet diagnosis 702 in the store layer, and the VEEDIMS fleet management 704 in the enterprise layer. In this example, a PI system provided by OSIsoft (San Leandro, CA) is used for data collection, compilation and analysis. However, it should be understood that other systems may be used and the present disclosure is not limited to PI systems.

  In this embodiment, the VCE 100 of FIG. 1 is configured to support sequential data storage, so that failure analysis can be performed based on time and excursion after an event (eg, failure) occurs. Become. Traditional automotive diagnostic systems are based on an error code paradigm. In the error code paradigm, a specific fault generates a predetermined error code that is stored in the computer, which theoretically allows service technicians to diagnose the root cause of the fault and repair the system. Become. Unfortunately, this predetermined error code approach cannot capture an unexpected failure event or sequence of events, and as a result, in many cases extends the time to solve the problem and still roots the original problem. May not be identified. For example, if the error cannot be isolated, a large portion of the wire harness or even a larger part assembly may be replaced in an attempt to remove the failed component. Such problem-solving techniques through trial and error are extremely burdensome for customers, distributors and manufacturers.

  The present disclosure provides this by providing a system architecture 700 that captures all time series and event driven data with high resolution and allows the data to be stored in a compact non-volatile digital medium. Address the problem. In addition, the system makes it possible to examine and analyze data to examine various system states while a specific failure occurs. This capability allows the system data to be associated with specific fault events that are noticed by the customer or recorded by the VCE 100, and also a comprehensive situation of what may have led to the fault. To clarify the data stream before the event. This analysis process allows service technicians to quickly and efficiently diagnose the cause of intermittent failures that were previously difficult to detect and repair using computerized tools. It becomes like this.

  The VCE 100 can also provide the ability to store all data that has been generated and collected. By allowing filtering only in the case of compression and exceptions, storage efficiency can be increased without losing resolution. Furthermore, it is accumulated by using transmission technologies (eg, Bluetooth, and other wired and wireless technologies) to later analyze for the purpose of confirming improvements rather than simply addressing current issues. Data can be downloaded. For example, the data can be analyzed to identify fault conditions that can be used to define predictive means for preventing future component failures.

  Data can be organized for quick and advanced searching, such as searching for logical expressions or excursion limits. In some embodiments, the data storage device (eg, database) can employ a batch subsystem that stores pointers to the start and end of a particular portion of the data stream, thereby using the overlay to do the same Such events can be compared. For example, to develop an optimal engine start model and to be able to quickly call up and compare start events to predict maintenance needs as parameter drift (eg, cranking time at cold start) Multiple engine start events can be organized by the batch subsystem. The efficiency of the database enables advanced analysis, including multivariate statistical analysis. As a result, data can be analyzed in real time, and not only fault detection can be performed, but also a preventive maintenance function can be performed by observing a tendency away from normal operating parameters. In some examples, the VCE 100 can be configured to control based on the highest profile (eg, an optimal set of performance parameters) and trigger an alarm when performance deviates from that profile.

  To accomplish this level of analysis, the V module 118 uses sensors and other feedback mechanisms to collect information about the attached subsystem / device 200 (FIG. 2). That information may be obtained via interfaces such as bus-based I / O interface 706, analog I / O interface 708, and digital I / O interface 710. Each of the I / O interfaces 706, 708, and 710 passes information through the general purpose I / O interface layer 712, which allows the V module 118 to be uniform with each of the various types of I / O interfaces. You can communicate.

  The I / O interface layer 712 stores the information in a register map 714, which includes a Modbus / TCP driver 716 and an Embedded Component Historian Object (ECHO) driver 718 (e.g., OSIsoft ( ECHO) corresponding to the PI system provided by San Leandro, CA). The Modbus / TCP driver 716 and the ECHO driver 718 constitute an interface with corresponding components of the V controller 112, as will be described later.

  Register map 714 can also access VEEDIMS dynamic controller 720, which is configured to obtain information from the register map, process the information, and update and maintain documentation 722. Documentation version control is a complex problem in very complex vehicles or vehicles that are mass-produced. To solve this problem, VEEDIMS embeds the entire documentation set in the V module 118 or in another subsystem, making it immediately available to service technicians. Furthermore, a service log may be stored, and the service log can be updated to accurately reflect the service history of the vehicle. In some embodiments, the service log may be linked to a billing system, which automatically updates the log.

  The dynamic controller 720 can perform diagnostics using the diagnostic module 724 and can also hold information resulting from the diagnostics, and can use the configuration module 726 to configure and configure V-module and subsystem / device parameters. Information can be retained. The dynamic controller 720 can use the embedded web server described above to access information related to the documentation 722 and the diagnostic module 724 and configuration module 726 via the Hypertext Transfer Protocol (HTTP) interface 728. You can also In this example, the information is made available to the VEEDIMS fleet diagnostic 702 in the store layer, but may be made available to many other users, including the driver of the vehicle corresponding to the VCE 100.

  The V controller 112 includes a Modbus / TCP driver 730 that receives information from the register map 714 via the Modbus / TCP driver 716 of the V module 118. The Modbus / TCP driver 730 passes the information to a visualization module 732 that can process the processed information before sending it to the ECHO component 736. The V controller 112 also includes an ECHO driver 734 that receives information from the register map 714 via the ECHO driver 718 of the V module 118. The ECHO driver 734 passes information to the ECHO component 736. The ECHO component 736 can send some or all of that information to the VEEDIMS fleet management 704 in the enterprise tier via the ECHO upload component 738. The ECHO component 736 can also store some or all of its information in the ECHO data database 740, which can quickly (eg, real-time or near real-time) a large amount of time-stamped data. To the role of collecting and archiving.

  When some or all of the data stored by V-controller 112 and V-module 118 is stored in a “black box” designed to withstand high shock and high temperature situations such as accidents There is. The above data can later be obtained for analysis even if the various subsystems are damaged or destroyed.

  The VEEDIMS fleet diagnostic 702 in the store tier includes a web browser 742 that uses the web browser 742 to access the documentation data 722 and diagnostic data 724 via the HTTP interface 728 provided by the web server of the V module 118. You can see those data. Due to the V module 118 data being provided by HTTP, access to that data can be achieved without the need for proprietary equipment and tools. When the data can be encrypted, only a user having an appropriate authentication certificate can access the data, so that security can be ensured. The VEEDIMS fleet diagnostic 702 may also include a configuration tool 744 that interacts with the configuration module 726 to obtain configuration information and uses the extensible markup language (XML) configuration information to provide a V module. 118, other V modules, and attached subsystem / device parameters may be used to configure.

  The VEEDIMS fleet diagnostic 702 further comprises an ECHO component 746 that obtains data from the ECHO data database 740 of the V controller 112. That data may be passed to the PI server 750 via the PI ECHO driver 748 and various PI analysis tools 752 may be used to analyze some or all of the data in the store tier. . That data may be passed to the VEEDIMS fleet management 704 in the enterprise layer via the ECHO upload component 754.

  The VEEDIMS fleet management 704 in the enterprise layer comprises an ECHO upload component 756 that receives data from the ECHO upload components 738 and 754. The ECHO upload component 756 passes the data to the ECHO component 758, which stores the data in the PI data database 762 via the PI ECHO driver 760. The PI analysis tool 766 can access data in the PI data database 762 via the PI server 764 for analysis.

  Referring to FIG. 8, in one embodiment, a vehicle 800 (vehicle) is shown as an environment that can be managed using the VCE 100 of FIG. The vehicle 800 includes a chassis 801 and has a plurality of subsystems and corresponding components that are disposed within or connected to the chassis, which are propelled, steered, braked relative to the vehicle 800. And provide other functions. It should be understood that the subsystems and components described herein are for illustrative purposes only and that many other subsystems and components may be used with vehicle 800. Further, the illustrated subsystems and components may be configured differently than illustrated and may be arranged differently within vehicle 800.

  The vehicle 800 includes tires 802a, 802b, 802c, and 802d and corresponding tire pressure monitoring system (TPMS) in-tire sensors 804a, 804b, 804c, and 804d, respectively, which are TPMS radio signal receivers 806. Send a signal to each. Tires 802a, 802b, 802c and 802d are connected to shafts 808a and 808b, which are driven via a transmission system (not shown) connected to engine 810. An engine control unit (ECU) 812 can monitor and manage the performance of the engine 810. For example, ECU 812 can control fuel injection in engine 810 based on monitored parameters. Headlight assemblies 814a and 814b, and taillight assemblies 816a and 816b may be connected to an electrical system that allows the various lights that form the headlight and taillight assembly to be operated.

  “Half door” sensors 820a and 820b may be used to monitor doors 818a and 818b, respectively. “Door open” switches 822a and 822b may be used to control room lighting, alarms, and other functions when doors 818a and 818b are opened, respectively. Driver seat 824a and passenger seat 824b may include occupant detection sensors 826a and 826b, respectively, which indicate that there is a person.

  The vehicle compartment includes a group of instruments 828 for providing feedback information (eg, speed, fuel level and engine temperature) to the driver, various actuation means (eg, switches and buttons) disposed on the steering wheel 830, instrumentation. A panel switch group 832 and interactive navigation and information screen 834 (eg, a flat panel) may also be accommodated. Using interactive screen 834, navigation information, vehicle information (eg, current fuel level, estimated number of miles remaining until refueling is required, and various temperatures (eg, engine and cabin temperature)), and Other information can be provided to the user. The windshield wiper assembly 836 may be controlled via actuation means on the steering wheel 830. Roll bar light assemblies 838a and 838b may be connected to an electrical system that allows the various lights on the roll bar light assembly to be manipulated via, for example, interactive screen 834.

  A fuel chamber 840 (fuel cell) may be connected to a flow meter 842 that measures fluid flow in the low pressure fuel return path from the engine 810 and a flow meter 844 that measures fluid flow in the high pressure fuel path to the engine. is there. A filler cap 846 can cover the refueling path, which is monitored by a flow meter 848. Although not shown in the figure, a sensor can monitor the filler cap 846 to ensure that it is in place. Fuel chamber 840 and various flow meters 842, 844, and 848 may be monitored.

  The vehicle 800 monitors vehicle functions such as ignition, propulsion, steering, braking, hydraulic and tire pressure, control panel indicators, cabin environmental parameters (eg, temperature and airflow), and audio / video entertainment system settings, It should be understood that various subsystems (not all shown) may be configured to control and / or control. Such subsystems can range from complex (eg, fuel injection as managed by ECU 812) to relatively simple (eg, control of indoor “dome” lights).

  Still referring to FIG. 9, one embodiment of the VCE 100 of FIG. 1 is shown in a vehicle 800 of FIG. The vehicle 800 includes a V controller 112 and a VCE power supply 114 that are connected to each other and to a V switch 116. The V switch 116 is connected to the first V module 118a, and the first V module 118a is further connected to the second V module 118b. V modules 118a and 118b are connected to taillight assemblies 816a and 816b, respectively. In this example, each taillight assembly 816a and 816b includes a plurality of LEDs that are divided into a reverse light area, a brake light area, and a direction indication area. In some embodiments, V modules 118a and 118b are incorporated into individual taillight assemblies. In other embodiments, V modules 118a and 118b are connected to individual taillights but are separate components. The V controller 112 is also connected to the V module 118c, and the V module 118c is further connected to the ECM 812 via a proprietary (proprietary) cable.

  In this example, the VCE 100 V module includes multiple passive switch classes, solenoid / actuator classes, motor classes, passive information display classes, interactive information display classes, passive data pass-through classes, feedback data collection classes, and lighting control classes. It is classified into the class. It should be understood that these classes are for purposes of illustration and are not intended to be limiting. Furthermore, there may be overlap between certain classes, and all or part of one class may form part of another class.

  The passive switch class includes subsystems and components such as simple on / off state switches or instantaneous contact switches that may be used for half-door sensors 820a and 820b or occupant detection sensors 826a and 826b. This class is used to control multiple functions or states that may be used in windshield wiper control to activate intermittent, low, medium and high speed wiping intervals of the windshield wiper assembly 836. In some cases, more complex multi-position passive switches are included.

  The solenoid / actuator class includes subsystems and components used to electrically open doors, trunk doors, or any other single action or process. The motor class is used to move subsystems and components used in moving wipers (eg, windshield wiper assembly 836), subsystems and components used in hood / door opening mechanisms, power seats or mirrors. Subsystems and components as well as subsystems and components used in similar motorized operations.

  Passive information display classes include visual displays for users, including active displays such as electrical / electronic dashboard instruments in the instrument group 828, addressable matrix liquid crystal display (LCD) and organic light emitting diode (OLED) displays. Includes subsystems and components to supply information. The interactive information display class includes an interactive screen 834, a global positioning system (GPS) navigation device, a sound system, an active display, and an interactive starter switch that provides engine standby / start / stop control switching capability using status displays. , Including subsystems and components.

  The passive data pass-through class includes subsystems and components for performing data collection and data pass-through, including passive displays. The feedback data collection class includes subsystems and components such as interactive displays, lighting control modules, and engine control modules. The lighting control class includes headlight assemblies 814a and 814b, daytime running lights, taillight assemblies 816a and 816b, and subsystems and components for temporary interior lighting and instrument panel lighting.

  According to the above class list, the V modules 118a and 118b in this example are classified as lighting control class modules. The V module 118c may be classified in a passive data path or feedback data collection class.

  V module 118c is an example of a V module that can interact with a non-VEEDIMS enabled legacy subsystem or component to provide at least a basic level of VEEDIMS functionality to the non-VEEDIMS enabled legacy subsystem or component. The V module 118c receives CAN bus data from the ECM 812 via a proprietary cable. Thereafter, the V module 118c converts the CAN bus data into V net data, and transmits the converted data via the V net backbone. This allows the VCE 100 to use the CAN bus data, at which time there is no need to perform other conversions at a higher VCE level than the V module 118c. In some embodiments, a VEEDIMS-enabled ECM can be used in place of an ECM 812, thereby allowing the ECM to be seamlessly incorporated within the VCE 100. The VEEDIMS-enabled ECM may also have the ability to cache engine start-up and travel data until a higher level control system is ready to receive. The cache technology can accommodate any latency, provide time stamping synchronization, and shut down higher level systems for upgrade or maintenance without losing any data Like that.

  For purposes of illustration, each of the V modules 118a and 118b includes a circuit board having a Netburner that executes instructions, such that each of the V modules 118a and 118b forms a MAXI board as described above. Each V module 118a and 118b has multiple power sources required to turn on the reverse lights in the reverse light areas of the taillight assemblies 816a and 816b, and others to drive the brake lights and direction indication areas. May also be provided.

  The V modules 118a and 118b can individually address each LED of the taillight assemblies 816a and 816b, receive feedback from the LEDs using a fiber optic link or other means, brightness levels, etc. Can be identified. For example, when the vehicle 800 is started, the V modules 118a and 118b can perform a quick test of each LED in the taillight assemblies 816a and 816b to ensure that the LEDs are functioning. . This can be accomplished using feedback obtained via a fiber optic link, which allows the V modules 118a and 118b to measure the brightness level and color of each LED or group of LEDs. The color test can be accurate to 18-bit resolution, which gives the V modules 118a and 118b a higher degree of control than the light output of the taillight assemblies 816a and 816b. Using this information, the V modules 118a and 118b can control the output of the LEDs using, for example, a pulse width modulation (PWM) collective drive.

  The feedback provided to the V modules 118a and 118b may be used for various purposes other than testing. For example, the feedback can be used to control daytime and nighttime lighting, such as daytime running lights, and can be used to adjust LED brightness based on ambient light levels. In another example, the feedback can be used to provide an active reflector using taillight assemblies 816a and 816b. To form an active reflector, the LED can be turned off until the optical fiber detects light coming from an external light source. One possible scenario in which this may occur is when the vehicle 800 has failed and stays on the shoulder at night. Rather than keeping the hazard lights blinking and draining the battery, the fiber optic can detect headlights from other vehicles and in response activates some or all of the LEDs. , Can actively indicate the presence of the vehicle. The LED can be flashed for a moment or it can be manipulated in other ways to provide additional indicators.

  The MAXI board that forms the V modules 118a and 118b may include one or more general purpose serial interfaces for purposes such as lighting control. For example, the MAXI board can support DMX (used for lighting control by the entertainment industry) via Ethernet or other dedicated digital control protocols. The MAXI board can also support other serial interfaces including RS232 compliant serial ports.

  In this example, taillight assemblies 816a and 816b each include a power supply (PS) board (not shown) disposed between the VCE power supply 114 and the LEDs. The PS board may not be VEEDIMS compliant, but may be connected to the V modules 118a and 118b via unidirectional and bidirectional signals. The PS board can set a maximum current to the LED, which can be controlled by the corresponding V modules 118a and 118b via an addressable potentiometer located on the PS board. . The PS board can also control the brightness by transmitting a PWM signal to the LED, and the PWM signal can be controlled by the V modules 118a and 118b. Note that some or all of the functions of the PS board may be controlled locally so that the taillight assemblies 816a and 816b can operate without using the V modules 118a and 118b.

  Referring to FIG. 10, in another embodiment, environment 1000 shows a structure 1002 that includes VCE 100 of FIG. In this example, the structure 1002 is a ground building that includes a plurality of floors 1004 and 1006 and one or more entrances 1008 (eg, doors). A garden such as a flower bed 1010 may be arranged around the structure 1002. Structure 1002 may be associated with multiple components and corresponding systems for monitoring and controlling those components. For example, the structure 1002 may be associated with a water injection system 1012, an environmental control system 1014, a lighting system 1016, an alarm system 1018, and a security system 1020. It should be understood that each of systems 1012, 1014, 1016, 1018, and 1020 may represent multiple systems or subsystems.

  The irrigation system 1012 may be configured to control and monitor the supply of moisture to the flower bed 1010 and other outdoor garden and indoor plant pots (not shown). The environmental control system 1014 may be configured to control and monitor heating and air conditioning equipment. The lighting system 1016 may be configured to control and monitor the indoor and outdoor lighting of the structure 1002 and may represent the indoor lighting system and the outdoor lighting system. Alarm system 1018 may represent a fire alarm system and a security alarm system. The alarm system 1018 may include a safety component within the structure 1002 (eg, fire alarm), as well as a security alarm (eg, an anti-theft alarm on the door 1008 to indicate unauthorized entry, or a room or office It may be configured to control and monitor alarms on indoor doors to manage access to the continuation room. Security system 1020 may be configured to control and monitor cameras, motion sensors, and similar security devices, and in some embodiments, control and monitor security alarms.

  One or more V-controllers 112 can be used to monitor and control the systems 1012, 1014, 1016, 1018 and 1020 via the V-net backbone, and the V-net backbone may include power distribution capabilities. , It may not be included. The V controller 112 is connected to a plurality of V modules 118a, 118b, and 118c. Although not shown in the figure, one or more V switches 116 may be disposed between the V controller 112 and the V modules 118a, 118b, and 118c.

  The V module 118 a is connected to the water injection system 1012. The V module 118b is connected to the environment control system 1014 and the lighting system 1016. The V module 118c is connected to the alarm system 1018 and the security system 1020. Each V module 118a, 118b, and 118c monitors and queries the connected systems 1012, 1014, 1016, 1018, and 1020 as described above in the previous embodiment, as well as their systems. Can be controlled.

  In some embodiments, the VCE 100 may be associated with a larger system, such as the main power distribution network of the structure 1002. In these cases, the data obtained by VCE 100 may be shared with other information sources. For example, power distribution network data may be shared with a power company, and the information may be integrated with other data for analysis. The analysis can be used to prevent problems including light restrictions and power outages, and to track demand within a given area.

  It should be understood that the drawings and detailed description herein are to be regarded as illustrative rather than limiting, and are not intended to be limited to the particular forms and examples disclosed. On the contrary, any further changes, modifications, alterations, substitutions, alternatives, design choices and Embodiments are included. Accordingly, the appended claims are intended to be construed to include all such changes, modifications, variations, substitutions, alternatives, design choices and embodiments.

Claims (29)

A virtual electrical / electronic device interface and management system (VEEDIMS) for a vehicle, comprising:
A backbone network formed by a plurality of cables, each cable configured to carry digital data and power simultaneously; and
A controller connected to the backbone network and configured to execute a plurality of control instructions;
A plurality of modules connected to the controller via the backbone network, configured to receive data and total power required by the module via the backbone network, the module controlling the plurality of controls A plurality of modules configured to receive control signals from the controller based on instructions;
At least one device connected to the first module via a direct input / output (I / O) interface disposed in the first module of the plurality of modules, the first module comprising: A virtual electrical / electronic for a vehicle comprising: a device-specific driver housed in a module of the device comprising: Device interface and management system.   The switch further comprises a switch located in the backbone network between the controller and the first module, the switch passing the required power from a power source to the first module and the first module. The VEEDIMS of claim 1, wherein the VEEDIMS is configured to transfer communication between the module and the controller.   The backbone network is based on Ethernet (registered trademark), and the controller and the first module each include a transmission control protocol (TCP) driver for communicating between the first module and the controller. The VEEDIMS according to claim 2.   The VEEDIMS of claim 2, wherein the switch comprises an Ethernet switch.   The VEEDIMS of claim 1, wherein the first module further comprises a hypertext transfer protocol (HTTP) server.   The first module further comprises a diagnostic component adapted to obtain diagnostic data for the first module and the device and to make the diagnostic data accessible via the HTTP server. The VEEDIMS according to Item 5.   The VEEDIMS of claim 5, wherein the first module further includes a documentation set that includes a service history of the first module, the documentation set being configured to be accessible via the HTTP. .   The VEEDIMS of claim 1, wherein the first module further comprises a setting component adapted to set operating parameters for at least one of the first module and the device.   The VEEDIMS of claim 1, wherein the first module further comprises a data collection component adapted to collect data for at least one of the first module and the device.   10. The VEEDIMS of claim 9, wherein the data collection component includes an embedded part historian object (ECHO) connected to an ECHO driver for transmitting the collected data from the first module to the controller. .   The VEEDIMS of claim 9, wherein the collected data is stored in a register map in the first module before being transferred to a database in the controller.   The VEEDIMS of claim 1, wherein the first module is integrated with the device. A virtual electrical / electronic device interface and management system (VEEDIMS) comprising:
A first power interface; a first network / power interface; a first processor connected to the first power interface and the first network / power interface; and executable by the first processor A first controller having a first memory containing a plurality of instructions, wherein the instructions include controller instructions adapted to control a plurality of modules;
An energy source connected directly to the first power interface via a first cable adapted to carry only power;
A second power interface connected directly to the energy source via a second cable adapted to carry only power, and a third adapted to carry both power and data simultaneously A first switch having a second network / power interface connected directly to the first network / power interface via a cable;
A first module of the plurality of modules, wherein the first module is connected to the second network / power interface via a fourth cable adapted to carry both power and data simultaneously; A third network / power interface directly connected to the device, a device input / output (I / O) port, and a second processor connected 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, wherein the instructions are received by the first module and the device I / O port through the first I / O port. Driver instructions adapted to enable communication with a device connected to a module, the first module comprising the device And the first controller and adapted to provide a communication interface between, and a first module, the virtual electrical / electronic device interface and management systems.   A second controller connected to the first controller via a fifth cable adapted to carry both power and data simultaneously, wherein the first memory is provided by the plurality of modules; 14. The VEEDIMS of claim 13, comprising a plurality of instructions executable by the first processor to balance an induced load between the first controller and the second controller.   A third power interface and a fourth network / power interface connected directly to the second network / power interface via a fifth cable adapted to carry both power and data simultaneously 14. The VEEDIMS of claim 13, further comprising a second switch comprising: the second switch configured to obtain power from the first switch rather than a power source.   The first switch and the second switch pass power from the first switch to the second switch via the fifth cable, and at the same time, the second switch via the fifth cable. The VEEDIMS of claim 15, configured to pass data from one switch to the first switch.   A second module having a fourth network / power interface connected directly to the third network / power interface via a fifth cable adapted to carry both power and data simultaneously; 14. The VEEDIMS of claim 13, wherein the second module is configured to obtain its power from the first module.   The second memory sends an inquiry to the device when the device is first connected to the first module and instructions to send data resulting from the inquiry to the first controller The VEEDIMS of claim 13, further comprising:   At least one of the first module and the device may indicate whether the first module or the device can be used after being connected to the first switch or the first module, respectively. The VEEDIMS of claim 13, comprising a light indicator configured to:   The second memory has instructions for transmitting data describing the function of the first module to the first controller when the first module is first connected to the first switch. The VEEDIMS of claim 13, further comprising:   The first switch comprises a third processor connected to the second network / power interface, and a third memory including a plurality of instructions executable by the third processor, the instructions The first switch uses sufficient power to meet the power requirements of the device, and instructions for determining the power requirements of the device when the device is first connected to the first module 14. The VEEDIMS of claim 13, comprising instructions for determining whether or not it can be performed.   The VEEDIMS of claim 13, wherein the first module and the device are integrated into a single unit.   The VEEDIMS of claim 13, wherein a plurality of devices are connected to the first module. A virtual electrical / electronic device interface and management system (VEEDIMS) support architecture comprising:
A module disposed in a vehicle, the module configured to connect to the device via an input / output (I / O) interface adapted to the device, and The module is configured to connect to the controller via a cable adapted to carry unidirectional power simultaneously, and the module includes a first processor and a first instruction set executable by the first processor. The first instruction set includes instructions for providing a hypertext transfer protocol (HTTP) server, the first memory including a service history of the module and the HTTP server A document including a module and a bill of materials for at least one of said devices accessible via Further comprising a Plantation set, and the module,
A controller disposed in the vehicle, the controller having a second processor and a second memory including a second instruction set executable by the second processor; A virtual electrical / electronic device interface and management system support architecture comprising: an instruction set comprising a controller that receives data from the module and includes instructions for storing the data in the second memory.   The first instruction set is configured to obtain diagnostic data for the module and the device and to transfer the diagnostic data via at least one of the HTTP server and the cable 25. The VEEDIMS support architecture of claim 24, further comprising instructions for elements.   25. The VEEDIMS support of claim 24, wherein the first instruction set further comprises instructions for a configuration component configured to set operating parameters for at least one of the module and the device. architecture.   25. The VEEDIMS support architecture of claim 24, wherein the first instruction set further comprises instructions for a data collection component configured to collect data for at least one of the module and the device. .   28. The data collection component includes an embedded part historian object (ECHO) connected to an ECHO driver for transmitting the collected data from the module to the controller via the cable. VEEDIMS support architecture.   25. The VEEDIMS support architecture of claim 24, wherein the first instruction set further includes instructions for monitoring the device to create a device profile and sending the device profile to the controller.

Images