On-vehicle device, program and information processing method

The in-vehicle device addresses diagnostic processing inefficiencies by detecting and reporting inhibiting events to the vehicle ECU, ensuring timely measures are taken.

JP2024166359AActive Publication Date: 2024-11-28SUMITOMO WIRING SYSTEMS LTD +1
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2024161053
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-09-18
Publication Date
2024-11-28
Estimated Expiration
2041-04-08

AI Technical Summary

Technical Problem

Existing in-vehicle drive devices lack diagnostic processing capabilities, leading to inefficiencies in addressing inhibiting events that interrupt diagnostic operations.

Method used

An in-vehicle device with a control unit that detects inhibiting events during diagnostic processing and sends a detection result notification to the vehicle ECU via a communication unit, allowing for efficient measures to be taken.

Benefits of technology

Enables efficient diagnostic processing by notifying the vehicle ECU of inhibiting events, ensuring timely measures are taken even when diagnostic processing is interrupted.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166359000001_ABST
    Figure 2024166359000001_ABST
Patent Text Reader

Abstract

To provide an on-vehicle device and others which can efficiently perform handling based on diagnostic processing by the device.SOLUTION: An on-vehicle device is mounted on a vehicle and includes a driving part, and comprises a control part that controls the driving part, and a communication part that performs communication with an on-vehicle ECU mounted on the vehicle. When performing diagnostic processing for the driving part, the control part, when detecting an inhibition event that inhibits the diagnostic processing, outputs a detection result notification showing that the inhibition event is detected to the on-vehicle ECU through the communication part.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an in-vehicle device, a program, and an information processing method. [Background technology]

[0002] A vehicle is equipped with a body ECU, which is an on-board ECU that controls body-related devices such as a wiper drive device, interior and exterior lighting devices, door lock devices, and power windows (see, for example, Patent Document 1). The wiper drive device of Patent Document 1 includes an on-board ECU (body ECU) and is driven by a control program applied to the on-board ECU. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-224926 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the drive device of Patent Document 1 has a problem in that no consideration is given to diagnostic processing of the drive parts included in the drive device itself.

[0005] An object of the present disclosure is to provide an in-vehicle device or the like that can efficiently take action based on diagnostic processing of the device itself. [Means for solving the problem]

[0006] An in-vehicle device according to one embodiment of the present disclosure is an in-vehicle device mounted on a vehicle and including a drive unit, and is equipped with a control unit that controls the drive unit and a communication unit for communicating with an in-vehicle ECU mounted on the vehicle, and when the control unit detects an obstruction event that obstructs the diagnostic processing when performing diagnostic processing on the drive unit, the control unit outputs a detection result notification indicating that the obstruction event has been detected to the in-vehicle ECU via the communication unit. Effect of the Invention

[0007] According to one aspect of the present disclosure, it is possible to provide an in-vehicle device or the like that can efficiently take action based on a diagnostic process of the device itself. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic diagram illustrating a configuration of an in-vehicle system including an in-vehicle device according to a first embodiment. [Diagram 2] 2 is a block diagram illustrating an example of an internal configuration of an in-vehicle device; [Diagram 3] 2 is an explanatory diagram illustrating a processing sequence by an in-vehicle device and an in-vehicle ECU; [Figure 4] 4 is a flowchart illustrating a process of a control unit of an in-vehicle device. [Diagram 5] 10 is a flowchart illustrating the process of a control unit of an in-vehicle device according to the second embodiment (when communication is not available). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] [Description of the embodiments of the present disclosure] First, embodiments of the present disclosure will be listed and described. In addition, at least some of the embodiments described below may be arbitrarily combined.

[0010] (1) An in-vehicle device according to one embodiment of the present disclosure is an in-vehicle device mounted on a vehicle and including a drive unit, and is equipped with a control unit that controls the drive unit and a communication unit for communicating with an in-vehicle ECU mounted on the vehicle, wherein when the control unit detects an obstruction event that obstructs diagnostic processing of the drive unit, the control unit outputs a detection result notification indicating that the obstruction event has been detected to the in-vehicle ECU via the communication unit.

[0011] In this aspect, the on-board device mounted on the vehicle includes a drive unit, a control unit, and a communication unit, and communicates with an on-board ECU mounted on the vehicle via the communication unit. The control unit performs diagnostic processing of the drive unit, and outputs (transmits) a diagnostic result, such as whether the drive unit is normal or abnormal, to the on-board ECU via the communication unit. Furthermore, when the control unit detects an obstruction event that obstructs the diagnostic processing during the diagnostic processing, the control unit outputs a detection result notification indicating that an obstruction event has been detected to the on-board ECU via the communication unit. Therefore, even if an obstruction event that obstructs the diagnostic processing occurs due to various factors, and the diagnostic processing of the drive unit mounted on the device is interrupted or the diagnostic processing cannot be started, the control unit can output a detection result notification indicating that the obstruction event has been detected to the on-board ECU based on the detection of the obstruction event. As a result, even if a state in which the diagnostic processing for the drive unit is not performed occurs or continues, the on-board device (control unit) can efficiently take measures based on the diagnostic processing of the device by outputting a detection result notification indicating that (the obstruction event has been detected) to the on-board ECU.

[0012] (2) In one aspect of the present disclosure, the on-board device is configured such that the inhibiting event includes an event in which the diagnostic process is interrupted.

[0013] In this embodiment, the obstruction event detected by the control unit includes an event in which the diagnostic process is interrupted. Therefore, even if the diagnostic process is interrupted after it has been started, a detection result notification indicating that the process has been interrupted can be output to the vehicle ECU, thereby making it possible to efficiently respond based on the diagnostic process of the device itself.

[0014] (3) In an in-vehicle device according to one embodiment of the present disclosure, when the diagnostic process is interrupted consecutively a predetermined number of times or more, the control unit outputs a detection result notification to the in-vehicle ECU indicating that the obstruction event has been detected.

[0015] In this embodiment, when the diagnostic process is interrupted, the control unit counts the number of consecutive interruptions by, for example, incrementing a counter value indicating the interruption by one, and stores the number of times (counter value) in an accessible storage area such as a storage unit mounted in the device. When the number of times (counter value) becomes equal to or exceeds a predetermined number, such as 100 times, that is, when the predetermined number of times is reached, the control unit outputs a detection result notification indicating that an obstruction event has been detected to the vehicle-mounted ECU. When counting the number of consecutive interruptions of the diagnostic process, if the diagnostic process is completed without interruption, the control unit may reset the counter value, which has been incremented by one according to the number of interruptions, to an initial value of, for example, 0. Even if the events that interrupt the diagnostic process are consecutive and the state in which the diagnostic process for the drive unit is not performed continues, when the number of consecutive interruptions of the diagnostic process reaches a predetermined number, the control unit can efficiently take measures based on the diagnostic process of the device by outputting a detection result notification indicating that an obstruction event has been detected to the vehicle-mounted ECU. In addition, even if events that cause the diagnostic process to be interrupted occur consecutively, the control unit will not output a detection result notification to the vehicle ECU until the number of consecutive interruptions reaches a predetermined number, i.e., when the number is less than the predetermined number, thereby preventing the detection result notification from being output excessively.

[0016] (4) In one embodiment of the in-vehicle device according to the present disclosure, the control unit performs diagnostic processing of the drive unit when the vehicle's ignition power is turned off, and interrupts the ongoing diagnostic processing when the ignition power is turned on.

[0017] In this embodiment, the vehicle is provided with an ignition switch (IG switch) for starting and stopping the vehicle, and the ignition power supply of the vehicle is switched from off to on or from on to off by pressing the IG switch. When the ignition power supply of the vehicle is turned off, the control unit acquires an off signal (sleep signal) indicating the off-state from the vehicle-mounted ECU via the communication unit, and starts diagnostic processing of the drive unit in response to the off signal. When the control unit is performing diagnostic processing of the drive unit, for example, when the ignition power supply is turned on by the vehicle operator pressing the IG switch, and acquires an on signal (wakeup signal) indicating the on-state from the vehicle-mounted ECU via the communication unit, the control unit interrupts diagnostic processing of the drive unit in response to the on signal. Thus, the control unit executes and interrupts diagnostic processing in response to the operation of the IG switch that starts and stops the vehicle, and when the interruption is performed, the control unit outputs a detection result notification indicating that an obstruction event has been detected to the vehicle-mounted ECU, thereby efficiently taking measures based on the diagnostic processing of the device itself.

[0018] (5) In an on-board device according to one aspect of the present disclosure, the obstruction event includes an event in which communication between the control unit and the on-board ECU is interrupted for a predetermined period of time or longer.

[0019] In this embodiment, the diagnostic sequence of the drive unit by the control unit includes a diagnostic process of the drive unit in the own device and a transmission process of outputting (transmitting) the result of the diagnostic process (diagnostic process result) to the vehicle-mounted ECU. For example, when the diagnostic process is output (transmitted) to the vehicle-mounted ECU, a state in which communication with the vehicle-mounted ECU is not possible (disconnected state) may continue. Or, when a signal indicating that the diagnostic process is to be started is output from the vehicle-mounted ECU to the vehicle-mounted device, it is assumed that the communication between the vehicle-mounted ECU and the vehicle-mounted device is disconnected, and the vehicle-mounted device cannot acquire (receive) the signal. Therefore, even in the case of the disconnected state, such an event (disconnected event) is included in the obstruction event, and a detection result notification indicating that the obstruction event has been detected is output to the vehicle-mounted ECU via the communication unit, so that a response based on the diagnostic process of the own device can be efficiently performed.

[0020] (6) In an in-vehicle device according to one aspect of the present disclosure, the control unit outputs a detection result notification indicating that the obstruction event has been detected to the in-vehicle ECU as a failure notification of the drive unit.

[0021] In this embodiment, the control unit performs diagnostic processing on the drive unit included in the device itself based on a predetermined trigger such as when the IG switch is turned off, and when the diagnostic processing results in the drive unit being diagnosed as abnormal due to, for example, an on-failure, the control unit outputs (transmits) a fault notification to the vehicle-mounted ECU via the communication unit. The control unit also outputs a detection result notification indicating that an obstruction event has been detected in performing diagnostic processing on the drive unit to the vehicle-mounted ECU as a fault notification for the drive unit. This makes it possible to output a detection result notification indicating that an obstruction event has been detected in performing diagnostic processing to the vehicle-mounted ECU, similar to a fault notification based on diagnostic processing that is regularly performed with the IG switch being turned off as a trigger, and thus simplifies the communication form between the vehicle-mounted device and the vehicle-mounted ECU, thereby enabling efficient communication processing.

[0022] (7) In one embodiment of the in-vehicle device according to the present disclosure, a fault notification output to the in-vehicle ECU includes an error code, and the control unit differentiates the error code generated when an inhibiting event that inhibits the diagnostic process is detected from an error code detected when the diagnostic process is completed without being inhibited.

[0023] In this embodiment, the control unit, for example, differentiates the error code included in the failure notification between a detection result notification indicating that an obstruction event such as an interruption of diagnostic processing has been continuously detected and a detection result notification indicating an actual failure such as an ON failure of the drive unit. By differentiating the error code included in the failure notification in this way depending on the reason for outputting the failure notification (detection result notification), it is possible to notify the in-vehicle ECU according to the failure state of the in-vehicle device.

[0024] (8) A program according to one embodiment of the present disclosure causes a computer controlling a drive unit to execute a process of outputting a detection result notification indicating that an obstruction event has been detected to an on-board ECU communicatively connected to the computer when the computer detects an obstruction event that obstructs the diagnostic process when the computer performs a diagnostic process on the drive unit.

[0025] In this aspect, the computer can be operated as an in-vehicle device that can efficiently take action based on the diagnostic processing of the device itself.

[0026] (9) An information processing method according to one embodiment of the present disclosure is an information processing method to be executed by a computer controlling a drive unit, and when performing diagnostic processing of the drive unit, the computer is caused to execute a process of outputting a detection result notification indicating that the obstruction event has been detected to an on-board ECU that is communicatively connected to the computer.

[0027] According to this aspect, it is possible to provide an information processing method for operating a computer as an in-vehicle device that can efficiently take action based on diagnostic processing of the device itself.

[0028] [Details of the embodiment of the present disclosure] Specific examples of the in-vehicle device 1 according to the embodiment of the present disclosure will be described below with reference to the drawings. Note that the present disclosure is not limited to these examples, but is defined by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0029] (Embodiment 1) Hereinafter, an embodiment will be described with reference to the drawings. FIG. 1 is a schematic diagram illustrating the configuration of an in-vehicle system S including an in-vehicle device 1 according to the first embodiment. FIG. 2 is a block diagram illustrating the internal configuration of the in-vehicle device 1. The in-vehicle system S includes an in-vehicle device 1 and an in-vehicle ECU 2 that are communicatively connected to each other by a communication line 5, and the in-vehicle device 1 is connected to a power supply device 4 and an in-vehicle load 3 via a power supply line 41. The in-vehicle device 1 controls the on- or off-state of a drive unit 14 included in the device itself based on a control signal output (transmitted) from the in-vehicle ECU 2, for example, and supplies or cuts off power output from the power supply device 4 to the in-vehicle load 3 connected to the device itself.

[0030] The in-vehicle ECU 2 is communicatively connected to an IG switch 21 (ignition switch) that starts or stops the vehicle C, and outputs (transmits) to the in-vehicle device 1 a signal (sleep signal for start, wakeup signal for interruption) instructing the in-vehicle device 1 to start or interrupt diagnostic processing of the drive unit 14 included in the in-vehicle device 1 based on a signal output from the IG switch 21. In the in-vehicle system S configured in this manner, the in-vehicle ECU 2 may correspond to a master ECU, and the in-vehicle device 1 may correspond to a slave ECU.

[0031] The power supply device 4 is, for example, a secondary battery such as a lead battery, an alternator, or a lithium battery, and is a power source for an in-vehicle load 3 mounted on a vehicle C. The in-vehicle load 3 is, for example, an actuator such as a lamp device or a motor, and is driven by power supplied from the power supply device 4 via a drive unit 14 of the in-vehicle device 1.

[0032] The in-vehicle device 1 includes a control unit 11, a storage unit 12, a communication unit 13, and a drive unit 14. The control unit 11 is configured with a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), and reads and executes programs and data stored in the storage unit 12, and performs various control processes including on / off control of the drive unit 14 and diagnostic processing of the drive unit 14. Alternatively, the control unit 11 may be configured with an FPGA (field-programmable gate array), a SoC (System-on-a-chip), or an ASIC (application specific integrated circuit).

[0033] The storage unit 12 is a volatile memory element such as a RAM (Random Access Memory) or a ROM. The storage unit 12 is configured with non-volatile memory elements such as a Read Only Memory (EEPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory. Programs and data for executing the programs are stored in the storage unit 12. These programs may be stored as programs read from a recording medium readable by the in-vehicle ECU 2. Alternatively, these programs may be downloaded from an external computer (not shown) connected to a communication network (not shown) and stored in the storage unit 12. A counter value, which will be described later, is stored in the storage unit 12.

[0034] The communication unit 13 is a communication interface compatible with protocols such as LIN (Local Interconnect Network), CAN (Controller Area Network) or Ethernet (registered trademark). The control unit 11 communicates with the in-vehicle ECU 2 via the communication unit 13 using a predetermined protocol such as LIN.

[0035] The driving unit 14 is a semiconductor switch such as a field effect transistor (FET) or an insulated gate bipolar transistor (IGBT), and is turned on or off based on a driving signal from the control unit 11. When the driving unit 14 is turned on, the power output from the power supply device 4 is supplied to the vehicle-mounted load 3. When the driving unit 14 is turned off, the power output from the power supply device 4 is cut off and is not supplied to the vehicle-mounted load 3. The driving unit 14 is a semiconductor switch such as a FET, but is not limited to this and may be a mechanical relay, a driving circuit, a motor mechanism, or the like. In the drawings and the like in this embodiment, the driving unit 14 will be described as a semiconductor switch (FET), which is one example of the semiconductor switch.

[0036] The control unit 11 executes a program stored in the storage unit 12, thereby functioning as a diagnostic processing unit that performs diagnostic processing (diagnosis processing) of the drive unit 14. The control unit 11 functioning as the diagnostic processing unit starts diagnostic processing of the drive unit 14 in response to, for example, a sleep signal transmitted from the vehicle-mounted ECU 2. The diagnostic processing detects, for example, an on-failure (short-circuit failure) or an off-failure (open-circuit failure) of the drive unit 14, and determines whether or not there is an abnormality in the drive unit 14 based on the detection result. When the control unit 11 determines that the drive unit 14 is abnormal based on the result of the diagnostic processing of the drive unit 14, it outputs a failure notification to the vehicle-mounted ECU 2. Furthermore, when the control unit 11 detects an obstructing event that obstructs the diagnostic processing, such as the diagnostic processing being interrupted due to some factor, it outputs a detection result notification indicating that an obstructing event has been detected to the vehicle-mounted ECU 2 via the communication unit 13. Details of the detection result notification processing will be described later.

[0037] The in-vehicle ECU 2 includes a control unit (not shown), a storage unit (not shown), and a communication unit (not shown) similar to the in-vehicle device 1, and the configuration of these hardware functional units is similar to that of the in-vehicle device 1. The in-vehicle ECU 2 is, for example, a body ECU that controls the entire vehicle C, an engine ECU that controls actuators such as an engine or a motor, etc.

[0038] The in-vehicle ECU 2 is communicatively connected to the IG switch 21, and when the IG switch 21 is pressed and the ignition power of the vehicle C is turned on from off, the in-vehicle ECU 2 outputs a wakeup signal to the in-vehicle device 1, causing the in-vehicle device 1 to transition from a sleep state to an active state when the IG switch 21 is pressed and the ignition power of the vehicle C is turned off from on, the in-vehicle ECU 2 outputs a sleep signal to the in-vehicle device 1, causing the in-vehicle device 1 to transition from an active state to a sleep state when the IG switch 21 is pressed and the ignition power of the vehicle C is turned off from on.

[0039] The in-vehicle ECU 2 and the in-vehicle device 1 periodically perform polling communication, and the in-vehicle device 1 determines the communication state between the in-vehicle ECU 2 and the in-vehicle device 1, that is, whether the communication is normal or abnormal.

[0040] 3 is an explanatory diagram illustrating a processing sequence by the in-vehicle device 1 and the in-vehicle ECU 2. The processing by the in-vehicle device 1 and the in-vehicle ECU 2 in this embodiment is triggered by, for example, the IG switch 21 being turned on or off.

[0041] The in-vehicle device 1 and the in-vehicle ECU 2 periodically perform, for example, polling communication, and the in-vehicle device 1 detects whether the communication between the in-vehicle device 1 and the in-vehicle ECU 2 is normal or abnormal, causing a communication interruption, based on a response to the polling communication from the in-vehicle ECU 2. The in-vehicle device 1 may determine that the communication between the in-vehicle device 1 and the in-vehicle ECU 2 is interrupted when the communication between the in-vehicle device 1 and the in-vehicle ECU 2 becomes impossible for a predetermined period of time, such as one second.

[0042] The in-vehicle ECU 2 acquires an off signal (turning off the ignition power) output from the IG switch 21 (S01). The in-vehicle ECU 2 outputs (transmits) a sleep signal to the in-vehicle device 1 based on the acquired off signal (S02). The in-vehicle ECU 2 acquires an off signal output from the IG switch 21 that is directly or indirectly communicatively connected to its own EUC, that is, a signal that turns off the ignition power, and outputs (transmits) a sleep signal generated in response to the off signal to the in-vehicle device 1.

[0043] The in-vehicle device 1 starts diagnostic processing of the drive unit 14 based on the acquired sleep signal (S03). The in-vehicle device 1 starts diagnostic processing of the drive unit 14 included in its own device based on the sleep signal acquired from the in-vehicle ECU 2 via the communication unit 13. If the diagnostic processing ends (completes) normally, the in-vehicle device 1 outputs (transmits) the result of the diagnostic processing (diagnostic processing result) to the in-vehicle ECU 2 (S04). A series of processes from the start of the diagnostic processing to the output of the result of the diagnostic processing (diagnostic processing result) to the in-vehicle ECU 2 is performed by the in-vehicle device 1 as a diagnostic processing sequence.

[0044] When the in-vehicle device 1 normally completes the diagnostic process and the output of the diagnostic process result to the in-vehicle ECU 2 (diagnostic process sequence), it sets (initializes) the counter value, which is counted (incremented) when an obstruction event is detected, to 0 (S05). The counter value is stored in a storage area accessible from the control unit 11, such as the storage unit 12 mounted in the in-vehicle device 1, and is a value that is counted (incremented) and increased when an obstruction event is detected, but as described above, when the diagnostic process sequence is normally completed, it is initialized (resets) to a value such as 0. By performing such increment processing and initialization processing on the counter value, the counter value indicates the number of times the diagnostic process has been interrupted consecutively (number of consecutive interruptions), i.e., the number of times obstruction events that obstruct the diagnostic process have been detected consecutively (number of consecutive occurrences of obstruction events).

[0045] The processes from S01 to S05 are performed when the diagnostic process is normally completed. The processes from S06 onwards are performed when the diagnostic process is interrupted.

[0046] The in-vehicle ECU 2 acquires an off signal (turning off the ignition power) output from the IG switch 21 (S06). Based on the acquired off signal, the in-vehicle ECU 2 outputs (transmits) a sleep signal to the in-vehicle device 1 (S07). Based on the acquired sleep signal, the in-vehicle device 1 starts a diagnostic process for the drive unit 14 (S08). The processes from S06 to S08 are the same as the processes from S01 to S03.

[0047] The in-vehicle ECU 2 acquires an ON signal (turning on the ignition power) output from the IG switch 21 (S09). The in-vehicle ECU 2 outputs (transmits) a wakeup signal to the in-vehicle device 1 based on the acquired ON signal (S10). The in-vehicle ECU 2 acquires an ON signal output from the IG switch 21 that is directly or indirectly communicatively connected to its own EUC, that is, a signal that turns on the ignition power, and outputs (transmits) a wakeup signal generated in response to the ON signal to the in-vehicle device 1.

[0048] The in-vehicle device 1 suspends the diagnostic process of the drive unit 14 based on the acquired wakeup signal. (S11). When the in-vehicle device 1 acquires (receives) a wakeup signal output from the in-vehicle ECU 2 during the execution of the diagnostic process of the drive unit 14, the in-vehicle device 1 interrupts the diagnostic process being executed.

[0049] When the diagnostic process is interrupted, the in-vehicle device 1 increments the counter value indicating the number of consecutive occurrences of the obstruction event by one (increment process) (S12). The process of incrementing the counter value by one (increment process) is not limited to when the diagnostic process is interrupted, and the increment process may be executed even when it is determined that communication between the in-vehicle device 1 and the in-vehicle ECU 2 is interrupted. In other words, the obstruction event that obstructs the diagnostic process may include an interruption of the diagnostic process and a communication interruption state between the in-vehicle device 1 and the in-vehicle ECU 2.

[0050] When the counter value reaches the predetermined number of times, the in-vehicle device 1 outputs a detection result notification indicating that an obstruction event has been detected consecutively to the in-vehicle ECU 2 as a malfunction notification of the drive unit 14 (S13). The predetermined number of times, which is a threshold value for the counter value, is stored in the storage unit 12 of the in-vehicle device 1 as, for example, 100 times. When the counter value reaches the predetermined number of times, i.e., when the counter value is equal to or greater than the predetermined number of times, the in-vehicle device 1 outputs a detection result notification indicating that an obstruction event has been detected consecutively to the in-vehicle ECU 2. The in-vehicle device 1 may output the detection result notification to the in-vehicle ECU 2 as a malfunction notification of the drive unit 14.

[0051] The fault notification may include, for example, different error codes in the detection result notification (fault notification) depending on whether the detection result notification indicates that an obstruction event such as an interruption of the diagnostic process has been detected consecutively or an actual fault such as an ON fault of the drive unit 14. That is, when the control unit 11 of the in-vehicle device 1 starts a diagnostic process for the drive unit 14 and the diagnostic process is completed without obstruction, the error code in the case where an actual fault such as an ON fault of the drive unit 14 is detected as the diagnostic result is set to, for example, 01. The control unit 11 of the in-vehicle device 1 sets an error code in the case where an obstruction event such as an interruption of the started diagnostic process is detected consecutively to, for example, 99. In this way, by differentiating the error code included in the detection result notification (fault notification) depending on the reason for outputting the detection result notification (fault notification), the in-vehicle ECU 2 can take appropriate measures according to the error code.

[0052] 4 is a flowchart illustrating the processing of the control unit 11 of the in-vehicle device 1. The control unit 11 of the in-vehicle device 1 performs the following processing based on a signal output from the in-vehicle ECU 2 in response to an operation of an IG switch 21 (ignition switch) that starts or stops the vehicle C, for example.

[0053] The control unit 11 of the in-vehicle device 1 determines whether or not it has acquired a signal instructing the start of diagnostic processing of the drive unit 14 (S101). The control unit 11 of the in-vehicle device 1 determines whether or not it has acquired a signal instructing the start of diagnostic processing of the drive unit 14, such as a sleep signal output from the in-vehicle ECU 2. If it has not acquired a signal instructing the start of diagnostic processing (sleep signal) (S101: NO), the control unit 11 of the in-vehicle device 1 continues waiting for a signal output from the in-vehicle device 1 by performing loop processing to execute the processing of S101 again.

[0054] When a signal (sleep signal) instructing the start of diagnostic processing is acquired (S101: YES), the control unit 11 of the in-vehicle device 1 executes diagnostic processing of the drive unit 14 (S102). When a signal instructing the start of diagnostic processing, such as a sleep signal, is output from the in-vehicle ECU 2, the control unit 11 of the in-vehicle device 1 starts diagnostic processing of the drive unit 14 in response to the sleep signal. This puts the in-vehicle device 1 in a state in which diagnostic processing of the drive unit 14 is being executed.

[0055] The control unit 11 of the in-vehicle device 1 determines whether an inhibiting event that inhibits the diagnostic process has occurred. (S103). The control unit 11 of the in-vehicle device 1 determines whether or not an inhibiting event that inhibits the diagnostic process has occurred while the diagnostic process is being executed for the drive unit 14. An inhibiting event that inhibits the diagnostic process is, for example, an interruption of the diagnostic process due to a wakeup signal output from the in-vehicle ECU 2.

[0056] If no obstruction event has occurred (S103: NO), the control unit 11 of the in-vehicle device 1 judges whether the diagnostic process has been completed (S1031). The diagnostic process includes, for example, a predetermined process sequence for diagnosing the presence or absence of an ON failure and an OFF failure in the driving unit 14 such as a FET. The control unit 11 of the in-vehicle device 1 judges that the diagnostic process has been completed when the process sequence has been executed to the end. The control unit 11 of the in-vehicle device 1 may monitor the progress of the process sequence at a predetermined period and judge that the diagnostic process has been completed by detecting a completion signal or the like that is output when the process sequence has been executed to the end. If the diagnostic process has not been completed (S1031: NO), the diagnostic process is being executed, and the control unit 11 of the in-vehicle device 1 continues to execute the diagnostic process (S102). That is, the control unit 11 of the in-vehicle device 1 continues the process of periodically judging whether a wakeup signal has been output from the in-vehicle ECU 2 while the diagnostic process of the driving unit 14 is being executed.

[0057] In the illustrated embodiment, the processes of S103 and S1031 are performed sequentially, and if no obstruction event occurs (S103: NO) and the diagnostic process is not completed (S1031: NO), the control unit 11 of the in-vehicle device 1 performs loop processing to execute the process of S102 again, but this is not limited to this. When the control unit 11 of the in-vehicle device 1 acquires (receives) a signal such as a wakeup signal from the in-vehicle ECU 2 during execution of the diagnostic process (S102), which instructs interruption of the diagnostic process, the control unit 11 of the in-vehicle device 1 may generate an interrupt signal based on the signal and output the interrupt signal to the process performing the diagnostic process, thereby interrupting the diagnostic process.

[0058] When the diagnostic process is completed (S1031: YES), the control unit 11 of the in-vehicle device 1 outputs the diagnostic process result to the in-vehicle ECU 2 (S1032). When the diagnostic process for the drive unit 14 is completed normally and the control unit 11 of the in-vehicle device 1 determines that the drive unit 14 is abnormal based on the result of the diagnostic process, the control unit 11 outputs a failure notification (diagnostic process result) to the in-vehicle ECU 2.

[0059] The control unit 11 of the in-vehicle device 1 initializes a counter value indicating the number of consecutive occurrences of the obstruction event (S1033). The control unit 11 of the in-vehicle device 1 initializes the counter value stored in the storage unit 12 to, for example, "0." That is, the counter value is reset when the diagnostic process is normally completed.

[0060] If an obstruction event occurs (S103: YES), the control unit 11 of the in-vehicle device 1 interrupts the diagnostic process (S104). As described above, an obstruction event is, for example, an interruption of the diagnostic process due to a wakeup signal output from the in-vehicle ECU 2, and when the control unit 11 of the in-vehicle device 1 acquires (receives) the wakeup signal, it interrupts the ongoing diagnostic process.

[0061] The control unit 11 of the in-vehicle device 1 increments the counter value indicating the number of consecutive occurrences of the obstruction event by one (increment process) (S105). The control unit 11 of the in-vehicle device 1 increments the counter value stored in the storage unit 12 by one (increment process).

[0062] The control unit 11 of the in-vehicle device 1 determines whether the counter value is equal to or greater than a predetermined number (S106). The predetermined number, which is a threshold value for the counter value, is stored in the storage unit 12 of the in-vehicle device 1 as, for example, 100 times, and the control unit 11 of the in-vehicle device 1 determines whether the counter value is equal to or greater than the predetermined number, i.e., whether the counter value has reached the predetermined number.

[0063] If the counter value is equal to or greater than the predetermined number of times (S106: YES), the control unit 11 of the in-vehicle device 1 outputs a detection result notification to the in-vehicle ECU 2 indicating that an obstruction event has been detected consecutively (S107). If the counter value is equal to or greater than the predetermined number of times, the control unit 11 of the in-vehicle device 1 outputs a detection result notification to the in-vehicle ECU 2 indicating that the interruption of the diagnostic process, which is an obstruction event, has been performed consecutively a predetermined number of times or more. The control unit 11 of the in-vehicle device 1 may output the detection result notification to the in-vehicle ECU 2 as a malfunction notification of the drive unit 14. In this way, even if the events that interrupt the diagnostic process are consecutive and the state in which the diagnostic process for the drive unit 14 is not performed continues, when the number of consecutive interruptions of the diagnostic process reaches the predetermined number of times, a malfunction notification is output to the in-vehicle ECU 2, thereby making it possible to efficiently take measures based on the diagnostic process of the device itself.

[0064] If the counter value is not equal to or greater than the predetermined number (S106: NO), the control unit 11 of the in-car device 1 ends the series of processes in this flowchart after executing S107 or S1033. Alternatively, the control unit 11 of the in-car device 1 may perform a loop process to execute the process of S101 again after executing these processes.

[0065] (Embodiment 2) 5 is a flowchart illustrating the processing of the control unit 11 of the in-vehicle device 1 according to the second embodiment (communication out). As in the first embodiment, the control unit 11 of the in-vehicle device 1 performs the following processing based on a signal output from the in-vehicle ECU 2 in response to an operation on an IG switch 21 (ignition switch) that starts or stops the vehicle C. The control unit 11 of the in-vehicle device 1 performs the processing from S201 to S206 or S2033 in the same manner as the processing from S101 to S106 or S1033 in the first embodiment.

[0066] The control unit 11 of the in-vehicle device 1 determines whether communication with the in-vehicle ECU 2 has been interrupted (S2011). The control unit 11 of the in-vehicle device 1 performs, for example, periodic polling communication with the in-vehicle ECU 2 via the communication unit 13. The control unit 11 of the in-vehicle device 1 determines whether the communication between the in-vehicle device 1 and the in-vehicle ECU 2 is normal or abnormal (disconnected) based on a response from the in-vehicle ECU 2 to the polling communication. The control unit 11 of the in-vehicle device 1 may determine that the communication between the in-vehicle device 1 and the in-vehicle ECU 2 has been interrupted when the communication between the in-vehicle device 1 and the in-vehicle ECU 2 has been interrupted for a predetermined period of time or more, such as one second or more. The control unit 11 of the in-vehicle device 1 may execute the processes of S201 and S2011 as parallel processes, for example, by generating a sub-process or by using multithreading.

[0067] If the communication with the in-vehicle ECU 2 is not interrupted (S2011: NO), that is, if the communication between the in-vehicle device 1 and the in-vehicle ECU 2 is normal, the control unit 11 of the in-vehicle device 1 performs a loop process to execute the process of S2011 again. That is, the control unit 11 of the in-vehicle device 1 continues to determine the success or failure of the communication between the in-vehicle device 1 and the in-vehicle ECU 2 by using polling communication with the in-vehicle ECU 2.

[0068] When communication with the in-vehicle ECU 2 is interrupted (S2011: YES), the control unit 11 of the in-vehicle device 1 increments (increments) the counter value indicating the number of consecutive occurrences of the inhibition event by one (S2012). The control unit 11 of the in-vehicle device 1 increments (increments) the counter value stored in the storage unit 12 by one, similar to the process S105 (S205) of the first embodiment. That is, the counter value incremented in S205 and the counter value incremented in S2012 are the same counter value (counter value defined by the same variable).

[0069] The control unit 11 of the in-vehicle device 1 determines whether the counter value is equal to or greater than a predetermined number (S2013). The control unit 11 of the in-vehicle device 1 performs the process of S2013 similar to the process of S106 (S206) of the first embodiment. If the counter value is not equal to or greater than the predetermined number (S2013: NO), that is, if the counter value is less than the predetermined number, the control unit 11 of the in-vehicle device 1 performs a loop process to execute the process of S2011 again.

[0070] If the counter value is equal to or greater than the predetermined number of times (S2013: YES), or after execution of S206, the control unit 11 of the in-vehicle device 1 outputs a detection result notification indicating that the inhibition event has been detected consecutively to the in-vehicle ECU 2 (S207). The control unit 11 performs the process of S207 in the same manner as the process of S107 in the first embodiment.

[0071] When the in-vehicle ECU 2 outputs a signal (sleep signal) indicating the start of diagnostic processing to the in-vehicle device 1, it is assumed that communication between the in-vehicle ECU 2 and the in-vehicle device 1 is interrupted, and the in-vehicle device 1 cannot acquire (receive) the signal. In response to this, by outputting to the in-vehicle ECU 2 a detection result notification (fault notification) indicating that the relevant obstruction event, including a communication interruption state between the in-vehicle ECU 2 and the in-vehicle device 1 in addition to interruption of diagnostic processing as an obstruction event for incrementing the counter value, has been detected consecutively, it is possible to efficiently take measures based on the diagnostic processing of the in-vehicle device 1.

[0072] The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present disclosure is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0073] C Vehicle S In-vehicle system 1 In-vehicle device 11 Control section 12 Storage section 13. Communications Department 14 Drive unit 2 In-vehicle ECU 21 IG Switch 3 On-vehicle load 4 Power supply 41 Power line 5. Communication lines

Claims

1. An in-vehicle device that is mounted on a vehicle and includes a drive unit, A control unit that controls the drive unit; A communication unit for communicating with an on-board ECU mounted on the vehicle, When the control unit detects an obstructing event that obstructs the diagnostic process of the drive unit, the control unit outputs a detection result notification indicating that the obstructing event has been detected to the in-vehicle ECU via the communication unit. In-vehicle device.

2. The inhibiting event includes an event in which the diagnostic process is interrupted. The in-vehicle device according to claim 1 .

3. When the diagnostic process is interrupted a predetermined number of times or more, the control unit outputs a detection result notification indicating that the inhibition event has been detected to the in-vehicle ECU. The vehicle-mounted device according to claim 2 .

4. The control unit is When an ignition power supply of the vehicle is turned off, a diagnostic process is performed on the drive unit. When the ignition power is turned on, the ongoing diagnostic process is interrupted. The in-vehicle device according to any one of claims 1 to 3.

5. The inhibition event includes an event in which communication between the control unit and the in-vehicle ECU is interrupted for a predetermined period of time or longer. The vehicle-mounted device according to any one of claims 1 to 4.

6. The control unit outputs a detection result notification indicating that the inhibition event has been detected to the in-vehicle ECU as a failure notification of the drive unit. The in-vehicle device according to any one of claims 1 to 5.

7. The fault notification output to the vehicle-mounted ECU includes an error code, The control unit differentiates an error code when the inhibiting event that inhibits the diagnostic process is detected from an error code detected when the diagnostic process is completed without being inhibited. The vehicle-mounted device according to claim 6.

8. The computer that controls the drive unit When performing a diagnostic process for the drive unit, if an obstructing event that obstructs the diagnostic process is detected, a detection result notification indicating that the obstructing event has been detected is output to an in-vehicle ECU that is communicably connected to the computer. A program that executes a process.

9. An information processing method executed by a computer that controls a drive unit, When performing a diagnostic process for the drive unit, if an obstructing event that obstructs the diagnostic process is detected, a detection result notification indicating that the obstructing event has been detected is output to an in-vehicle ECU that is communicably connected to the computer. An information processing method for causing a computer to execute processing.

Citation Information

Patent Citations

  • Method and system for issuing error information in the on-board diagnosis of vehicles

    EP2955699A1

  • On vehicle electronic controller

    JP1994286534A

  • Failure diagnostic device for fuel evaporative emission processing system

    JP1999190256A

  • Battery status diagnostic device

    JP2007131076A

  • Fault diagnosis device and program

    JP2014203181A