In-vehicle control system
The in-vehicle control system uses multiple control devices on separate networks to accurately notify failures, resolving user confusion by distinguishing between communication line faults and device malfunctions.
Patent Information
- Application Number
- JP2021015747
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-03
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-02-03
AI Technical Summary
Existing on-vehicle control systems fail to accurately distinguish between communication line faults and control device failures, leading to user misunderstandings about vehicle operation.
An in-vehicle control system with multiple control devices connected via different communication networks, allowing one device to verify the status of another and control a failure indicator accordingly, ensuring accurate failure notification without user confusion.
The system effectively notifies control device failures without misleading users, preventing inappropriate actions by distinguishing between communication errors and actual device malfunctions.
Smart Images

Figure 0007589573000001 
Figure 0007589573000002 
Figure 0007589573000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an in-vehicle control system. [Background technology]
[0002] Patent Document 1 describes that if it is determined that an abnormality that is a precursor to a disconnection has occurred on the CAN (Controller Area Network) bus between the engine control ECU (Electronic Control Unit) and the instrument panel control ECU, abnormality information is displayed on a display to warn the driver.
[0003] Conventionally, when a communication error occurred in the communication line to which a control device was connected, it was unclear whether the control device itself was at fault or whether only the communication line was at fault, so other control devices communicating with this control device would light up a fault indicator as a fail-safe. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2009-213092 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, such control has a problem in that even if the control device is operating to control the vehicle normally, the user may mistakenly believe that a serious malfunction has occurred. This mistaken belief may lead the user to take a different action than he or she should have taken.
[0006] Therefore, an object of the present invention is to provide an in-vehicle control system that can notify a user of a failure in a control device without misleading the user. [Means for solving the problem]
[0007] In order to solve the above problems, the present invention provides an in-vehicle control system including a first control device, a second control device, a third control device, a failure indicator that turns on when a failure of the first control device is detected, and an in-vehicle communication network to which at least the first control device, the second control device, and the third control device are connected, the in-vehicle control system including a communication line different from the in-vehicle communication network and to which at least the first control device and the third control device are connected, the second control device, when detecting the occurrence of a communication error of the first control device in the in-vehicle communication network, acquires information regarding a failure status of the first control device from the third control device, and when it is determined that the first control device is operating normally, turns off the failure indicator. When it is determined that the first control device is not operating normally, the malfunction indicator is turned on. This is what we have in mind. Effect of the Invention
[0008] In this way, according to the present invention, it is possible to notify the user of a failure in the control device without misleading the user. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a schematic diagram of an in-vehicle control system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a flowchart showing a procedure of a fault notification process of the in-vehicle control system according to the first embodiment of the present invention. [Diagram 3] FIG. 3 is a flowchart showing a procedure of the failure information transmission process of the in-vehicle control system according to the first embodiment of the present invention. [Figure 4] FIG. 4 is a flowchart showing a procedure of a fault notification process of the in-vehicle control system according to another aspect of the first embodiment of the present invention. [Diagram 5] FIG. 5 is a flowchart showing a procedure of a failure information transmission process of an in-vehicle control system according to another aspect of the first embodiment of the present invention. [Figure 6]FIG. 6 is a schematic diagram of an in-vehicle control system according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] An in-vehicle control system according to one embodiment of the present invention is an in-vehicle control system comprising a first control device, a second control device, a third control device, a fault indicator that is lit when a fault is detected in the first control device, and an in-vehicle communication network to which at least the first control device, the second control device, and the third control device are connected, the in-vehicle control system including a communication line different from the in-vehicle communication network and to which at least the first control device and the third control device are connected, and when the second control device detects the occurrence of a communication error in the first control device in the in-vehicle communication network, the second control device is configured to obtain information regarding the fault status of the first control device from the third control device, and to turn off the fault indicator when it is determined that the first control device is operating normally.
[0011] As a result, the in-vehicle control system according to one embodiment of the present invention can notify the user of a failure in the control device without misleading the user. EXAMPLES
[0012] Hereinafter, an in-vehicle control system according to an embodiment of the present invention will be described in detail with reference to the drawings.
[0013] (First embodiment) In FIG. 1, a vehicle 1 equipped with an on-board control system according to a first embodiment of the present invention is configured to include a malfunction indicator 2, a meter ECU 3 as a second control device, a first ECU 4 as a first control device, and a second ECU 5 as a third control device.
[0014] The malfunction indicator 2 is provided, for example, on an instrument panel of the vehicle 1, and notifies the user of a malfunction of the first ECU 4 by lighting up.
[0015] The meter ECU 3, the first ECU 4, and the second ECU 5 are each composed of a computer unit having a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory for storing backup data, etc., an input port, and an output port.
[0016] The ROM of these computer units stores various constants, various maps, and the like, as well as programs for causing the computer units to function as the meter ECU 3, the first ECU 4, and the second ECU 5, respectively.
[0017] That is, the CPU executes the programs stored in the ROM using the RAM as a working area, whereby these computer units function as the meter ECU 3, the first ECU 4, and the second ECU 5 in this embodiment, respectively.
[0018] The vehicle 1 is provided with a CAN (Controller Area Network) communication line 10 for forming an in-vehicle communication network conforming to standards such as CAN. The vehicle 1 is also provided with a communication line 11 for forming a network different from the in-vehicle communication network.
[0019] The meter ECU 3 is connected to the first ECU 4 and the second ECU 5 by a CAN communication line 10. The meter ECU 3, the first ECU 4, and the second ECU 5 transmit and receive signals such as control signals to and from each other via the CAN communication line 10.
[0020] The first ECU 4 and the second ECU 5 are connected by a communication line 11 that is different from the CAN communication line 10. The first ECU 4 and the second ECU 5 transmit and receive signals such as control signals to and from each other via the communication line 11.
[0021] When the meter ECU 3 detects a malfunction of the first ECU 4, it turns on the malfunction indicator 2. The malfunction of the first ECU 4 includes the occurrence of a communication error in the in-vehicle communication network.
[0022] When the meter ECU 3 detects the occurrence of a communication error in the first ECU 4 in the in-vehicle communication network, it acquires information regarding the fault condition of the first ECU 4 from the second ECU 5, and when it determines that the first ECU 4 is operating normally, it turns off the fault indicator 2.
[0023] When the second ECU 5 detects the occurrence of a communication error in the first ECU 4 in the in-vehicle communication network, the second ECU 5 acquires information regarding the fault condition from the first ECU 4 via the communication line 11, and transmits to the meter ECU 3 via the in-vehicle communication network, information indicating that the first ECU 4 is normal or that the first ECU 4 is faulty.
[0024] The meter ECU 3 may not turn on the malfunction indicator 2 when it detects that a communication error has occurred in the first ECU 4 in the in-vehicle communication network, but may obtain information regarding the malfunction status of the first ECU 4 from the second ECU 5 and turn on the malfunction indicator 2 when it determines that the first ECU 4 has malfunctioned.
[0025] The fault notification process by the meter ECU 3 of the in-vehicle control system according to the first embodiment configured as above will be described with reference to Fig. 2. The fault notification process described below is started when the meter ECU 3 starts operating, and is executed at preset time intervals.
[0026] In step S1, the meter ECU 3 determines whether the occurrence of a communication error in the first ECU 4 has been detected.
[0027] When it is determined that the occurrence of the communication error in the first ECU 4 is detected, the meter ECU 3 executes the process of step S2. When it is determined that the occurrence of the communication error in the first ECU 4 is not detected, the meter ECU 3 ends the malfunction notification process.
[0028] In step S2, the meter ECU 3 determines whether or not the first ECU 4 is normal. The meter ECU 3 determines whether or not the first ECU 4 is normal, based on the information transmitted from the second ECU 5.
[0029] If the first ECU 4 is determined to be normal, the meter ECU 3 executes the process of step S3. If the first ECU 4 is determined to be abnormal, the meter ECU 3 executes the process of step S4.
[0030] In step S3, the meter ECU 3 turns off the malfunction indicator 2. After executing the process of step S3, the meter ECU 3 ends the malfunction notification process.
[0031] In step S4, the meter ECU 3 turns on the malfunction indicator 2. After executing the process of step S4, the meter ECU 3 ends the malfunction notification process.
[0032] Next, a fault information transmission process by the second ECU 5 of the vehicle control system according to the first embodiment will be described with reference to Fig. 3. The fault notification process described below is started when the second ECU 5 starts operating, and is executed at preset time intervals.
[0033] In step S11, the second ECU 5 determines whether the occurrence of a communication error in the first ECU 4 has been detected.
[0034] If it is determined that the occurrence of the communication error in the first ECU 4 has been detected, the second ECU 5 executes the process of step S12. If it is determined that the occurrence of the communication error in the first ECU 4 has not been detected, the second ECU 5 ends the malfunction information transmission process.
[0035] In step S12, the second ECU 5 acquires information on the fault condition from the first ECU 4 via the communication line 11, and determines whether the first ECU 4 is normal or not.
[0036] If the first ECU 4 is determined to be normal, the second ECU 5 executes the process of step S13. If the first ECU 4 is determined to be abnormal, the second ECU 5 executes the process of step S14.
[0037] In step S13, the second ECU 5 transmits information indicating that the first ECU 4 is normal to the meter ECU 3. After executing the process of step S13, the second ECU 5 ends the malfunction information transmission process.
[0038] In step S14, the second ECU 5 transmits information that the first ECU 4 has a malfunction to the meter ECU 3. After executing the process of step S14, the second ECU 5 ends the malfunction information transmission process.
[0039] Thus, in the first embodiment, when the meter ECU 3 detects the occurrence of a communication error in the first ECU 4 in the in-vehicle communication network, it acquires information regarding the fault condition of the first ECU 4 from the second ECU 5, and when it determines that the first ECU 4 is operating normally, it turns off the fault indicator 2.
[0040] As a result, when the first ECU 4 is operating normally with only a communication error in the in-vehicle communication network of the first ECU 4, the malfunction indicator 2 is turned off, and when it is confirmed that the first ECU 4 has a malfunction, the malfunction indicator 2 is turned on. Therefore, it is possible to notify the user of the malfunction of the first ECU 4 without misleading the user.
[0041] In addition, when the meter ECU 3 detects the occurrence of a communication error in the first ECU 4 in the in-vehicle communication network, it does not turn on the malfunction indicator 2, but when it acquires information regarding the malfunction status of the first ECU 4 from the second ECU 5 and determines that the first ECU 4 has malfunctioned, it turns on the malfunction indicator 2.
[0042] As a result, the malfunction indicator 2 is not turned on when a communication error occurs in the in-vehicle communication network of the first ECU 4, but the malfunction indicator 2 is turned on when it is confirmed that the first ECU 4 has a malfunction. Therefore, it is possible to notify the user of the malfunction of the first ECU 4 without misleading the user.
[0043] In addition to the failure indicator 2, a communication abnormality indicator may be provided. If the fault indicator 2 does not light up when a communication error is detected in the in-vehicle communication network, the user cannot recognize that a communication error has occurred due to a fault or the like in the communication line on the in-vehicle communication network.
[0044] When a communication error occurs, the communication abnormality indicator is turned on to notify the user that a communication error has occurred.
[0045] This is expected to encourage the user to drive the vehicle and bring it to a service workshop at an appropriate time.
[0046] As another aspect of the first embodiment, the meter ECU 3 requests the second ECU 5 to transmit the fault condition of the first ECU 4 when the meter ECU 3 detects the occurrence of a communication error of the first ECU 4 in the in-vehicle communication network.
[0047] When the second ECU 5 receives a request from the meter ECU 3 to transmit information about the fault status of the first ECU 4, the second ECU 5 obtains information about the fault status from the first ECU 4 via the communication line 11 and transmits to the meter ECU 3 information indicating that the first ECU 4 is normal or that the first ECU 4 is faulty.
[0048] A fault notification process by the meter ECU 3 of the in-vehicle control system according to another aspect of the first embodiment configured as above will be described with reference to Fig. 4. The fault notification process described below is started when the meter ECU 3 starts operating, and is executed at preset time intervals.
[0049] In step S21, the meter ECU 3 determines whether the occurrence of a communication error in the first ECU 4 has been detected.
[0050] When it is determined that the occurrence of the communication error in the first ECU 4 is detected, the meter ECU 3 executes the process of step S22. When it is determined that the occurrence of the communication error in the first ECU 4 is not detected, the meter ECU 3 ends the malfunction notification process.
[0051] In step S22, the meter ECU 3 requests the second ECU 5 to transmit the failure state of the first ECU 4. After executing the process of step S22, the meter ECU 3 executes the process of step S23.
[0052] In step S23, the meter ECU 3 determines whether or not the first ECU 4 is normal. The meter ECU 3 determines whether or not the first ECU 4 is normal, based on the information transmitted from the second ECU 5.
[0053] If the first ECU 4 is determined to be normal, the meter ECU 3 executes the process of step S24. If the first ECU 4 is determined to be abnormal, the meter ECU 3 executes the process of step S25.
[0054] In step S24, the meter ECU 3 turns off the malfunction indicator 2. After executing the process of step S24, the meter ECU 3 ends the malfunction notification process.
[0055] In step S25, the meter ECU 3 turns on the malfunction indicator 2. After executing the process of step S25, the meter ECU 3 ends the malfunction notification process.
[0056] Next, a fault information transmission process by the second ECU 5 of the vehicle control system according to another aspect of the first embodiment will be described with reference to Fig. 5. The fault notification process described below is started when the second ECU 5 starts operating, and is executed at preset time intervals.
[0057] In step S31, the second ECU 5 determines whether or not a request for transmission of the failure state of the first ECU 4 has been received from the meter ECU 3.
[0058] If it is determined that the request for transmitting the malfunction status of the first ECU 4 has been received, the second ECU 5 executes the process of step S32. If it is determined that the request for transmitting the malfunction status of the first ECU 4 has not been received, the second ECU 5 ends the malfunction information transmission process.
[0059] In step S32, the second ECU 5 acquires information on the fault condition from the first ECU 4 via the communication line 11, and determines whether the first ECU 4 is normal.
[0060] If the first ECU 4 is determined to be normal, the second ECU 5 executes the process of step S33. If the first ECU 4 is determined to be abnormal, the second ECU 5 executes the process of step S34.
[0061] In step S33, the second ECU 5 transmits information indicating that the first ECU 4 is normal to the meter ECU 3. After executing the process of step S33, the second ECU 5 ends the malfunction information transmission process.
[0062] In step S34, the second ECU 5 transmits information that the first ECU 4 has a malfunction to the meter ECU 3. After executing the process of step S34, the second ECU 5 ends the malfunction information transmission process.
[0063] Thus, in another aspect of the first embodiment, when the meter ECU 3 detects the occurrence of a communication error in the first ECU 4 in the in-vehicle communication network, it requests the second ECU 5 to transmit information regarding the failure status of the first ECU 4, and when it determines that the first ECU 4 is operating normally based on the information regarding the failure status of the first ECU 4 received from the second ECU 5, it turns off the failure indicator 2.
[0064] As a result, when the first ECU 4 is operating normally with only a communication error in the in-vehicle communication network of the first ECU 4, the malfunction indicator 2 is turned off, and when it is confirmed that the first ECU 4 has a malfunction, the malfunction indicator 2 is turned on. Therefore, it is possible to notify the user of the malfunction of the first ECU 4 without misleading the user.
[0065] In the first embodiment and other aspects of the first embodiment, the communication line 11 between the first ECU 4 and the second ECU 5 is connected in a bus-type configuration, but a one-to-one connection may also be used.
[0066] (Second Example) Next, a second embodiment of the present invention will be described. Since the second embodiment has substantially the same configuration as the first embodiment, the same reference numerals will be used to designate the same components, and only the characteristic parts will be described.
[0067] In FIG. 6, a vehicle 100 equipped with an on-board control system according to a second embodiment of the present invention includes a third ECU 6 connected to a first ECU 4 by a communication line 12, and the third ECU 6 and a second ECU 5 are connected to each other by a communication line 13.
[0068] The third ECU 6 is configured by a computer unit having a CPU, a RAM, a ROM, a flash memory for storing backup data and the like, an input port, and an output port.
[0069] The ROM of this computer unit stores various constants, various maps, and the like, as well as programs for causing the computer unit to function as the third ECU 6.
[0070] That is, the CPU executes the programs stored in the ROM using the RAM as a working area, whereby this computer unit functions as the third ECU 6 in the second embodiment.
[0071] In the second embodiment, the third ECU 6 acquires information regarding a failure from the first ECU 4 via the communication line 12, the second ECU 5 acquires information regarding a failure of the first ECU 4 from the third ECU 6 via the communication line 13, and the meter ECU 3 acquires information regarding a failure of the first ECU 4 from the second ECU 5 via the in-vehicle communication network.
[0072] In this manner, similarly to the first embodiment, even if a communication error is detected in the in-vehicle communication network of the first ECU 4, information on the failure of the first ECU 4 can be obtained from the third ECU 6 via the second ECU 5. Therefore, it is possible to notify the user of the failure of the first ECU 4 without misleading the user.
[0073] In the configuration of FIG. 6, the communication line 12 between the first ECU 4 and the third ECU 6 and the communication line 13 between the second ECU 5 and the third ECU 6 are connected in a bus-type configuration, but a one-to-one connection may also be used.
[0074] Although an embodiment of the invention has been disclosed, it will be apparent to one of ordinary skill in the art that modifications may be made thereto without departing from the spirit and scope of the invention, and it is intended that all such modifications and equivalents be included in the following claims. [Explanation of symbols]
[0075] 1 vehicle 2 Fault indicator 3 Meter ECU (second control device) 4. First ECU (first control unit) 5. Second ECU (third control device) 6 3rd ECU 10 CAN communication line (vehicle communication network) 11 Communication lines 12 Communication lines 13. Communication Lines 100 vehicles
Claims
1. A first control device, a second control device, and a third control device; a fault indicator that is illuminated when a fault is detected in the first control device; An in-vehicle control system including an in-vehicle communication network to which at least the first control device, the second control device, and the third control device are connected, a communication line different from the in-vehicle communication network, to which at least the first control device and the third control device are connected; An in-vehicle control system in which, when the second control device detects a communication error of the first control device in the in-vehicle communication network, it acquires information regarding the failure status of the first control device from the third control device, and when it determines that the first control device is operating normally, it turns off the failure indicator, and when it determines that the first control device is not operating normally, it turns on the failure indicator.
2. The in-vehicle control system of claim 1, wherein the second control device does not turn on the fault indicator when it detects a communication error of the first control device in the in-vehicle communication network, but turns on the fault indicator when it obtains information regarding the fault status of the first control device from the third control device and determines that the first control device has failed.
Citation Information
Patent Citations
Multiplex transmitter
JP1993003483A
Multiplex transmitter
JP1996182055A
Control system for vehicle
JP2003291692A
Vehicle communication system and data communication method
JP2006333007A
Abnormity location identifying apparatus, its control program, and abnormity location identifying system
JP2009213092A
