Abstract: A method of performing automated discovery and mapping of the topology of a network is provided, wherein the networked modules include discovery and mapping-enabled modules and standard modules that are not discovery and mapping-enabled and wherein the network connections include both data connections and power connections. The method comprises the following steps: a) powering up all discovery and mapping-enabled modules on the network with current trips set to maximum level; b) powering up all standard modules; c) determining what modules are on the network; d) determine the topology of the network, including where the modules are connected within the network; e) using the determined topology to determine power requirements for the modules on the network; and f) adjusting the power distribution on the network to accommodate the identified power needs of the network.

Abstract: A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture is provided. In one example, the VEEDIMS support architecture includes a vehicle layer and a shop layer. The vehicle layer has a module and a controller positioned in a vehicle. The module is configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to the controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module. The shop layer is separate from the vehicle layer and has a browser configured to communicate with an HTTP server in the module and an analysis tool configured to receive and analyze event driven and time series data from the controller.

Abstract: A power management system including granularized control and intelligent power reduction comprises a plurality of devices interconnected on a data/power network. A control node is connected on the data/power network in data communication with the plurality of devices and receiving signals indicative of the power requirements of the individual devices and detecting a total available power for the system. The system further comprises a respective operational priority value corresponding to each of the respective devices. The control node compares the total of the power requirements for all of the devices to the total available power for the system. When the total of the power requirements exceeds the total power available, the control node determines which of the devices has the lowest operational priority value and sends control signals to that device, causing it to either reduce its power use by an incremental amount or turn OFF.

Abstract: A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture is provided. In one example, the VEEDIMS support architecture includes a vehicle layer and a shop layer. The vehicle layer has a module and a controller positioned in a vehicle. The module is configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to the controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module. The shop layer is separate from the vehicle layer and has a browser configured to communicate with an HTTP server in the module and an analysis tool configured to receive and analyze event driven and time series data from the controller.

Abstract: A method of performing automated discovery and mapping of the topology of a network is provided, wherein the networked modules include discovery and mapping-enabled modules and standard modules that are not discovery and mapping-enabled and wherein the network connections include both data connections and power connections. The method comprises the following steps: a) powering up all discovery and mapping-enabled modules on the network with current trips set to maximum level; b) powering up all standard modules; c) determining what modules are on the network; d) determine the topology of the network, including where the modules are connected within the network; e) using the determined topology to determine power requirements for the modules on the network; and f) adjusting the power distribution on the network to accommodate the identified power needs of the network.

Abstract: Hybrid cables for conveying data and conducting operating power to electrically powered devices and a vehicle utilizing such cables are disclosed.

Abstract: A virtual electronic switch system for a vehicle is provided. In one example, the system includes a switch assembly, a switch interface, and a computer. The switch assembly provides actuators that interface with non-contact sensors in the switch interface. The computer is coupled to the switch interface and assigns functions to each of the actuators. The non-contact sensors detect movement of the actuators and signal the computer, which manipulates an electrical system in the vehicle based on the assigned function.

Abstract: An analog-style gauge for displaying the value of a parameter measured or sensed by a remote sensor. The gauge comprises an actuator having a selectively rotatable shaft and a pointer fixedly attached to the actuator shaft and capable of being internally illuminated by light directed into the pointer. A light source is disposed to direct light of at least two colors into the pointer. Control circuitry is operably connected to the actuator, the light source and a remote sensor. The control circuitry rotates the actuator shaft within a range of motion in response to signals received from the remote sensor indicative of changes in the value of the sensed parameter. The control circuitry changes the color of light directed into the pointer when the pointer reaches a pre-determined point within the range of motion, whereby the internal illumination of the pointer will change color when the pointer reaches a predetermined point within the range of motion.

Abstract: A single-button ignition control and starting system for a vehicle. The system comprises an onboard computer, a start button, a light source, a clutch sensor, engine sensor and an identity sensor. The computer is connected to the ignition system and starter motor. The start button is connected to the computer to indicate whether the start button is depressed. The light source is connected to the computer to selectively illuminate the start button in a first, a second and a third illumination color. The clutch sensor is connected to the computer to indicate whether the clutch pedal is depressed. The engine sensor is connected to the computer to indicate whether the engine is running. The identity sensor adapted to receive identity indicia and is connected to the computer for producing signals indicative of the identity indicia.

Abstract: A Virtual Electrical and Electronic Device Interface and Management System (VEEDIMS) support architecture is provided. In one example, the VEEDIMS support architecture includes a vehicle layer and a shop layer. The vehicle layer has a module and a controller positioned in a vehicle. The module is configured to couple to a device via an input/output (I/O) interface compatible with the device and configured to couple to the controller via a cable adapted to simultaneously carry bi-directional data and uni-directional power to the module. The shop layer is separate from the vehicle layer and has a browser configured to communicate with an HTTP server in the module and an analysis tool configured to receive and analyze event driven and time series data from the controller.

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.