JP2005300390A - Vehicle monitoring device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To collect information for specifying a defective spot by connecting a diagnosis device to a vehicle monitoring module, without accessing a plurality of information sources with different means by a vehicle mechanic. <P>SOLUTION: Concerning this vehicle monitoring device equipped with an interface for communicating with the diagnosis device, ECU, a server device and a GPS receiver, when the diagnosis device is connected to the vehicle monitoring device loaded on the vehicle, the vehicle monitoring device establishes communication connection to a proper information source and receives a diagnosis request from the diagnosis device. The vehicle monitoring device receiving the request from the diagnosis device selects a communication means and a communication connection place based on the vehicle state and the communication state acquired from LAN in the vehicle, acquires information corresponding to the request from the diagnosis device from the selected connection place, transmits the information to the diagnosis device, and thereby displays maintenance information necessary for inspection/repair of the vehicle on a display of the diagnosis device. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a vehicle monitoring device that processes vehicle information in response to a request from a diagnostic device.

  When a bad car is brought into an automobile dealer or repair shop, the maintenance staff checks the appearance and sound to identify the defective part. In addition, when a defective part cannot be easily identified, information necessary for maintenance is collected and identified using various means such as a maintenance manual, a diagnostic device, and an inquiry to an automobile manufacturer. The maintenance manual is published by the automobile manufacturer that manufactured the vehicle and distributed to a repair shop or the like, and describes the inspection procedure. The diagnostic device is connected to a vehicle with a cable and used to read vehicle information from an ECU (Electronic Control Unit) or the like, and the read information is displayed on the display of the diagnostic device. In addition, in order to respond to an inquiry from a repair shop, an automobile manufacturer may have an inquiry window that an operator can handle, and advises various troubleshooting methods that can cope with the latest vehicle malfunction.

  In addition, as disclosed in Japanese Patent Application Laid-Open No. 2003-114943, information items checked and repaired at a repair shop are collected and statistically processed in a data center, and checked items are listed in order of appropriate diagnostic reference values and failure frequencies. When a vehicle is inspected and repaired at each repair shop, it is considered to make a diagnosis / repair by referring to the diagnostic standard values and inspection items sent from the data center database.

JP 2003-114943 A

  However, in order for vehicle mechanics to deal with vehicle malfunctions and perform appropriate repairs and diagnoses, different means are used to access multiple information sources such as maintenance manuals, vehicle information, and inquiries to automobile manufacturers as described above. Thus, it is necessary to collect information for identifying the defective part of the vehicle. For this reason, access to an appropriate information source among a plurality of information sources depends on selection based on the experience of maintenance personnel, and the burden on maintenance personnel increases due to the complexity of accessing multiple information sources. End up. In addition, there is a problem in that the time and effort required to determine a vehicle defect increases and it takes time to make an appropriate determination.

  In order to solve such problems, in the present invention, when a diagnostic device and a vehicle monitoring device are connected, the vehicle monitoring device establishes a communication connection with an appropriate information source, collects and processes information, and provides the diagnostic device It is characterized by doing. This vehicle monitoring device includes an interface for communicating with a diagnostic device, an ECU, a server device, and a GPS receiver. Upon receiving a request from the diagnostic device, the vehicle monitoring device selects a communication connection destination based on the vehicle state acquired from the in-vehicle LAN. The information is acquired from at least one selected connection destination, and the acquired information is transmitted to the diagnostic apparatus.

  The vehicle monitoring device includes a storage device for leaving a history of information transmitted to the diagnostic device. When the latest inspection procedure is acquired from the server device, the vehicle monitoring device is finally stored in the diagnostic device. Compared with the transmitted inspection procedure, if the inspection procedure has been updated, information indicating that the inspection procedure has been updated is added, and the inspection procedure is transmitted to the diagnostic apparatus. In addition, if the hit rate of the latest abnormality factor acquired from the server device is compared with the hit rate of the failure factor compared with the hit rate of the error factor that was last sent to the diagnostic device accumulated in the storage device, The difference is calculated, and the correctness ratio of the latest abnormality factor and the difference are transmitted to the diagnostic apparatus.

  This vehicle monitoring device is provided with two types of storage devices, and one storage device is provided with position information and date / time received by the GPS receiver, which is obtained by the vehicle monitoring module and indicates the vehicle state flowing on the in-vehicle LAN. When this data is data indicating the occurrence of an abnormality, the number of abnormalities occurring in the vehicle is updated, and when the information of one storage device is transmitted to the other storage device to the diagnostic device, The information is stored with a transmission date and time. Also, the information stored in the storage device is transmitted to the server device, the weather information at the time of occurrence of the abnormality is acquired from the server device using the position information and the date and time, and the content of the abnormality and the weather information are transmitted to the diagnostic device. To do.

  The vehicle monitoring device of the present invention includes a plurality of communication interfaces for connecting to a diagnostic device, a server device, an ECU, etc., and selects an appropriate communication connection destination according to the request contents from the diagnostic device, the vehicle state, and the communication state. By collecting and processing information and providing it to the diagnostic device, maintenance information necessary for vehicle inspection and repair can be displayed on the diagnostic device display simply by connecting the diagnostic device to the vehicle monitoring device. The burden on maintenance staff can be reduced, and prompt diagnosis and repair can be supported.

  The purpose of the maintenance staff to access multiple information sources by different means and collect the information required for vehicle inspection and repair was realized by a simple procedure of connecting the diagnostic device to the vehicle monitoring module.

FIG. 1 shows an example of a system configuration using a vehicle monitoring module 100 according to the present invention. The vehicle monitoring module 100 is connected to ECUs 150 and 160 via a diagnostic device 110 and an in-vehicle LAN 140, and the server device 120 via wireless communication. It is connected to the. The server device 120 includes a database 130 and can store information. The server device is connected to the Internet 170, and the latest weather information and the like can be acquired from other server devices via the Internet 170. The ECUs 150 and 160 are examples of devices connected to the in-vehicle LAN 140, and may be devices such as sensors and motors.

FIG. 2 is a configuration example of the vehicle monitoring module 100 according to the present invention. The vehicle monitoring module 100 includes a CPU 201 for executing calculations and an interface for exchanging information with other devices and peripheral devices. CPU201 performs serial communication RS-232C
(Recommended Standard 232 C) Interfaces 202, 203, and 204 are provided, and can communicate with a diagnostic device 110, a GPS (Global Positioning System) receiver 230, and a development tool 240. The CPU 201 includes a flash ROM (FROM) 205, which can store programs executed by the CPU 201 and information received from other devices. The CPU 201 includes an ATA (AT Attachment) interface 206,
Communication with the HDD 250 is possible. The CPU 201 includes PCMCIA (Personal Computer Memory Card International Association) interfaces 207 and 208 and can be connected to a mobile phone card 260 and a wireless LAN card 270. Mobile phone card 260
The wireless LAN card 270 is used to communicate with the server device 120. CPU
201 includes CAN (Control Area Network) interfaces 209 and 210 and can communicate with the ECUs 150 and 160 via the in-vehicle LAN 140. The diagnosis device 110 is a device used by a maintenance shop mechanic or the like to diagnose a vehicle. The GPS receiver 230 is a device for acquiring position information. The development tool 240 is used for rewriting and testing programs and data stored in the FROM 205 of the vehicle monitoring module 100. The HDD 250 is a large-capacity storage device and is used for storing various history information. The server device 120 provides information necessary for maintenance such as a vehicle inspection procedure.
The ECUs 150 and 160 are control devices for controlling the vehicle, and include a RAM and an EEPROM for temporarily storing vehicle control data and error information. Although not shown in the figure, the CPU 201 includes a timer, and can acquire information related to the date and time. In the configuration example illustrated in FIG. 2, an example in which an RS-232C cable is used for communication between the vehicle monitoring module 100 and the diagnostic device 110 is illustrated. However, a wireless communication device, an infrared communication device, a wireless LAN, Wireless communication means such as a cellular phone network may be used.

  FIG. 3 is a configuration example of a table stored in the FROM 205. The vehicle attribute management table 300 manages the attribute information of the vehicle and the customer who purchased the vehicle. The vehicle number 301, the vehicle type 302, the vehicle manufacturing date 303, the customer number 304 for identifying the customer who purchased the vehicle, etc. Stored. The attribute information of the vehicle is registered when the vehicle is shipped, and the attribute information of the customer is registered using the development tool 240 when the vehicle is sold at a vehicle dealer. The abnormality occurrence number management table 350 manages the number of occurrences of abnormality in the vehicle for each part and phenomenon, and a part 351 where the occurrence of abnormality is detected, an abnormal phenomenon 352, and an abnormality history 353 indicating the number of abnormalities that occurred in the past Is stored. The number of abnormalities that have occurred in the past one day, the number of abnormalities that have occurred in the past seven days, and the total number of abnormalities that have occurred since the vehicle was shipped are managed for each part and phenomenon.

FIG. 4 is a configuration example of a table stored in the HDD 250. The history information management table 400 stores the message received from the in-vehicle LAN 140 with the position 401 and time 402 at which the message was received. A message received from the in-vehicle LAN 140 includes an ID 403 and data 404 for identifying the message. For example, in the case of a message that conveys the vehicle speed, the message is composed of an ID 403 that indicates information related to the vehicle speed and numerical data 404 that indicates the vehicle speed. Messages for controlling the vehicle are constantly transmitted and received between the ECUs 150 and 160. The vehicle monitoring module 100 can read these messages flowing on the in-vehicle LAN 140 via the CAN interfaces 209 and 210. The vehicle monitoring module 100 reads these messages and stores them in the HDD 250.

The transmission history management table 450 stores a history of information transmitted to the diagnostic device 110. In this history, the relationship between the date / time 451 at which information is transmitted from the vehicle monitoring module 100 to the diagnostic device 110 and the file name 452 of the file storing the transmitted information is managed. The file indicated by the file name 452 is stored in the HDD 250. When the vehicle monitoring module 100 transmits information to the diagnostic apparatus 110, the vehicle monitoring module 100 stores the transmitted information as a file in the HDD, and registers the file name 452 and the transmitted date and time 451 in the transmission history management table 450.

5 and 6 are configuration examples of tables stored in the database 130 of the server apparatus 120. FIG. The inspection procedure management table 500 shown in FIG. 5 stores an inspection procedure 504 for each part 501, phenomenon 502, and factor 503 of the vehicle. For example, when abnormal noise is heard from the engine of the vehicle, the factor 503 of the item in which the part 501 of the inspection procedure management table 500 is “engine” and the phenomenon 502 is “abnormal noise” causes the abnormal noise. As examples, there are a reduction gear abnormality, a roller abnormality, and a clutch abnormality. The inspection procedure management table 500 stores an inspection procedure 504 corresponding to these factors. These inspection procedures 504 are registered in the database 130 in correspondence with the cause of abnormality that is assumed in advance, for example, when a designer of an automobile manufacturer ships a vehicle. The inspection procedure 504 is periodically updated based on the maintenance situation when an abnormality occurs.

The weather information management table 550 manages the weather information of each place and acquires the acquired weather information 553.
(Weather, temperature, humidity) and the date and time 551 and information on the target area 552 are stored. For example, in Kawasaki City, Kanagawa Prefecture, the weather from 15:00 to 18:00 on July 20, 2004 is rainy, the temperature is 25 degrees, and the humidity is 82 degrees (5051). These pieces of information are transmitted from the server device that provides weather information to the server device 120 via the Internet 170 and stored in the database 130.

  The hit rate management table 600 shown in FIG. 6 stores the hit rate for each factor of the decrease occurring in each part. In the hit rate management table 600, the relationship between the part 601, the phenomenon 602, the factor 603 and the hit rate is managed, and the latest hit rate 604 calculated from the cumulative total of past diagnosis results for each factor 603, Information about the hit rate 605 of 30 days ago, which is roughly equivalent to one month ago, is stored. Here, the hit rate is the probability of the factor for each phenomenon in each part, and is the ratio of the number of times determined as a factor in the diagnosis result to the corresponding number of times of diagnosis. For example, if diagnosis is performed while detecting abnormal noise of the engine 50 times, and it is determined 45 times that there is a cause in the reduction gear, the hit rate can be calculated as 90% by dividing both (6001).

  The diagnosis result log management table 650 stores the diagnosis result, and stores the car type 651, the part 652, the phenomenon 653, the factor 654 found as a result of the diagnosis, and the date and time 655 of the diagnosis. Is done. For example, information is registered that “the cause was the roller as a result of diagnosis at 15:30 on July 21, 2004 because an abnormal noise was detected in the engine of vehicle type A” (6051). . The date and time 655 is the date and time when the server device 120 receives information related to the diagnosis result transmitted by the vehicle monitoring module 100.

FIG. 7 is a configuration example of data stored on the memories of the ECUs 150 and 160, and includes data items 711 and control data 712. In the case of an engine ECU, the control data management table 700 stores frequency components (7001) of acoustic data, engine speed (7002), intake air volume (7003), intake pipe pressure (7004), and the like. .

FIG. 8 is a screen configuration example of the diagnostic apparatus 110. When the diagnosis device 110 is connected to the vehicle monitoring module 100, a vehicle attribute information 810 and a pull-down menu 820 for selecting a part are displayed on the diagnosis screen 800. When a part is selected and the transmission button 881 is pressed, a pull-down menu 840 for selecting a state 830 and a phenomenon of the selected part is displayed. The example of FIG. 8 shows the engine state, and the abnormal phenomenon of the engine (abnormal noise, charging failure, engine stall, knocking, etc.), the number of times the abnormal phenomenon has been detected in the past (number of times detected in the past one day, the past seven days) , The total number of times detected in the past, etc.), the date and time when the diagnosis was performed by connecting the previous diagnostic device 110 to the vehicle monitoring module 100, and the date and time when the current diagnosis is performed. The numerical value in parentheses indicates the difference between the number of times displayed at the previous diagnosis and the current number of times.

  When a phenomenon is selected from the pull-down menu 840 for selecting a phenomenon, an inspection item 850, an inspection procedure 860, environmental information 870, and a diagnosis result input 890 are displayed. In the check item 850, the cause of the phenomenon (deceleration gear abnormality, roller abnormality, clutch abnormality, etc.), the current hit rate for each factor, the hit rate 30 days ago, and a detailed display button 880 are displayed. The numerical value in parentheses displayed on the right side of the hit rate is the difference from the hit rate at the time of the previous diagnosis, and indicates how much the hit rate has changed. As a result, it is possible to grasp the recent trend of change in the hit rate. The detail display button 880 may or may not be displayed depending on the vehicle state. When the vehicle is running and there is a safety problem in reading the ECU data, the detail display button 880 is displayed. It is not displayed on the screen.

  The inspection procedure 860 displays an inspection procedure for each factor, and when the inspection procedure for the corresponding factor is updated and the procedure has changed from the previous diagnosis, “NEW” is displayed below the factor name. Is displayed. The environment information 870 is meteorological information at the date and place where the abnormality was detected. The selected phenomenon (abnormal noise) of the selected part (engine) has been detected four times in the past seven days (830), and the weather, temperature, and humidity at the date and place where the abnormal noise was detected are It is retrieved from the weather information management table of the server device 120 and displayed. For example, the last detected date of engine noise is Kawasaki City on July 20, 2004 at 21:31:11 (by searching for information in the history information management table 400, the location is The weather at that time is rain, the temperature is 23 degrees, and the humidity is 79 degrees. The user of the diagnostic device can identify the cause of the phenomenon that has occurred by performing the inspection according to the procedure displayed in the inspection procedure 860. The identified factor is input to the diagnosis result input 890. A factor is selected from the pull-down menu 890 and described in the remarks if there is any special mention.

Information in the database 130, the FROM 205, the HDD 250, and the ECUs 150 and 160 of the server device 120 changes every moment. For example, the server device 120 updates the hit rate management table 600 and the diagnosis result log management table 650 based on the diagnosis results received from a large number of vehicle monitoring modules 100, and the inspection procedure management table 500 and the weather information management table 550. This information is also updated by information from the designer and other server devices. When the update button 882 is pressed, the server device 120, FROM 205, HDD 250, ECU 150,
The latest information 160 is read, and the result of reflecting the information is displayed on the diagnosis screen 800.

  FIG. 9 is a configuration example of a detailed information display screen 900 that displays the detailed state of the vehicle. When the detail display button 880 is pressed, a detailed information display screen 900 is displayed. First, a screen 910 for selecting online information of the part (engine in this example) selected in FIG. 8 is displayed. Here, data items of the engine ECU are displayed, and items of detailed information to be displayed can be selected from acoustic data, engine speed, intake air amount, and the like. When an item of detailed information desired to be displayed is selected and a display button 930 is pressed, detailed data is displayed. When the acoustic data is selected and the display button 930 is pressed, a screen 920 showing the acoustic data is displayed, and it is possible to analyze what kind of abnormality has occurred by looking at the waveform of the detailed acoustic data.

FIG. 10 is a processing flow example showing normal processing in the vehicle monitoring module 100. When the vehicle monitoring module 100 is powered on (step 1001), the CAN interface 209 is checked to determine whether it is connected to the in-vehicle LAN 140 (step 1002). For example, the ECUs 150 and 160 connected to the in-vehicle LAN 140 transmit messages to the in-vehicle LAN 140 at regular time intervals, and the vehicle monitoring module 100 determines that the in-vehicle LAN 140 is not connected unless it receives a message for a fixed time. If it is not connected to the in-vehicle LAN 140, the process is terminated. When connected to the in-vehicle LAN 140, a message flowing through the in-vehicle LAN 140 is received (step 1003). If a message is transmitted to ECUs 150 and 160, there is a risk of affecting the running of the vehicle. Absent. When the vehicle monitoring module 100 receives a message from the in-vehicle LAN 140, the vehicle monitoring module 100 acquires the position and date from the GPS receiver 230 and the timer (step 1004).

Next, the received message ID and data are read, and if it is determined that the message is a message indicating the occurrence of an abnormality (step 1005), it corresponds to the message ID received in the abnormality occurrence count management table 350 of the FROM 205. The part information is updated (step 1006). If it is determined that the message is not a message indicating the occurrence of an abnormality (step 1005), a position (latitude / longitude information) and date / time are added to the message and stored in the history information management table 400 of the HDD 250 (step 1007). The processing from step 1003 to step 1007 is repeated until the power source of the vehicle monitoring module 100 is turned off (step 1008). Specifically, the message is composed of ID and data. For example, the message ID 0101 indicates that the message is related to engine noise, and if the first bit of the data portion of this message is set ( If the bit is “1”), it is assumed that an abnormality has been detected. When a message indicating that an abnormal noise in the engine has been detected is received, the number of times in the past 1 day or the number of times in the past 7 days of the item in which the phenomenon 352 in the abnormal frequency management table 350 of the FROM 205 corresponds to the abnormal noise , 1 is added to each of the accumulated values (step 1006). Further, by searching for a message indicating that an abnormality has been detected from the messages stored in the history information management table 400 and the history information of the date and time, and accumulating the number of messages for each part and phenomenon, the abnormality occurrence number management table 350 Can be created. The CPU 201 periodically reads the history information management table 400 from the HDD 250 to create the abnormality occurrence number management table 350, and executes the FROM
In comparison with the abnormality occurrence count management table 350 stored in 205, when the number of abnormality histories is different, updating is performed, so that the number of the past one day and the number of the past seven days in the history information management table 400 of the HDD 250 are updated. Set to the correct value.

FIGS. 11 and 12 are examples of processing flows when the diagnostic device 110 is connected to the vehicle monitoring module 100 and a diagnostic request is received from the diagnostic device 110. As shown in FIG. 11, when the vehicle monitoring module 100 receives a message telling a diagnosis request from the diagnostic device 110 (step 1101), the vehicle monitoring module 100 receives a message related to the vehicle speed from the messages flowing through the in-vehicle LAN 140, and increases the vehicle speed. Read (step 1102). It is assumed that the vehicle speed is important data for vehicle control and frequently flows on the in-vehicle LAN 140. When the vehicle state is determined based on the vehicle speed data, and it is determined that the vehicle is not stopped, the message is not transmitted to and received from the ECUs 150 and 160, and the data is not acquired.
250, data is acquired from the server device 120 (step 1103). In addition, messages are transmitted and received between the mobile phone card 260 and the wireless LAN card 270 via the PCMCIA interfaces 207 and 208, and whether or not communication is possible, that is, the communication area between the mobile phone network and the wireless LAN. It is judged whether it is in. When the wireless LAN is in a communicable state, the wireless LAN card 270 is used as a communication unit with the server apparatus 120. When the wireless LAN is not in a communicable state, the mobile phone card 260 is communicated with the server apparatus 120. When both are in a state where they cannot communicate with each other, it is determined that there is no means for communication with the server device 120 (step 1104).

Next, the vehicle monitoring module 100 transmits information of the vehicle attribute management table 300 in the FROM 205 to the diagnostic device 110 (step 1105). Then, an instruction as to which part is to be diagnosed is received from the diagnostic apparatus 110 (step 1106). Based on the received instruction, information related to the part to be diagnosed is read from the abnormality occurrence count management table 350 in the FROM 205, and information transmitted to the previous diagnosis device 110 is read from the transmission history management table 450 in the HDD 250. That is, information is read from the file indicated by the file name 452 corresponding to the latest date 451 in the transmission history management table 450. The number of times counted in the abnormality occurrence number management table 350 and the number of times the abnormality occurrence number management table 350 sent to the diagnostic device 110 are compared to calculate the difference, and the information and calculation of the abnormality occurrence number management table 350 in the FROM 205 As a result, the date and time 451 of the last diagnosis are transmitted to the diagnosis device 110 (step 1107). Next, an abnormal phenomenon is received from the diagnostic device 110 (step 1108).

Next, as shown in FIG. 12, when there is no means for communication with the server apparatus 120, that is, when the communication state with the server apparatus 120 cannot be established by examining the PCMCIA interfaces 207 and 208 (step 1201), The diagnosis device 110 is notified that communication is not possible (step 1212), and the process is terminated. When there is a communication means with the server device 120 (step 1201), the history information regarding the part and phenomenon received from the diagnostic device 110 is acquired from the history information management table 400 of the HDD 250 (step 1202). It is determined based on the ID 403 whether it is history information regarding the received part and phenomenon.
The information in the vehicle attribute management table 300 in the FROM 205, the part and phenomenon received from the diagnostic device 110, and the history information acquired from the history information management table 400 in the HDD 250 are transmitted to the server device 120 (step 1203).

  Upon receiving these pieces of information, the server device 120 reads the factor 503 and the inspection procedure 504 that match the part 501 and the phenomenon 502 from the inspection procedure management table 500, and includes the time and position of the history information from the weather information management table 550. The date and time 551 and the region 552 are searched and the weather information 553 is read, and the factor 603, the cumulative target rate 604, and the target target rate 605 30 days before are read from the target rate management table 600. These pieces of information are transmitted to the vehicle monitoring module 100. The vehicle monitoring module 100 receives the factor, inspection procedure, weather information, and hit rate from the server device 120 (step 1204), and performed the previous diagnosis read from the file indicated by the file name 452 of the transmission history management table 450. When the hit rate included in the information transmitted to the diagnostic device 110 at this time is compared with the hit rate received from the server device 120, a difference is calculated. The calculation result of the hit rate and the comparison result of the check procedure, the factors received from the server device 120, the check procedure, weather information, the hit rate, and whether or not the data can be acquired from the ECUs 150 and 160 are transmitted to the diagnosis device 110. (Step 1205).

  As described above, when the data of the ECUs 150 and 160 cannot be acquired (step 1206), the diagnostic device 110 is notified that online information cannot be acquired (step 1211). The diagnostic device 110 does not display the detail display button 880 upon receiving this notification. When the data of the ECUs 150 and 160 can be acquired (step 1206), the data is periodically read from the control data management table 700 of the ECU 150 that controls the part received from the diagnostic device 110 for a predetermined time period. Are stored in the HDD 250 (step 1207). The data stored in the HDD 250 is transmitted to the diagnostic device 110 (step 1208).

The vehicle monitoring module 100 receives the diagnosis result (factor) from the diagnosis device 110 (step 1209), and the server type 302 receives the vehicle type 302 of the vehicle attribute management table 300 of the FROM 205, the part, phenomenon, and diagnosis result received from the diagnosis device 110. It transmits to 120 (step 1210).

FIG. 13 is an example of a processing flow showing a method for calculating the hit rate in the server device 120. The server device 120 receives the part, phenomenon, and diagnosis result (factor) from the vehicle monitoring module 100 (step 1301), and stores them in the diagnosis result log management table 650 together with the received date and time (step 1302). In addition, the hit ratio is calculated by adding 1 to the cumulative number of diagnoses and diagnosis results in which the part 601, the phenomenon 602, and the factor 603 of the hit ratio management table 600 match, and dividing the diagnosis result by the number of diagnoses (step 1303). ). In addition, from the diagnosis result log management table 650, the data within 30 days and the data that matches the vehicle type, part, and phenomenon are read, the number of data and the number of each factor are integrated, and the number of each factor is divided by the number of data. Thus, the hit rate 30 days before the hit rate management table 600 can be calculated. The server device 120 calculates the hit rate of 30 days before at least once a day, and updates the hit rate in the hit rate management table 600.

  When the vehicle has a car navigation device equipped with a GPS receiver and HDD, the vehicle monitoring device according to the present invention can share these devices with the car navigation device, and the vehicle monitoring device is incorporated in the car navigation device. Can be applied.

1 is a configuration example of a system using a vehicle monitoring module according to the present invention. It is a structural example of the vehicle monitoring module which concerns on this invention. It is a structural example of the table preserve | saved at FROM. It is an example of a structure of the table preserve | saved at HDD. It is a structural example of the table preserve | saved in the database of a server apparatus. It is a structural example of the table preserve | saved in the database of a server apparatus. It is a structural example of the table preserve | saved at ECU. It is an example of a screen structure of a diagnostic apparatus. It is an example of a screen structure of a diagnostic apparatus. It is an example of the normal process flow in a vehicle monitoring module. It is an example of a processing flow when a diagnosis request is received in the vehicle monitoring module. It is an example of a processing flow when a diagnosis request is received in the vehicle monitoring module. It is an example of the processing flow which calculates a hit rate in a server apparatus.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 ... Vehicle monitoring module, 110 ... Diagnostic apparatus, 120 ... Server apparatus, 140 ... In-vehicle LAN, 150, 160 ... ECU, 205 ... FROM, 230 ... GPS receiver, 250 ... HDD.

Claims (5)

A first communication interface for communicating with a diagnostic device or a GPS receiver, a second communication interface for connecting to an in-vehicle LAN to which at least one ECU is connected, and a third communication interface for connecting to a server device In a vehicle monitoring device comprising:
The vehicle monitoring device includes a storage device that stores a history of information transmitted to the diagnostic device,
The vehicle monitoring device accepts a request from the diagnostic device via a third communication interface,
Based on the vehicle state acquired from the in-vehicle LAN, the server device or the ECU is selected as a communication connection destination,
Send a request to obtain information to the communication interface connected to at least one selected connection destination,
Sending information acquired from the connection destination selected based on the request to the diagnostic device, and storing the information in the storage device,
When the connection destination is the server device, the information acquired from the server device and transmitted to the diagnostic device is compared with the information stored in the storage device, and the information acquired from the server device is updated. In this case, the vehicle monitoring device is characterized in that a difference between the information and the information stored in the storage device is obtained and transmitted to the diagnostic device. The vehicle monitoring device according to claim 1,
The inspection procedure acquired from the server device is compared with the inspection procedure transmitted to the diagnostic device last stored in the storage device. If the inspection procedure acquired from the server device is updated, the inspection procedure is updated. The vehicle monitoring device is characterized in that information indicating this is given and an inspection procedure is transmitted to the diagnostic device. The vehicle monitoring device according to claim 1,
When the hit rate of abnormal factors acquired from the server device is compared with the hit rate of abnormal factors compared with the hit rate of the abnormal factor that was last transmitted to the storage device and stored in the storage device. Calculates the difference between the two, and transmits the accuracy of the abnormality factor acquired from the server device and the difference to the diagnostic device. The vehicle monitoring device according to claim 1, wherein the storage device is configured by two different storage devices, and one storage device stores the number of abnormalities occurring in the vehicle,
The vehicle monitoring device acquires information indicating the vehicle state acquired from the ECU from the in-vehicle LAN via the second communication interface, and when the occurrence of abnormality is detected by the acquired information, The location information and date / time at which the abnormality has occurred based on the location information received from the GPS receiver is accumulated in another storage device of the two storage devices, and the number of occurrences of the abnormality recorded in the one storage device is updated. The vehicle monitoring apparatus characterized by the above-mentioned. 5. The vehicle monitoring device according to claim 4, wherein when the information stored in the other storage device is transmitted to the server device, the position and time information attached to the information stored in the other storage device is supported. The vehicle monitoring device is characterized by acquiring the meteorological information from the server device, and transmitting the abnormal content of the information and the acquired weather information to the diagnostic device.

Images