Vehicle data management device, vehicle, analysis system, vehicle data management program product, and vehicle data management method

Abstract

The invention provides a vehicle data management device, a vehicle, an analysis system, a vehicle data management program product, and a vehicle data management method. When a fault of the vehicle is detected, the processing circuit acquires a fault analysis data set for analyzing the fault. The newly acquired fault analysis data set is stored in the first storage area until the total capacity of the stored fault analysis data set reaches a predetermined capacity. When the newly acquired fault analysis data set satisfies a predetermined specific condition, the newly acquired fault analysis data set is stored in the second storage area by a ring buffer method.

Description

[0001] This application claims priority based on Japanese Patent Application No. 2024-015624, filed on February 5, 2024, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0002] The present disclosure relates to a vehicle data management device, a vehicle, an analysis system, a vehicle data management program product, and a vehicle data management method. Background Art

[0003] The analysis system disclosed in Japanese Patent Application Laid-Open No. 2008-234375 includes a vehicle and a terminal device. The vehicle includes a vehicle control device and various sensors. The vehicle control device includes a vehicle processing device and a storage device. The vehicle processing device determines whether a sensor failure has occurred based on output signals from the various sensors.

[0004] If a sensor or other device is determined to have failed, the vehicle processing device stores a fault analysis dataset used to analyze the fault in two storage areas of the storage device. For example, an operator at a repair shop operates a terminal device connected to the vehicle's control device. By operating the terminal device, the operator can read or delete the fault analysis dataset stored in the two storage areas. Summary of the Invention

[0005] According to one aspect of the present disclosure, a vehicle data management device is provided. The data management device includes a processing circuit. The processing circuit is configured to perform the following processing: when a fault of the vehicle is detected, a fault analysis dataset is obtained for analyzing the fault. The newly obtained fault analysis dataset is stored in a first storage area until the total capacity of the stored fault analysis datasets reaches a predetermined capacity. When the newly obtained fault analysis dataset satisfies a predetermined specific condition, the newly obtained fault analysis dataset is stored in a second storage area using a ring buffer.

[0006] According to other aspects of the present disclosure, a vehicle is provided. The vehicle includes a data management device; and a storage device that stores a fault analysis data set for analyzing the fault of the vehicle. The storage device includes a first storage area and a second storage area. The data management device includes a processing circuit. The processing circuit is configured to perform the following processing: when a fault of the vehicle is detected, the fault analysis data set is obtained. The newly obtained fault analysis data set is stored in the first storage area until the total capacity of the stored fault analysis data sets reaches a predetermined specified capacity. When the newly obtained fault analysis data set meets a predetermined specific condition, the newly obtained fault analysis data set is stored in the second storage area by a ring buffer method.

[0007] According to another aspect of the present disclosure, an analysis system is provided. The analysis system includes: a data management device mounted on a vehicle; and a storage device mounted on the vehicle. The storage device stores a fault analysis data set used to analyze faults of the vehicle. The analysis system includes a terminal device located outside the vehicle. The terminal device is capable of communicating with the data management device. The storage device includes a first storage area and a second storage area. The data management device includes a processing circuit. The processing circuit is configured to perform the following processing: when a fault of the vehicle is detected, the fault analysis data set is acquired. The newly acquired fault analysis data set is stored in the first storage area until the total capacity of the stored fault analysis data sets reaches a predetermined capacity. When the newly acquired fault analysis data set meets a predetermined specific condition, the newly acquired fault analysis data set is stored in the second storage area using a ring buffer method. The fault analysis data set stored in the first storage area is sent to the terminal device in response to an acquisition request signal from the terminal device.

[0008] According to another aspect of the present disclosure, a data management program product is provided that causes a processing circuit to perform vehicle data management processing. The processing circuit is mounted on the vehicle. The data management processing comprises: upon detecting a fault in the vehicle, obtaining a fault analysis dataset for analyzing the fault; storing the newly obtained fault analysis dataset in a first storage area until the total capacity of the stored fault analysis datasets reaches a predetermined capacity; and, upon satisfying a predetermined specific condition, storing the newly obtained fault analysis dataset in a second storage area using a ring buffer.

[0009] According to another aspect of the present disclosure, a vehicle data management method is provided. The data management method comprises: upon detecting a fault in the vehicle, a processing circuit mounted on the vehicle acquires a fault analysis dataset used to analyze the fault. The data management method comprises: storing the newly acquired fault analysis dataset in a first storage area until the total capacity of the stored fault analysis datasets reaches a predetermined capacity. The data management method comprises: upon satisfying a predetermined specific condition, storing the newly acquired fault analysis dataset in a second storage area using a ring buffer.

[0010] According to the above-mentioned structure or method, when a newly acquired fault analysis data set meets specific conditions, the fault analysis data set is stored not only in the first storage area but also in the second storage area. For example, only important fault analysis data sets are stored in the first storage area and the second storage area. Therefore, for example, important fault analysis data sets are stored in both the first storage area and the second storage area. On the other hand, the storage frequency of storing the fault analysis data set in the second storage area can be reduced compared to the storage frequency of the first storage area. In addition, the second storage area is stored using a ring buffer method. Therefore, even if the capacity of the second storage area is filled, the oldest data set in the second storage area will be overwritten, so that the new fault analysis data set will be stored in the second storage area. In other words, it is possible to prevent the occurrence of situations such as the inability to store the new fault analysis data set in the second storage area.

[0011] For example, the vehicle control device of the aforementioned document stores a fault analysis dataset in two storage areas of the storage device each time a fault is determined to have occurred. Therefore, as the number of faults detected increases, the available capacity of the storage areas in the storage device decreases. If the available capacity of the storage areas eventually runs out, it becomes impossible to store new fault analysis datasets in the storage areas. The aforementioned configuration and method can mitigate this problem. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 This is a brief diagram of the analysis system.

[0013] Figure 2 is with Figure 1 Functional block diagram related to the control device shown.

[0014] Figure 3 It means by Figure 2 Flowchart of storage control performed by the control device.

[0015] Figure 4 It means by Figure 2 A timing diagram of data acquisition control executed by a control device.

[0016] Figure 5 It means by Figure 2 A timing diagram of storage deletion control executed by the control device. DETAILED DESCRIPTION

[0017] In this specification, “at least one of A and B” should be understood to mean “only A”, “only B”, or “both A and B”.

[0018] <Brief Structure of the Analysis System>

[0019] Figures 1 to 5 A vehicle data management device, a vehicle, an analysis system, a storage medium, a data management process, a data management program, a data management program product, and a vehicle data management method according to an embodiment of the present disclosure will be described. First, a brief description of the structure of the analysis system SA will be given.

[0020] like Figure 1 As shown, the analysis system SA includes a vehicle 100 . The vehicle 100 is owned by a user, for example. The vehicle 100 includes an internal combustion engine 10 , a torque converter 20 , an automatic transmission 30 , a differential 41 , a plurality of drive wheels 42 , and a hydraulic mechanism 50 .

[0021] The internal combustion engine 10 includes four cylinders 11 and a crankshaft 12. The cylinders 11 are spaces for burning a mixture of fuel and intake air. The crankshaft 12 rotates as the mixture in the cylinders 11 is burned.

[0022] The torque converter 20 includes an input shaft 21 and an output shaft 22. The torque converter 20 transmits the driving force of the input shaft 21 to the output shaft 22 via a fluid. The torque converter 20 decelerates the rotation of the input shaft 21 and outputs it through the output shaft 22. The first end of the input shaft 21 is connected to the crankshaft 12. The torque converter 20 includes a lockup clutch (not shown). The second end of the input shaft 21 is connected to the first end of the output shaft 22 via the lockup clutch. Therefore, when the lockup clutch is engaged, the input shaft 21 and the output shaft 22 rotate integrally.

[0023] The automatic transmission 30 includes an input shaft 31 and an output shaft 32. The first end of the input shaft 31 is connected to the second end of the output shaft 22 in the torque converter 20. The second end of the input shaft 31 is connected to the first end of the output shaft 32 via a clutch and gears (not shown). The second end of the output shaft 32 is connected to the left and right drive wheels 42 via a differential 41. The automatic transmission 30 can change the ratio of the rotational speed of the input shaft 31 to the rotational speed of the output shaft 32, or the speed ratio. The speed ratio of the automatic transmission 30 represents the number of rotations of the input shaft 31 per one rotation of the output shaft 32. Therefore, the larger the speed ratio, the higher the speed at which the input shaft 31 rotates relative to the output shaft 32. An example of the automatic transmission 30 is a stepped automatic transmission. Therefore, the automatic transmission 30 changes the speed ratio by changing the gear stage.

[0024] The hydraulic mechanism 50 is attached to the automatic transmission 30. The hydraulic mechanism 50 supplies oil to the automatic transmission 30. The operation of the automatic transmission 30 is controlled by the oil supplied from the hydraulic mechanism 50.

[0025] like Figure 1 As shown in FIG. 1 , the vehicle 100 is provided with various sensors 70. Examples of the various sensors 70 include an accelerator operation amount sensor, a vehicle speed sensor, an acceleration sensor, and the like. Figure 1 In FIG, only one sensor 70 is shown as a representative example.

[0026] like Figure 1 As shown, vehicle 100 includes a vehicle control device 90. Vehicle control device 90 includes a vehicle processing device 91 and a vehicle storage device 92. An example of vehicle processing device 91 is a CPU. Vehicle storage device 92 includes a ROM that is only readable, a volatile RAM that is readable and writable, and a non-volatile memory that is readable and writable. Vehicle storage device 92 pre-stores various programs and various data sets. Specifically, vehicle storage device 92 pre-stores a control program PG as one of the various programs. Vehicle processing device 91 is a processing circuit that executes various processes described below by executing control program PG stored in vehicle storage device 92. Vehicle processing device 91 functions as data management device 91Z, described below, by executing control program PG stored in vehicle storage device 92. That is, vehicle processing device 91 and data management device 91Z are mounted on vehicle 100. In other words, vehicle processing device 91 executes various processes related to data management methods and data management processing. In this embodiment, control program PG is an example of a data management program.

[0027] The vehicle control device 90 obtains various information from the various sensors 70. The vehicle processing device 91 of the vehicle control device 90 controls the internal combustion engine 10 and the automatic transmission 30 based on the information obtained from the various sensors 70. Specifically, the vehicle processing device 91 controls the internal combustion engine 10 by outputting a control signal to the internal combustion engine 10. The vehicle processing device 91 controls the automatic transmission 30 via the hydraulic mechanism 50 by outputting a control signal to the hydraulic mechanism 50.

[0028] The vehicle 100 includes a vehicle connector 80 . The vehicle connector 80 is connected to a vehicle control device 90 . When the vehicle control device 90 is connected to another device via the vehicle connector 80 , the vehicle control device 90 can communicate with the other device via the vehicle connector 80 .

[0029] like Figure 1 As shown, the analysis system SA includes a terminal device 200 . The terminal device 200 is installed at a location where maintenance of the vehicle 100 is performed, such as an automobile repair shop. In other words, the terminal device 200 is a device located outside the vehicle 100 .

[0030] The terminal device 200 includes a terminal body 200A, a terminal display 200B, and a terminal connector 200C. The terminal display 200B can display various images. The terminal display 200B is a so-called touch panel display. Therefore, for example, workers at an auto repair shop can input various information via the terminal display 200B. The terminal display 200B is connected to the terminal body 200A. The terminal connector 200C is connected to the terminal body 200A. When the terminal body 200A is connected to another device via the terminal connector 200C, the terminal body 200A can communicate with the other device via the terminal connector 200C.

[0031] The terminal main body 200A includes a terminal processing device 210 and a terminal storage device 220. An example of the terminal processing device 210 is a CPU. The terminal storage device 220 includes a ROM that can only be read, a volatile RAM that can be read and written, and a non-volatile memory that can be read and written. The terminal storage device 220 pre-stores various programs and various data sets. The terminal processing device 210 is a processing circuit that executes the programs stored in the terminal storage device 220 to perform the various processes described below.

[0032] <Data management device peripheral configuration>

[0033] Next, refer to Figure 2 The peripheral structure of the data management device 91Z will be described. Figure 2As shown, data management device 91Z treats a portion of the storage area of vehicle storage device 92 as first storage area 92A. Data management device 91Z treats a portion of the storage area of vehicle storage device 92, which is different from first storage area 92A, as second storage area 92B. In this embodiment, first storage area 92A is a nonvolatile memory in vehicle storage device 92 that is readable and writable. Second storage area 92B is a nonvolatile memory in vehicle storage device 92 that is readable and writable.

[0034] In the first storage area 92A, a fault analysis dataset DB is stored in the storage control described later. The fault analysis dataset DB is used to analyze faults in the vehicle 100. Faults in the vehicle 100 may include, for example, a physical fault in the sensor 70 itself, a communication error between the sensor 70 and the vehicle control device 90, or an error in the internal program of the vehicle control device 90. The data management device 91Z stores newly acquired fault analysis dataset DBs in the first storage area 92A until the total capacity of the stored fault analysis dataset DBs reaches a predetermined capacity. Specifically, the data management device 91Z stores the fault analysis dataset DBs in the first storage area 92A as follows. As a prerequisite, the first storage area 92A has, for example, X storage locations for fault analysis dataset DBs. "X" is an integer greater than or equal to 2. Each of the X storage locations is predetermined with numbers "1" to "X". When storing a fault analysis dataset DB in first storage area 92A, data management device 91Z stores the fault analysis dataset DB in order from the smallest available storage location between "1" and "X." For example, if the storage location where the fault analysis dataset DB was previously stored is numbered "1," data management device 91Z stores the new fault analysis dataset DB in the second storage location. For example, if the storage location where the fault analysis dataset DB was previously stored is numbered "2," data management device 91Z stores the new fault analysis dataset DB in the third storage location. If the storage location where the fault analysis dataset DB was previously stored is numbered "X," data management device 91Z does not store the new fault analysis dataset DB in first storage area 92A. Therefore, if there is no free space in first storage area 92A, data management device 91Z does not store the new fault analysis dataset DB in first storage area 92A. Figure 2 The configuration in which the first storage area 92A includes storage locations for four data sets is shown as an example.

[0035] The second storage area 92B stores the fault analysis dataset DB under storage control described below. The data management device 91Z stores newly acquired fault analysis dataset DBs in the second storage area 92B using a ring buffer method. Specifically, the data management device 91Z stores the fault analysis dataset DBs in the second storage area 92B as follows. As a prerequisite, the second storage area 92B has, for example, N storage locations for the fault analysis dataset DBs. "N" is an integer greater than or equal to 2. Each of the N storage locations is pre-determined to be numbered "1" through "N." When storing the fault analysis dataset DBs in the second storage area 92B, the data management device 91Z basically stores the fault analysis dataset DBs in order, starting with the smallest available number among the "1" through "N" storage locations. For example, if the storage location that previously stored the fault analysis dataset DB is numbered "1," the data management device 91Z stores the fault analysis dataset DB in the "2" storage location. For example, if the storage location of the previously stored fault analysis dataset DB is numbered "2," data management device 91Z stores a new fault analysis dataset DB in the "3" storage location. On the other hand, if the storage location of second storage area 92B, where the previously stored fault analysis dataset DB was numbered "N," data management device 91Z stores the new fault analysis dataset DB in the "1" storage location of second storage area 92B. Second storage area 92B stores data using a ring buffer. Therefore, even if the storage capacity of second storage area 92B is full, the oldest fault analysis dataset DB in second storage area 92B is overwritten to the "1" storage location of second storage area 92B. Therefore, the new fault analysis dataset DB is stored in second storage area 92B. Figure 2 The configuration in which the second storage area 92B includes storage locations for four data sets is shown as an example.

[0036] The data management device 91Z includes a receiving unit 91A, an internal monitoring unit 91B, and a fault writing unit 91C as functional modules. The receiving unit 91A receives information from various sensors 70. The internal monitoring unit 91B obtains processing information related to the vehicle control device 90, such as values calculated by the vehicle control device 90 and values output by the vehicle control device 90. The fault writing unit 91C can obtain information from various sensors 70 via the receiving unit 91A. The fault writing unit 91C can obtain processing information related to the vehicle control device 90 via the internal monitoring unit 91B. The fault writing unit 91C can communicate with the first storage area 92A. The fault writing unit 91C can communicate with the second storage area 92B.

[0037] Storage Control

[0038] Reference Figure 3The storage control executed by the data management device 91Z will be described. This storage control is for storing the fault analysis dataset DB. In this embodiment, the fault writing unit 91C of the data management device 91Z starts the storage control at each predetermined control cycle.

[0039] like Figure 3 As shown, when the fault writing unit 91C of the data management device 91Z starts storage control, the process of step S11 is executed. In step S11, the fault writing unit 91C obtains information from various sensors 70 via the receiving unit 91A. The fault writing unit 91C obtains processing information related to the vehicle control device 90 via the internal monitoring unit 91B. After step S11, the fault writing unit 91C advances the process to step S12.

[0040] In step S12, the fault writing unit 91C determines whether a fault has occurred in the vehicle 100 based on the information from the various sensors 70 and the information processed by the vehicle control device 90. For example, if all of the information from the various sensors 70 and the information processed by the vehicle control device 90 is within a predetermined normal range, the fault writing unit 91C determines that no fault has occurred in the vehicle 100. On the other hand, if at least one or more pieces of information from the information from the various sensors 70 and the information processed by the vehicle control device 90 are outside the predetermined normal range, the fault writing unit 91C determines that a fault has occurred in the vehicle 100. The normal range can be arbitrarily set in advance for each parameter included in the information, based on various components of the vehicle 100, including the internal combustion engine 10, and the communication standards of the various communication devices within the vehicle 100. If the fault writing unit 91C determines in step S12 that no fault has occurred in the vehicle 100 (S12: No), the fault writing unit 91C terminates this storage control. On the other hand, if the fault writing unit 91C determines in step S12 that a fault has occurred in the vehicle 100 (S12: YES), the fault writing unit 91C advances the process to step S21. In other words, if a fault has been detected in the vehicle 100, the fault writing unit 91C advances the process to step S21.

[0041] In step S21, the fault writing unit 91C determines a fault code CB representing the type of fault in the vehicle 100 based on the information from the various sensors 70 and the processing information involved in the vehicle control device 90. For example, the fault writing unit 91C determines the fault code CB by establishing a correspondence between the information from the various sensors 70 and the processing information involved in the vehicle control device 90 and a predetermined fault table. The fault table establishes a correspondence between the combination of the information from the various sensors 70 and the processing information involved in the vehicle control device 90 and the fault code CB. The fault code CB is roughly divided into each system of the vehicle 100. Furthermore, the fault code CB is further subdivided according to the content of the fault of each system. Specifically, the fault code CB is expressed in alphanumeric characters, such as "P0131". The first half of the alphanumeric characters of the fault code CB indicates the system in which the fault has occurred among the multiple systems of the vehicle 100. An example of the multiple systems of the vehicle 100 includes the body system, the chassis system, the powertrain system, the network system, etc. The second half of the alphanumeric characters of the fault code CB indicates the detailed fault of the above-mentioned system. The detailed fault is classified, for example, as a physical fault of the sensor 70 itself, a communication error between the sensor 70 and the vehicle control device 90, or an internal program error of the vehicle control device 90. The above-mentioned fault categories are merely examples. There may be fault categories other than the above-mentioned examples, and the above-mentioned fault categories may be further subdivided. The fault code CB is sometimes also referred to as a "DTC". "DTC" is the abbreviation of Diagnostic Trouble Codes. After step S21, the fault writing unit 91C causes the processing to enter step S22.

[0042] In step S22, the fault writing unit 91C generates a fault analysis data set DB. In the present embodiment, the fault analysis data set DB is a collection of data sets including the fault code CB determined in step S21, the information from the various sensors 70 obtained in step S11, and the processing information related to the vehicle control device 90. Thus, in the present embodiment, the fault writing unit 91C obtains the fault analysis data set DB by generating the fault analysis data set DB. In the present embodiment, the processing information related to the vehicle control device 90 obtained in step S11 includes a data set representing the total travel distance of the vehicle 100. Therefore, the fault analysis data set DB includes a data set representing the driving condition of the vehicle 100. In other words, the fault analysis data set DB includes a data set representing the total travel distance of the vehicle 100 as a data set representing the driving condition of the vehicle 100. The fault analysis data set DB is sometimes also referred to as DTC Snapshot Record Data. After step S22, the fault writing unit 91C advances the processing to step S23.

[0043] In step S23, the fault writing unit 91C stores the newly acquired fault analysis dataset DB in the first storage area 92A. The fault writing unit 91C then proceeds to step S31. If the total capacity of the fault analysis dataset DB stored in the first storage area 92A reaches a predetermined capacity, the fault writing unit 91C does not store the newly acquired fault analysis dataset DB in the first storage area 92A. In this case, the fault writing unit 91C also proceeds to step S31. In this embodiment, the process of step S23 is to store the newly acquired fault analysis dataset DB in the first storage area 92A until the total capacity of the already stored fault analysis dataset DB reaches the predetermined capacity.

[0044] In step S31, the fault writing unit 91C determines whether the fault analysis data set DB satisfies a predetermined specific condition. Specifically, the fault writing unit 91C determines whether the fault code CB included in the fault analysis data set DB is a predetermined specific code. The specific code represents a specific fault category among a plurality of fault categories that are pre-classified for each system possessed by the vehicle 100. For example, the specific fault category of the body system of the vehicle 100 includes a physical fault of the sensor 70 itself. For example, the specific fault category of the chassis system of the vehicle 100 includes a physical fault of the sensor 70 itself. For example, the specific fault category of the powertrain system of the vehicle 100 includes a physical fault of the sensor 70 itself and a communication error between the sensor 70 and the vehicle control device 90. For example, the specific fault category of the network system of the vehicle 100 includes a physical fault of the sensor 70 itself. The above-mentioned specific fault categories are merely examples. The specific fault categories may be different or the same among the systems possessed by the vehicle 100. The specific conditions of the present embodiment include the requirement that the fault analysis dataset DB corresponds to a specific system among a plurality of systems included in the vehicle 100 and corresponds to a specific fault type among a plurality of fault types classified in advance.

[0045] If the fault writing unit 91C determines in step S31 that the fault analysis dataset DB does not satisfy the specific conditions (S31: No), the fault writing unit 91C ends the current storage control. On the other hand, if the fault writing unit 91C determines in step S31 that the fault analysis dataset DB satisfies the specific conditions (S31: Yes), the fault writing unit 91C proceeds to step S41.

[0046] In step S41, the fault writing unit 91C stores the fault analysis dataset DB in the second storage area 92B. Specifically, the fault writing unit 91C stores the newly acquired fault analysis dataset DB in the second storage area 92B using a ring buffer. In this embodiment, the processing in steps S31 and S41 involves storing the newly acquired fault analysis dataset DB in the second storage area 92B using a ring buffer when the newly acquired fault analysis dataset DB meets predetermined specific conditions. After step S41, the fault writing unit 91C terminates this storage control.

[0047] <Data acquisition control>

[0048] Reference Figure 4 The following describes the data acquisition control performed by vehicle control device 90 and terminal device 200. Data acquisition control involves terminal device 200 acquiring the fault analysis dataset DB from vehicle 100. In this embodiment, for example, connection between terminal connector 200C and vehicle connector 80 is a prerequisite. When an operator, etc., requests acquisition of the fault analysis dataset DB via terminal display 200B, terminal device 200 initiates data acquisition control.

[0049] like Figure 4 As shown, once the terminal processing device 210 starts data acquisition control, it executes the process of step S61. In step S61, the terminal processing device 210 transmits an acquisition request signal to the vehicle control device 90. If the vehicle control device 90 receives the acquisition request signal, the data management device 91Z of the vehicle control device 90 advances the process to step S62.

[0050] In step S62, data management device 91Z of vehicle control device 90 transmits all fault analysis datasets DB stored in first storage area 92A to terminal device 200. Once terminal device 200 has acquired the fault analysis dataset DB, terminal processing device 210 stores the fault analysis dataset DB in terminal storage device 220. After step S62, terminal processing device 210 proceeds to step S63.

[0051] In step S63, the terminal processing device 210 outputs a control signal to the terminal display 200B to display the fault analysis dataset DB on the terminal display 200B. In step S63, the terminal processing device 210 ends the current data acquisition control.

[0052] <Storage deletion control>

[0053] Reference Figure 5Next, the storage deletion control executed by vehicle control device 90 and terminal device 200 will be described. This storage deletion control deletes the fault analysis dataset DB stored in first storage area 92A of vehicle 100. In this embodiment, connection of terminal connector 200C to vehicle connector 80 is a prerequisite. For example, when an operator requests deletion of the fault analysis dataset DB via terminal display 200B, terminal device 200 initiates the storage deletion control.

[0054] like Figure 5 As shown, when the terminal processing device 210 starts storage deletion control, it executes the process of step S71. In step S71, the terminal processing device 210 transmits a deletion request signal to the vehicle control device 90. If the vehicle control device 90 receives the deletion request signal, the data management device 91Z of the vehicle control device 90 advances the process to step S72.

[0055] In step S72, data management device 91Z of vehicle control unit 90 deletes all fault analysis datasets DB stored in first storage area 92A. Meanwhile, data management device 91Z maintains all fault analysis datasets DB stored in second storage area 92B. In other words, the fault analysis dataset DB in second storage area 92B cannot be deleted in response to a signal from terminal device 200. After step S72, data management device 91Z terminates this storage and deletion control.

[0056] <Function of this embodiment>

[0057] Assume that some fault occurs in the vehicle 100. In this case, Figure 3 As shown, in step S23 of the storage control, fault writing unit 91C of data management device 91Z stores the fault analysis dataset DB used to analyze the fault of vehicle 100 in first storage area 92A. If the fault analysis dataset DB satisfies a predetermined specific condition, in step S41, fault writing unit 91C stores the newly acquired fault analysis dataset DB in second storage area 92B using a ring buffer method.

[0058] <Effects of this embodiment>

[0059] (1) According to this embodiment, if a newly acquired fault analysis dataset DB satisfies specific conditions, the fault analysis dataset DB is stored not only in first storage area 92A but also in second storage area 92B. For example, a fault analysis dataset DB with high importance is stored in second storage area 92B. Consequently, the frequency of storing fault analysis dataset DBs in second storage area 92B can be reduced. Therefore, there is no need to prepare an excessively large storage area for second storage area 92B. Furthermore, second storage area 92B stores data using a ring buffer. Therefore, even if second storage area 92B becomes full, the oldest dataset in second storage area 92B is overwritten. Therefore, a new fault analysis dataset DB is stored in second storage area 92B. Consequently, situations where a new fault analysis dataset DB cannot be stored in second storage area 92B can be prevented.

[0060] (2) Generally, the importance of a fault may vary depending on the type of fault in vehicle 100. In this regard, the specific condition in step S31 includes the requirement that the fault analysis dataset DB corresponds to a specific fault type among a plurality of fault types that have been pre-classified. Therefore, whether or not to execute the process of storing the fault analysis dataset DB in second storage area 92B can be switched based on the type of fault in vehicle 100, in other words, based on the importance associated with the fault type.

[0061] (3) Generally, the importance of failures varies between systems included in vehicle 100. For example, there may be a case where the necessity for storing a failure analysis dataset DB related to communication errors in the body system of vehicle 100 is relatively low. On the other hand, there may be a case where the necessity for storing a failure analysis dataset DB related to communication errors in the powertrain system of vehicle 100 is relatively high.

[0062] In this regard, the specific condition in step S31 requires that the fault analysis dataset DB corresponds to a specific system among the multiple systems provided by vehicle 100 and corresponds to a specific fault category among the multiple pre-classified fault categories. Therefore, for example, the fault analysis dataset DB related to communication errors in the body system is not stored in second storage area 92B. On the other hand, a distinction can be made, such as storing the fault analysis dataset DB related to communication errors in the powertrain system in second storage area 92B. In other words, whether or not to store the fault analysis dataset DB in second storage area 92B can be switched based on the severity of each system's fault.

[0063] (4) In vehicle 100, the location of a fault occurring in vehicle 100 may vary depending on the driving condition of vehicle 100. Furthermore, the frequency of faults occurring in vehicle 100 may vary. In this regard, the fault analysis dataset DB includes a dataset representing the driving condition of vehicle 100. With this configuration, by referring to the dataset representing the driving condition of vehicle 100 in the fault analysis dataset DB, that is, referring to a dataset that is highly relevant to the fault of vehicle 100, it is possible to appropriately analyze the fault of vehicle 100.

[0064] (5) In vehicle 100, the location of a fault occurring in vehicle 100 tends to change in accordance with changes in the total travel distance of vehicle 100, particularly in the information representing the driving condition of vehicle 100. The frequency of faults occurring in vehicle 100 tends to change in accordance with changes in the total travel distance of vehicle 100. In this regard, the fault analysis dataset DB includes a dataset representing the total travel distance of vehicle 100 as a dataset representing the driving condition of vehicle 100. Therefore, by referring to the dataset representing the total travel distance of vehicle 100 in the fault analysis dataset DB, that is, referring to a dataset that is particularly highly correlated with the fault of vehicle 100, the fault of vehicle 100 can be analyzed more appropriately.

[0065] (6) The first storage area 92A is a nonvolatile storage area. Therefore, it is possible to suppress the failure analysis dataset DB stored in the first storage area 92A from being lost due to, for example, an interruption in the power supply to the vehicle control device 90 .

[0066] (7) The second storage area 92B is a nonvolatile storage area. Therefore, it is possible to suppress the failure analysis dataset DB stored in the second storage area 92B from being lost due to, for example, an interruption in the power supply to the vehicle control device 90 .

[0067] (8) Figure 4 As shown, during data acquisition control, data management device 91Z of vehicle 100 transmits the fault analysis dataset DB stored in first storage area 92A to terminal device 200 in response to an acquisition request signal from terminal device 200. Thus, an operator at, for example, a car repair shop can access the fault analysis dataset DB via terminal device 200.

[0068] (9) Figure 5As shown, during storage and deletion control, data management device 91Z of vehicle 100 deletes only the fault analysis dataset DB stored in first storage area 92A in response to a deletion request signal from terminal device 200. Thus, a worker at, for example, a repair shop can delete unnecessary content from the fault analysis dataset DB stored in first storage area 92A of vehicle 100 by operating terminal device 200. On the other hand, even if the worker operates terminal device 200, they cannot delete the fault analysis dataset DB stored in second storage area 92B of vehicle 100. This prevents accidental deletion of the fault analysis dataset DB stored in second storage area 92B, for example, due to erroneous operation of terminal device 200.

[0069] <Change Example>

[0070] This embodiment can be implemented by modifying as follows: This embodiment and the following modified examples can be implemented in combination with each other within a range that does not technically conflict.

[0071] In the above embodiment, storage control can be changed.

[0072] For example, in step S22, the method for generating the fault analysis dataset DB may be modified. Specifically, the fault analysis dataset DB may include other datasets representing the driving conditions of vehicle 100, in addition to or in place of the dataset representing the total distance traveled by vehicle 100. Examples of other datasets include a dataset representing the speed of vehicle 100, a dataset representing the amount of accelerator pedal operation on vehicle 100, a dataset representing the amount of brake pedal operation on vehicle 100, and a dataset representing the acceleration of vehicle 100. The fault analysis dataset DB may also not include a dataset representing the driving conditions of vehicle 100.

[0073] For example, the specific condition of step S31 may be changed. That is, the specific condition may be replaced with or include other requirements in addition to the requirement that the fault analysis dataset DB corresponds to a specific system among the multiple systems of the vehicle 100 and corresponds to a specific fault category among the categories of faults pre-classified into multiple types. An example of other requirements may include the requirement that the frequency of faults corresponding to the fault analysis dataset DB is greater than a predetermined frequency. In addition, the specific condition may be only the requirement that the fault analysis dataset DB corresponds to a specific fault category among the categories of faults pre-classified into multiple types. As an example, in the case where the difference in importance between the systems of the vehicle 100 is relatively small, even if the specific condition that the fault analysis dataset DB corresponds to a specific system among the multiple systems of the vehicle 100 is changed, the impact caused by the change is small.

[0074] For example, the entity that executes the storage control process can be changed. As a specific example, a device other than the vehicle control device 90 included in the vehicle 100 can execute the processes of steps S11 and S12. In other words, a device other than the data management device 91Z can execute the processes of steps S11 and S12.

[0075] In the above-mentioned embodiment, data acquisition control can be changed.

[0076] For example, in step S62 , the data management device 91Z of the vehicle control device 90 may transmit only a portion of the fault analysis dataset DB stored in the first storage area 92A to the terminal device 200 .

[0077] For example, in step S62 , the data management device 91Z of the vehicle control device 90 may transmit all the fault analysis datasets DB stored in the second storage area 92B to the terminal device 200 in addition to or instead of all the fault analysis datasets DB stored in the first storage area 92A.

[0078] In the above embodiment, the storage deletion control can be changed.

[0079] For example, in step S72 , the data management device 91Z of the vehicle control device 90 may delete a portion of the fault analysis dataset DB stored in the first storage area 92A.

[0080] For example, in step S72, data management device 91Z of vehicle control device 90 may delete all fault analysis datasets DB stored in second storage area 92B in addition to or instead of all fault analysis datasets DB stored in first storage area 92A. To prevent accidental deletion of fault analysis datasets DB stored in second storage area 92B, fault analysis datasets DB stored in second storage area 92B may be deleted in response to a deletion request signal from a device other than terminal device 200.

[0081] In the above embodiment, storage deletion control in response to a deletion request signal from terminal device 200 can be omitted. For example, in step S62 of the data acquisition control, data management device 91Z of vehicle control device 90 can delete the fault analysis dataset DB stored in first storage area 92A after sending the fault analysis dataset DB stored in first storage area 92A to terminal device 200. In this case, the impact of the change is minimal.

[0082] In the above-described embodiment, the configuration of the analysis system SA may be changed.

[0083] For example, the vehicle control device 90 and the terminal device 200 may be able to communicate not via the vehicle connector 80 and the terminal connector 200C, and as a specific example, may be able to communicate wirelessly.

[0084] For example, the configuration of vehicle storage device 92 may be modified. Specifically, first storage area 92A may be a volatile storage area. Even in this case, as long as the power supply to vehicle control device 90 is maintained, the failure analysis data set DB stored in first storage area 92A can be prevented from being lost. Second storage area 92B may be a volatile storage area. Even in this case, as long as the power supply to vehicle control device 90 is maintained, the failure analysis data set DB stored in second storage area 92B can be prevented from being lost.

[0085] For example, the configuration of the vehicle control device 90 can be modified. Specifically, the vehicle control device 90 can be composed of multiple devices. In other words, the device comprising the vehicle processing device 91 and the device comprising the vehicle storage device 92 can be different. The device comprising the first storage area 92A and the device comprising the second storage area 92B can be different. Furthermore, the device functioning as the reception unit 91A, the device functioning as the internal monitoring unit 91B, and the device functioning as the fault recording unit 91C can be different.

[0086] Processing devices such as the vehicle processing device 91 and the terminal processing device 210 may be configured as long as they include a CPU and ROM and execute software processing. The processing device is not limited to this configuration. Specifically, the processing device may be configured as any of the following (a), (b), and (c).

[0087] (a) The processing device includes one or more processors that execute various processes according to a computer program. The processor includes a CPU and memory such as RAM and ROM. The memory stores program code or instructions that cause the CPU to execute processes, such as information provision processing. Memory, i.e., non-transitory computer-readable storage media, includes all available media that can be accessed by general-purpose or special-purpose computers.

[0088] (b) The processing device includes one or more dedicated hardware circuits for performing various processing operations. Examples of dedicated hardware circuits include application-specific integrated circuits (ASICs) or FPGAs. ASIC stands for "Application Specific Integrated Circuit," and FPGA stands for "Field Programmable Gate Array."

[0089] (c) The processing device includes a processor that executes part of various processes according to a computer program and a dedicated hardware circuit that executes the remaining processes among the various processes.

Claims

1. A vehicle data management device, wherein: The data management device includes a processing circuit, The processing circuit is configured to perform the following processing: When a fault of the vehicle is detected, obtaining a fault analysis data set for analyzing the fault; storing the newly acquired fault analysis data set in the first storage area until the total capacity of the stored fault analysis data set reaches a predetermined capacity; as well as When the newly acquired fault analysis data set satisfies a predetermined specific condition, the newly acquired fault analysis data set is stored in the second storage area using a ring buffer method.

2. The vehicle data management device according to claim 1, wherein: The fault categories are pre-classified into multiple categories, and the fault categories have specific fault categories. The specific condition has a requirement that the fault analysis dataset corresponds to the specific fault type.

3. The vehicle data management device according to claim 2, wherein: The vehicle includes a plurality of systems, wherein the plurality of systems include a specific system. The specific condition has the requirement that the fault analysis dataset corresponds to the specific system and the specific fault type.

4. The vehicle data management device according to any one of claims 1 to 3, wherein: The fault analysis data set includes a data set representing a driving condition of the vehicle.

5. The vehicle data management device according to claim 4, wherein: The fault analysis data set includes a data set indicating a total travel distance of the vehicle as the data set indicating the travel condition.

6. A vehicle, wherein: The vehicle has: Data management devices; and a storage device storing a fault analysis data set for analyzing the fault of the vehicle, The storage device includes a first storage area and a second storage area. The data management device includes a processing circuit configured to execute the following processing: When a fault of the vehicle is detected, obtaining the fault analysis data set; storing the newly acquired fault analysis data set in the first storage area until the total capacity of the stored fault analysis data set reaches a predetermined capacity; as well as When the newly acquired fault analysis data set satisfies a predetermined specific condition, the newly acquired fault analysis data set is stored in the second storage area using a ring buffer method.

7. The vehicle according to claim 6, wherein: The second storage area is non-volatile.

8. A parsing system, wherein: The analysis system has: A data management device is mounted on the vehicle; a storage device, mounted on the vehicle, storing a fault analysis data set for analyzing a fault of the vehicle; as well as a terminal device, located outside the vehicle, capable of communicating with the data management device, The storage device includes a first storage area and a second storage area. The data management device includes a processing circuit configured to execute the following processing: When a fault of the vehicle is detected, obtaining the fault analysis data set; storing the newly acquired fault analysis data set in the first storage area until the total capacity of the stored fault analysis data set reaches a predetermined capacity; When the newly acquired fault analysis data set satisfies a predetermined specific condition, storing the newly acquired fault analysis data set in the second storage area by means of a ring buffer; as well as The fault analysis data set stored in the first storage area is transmitted to the terminal device in response to an acquisition request signal from the terminal device.

9. The analysis system according to claim 8, wherein: The data management device is configured to perform the following processing: Only the fault analysis data set stored in the first storage area is deleted in response to a deletion request signal from the terminal device.

10. A vehicle data management program product causing a processing circuit to execute vehicle data management processing, wherein: The processing circuit is mounted on the vehicle, and the data management process includes: When a fault of the vehicle is detected, obtaining a fault analysis data set for analyzing the fault; storing the newly acquired fault analysis data set in the first storage area until the total capacity of the stored fault analysis data set reaches a predetermined capacity; as well as When the newly acquired fault analysis data set satisfies a predetermined specific condition, the newly acquired fault analysis data set is stored in the second storage area using a ring buffer method.

11. A vehicle data management method, wherein: The data management method comprises: When a fault of the vehicle is detected, a processing circuit mounted on the vehicle acquires a fault analysis data set for analyzing the fault; storing the newly acquired fault analysis data set in the first storage area until the total capacity of the stored fault analysis data set reaches a predetermined capacity; as well as When the newly acquired fault analysis data set satisfies a predetermined specific condition, the newly acquired fault analysis data set is stored in the second storage area using a ring buffer method.

Images