Softwareless integration system

Abstract

A softwareless integrated system is disclosed. The softwareless component includes: multiple electronic components, each including one or more input devices and one or more output devices; a shared communication interface configured to transmit status data from one or more input devices to an external consumer located outside the softwareless component, and to transmit control signals from an external command source located outside the softwareless component to one or more output devices; and multiple remote control interfaces, each operatively connected to one or more electronic components. The multiple remote control interfaces are configured to transmit at least one of the following between the shared communication interface and one or more electronic components operatively connected to the shared communication interface: status data and / or control signals. All multiple remote control interfaces are softwareless devices without a rewritable memory containing software instructions.

Description

[0001] Cross-reference to related applications

[0002] This invention patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 787,194, filed April 11, 2025, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to electrical and electronic control systems used in vehicles such as buses or trucks. Background Technology

[0004] Microcontrollers and their associated software pose several challenges to electronic control systems, including the cost and complexity of maintenance. Dedicated fixed controllers (such as stepper motor controllers or blind-spot radar controllers with LIN or CAN interfaces) can support specific functions without requiring a microcontroller or software. However, these dedicated controllers are typically function-specific. Summary of the Invention

[0005] This disclosure provides a softwareless component. The softwareless component includes: a plurality of electronic components, the plurality of electronic components including one or more input devices and one or more output devices; a shared communication interface configured to transmit status data from one or more input devices to an external consumer located outside the softwareless component, and to transmit control signals from an external command source located outside the softwareless component to one or more output devices. The softwareless component also includes a plurality of remote control interfaces, each operatively connected to one or more of the electronic components. The plurality of remote control interfaces are configured to transmit at least one of the following between the shared communication interface and one or more electronic components operatively connected to the shared communication interface: status data and / or control signals. All of the plurality of remote control interfaces are softwareless devices without a rewritable memory containing software instructions.

[0006] This disclosure also provides a control system for software-free components. The control system includes: a shared communication interface; a shared electronic control unit (ECU) operatively connected to the shared communication interface; and a plurality of remote control interfaces. Each of the remote control interfaces is operatively connected between the shared communication interface and one or more electronic components operatively connected to the shared communication interface. Each remote control interface is configured to transmit at least one of the following between the shared communication interface and one or more electronic components operatively connected to the shared communication interface: status data from one or more input devices and / or control signals from one or more output devices. All of the plurality of remote control interfaces are software-free devices without a rewritable memory containing software instructions.

[0007] These and other aspects of this disclosure are disclosed in the following detailed description of embodiments, the appended claims, and the accompanying drawings. Attached Figure Description

[0008] Further details, features, and advantages of the design of the present invention will become apparent from the following description of exemplary embodiments with reference to the accompanying drawings.

[0009] Figure 1 A top view of the vehicle is shown, in which the schematic diagram illustrates various electrical devices, controllers, and wiring interconnections, and has four areas;

[0010] Figure 2 A block diagram of a first dashboard assembly for a vehicle with conventional electrical and electronic (E / E) configuration is shown;

[0011] Figure 3 A block diagram of a second instrument panel assembly for a vehicle and having a software-free E / E configuration is shown, according to one aspect of this disclosure;

[0012] Figure 4 It shows Figure 2 A block diagram of the control software stack of several microcontrollers in the first dashboard component;

[0013] Figure 5 This illustrates a configuration for controlling, according to one aspect of this disclosure. Figure 3 A block diagram of the control software stack of the processor of the components in the second dashboard assembly;

[0014] Figure 6 It shows the use of Figure 2 A block diagram of the controller for the smart sensor or actuator in the first dashboard component;

[0015] Figure 7 An example of a method for using according to one aspect of this disclosure is shown. Figure 3 A block diagram of the first edge bus interface of the smart sensor or actuator in the second instrument panel component;

[0016] Figure 8 This illustrates an embodiment of the present disclosure with separate power and communication lines. Figure 7 A block diagram of the first edge bus interface; and

[0017] Figure 9 A block diagram is shown of a second edge bus interface configured via power-via-bus, according to one aspect of this disclosure. Detailed Implementation

[0018] The present invention will be described in detail with reference to the accompanying drawings and in view of the following embodiments.

[0019] The purpose of the systems and methods disclosed herein is to provide integrated electrical and electronic (E / E) systems or subsystems without a microcontroller and associated software. Alternatively, the E / E system or subsystem may include an Ethernet-based remote control interface in place of a microcontroller in a conventional system or subsystem. The Ethernet-based remote control interface can directly drive the microcontroller's traditional peripheral interfaces (e.g., SPI, I2C, UART, etc.) based on Ethernet messages, without requiring an actual microcontroller and software.

[0020] This disclosure provides a softwareless subsystem, which refers to an assembled system having multiple electronic components that do not contain any microcontroller or programmable software. The electronic components in the subsystem are interconnected via a single communication interface (e.g., a single example Ethernet link). This same communication interface is used to connect the subsystem to a larger system.

[0021] Typical application areas can include aerospace, industrial transportation, automotive, and robotics industries, which have a high content of electromechanical components. A subsystem can refer to a vehicle's sub-components, such as front components or door components, which can be manufactured and assembled independently before being integrated into a larger system. Eliminating software and microcontrollers on this subsystem, while minimizing wiring (harness) complexity, will reduce costs, eliminate software maintenance, and reduce the overall complexity of the vehicle architecture.

[0022] background

[0023] Although the principles of this disclosure can be applied to a variety of applications, this disclosure provides a motor vehicle as an example to illustrate and discuss the concept of a softwareless subsystem.

[0024] With the increasing number of advanced driver assistance systems (ADAS) features, convenience control functions, and data collection and sensor measurements included in modern vehicles, the electrical and electronic (E / E) architecture for vehicles has become increasingly complex.

[0025] Initially, each of these devices was directly connected to a dedicated electronic control module (ECU), which controlled the devices and implemented the logic for their behavior and functions. Over time, multiple functions have been integrated into domain controllers, which can operate on multiple devices simultaneously. To avoid using long cables to receive sensor information or drive actuators to and from these devices, these domain controllers use communication signals such as Controller Area Network (CAN) or Local Interconnect Network (LIN). For devices operating via these networks, they will need to interpret commands from signals within the network and be able to return information via signals over the network. This means that each device connected to these networks needs a microcontroller with associated software to support the communication protocols and translate signals into functional peripheral actions for the device. These peripheral actions are typically implemented using local signals such as General Purpose Input / Output (GPIO), Pulse Width Modulation (PWM), Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C), or Universal Asynchronous Receiver / Transmitter (UART).

[0026] Recently, a technology called Ethernet to Edge Bus (E2B) has emerged, which implements a fixed message delivery protocol over Ethernet packets. This protocol supports signals used for the most common peripheral actions mentioned above. This means that this new technology can now replace the need for dedicated microcontrollers and software for each device to translate command and control messages, effectively supporting Remote Control Protocol (RCP) over Ethernet. See, for example... Figures 6 to 7 .

[0027] benefit

[0028] This disclosure can provide optimizations for subsystems that may be driven by cost reduction pressures. Removing the microcontroller and CAN / LIN transceiver will eliminate these silicon components from the device's circuit design, but they will be replaced by E2B endpoint components. Reducing printed circuit board (PCB) space and power consumption by eliminating the microcontroller can also ultimately contribute to design optimization.

[0029] Furthermore, throughout the assembly of the subsystem, where all E / E components are interconnected via the same Ethernet interface cable and the devices are powered by a single common power supply line, optimizations are achieved by reducing wiring complexity. Most importantly, significant optimizations are achieved by eliminating software layers such as the operating system, communication stack, and bootloader from each device, thus removing all software from the subsystem. See, for example... Figures 4 to 5 Additionally, the system disclosed herein may include a group control algorithm for a virtual device driver of a software-defined vehicle.

[0030] Figure 1A top view of a vehicle 10 is shown, illustrating various electrical devices, electrical control units (ECUs), and wiring interconnections, wherein the vehicle 10 is divided into four sections 20, 22, 24, and 26. Figure 1 A typical vehicle is shown. High-end vehicles may have more than one hundred ECUs distributed across vehicle 10. Each of the four zones 20, 22, 24, and 26 includes a zone controller 30 configured to interface with input and / or output devices (such as sensors and actuators) in the corresponding zone 20, 22, 24, and 26.

[0031] Example Subsystem

[0032] To illustrate the concept of a software-free subsystem, this disclosure provides a front subsystem component of a vehicle that may be referred to as the dashboard.

[0033] The dashboard of a modern motor vehicle contains many electronic components, such as headlights, cameras, long-range radar, grille shutters, fog lights, turn signals, ultrasonic sensors, blind spot detection radar, horn, etc.

[0034] Figure 2 A block diagram of a first instrument panel assembly 50 for a vehicle with a conventional electrical and electronic (E / E) configuration is shown. The first instrument panel assembly 50 includes several complex devices 52, such as headlight assemblies and radar sensors, and its operation may be relatively computationally intensive. Therefore, each of the highly complex devices 52 is directly connected to a dedicated first electronic control unit (ECU) 60, wherein onboard software 61 manages the operation of the corresponding highly complex device 52. Each of the highly complex devices 52 may include several different output devices, such as lighting arrays or radar transmitters. Additionally or alternatively, each of the highly complex devices 52 may include several different input devices, such as sensors or radar receivers.

[0035] The first instrument panel assembly 50 also includes several medium-complexity devices 54, such as air intake grille louvers. Each medium-complexity device 54 may include actuators coupled to one or more sensors, such as end-of-stroke limit switches and / or current sensors. Each of the medium-complexity devices 54 is directly connected to a dedicated second ECU 62 to manage the operation of the corresponding medium-complexity device 54. The second ECU 62 may not include software, but may include dedicated hardware to control the operation of the corresponding medium-complexity device 54.

[0036] The first instrument panel assembly 50 also includes several low-complexity devices 53, such as fog lights, a horn, a washer fluid pump, and an ultrasonic parking sensor. Each of the low-complexity devices 53 can perform a corresponding function when power is applied to it. Some of the low-complexity devices 53 (such as the ultrasonic parking sensor) can generate control signals indicating the detected object.

[0037] The first dashboard assembly 50 also includes a camera device 56 that generates image signals and transmits them to a receiving device (such as an ADAS controller) via a video interface 57 (such as HDMI or other electrical interface configured to send one or more analog and / or digital video signals).

[0038] like Figure 2 As shown, each of ECUs 60, 62 and each of the low-complexity devices 53 has power and signal interface wiring 64, which is aggregated and mated to the outside of the first instrument panel assembly 50 at a first connector 66. The first connector 66 may include a large multi-pin wiring plug / receptacle for transmitting power and communication signals. Also as shown, a video interface 57 is connected to the outside of the first instrument panel assembly 50 at a camera device interface connector 68, which is separate from and independent of the first connector 66.

[0039] Each of ECUs 60 and 62 may be a relatively small device, including a small circuit board attached to or adjacent to the corresponding sensor or actuator device. In some cases, ECUs 60 and 62 may include dedicated circuit boards in a separate housing attached to the corresponding devices 52 and 54.

[0040] Some devices may include dedicated device controller chips that already support LIN or CAN interfaces, such as stepper motor drivers or blind-spot radars. These devices may not require custom software or microcontrollers and can be directly connected to E2B endpoint interfaces.

[0041] Figure 3A block diagram of a second instrument panel assembly 80 for a vehicle and having a software-free E / E configuration is shown according to one aspect of this disclosure. The second instrument panel assembly 80 includes the same devices 52, 54, 53 as the first instrument panel assembly 50. However, the second instrument panel assembly 80 includes a plurality of remote control interfaces 90 in place of the ECUs 60, 62. The remote control interfaces 90 may also be referred to as edge bus interfaces. As shown, each of the remote control interfaces 90 implements a remote control protocol (RCP) 91 for communication and / or power supply via an Ethernet bus 94. The second instrument panel assembly 80 includes a second connector 92 that provides removable attachment of the second instrument panel assembly 80 to the vehicle's control and electrical infrastructure. The second connector 92 includes a connection for the Ethernet bus 94. Additionally or alternatively, the second connector 92 may include a connection for a video interface 57.

[0042] Eliminate software and remote control

[0043] Figure 4 It shows Figure 2 A block diagram of the control software stack of several microcontrollers 102, 104, 106, and 108 in the first dashboard component, and Figure 5 It shows the configuration to control Figure 3 A block diagram of the control software stack of the processor 120 in the second dashboard component. Figure 5 The control software stack can be implemented, for example, by one of the area controllers 30.

[0044] like Figure 4As shown, each of the first ECU 60 and the second ECU 62 includes a corresponding microcontroller among microcontrollers 102, 104, 106, and 108, and each of the microcontrollers 102, 104, 106, and 108 includes a base software stack 110 such as a real-time operating system (RTOS), and drivers for various hardware interfaces, such as analog-to-digital converters (ADCs), vector stacks, memory management, general purpose input / output (GPIO), local interconnect network (LIN), Ethernet (ETH), and controller area network (CAN). Each of the microcontrollers 102, 104, 106, and 108 also includes a bootloader 111 and hardware interface drivers 112, 114, 116, and 118 for controlling interaction with the corresponding electronic components. Specifically, the first microcontroller 102 among the microcontrollers 102, 104, 106, and 108 includes an intake grille louver control driver 112 for controlling and monitoring the operation of one or more intake grille louvers. The second microcontroller 104 among microcontrollers 102, 104, 106, and 108 includes a radar driver 114 for controlling and monitoring the operation of a long-range or short-range radar device. The third microcontroller 106 among microcontrollers 102, 104, 106, and 108 includes a left headlight driver 116 for controlling and monitoring the operation of the left headlight assembly. The fourth microcontroller 108 among microcontrollers 102, 104, 106, and 108 includes a right headlight driver 118 for controlling and monitoring the operation of the right headlight assembly.

[0045] As in Figure 5 As can be seen, a separate software stack has been eliminated, and control of the devices is implemented in a shared ECU (e.g., one of the area controllers 30) located far from the subsystem. Each device will have representative device drivers 122, 124, 126, 128, which implement specific communications with peripheral functions to operate the device hardware to achieve the required functions. Each of the device drivers 122, 124, 126, 128 can implement similar or identical functions to the corresponding hardware interface drivers 112, 114, 116, 118. The basic software stack 110, including the operating system and communication stack, as well as the bootloader 111, can be shared with the rest of the software on the processor 120.

[0046] Device-specific control software, which was initially on the microcontroller that came with the device and has now moved to shared ECUs, can consist of multiple layers.

[0047] 1) Peripheral configuration, calibration, and diagnostics

[0048] 2) Basic functions and commands

[0049] 3) Low-level control algorithms for motion control used in signal conditioning

[0050] 4) Implement application functions for specific behaviors of features.

[0051] Based on experience, the application functions that implement the specific behaviors described in 4) do not necessarily need to be part of the virtual device driver. Instead, they are implemented separately on top of the control logic software described in 1), 2), and 3). These first three layers expose application programming interfaces (APIs) to the shared ECU environment when the application software can command the device to perform a specific function using a single command.

[0052] Reduce wiring harness

[0053] Further optimization of the software-free subsystem can be achieved by combining power and communication on the same line. This is called Power over Bus or Power over Line. See example Figures 8 to 9 .like Figure 9 As shown, device power and communication lines (such as) can be combined using bus power supply. Figure 8 (As shown) to reduce the complexity of the wiring harness.

[0054] The softwareless subsystem can be part of a larger integrated system. As part of the wiring harness optimization of the larger system, this disclosure also includes the implementation of electrical fuses by each device in the softwareless subsystem. See, for example... Figures 8 to 9 One or more electronic fuses (which may be referred to as e-fuses or eFuses) can be used to reduce or eliminate the need to route power supplies for individual devices to a central fuse box in a larger system for maintainability. If e-fuses are installed on devices within a subsystem, they can be configured and controlled using the same E2B interface without the need for a microcontroller or software, thus maintaining the concept of a software-free subsystem while further optimizing the system's wiring harness.

[0055] Conventional fuses can provide thermal tripping functionality, which disconnects the conductive path in response to a current exceeding a predetermined value. In some cases, conventional fuses may include a time delay to allow combined overcurrents for a period of time before the conductive path is disconnected. To restore the conductive path, the conventional fuse may need to be replaced after disconnection. Electric fuses can provide similar or identical functionality to conventional fuses, such as causing an open circuit in response to an overcurrent condition and / or in response to a current exceeding a predetermined amount for a predetermined period of time. Electric fuses can be reset via software and do not need to be serviceable.

[0056] Additional features

[0057] The following characteristics may be included in a system without a software subsystem:

[0058] Subsystems can be designed to comply with safety regulations (functional safety).

[0059] Ethernet communication interfaces can support security features such as encryption and authentication;

[0060] The device can support features that uniquely identify the hardware, without the ability to remanufacture or reverse engineer it. This will ensure that control software residing on the main system, far removed from the current software subsystem, cannot be used to control copies or replicas of the subsystem; and

[0061] The device can be configured to provide self-diagnostics and health monitoring. These functions can be installed as hardware peripherals of the device and remotely controlled via E2B, supported by virtual device drivers in the remote control software; and

[0062] Device configuration can also be supported via the E2B interface.

[0063] Figure 6 It shows the use of Figure 2 A block diagram of ECUs 60 and 62, which are intelligent sensors or actuators in the first component assembly. ECUs 60 and 62 include a first power converter 150 connected to a power line 152 to receive power from the power line 152. The first power converter 150 can generate power at one or more different voltages required by various loads. The first power converter 150 can perform other functions, such as voltage stabilization or filtering. ECUs 60 and 62 also include a Local Interconnect Network (LIN) interface 154, which is configured to communicate with an external controller via a LIN bus interconnect bus 156. ECUs 60 and 62 also include a hardware sensor or actuator driver 162, which is electrically connected to one or more electronic components, such as... Figures 2 to 3 One or more of devices 52, 53, and 54 shown. Hardware sensor or actuator driver 162 may include input hardware for monitoring sensing signals from input devices of the electronic component. Additionally or alternatively, hardware sensor or actuator driver 162 may include output hardware for sending command and / or electrical signals to operate output devices of the electronic component.

[0064] ECUs 60 and 62 also include a software-enabled microcontroller 164 that functionally communicates with a (LIN) interface 154 and a hardware sensor or actuator driver 162. The microcontroller 164 is shown connected to the hardware sensor or actuator driver 162 via a first Serial Peripheral Interface (SPI) bus 166. However, another type of interconnect can be used for data transfer between them.

[0065] Figure 7 A block diagram of a first edge bus interface 200 for a smart sensor or actuator is shown, and this first edge bus interface can be used as... Figure 3 One of the remote control interfaces 90 in the second instrument panel assembly 80. The first edge bus interface 200 includes a second power converter 210 connected to a power line 152 for receiving power from the power line 152. The second power converter 210 may be similar to or the same as the first power converter 150 of ECUs 60, 62. However, the second power converter 210 may be simplified because it may not need to deliver power to meet the specific requirements of the microcontroller. The first edge bus interface 200 also includes a hardware sensor or actuator driver 162, which may be similar to or the same as the hardware sensor or actuator driver 162 of ECUs 60, 62.

[0066] The first edge bus interface 200 also includes an Ethernet to Edge Bus (E2B) endpoint device 202, which is connected to the Ethernet bus 94 and the hardware sensor or actuator driver 162 via a second SPI bus 206. The E2B endpoint device 202 can be configured to translate messages between the Ethernet bus 94 and the second SPI bus 206 for controlling and / or monitoring one or more electronic components connected to the hardware sensor or actuator driver 162. The first edge bus interface 200 including the E2B endpoint device 202 may be a softwareless device without rewritable memory containing software instructions. For example, the E2B endpoint device 202 may not have writable memory. In some embodiments, the E2B endpoint device 202 may be a purely hardware device whose functionality is hard-coded and cannot be changed. In some embodiments, the E2B endpoint device 202 may include memory containing instructions for its operation. However, the memory may be configured as a read-only memory that cannot be rewritten after the device is manufactured and placed in an operational configuration.

[0067] Figure 8 It shows Figure 7 A block diagram of the first edge bus interface 200 with separate power and communication lines. Figure 9A block diagram is shown showing a second edge bus interface 250 configured to be powered via a bus. The second edge bus interface 250 can be similar to or the same as the first edge bus interface 200, except for the addition of a power distributor 252, which is configured to draw power from the Ethernet bus 94 and provide input power to the second power converter 210. Therefore, the second edge bus interface 250 may not include any power line 152 connection, and the Ethernet bus 94 can instead be used for both data and power interfaces.

[0068] This disclosure provides a softwareless component. The softwareless component includes: a plurality of electronic components, the plurality of electronic components including one or more input devices and one or more output devices; a shared communication interface configured to transmit status data from one or more input devices to an external consumer located outside the softwareless component, and to transmit control signals from an external command source located outside the softwareless component to one or more output devices. The softwareless component also includes a plurality of remote control interfaces, each operatively connected to one or more electronic components. The plurality of remote control interfaces are configured to transmit at least one of the following between the shared communication interface and one or more electronic components operatively connected to the shared communication interface: status data and control signals. All of the plurality of remote control interfaces are softwareless devices without a rewritable memory containing software instructions.

[0069] In some implementations, the shared communication interface includes an Ethernet bus. However, different communication buses, such as a Controller Area Network (CAN) bus, can be used.

[0070] In some implementations, at least one of the external consumer and the external command source is configured to communicate with multiple remote control interfaces via an Ethernet bus using the Remote Control Protocol (RCP).

[0071] In some implementations, at least one of the remote control interfaces is configured to receive power substantially entirely via a shared communication interface. For example, one or more remote control interfaces may include… Figure 9 The second edge bus interface 250 is shown in the figure.

[0072] In some implementations, at least one of the external consumer and the external command source includes a device driver for at least one of the following: one or more input devices and one or more output devices. For example, the external consumer and the external command source may each be implemented in a region controller 30, which may include a device driver, such as... Figure 5 The device drivers shown are 122, 124, 126, and 128.

[0073] In some implementations, at least one of the remote control interfaces includes an electronic fuse configured to limit current supplied to a corresponding electronic component among a plurality of electronic components, and the remote control interface may be configured to selectively reset the electronic fuse based on messages received via a shared communication interface. For example, edge bus interfaces 200, 250 may include references to... Figure 9 The electric fuse shown and described.

[0074] This disclosure also provides a component for a vehicle that includes the software-free components described herein. For example, the component for a vehicle may include a second instrument panel component 80. However, the principles of this disclosure can be applied to other vehicle components, such as door components or integrated powertrain modules.

[0075] In some implementations, at least one of the remote control interfaces includes a peripheral interface for communicating with a corresponding electronic component among a plurality of electronic components. The peripheral interface includes at least one of the following: a serial peripheral interface (SPI), an internal integrated circuit (I2C) interface, or a universal asynchronous receiver / transmitter (UART). Furthermore, at least one of the remote control interfaces is configured to convert messages between a shared communication interface and the peripheral interface.

[0076] This disclosure also provides a control system for software-free components. The control system includes: a shared communication interface; a shared electronic control unit (ECU) operatively connected to the shared communication interface; and a plurality of remote control interfaces. Each of the remote control interfaces is operatively connected between the shared communication interface and one or more electronic components operatively connected to the shared communication interface. Each remote control interface is configured to transmit at least one of the following between the shared communication interface and one or more electronic components operatively connected to the shared communication interface: a status data message or a control signal. All of the plurality of remote control interfaces are software-free devices without a rewritable memory containing software instructions.

[0077] This disclosure also provides a component for a vehicle that includes the control system described herein. For example, the component for a vehicle may include a second instrument panel component 80. However, the principles of this disclosure can be applied to other vehicle components, such as door components or integrated powertrain modules.

[0078] The systems, methods, and / or processes and their steps described above can be implemented in hardware, software, or any combination of hardware and software suitable for a particular application. Hardware may include general-purpose computers and / or special-purpose computing devices, or specific aspects or components of specific computing devices. These processes may be implemented in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors, or other programmable devices together with internal and / or external memory. These processes may also be implemented, or alternatively, in application-specific integrated circuits, programmable gate arrays, programmable array logic, or any other device or combination of these devices that can be configured to process electronic signals. It will also be understood that one or more of the processes may be implemented as computer-executable code capable of executing on a machine-readable medium.

[0079] Computer executable code can be created using structured programming languages ​​such as C, object-oriented programming languages ​​such as C++, or any other high- or low-level programming languages ​​(including assembly language, hardware description languages, and database programming languages ​​and techniques). Computer executable code can be stored, compiled, or interpreted to run on one of the following: heterogeneous combinations of the aforementioned devices and processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.

[0080] Therefore, in one aspect, each of the methods and combinations thereof described above can be implemented as computer-executable code that performs the steps of the methods when executed on one or more computing devices. In another aspect, these methods can be implemented in a system that performs their steps and can be distributed across devices in various ways, or all functionality can be integrated into a dedicated, standalone device or other hardware. In yet another aspect, the means for performing the steps associated with the processes described above can include any of the aforementioned hardware and / or software. All such enumerations and combinations are intended to fall within the scope of this disclosure.

[0081] The foregoing description is not intended to be exhaustive or limiting of this disclosure. Elements or features of a particular embodiment are generally not limited to that particular embodiment, but are interchangeable where applicable and can be used in chosen embodiments, even if not specifically shown or described. Elements or features of a particular embodiment can also vary in many ways. Such variations should not be considered as departing from this disclosure, and all such modifications are intended to be included within the scope of this disclosure.

[0082] Note that this disclosure may also have the following configurations.

[0083] (1) A software-free component, comprising:

[0084] Multiple electronic components, the multiple electronic components including one or more input devices and one or more output devices;

[0085] A shared communication interface configured to transmit status data from the one or more input devices to an external consumer located outside the software-free component, and to transmit control signals from an external command source located outside the software-free component to the one or more output devices; and

[0086] A plurality of remote control interfaces, each operably connected to one or more of the plurality of electronic components, wherein each of the plurality of remote control interfaces is configured to transmit at least one of the following between the shared communication interface and one or more electronic components operably connected to the shared communication interface: the status data and / or the control signal, and

[0087] Among them, the multiple remote control interfaces are all softwareless devices that do not have a rewritable memory containing software instructions.

[0088] (2) The software-free component according to (1), wherein the shared communication interface includes an Ethernet bus.

[0089] (3) The software-free component according to (2), wherein at least one of the external consumer and the external command source is configured to communicate with the plurality of remote control interfaces via the Ethernet bus using the Remote Control Protocol (RCP).

[0090] (4) The software-free component according to (1), wherein at least one of the plurality of remote control interfaces is configured to receive power substantially entirely via the shared communication interface.

[0091] (5) The software-free component according to (1), wherein at least one of the external consumer and the external command source includes a device driver for at least one of the following: the one or more input devices and the one or more output devices.

[0092] (6) The software-free component according to (1), wherein at least one of the remote control interfaces includes an electronic fuse, the electronic fuse being configured to limit the current supplied to a corresponding electronic component among the plurality of electronic components, and

[0093] The at least one of the remote control interfaces is configured to selectively reset the electronic fuse based on messages received via the shared communication interface.

[0094] (7) A component for a vehicle, the component comprising the software-free component according to (1).

[0095] (8) The component for a vehicle according to (7), wherein the component includes a dashboard.

[0096] (9) The software-free component according to (1), wherein at least one of the remote control interfaces includes a peripheral interface for communicating with a corresponding electronic component among the plurality of electronic components.

[0097] The peripheral interface includes at least one of the following: Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C) interface, or Universal Asynchronous Receiver / Transmitter (UART), and

[0098] The remote control interface is configured to switch messages between the shared communication interface and the peripheral interface.

[0099] (10) A control system for software-free components, the control system comprising:

[0100] Shared communication interface;

[0101] A shared electronic control unit (ECU), operably connected to the shared communication interface; and

[0102] Multiple remote control interfaces, each operably connected between the shared communication interface and one or more electronic components, wherein each of the multiple remote control interfaces is configured to transmit at least one of the following between the shared communication interface and the one or more electronic components operably connected to the shared communication interface: status data from one or more input devices and / or control signals from one or more output devices.

[0103] Among them, the multiple remote control interfaces are all softwareless devices that do not have a rewritable memory containing software instructions.

[0104] (11) The control system according to (10), wherein the shared communication interface includes an Ethernet bus.

[0105] (12) The control system according to (11), wherein the shared ECU is configured to communicate with the plurality of remote control interfaces via the Ethernet bus using the Remote Control Protocol (RCP).

[0106] (13) The control system according to (10), wherein at least one of the plurality of remote control interfaces is configured to receive power substantially entirely via the shared communication interface.

[0107] (14) The control system according to (10), wherein the shared ECU includes a device driver for at least one of the electronic components.

[0108] (15) The control system according to (10), wherein at least one of the remote control interfaces includes an electronic fuse, the electronic fuse being configured to limit the current supplied to the one or more electronic components, and

[0109] The at least one of the remote control interfaces is configured to selectively reset the electronic fuse based on messages received via the shared communication interface.

[0110] (16) A component for a vehicle, the component comprising the control system according to (10).

[0111] (17) The component for a vehicle according to (16), wherein the component includes an instrument panel.

Claims

1. A software component-free device, comprising: Multiple electronic components, including one or more input devices (52, 53, 54) and one or more output devices (52, 53, 54). A shared communication interface is configured to transmit status data from the one or more input devices (52, 53, 54) to an external consumer located outside the software-free component, and to transmit control signals from an external command source located outside the software-free component to the one or more output devices (52, 53, 54). as well as A plurality of remote control interfaces (90), each operably connected to one or more of the plurality of electronic components, wherein each of the plurality of remote control interfaces (90) is configured to transmit at least one of the following between the shared communication interface and one or more electronic components operably connected to the shared communication interface: the status data and / or the control signal, and Among them, the plurality of remote control interfaces (90) are all softwareless devices (52, 53, 54) without a rewritable memory containing software instructions.

2. The software-free component according to claim 1, wherein, The shared communication interface includes an Ethernet bus (94).

3. The software-free component according to claim 2, wherein, At least one of the external consumer and the external command source is configured to communicate with the plurality of remote control interfaces (90) via the Ethernet bus (94) using the Remote Control Protocol (RCP).

4. The software-free component according to claim 1, wherein, At least one of the plurality of remote control interfaces (90) is configured to receive power substantially entirely via the shared communication interface.

5. The software-free component according to claim 1, wherein, At least one of the external consumer and the external command source includes a device driver for at least one of the following: the one or more input devices (52, 53, 54) and the one or more output devices (52, 53, 54).

6. The software-free component according to claim 1, wherein, At least one of the remote control interfaces (90) includes an electronic fuse, which is configured to limit the current supplied to a corresponding electronic component among the plurality of electronic components, and The remote control interface (90) is configured to selectively reset the electronic fuse based on messages received via the shared communication interface.

7. The software-free component according to claim 1, wherein, At least one of the remote control interfaces (90) includes a peripheral interface for communicating with a corresponding electronic component among the plurality of electronic components. The peripheral interface includes at least one of the following: Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C) interface, or Universal Asynchronous Receiver / Transmitter (UART), and The remote control interface (90) is configured to switch messages between the shared communication interface and the peripheral interface.

8. A component for a vehicle (10), the component comprising the software-free component according to claim 1.

9. A control system for software-free components, the control system comprising: Shared communication interface; A shared electronic control unit (30) is operatively connected to the shared communication interface; as well as A plurality of remote control interfaces (90), each operably connected between the shared communication interface and one or more electronic components, wherein each of the plurality of remote control interfaces (90) is configured to transmit between the shared communication interface and the one or more electronic components operably connected to the shared communication interface at least one of the following: status data from one or more input devices (52, 53, 54) and / or control signals from one or more output devices (52, 53, 54), and Among them, the multiple remote control interfaces (90) are all softwareless devices (52, 53, 54) without a rewritable memory containing software instructions.

10. The control system according to claim 9, wherein, The shared communication interface includes an Ethernet bus (94).

11. The control system according to claim 10, wherein, The shared electronic control unit (30) is configured to communicate with the plurality of remote control interfaces (90) via the Ethernet bus (94) using the Remote Control Protocol (RCP).

12. The control system according to claim 9, wherein, At least one of the plurality of remote control interfaces (90) is configured to receive power substantially entirely via the shared communication interface.

13. The control system according to claim 9, wherein, The shared electronic control unit (30) includes a device driver for at least one of the electronic components.

14. The control system according to claim 9, wherein, At least one of the remote control interfaces (90) includes an electronic fuse, which is configured to limit the current supplied to the one or more electronic components, and The remote control interface (90) is configured to selectively reset the electronic fuse based on messages received via the shared communication interface.

15. A component for a vehicle (10), the component comprising the control system according to claim 9.

Images