Vehicle control device
The vehicle control device manages data transmission cycles to facilitate low-cost data transfer between ECUs using existing ECUs, addressing the need for FIFO functionality without BSW changes.
Patent Information
- Application Number
- JP2023082591
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-18
- Publication Date
- 2024-11-28
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing electronic control units (ECUs) lack FIFO functionality, necessitating costly changes to Basic Software (BSW) for data transfer between multiple ECUs.
A vehicle control device with a determination unit that manages data transmission cycles and utilizes event transmission for fast cycles and regular transmission for longer cycles, without implementing FIFO, allowing data transfer using existing ECUs without BSW changes.
Enables low-cost data transfer between multiple ECUs by reducing processing load and avoiding BSW modifications.
Smart Images

Figure 2024165964000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a vehicle control device. [Background technology]
[0002] BACKGROUND ART An in-vehicle LAN (Local Area Network) is known that interconnects a plurality of electronic control units (ECUs) mounted on a vehicle. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Publication No. 7-7504 Summary of the Invention [Problem to be solved by the invention]
[0004] When data transfer is required between multiple electronic control units, it is desirable to use an ECU equipped with a FIFO (First In First Out), but various restrictions may require the use of an existing ECU. However, since FIFO is not implemented in typical ECUs, implementing a FIFO requires modifications to the basic software (BSW), which is very costly.
[0005] The present invention has been made in consideration of the above, and aims to provide a vehicle control device that enables data transfer between multiple electronic control devices at low cost using existing ECUs without changing the BSW. [Means for solving the problem]
[0006] In order to solve the above-mentioned problems and achieve the object, the vehicle control device of the present invention is a vehicle control device that does not implement FIFO (First In First Out), and is equipped with a judgment unit that judges the transmission period of received data received from a first electronic control device, and an APL layer that takes in the received data and, if the transmission period is less than a predetermined transmission period, controls the transmission of the received data to a second electronic control device by event transmission.
[0007] According to this configuration, data transfer between a plurality of electronic control units can be realized at low cost using existing ECUs without modifying the BSW.
[0008] Furthermore, in the vehicle control device according to the present invention, the APL layer controls transmission of the received data to the second electronic control device by periodic transmission when the transmission period is equal to or longer than a predetermined transmission period.
[0009] According to this configuration, the processing load on the vehicle control device due to transmission of received data can be reduced. [Effects of the Invention]
[0010] The vehicle control device according to the present invention has the effect of enabling data transfer between a plurality of electronic control devices to be realized at low cost using existing ECUs without modifying the BSW. [Brief explanation of the drawings]
[0011] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a vehicle control system to which a vehicle control device according to this embodiment is applied. [Figure 2] FIG. 2 is a diagram illustrating an example of a functional configuration of the vehicle control device according to this embodiment. [Figure 3] FIG. 3 is a flowchart showing an example of the flow of the reception data transmission and reception process in the vehicle control device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0012] An example of a vehicle control device according to the present invention will be described in detail below with reference to the drawings.
[0013] 1 is a diagram showing an example of the configuration of a vehicle control system to which a vehicle control device according to this embodiment is applied. First, an example of the configuration of a vehicle control system 1 according to this embodiment will be described with reference to FIG.
[0014] The vehicle control system 1 according to this embodiment includes a vehicle system 11, a gateway 12, a vehicle control device 13, and an EV system 14. The vehicle system 11 and the EV (Electric Vehicle) system 14 are connected to each other via the gateway 12 and the vehicle control device 13.
[0015] The gateway 12 is a device or software that relays communications between two parties or networks that use different communication procedures (for example, protocols).
[0016] The vehicle system 11 includes electronic control devices such as an A / C ECU 111, a BDY ECU 112, a VSC ECU 113, an A / B ECU 114, and an EPS ECU 115. The A / C ECU 111 controls an air conditioning system mounted on the vehicle. The BDY ECU 112 controls so-called body systems such as meters, wipers, and lights, and also controls left and right turn signals and door lock motors that must operate even when the vehicle ignition switch is off. The VSC (Vehicle Stability Control) ECU 113 controls the vehicle's braking system and suppresses skidding of the vehicle by controlling the braking system. The A / B ECU 114 controls the operation of passenger protection devices such as airbags. The EPS (Electric Power Steering) ECU 115 receives detection signals from a steering angle sensor and controls the vehicle's steering system.
[0017] The EV system 14 includes electronic control devices such as an EV ECU 141 and a battery ECU 142, and controls the drive motor. The EV ECU 141 controls the output of the BEV (Battery Electric Vehicle) system based on signals from various sensors and computers. The EV ECU 141 also monitors the status of the EV supply battery (e.g., SOC (State of Charge), battery voltage, current value, and temperature). When the charging connector is connected, the EV ECU 141 stops the BEV control system based on a signal from the charging cable (EV charger cable assembly). The EV ECU 141 also controls the DC-DC converter. The EV ECU 141 also variably controls the discharge rate of the inverter water pump (water pump assembly). When the EV ECU 141 receives an airbag deployment signal from the airbag computer assembly, it activates the SMR (System Main Relay) to cut off power to the high-voltage circuit. The battery ECU 142 sends various information to the EV control computer. The battery ECU 142 also drives a temperature rise relay based on battery temperature sensor information from a water temperature sensor, a heater thermistor in the battery coolant heater assembly, and a satellite battery module (SBM).
[0018] The vehicle control device 13 is an example of a vehicle control device that does not have a FIFO. The vehicle control device 13 realizes data transfer between the vehicle system 11 and the EV system 14 using a CAN (Controller Area Network) transmission / reception function, which is an example of a serial communication protocol. Specifically, the vehicle control device 13 receives data with a fast transmission cycle at the fastest possible cycle using the APL layer, and immediately transmits the data by utilizing an existing event transmission function.
[0019] This reduces the processing load on the ECU by determining whether or not an event needs to be sent based on the data transmission cycle. Furthermore, because existing ECUs can be used, there is no need to modify the BSW, making it possible to achieve this at low cost. Furthermore, this can be achieved with any ECU that is a general vehicle ECU and has CAN transmission / reception functionality.
[0020] 2 is a diagram showing an example of the functional configuration of the vehicle control device according to this embodiment. Next, an example of the functional configuration of the vehicle control device 13 according to this embodiment will be described with reference to FIG.
[0021] As shown in FIG. 2, the vehicle control device 13 according to this embodiment includes a message box 131, a BSW 132, an RTE 133, and an APL layer 134.
[0022] The message box 131 stores data (received data) received from an ECU (first electronic control unit) included in the vehicle system 11 or the EV system 14. At this time, the message box 131 stores the received data in the order in which it was received. The message box 131 also stores received data to be transmitted to an ECU (second electronic control unit) included in the vehicle system 11 or the EV system 14. Here, the second electronic control unit is an ECU different from the first electronic control unit. In this embodiment, the message box 131 stores received data transmitted and received by the CAN transmission / reception function.
[0023] The BSW (Basic Software) 132 is a group of software modules that provide various functions. Specifically, the BSW 132 includes a SVL (Services Layer) 132a, an EAL (ECU Abstraction Layer) 132b, a COM (Complex Drivers) 132c, and an MCAL (Microcontroller Abstraction Layer) 132d.
[0024] The SVL 132a manages the status of the OS (Operating System), the network, and various ECUs, etc. The EAL 132b acts as an interface with the MCAL 132d and is responsible for accessing peripheral equipment and devices.
[0025] The MCAL 132d corresponds to a device driver, absorbing differences between peripheral devices and making upper level software independent of the microcomputer. Specifically, the MCAL 132d functions as a determination unit that determines the transmission period of received data received from another ECU included in the vehicle system 11 or the EV system 14. Here, the other ECU may be an ECU external to the vehicle control device 13. In this embodiment, the COM 132c may determine the priority of the received data (e.g., a CAN signal) based on the ID of the received data, and determine the transmission period of the received data based on the determined priority.
[0026] Furthermore, the MCAL 132d determines whether the transmission cycle of the received data is short, in other words, whether the transmission cycle of the received data is shorter than a predetermined transmission cycle. Here, the predetermined transmission cycle may be a transmission cycle that is set in advance and determines that the transmission cycle of the received data is short. Alternatively, the MCAL 132d may determine whether the priority of the received data is higher than a predetermined priority. Here, the predetermined priority may be a priority that is set in advance and determined based on the transmission cycle of the received data.
[0027] Furthermore, the MCAL 132d receives reception data from another ECU using the CAN transmission / reception function, and stores the reception data in the order in which it was received in the message box 131. Furthermore, the MCAL 132d transmits the reception data stored in the message box 131 to another ECU using the CAN transmission / reception function.
[0028] Furthermore, when an event transmission request is issued by the APL layer 134 for the received data, the MCAL 132d stores the received data in a transmission queue and stores the received data stored in the transmission queue in the message box 131 at the timing of the transmission cycle. Furthermore, when an event transmission request is not issued by the APL layer 134 for the received data, the MCAL 132d stores the received data in a transmission queue and stores the received data stored in the transmission queue in the message box 131 at the timing of a fixed cycle (periodic transmission).
[0029] COM 132c is used when directly accessing the microcomputer from an upper layer when high responsiveness is required, etc. Specifically, COM 132c is triggered by the reception of reception data by the CAN transmission / reception function to store the reception data stored in the message box 131 in the reception buffer. However, when receiving data whose determined transmission cycle is shorter than a predetermined transmission cycle to be stored in the reception buffer, COM 132c interrupts the storage of other reception data in the reception buffer and stores the reception data whose transmission cycle is shorter than the predetermined transmission cycle in the reception buffer.
[0030] In this embodiment, the COM 132c interrupts other received data and stores the received data in the receive buffer based on the transmission cycle of the received data, but it may also interrupt other received data and store the received data in the receive buffer based on the priority based on the ID of the received data. Specifically, if the priority based on the ID of the received data is higher than a predetermined priority, the COM 132c interrupts other received data and stores the received data in the receive buffer.
[0031] Furthermore, the COM 132c stores in a transmission buffer the received data acquired by the APL layer 134. Furthermore, when the APL layer 134 issues an event transmission request for the received data, the COM 132c immediately stores the acquired received data in a transmission buffer.
[0032] The RTE (Runtime Environment) 133 connects the APL layer 134 and the BSW 132 .
[0033] The APL layer (Application Layer) 134 is a layer that implements specific systems and required functions, and realizes various functions such as control. Specifically, the APL layer 134 takes in received data from a receive buffer. Next, if the transmission cycle of the taken-in received data is shorter than a predetermined transmission cycle, the APL layer 134 executes transmission control processing of the received data at the fastest APL cycle.
[0034] As a result, received data with a fast transmission cycle can be taken into the APL layer 134 at the fastest possible cycle, and data can be transmitted immediately by utilizing the existing event transmission function. As a result, even if the vehicle control device 13 does not have a FIFO, the APL layer 134 can control the transmission of the received data, suppressing transmission delays of the received data and transmitting the received data as if it were a FIFO. Furthermore, data transfer between multiple electronic control devices can be achieved at low cost using existing ECUs without changing the BSW.
[0035] Here, the transmission control process for the received data in the fastest APL cycle may be transmission control of the received data in the event transmission to an ECU of the vehicle system 11 or the EV system 14. The event transmission is a process of immediately transmitting the received data, and may be a transmission process with a transmission cycle of 1 ms, for example. In this embodiment, the transmission control process for the received data in the fastest APL cycle includes a process of issuing an event transmission request (for example, a request to turn on the headlights) to the COM 132c, which requests transmission of the received data in the event transmission.
[0036] Furthermore, if the transmission cycle of the captured received data is equal to or longer than a predetermined transmission cycle, the APL layer 134 executes a process for controlling transmission of the received data at a fixed cycle (periodic transmission). As a result, if an event transmission request is not issued, the transmission control of the received data is performed at a fixed cycle, and whether or not an event transmission is required can be determined depending on the transmission cycle of the received data, thereby reducing the processing load on the vehicle control device 13 due to transmission of the received data. Here, the process for controlling transmission of the received data at a fixed cycle may be control for transmitting the received data to an ECU in the vehicle system 11 or the EV system 14 at a transmission cycle (e.g., 8 ms) longer than the event transmission.
[0037] 3 is a flowchart showing an example of the flow of the transmission and reception process of received data in the vehicle control device 13 according to this embodiment. Next, an example of the flow of the transmission and reception process of received data in the vehicle control device 13 according to this embodiment will be described with reference to FIG.
[0038] The MCAL 132d receives received data from another ECU, for example, via channel 1 of the CAN bus (step S301). Next, the MCAL 132d determines whether the transmission cycle of the received data is faster than a predetermined transmission cycle or whether the priority of the received data is higher than a predetermined priority (step S302). If the transmission cycle of the received data is faster than the predetermined transmission cycle or if the priority of the received data is higher than the predetermined priority (step S302: Yes), the MCAL 132d stores the received data in the message box 131 (step S303).
[0039] Next, the COM 132c interrupts the storage of other received data in the receive buffer and stores received data whose transmission period is faster than the predetermined transmission period or whose priority is higher than the predetermined priority in the receive buffer (step S304). Next, the APL layer 134 retrieves the received data from the receive buffer, and if the transmission period of the retrieved received data is shorter than the predetermined transmission period, executes transmission control processing for the received data at the fastest APL period (step S305). When an event transmission request is issued by the APL layer 134, the COM 132c immediately stores the retrieved received data in the transmission buffer (step S306).
[0040] When an event transmission request is issued by the APL layer 134 (step S307: Yes), the MCAL 132d stores the received data in the message box 131 by an event transmission process, that is, at the timing of the transmission cycle of the received data (step S308). After that, the MCAL 132d transmits the received data stored in the message box 131 to another ECU, for example, via channel 2 of the CAN bus (step S309).
[0041] On the other hand, if the transmission period of the received data is equal to or greater than the predetermined transmission period or if the priority of the received data is equal to or less than the predetermined priority (step S302: No), the MCAL 132d stores the received data in the message box 131 (step S310). Next, the COM 132c stores the received data stored in the message box 131 in the receive buffer (step S311). Next, the APL layer 134 retrieves the received data from the receive buffer, and if the transmission period of the retrieved received data is equal to or greater than the predetermined transmission period, executes a periodic transmission control process for the received data (APL periodic process) (step S312). The COM 132c stores the received data retrieved by the APL layer 134 in the transmit buffer (step S306).
[0042] If the APL layer 134 has not issued an event transmission request (step S307: No), the MCAL 132d periodically stores the received data in the message box 131 (step S313). After that, the MCAL 132d transmits the received data stored in the message box 131 to another ECU, for example, via channel 2 of the CAN bus (step S309).
[0043] As described above, according to the vehicle control device 13 of this embodiment, the APL layer 134 retrieves received data from the receive buffer, and if the transmission cycle of the retrieved received data is shorter than a predetermined transmission cycle, executes transmission control processing for the received data at the fastest APL cycle. By doing so, received data with a fast transmission cycle is retrieved into the APL layer 134 at the fastest cycle, and data transmission can be performed immediately by utilizing the existing event transmission function. Therefore, even if the vehicle control device 13 does not have a FIFO, the APL layer 134 controls transmission of the received data, suppressing transmission delays of the received data and transmitting the received data as if it were a FIFO. Furthermore, data transfer between multiple electronic control devices can be achieved at low cost using existing ECUs without modifying the BSW.
[0044] Furthermore, according to the vehicle control device 13 of this embodiment, when the transmission period of the captured received data is equal to or longer than a predetermined transmission period, the APL layer 134 executes a transmission control process for the received data at a fixed period. Therefore, when an event transmission request is not issued, the transmission control of the received data is performed at a fixed period, and whether or not an event transmission is required can be determined depending on the transmission period of the received data, thereby reducing the processing load on the vehicle control device 13 due to the transmission of the received data. [Explanation of symbols]
[0045] 1. Vehicle control system 11 Vehicle Systems 12 Gateway 13 Vehicle control device 14 EV System 131 Message Box 132 BSW 132a 132b 132c 132d 133 RTE 134 APL layer
Claims
1. A vehicle control device that does not implement a FIFO (First In First Out) a determination unit that determines a transmission period of reception data received from the first electronic control unit; an APL layer that takes in the received data and, if the transmission period is less than a predetermined transmission period, controls transmission of the received data to a second electronic control unit by event transmission; A vehicle control device comprising:
2. The vehicle control device according to claim 1 , wherein the APL layer controls transmission of the received data to the second electronic control device by regular transmission when the transmission period is equal to or longer than the predetermined transmission period.
Citation Information
Patent Citations
Electrical equipment controller for vehicle
JP1995007504A
