KR20090000008A - Anticollision system among diagnosis terminals and method thereof - Google Patents

Abstract

A control algorithm and a method for preventing collision among diagnosis terminals during vehicle diagnosis are provided to prevent cost increase and realize a vehicle diagnosis service function efficiently by detecting connection with an external diagnosis device with software. A diagnosis daemon(111) performs a vehicle diagnosis service by reading and writing data to a vehicle information terminal through a communication line driver. A read thread(114) detects connection with an external diagnosis device by reading the data through the communication line driver. A request thread(118) sets a diagnosis request message of an upper application program according to a communication line frame and requests a diagnosis to an ECU(Engine Control Unit) through the communication line driver. The read thread detects that the external diagnosis device is connected when the read data is a response data frame.

Description

Anti-collision system and method for diagnosis terminal period during vehicle diagnosis {Anticollision System Among Diagnosis Terminals and Method}

1 is a configuration diagram of a vehicle diagnostic system applied to the present invention,

2 illustrates a diagnostic software architecture implemented in the vehicle information terminal shown in FIG. 1 according to the present invention;

FIG. 3 is a diagram illustrating an internal software architecture of the diagnostic daemon shown in FIG. 2;

Figure 4 is a flow chart of the collision avoidance method for diagnosis of the vehicle information terminal according to the present invention.

<Description of the symbols for the main parts of the drawings>

10: vehicle information terminal 20: external diagnostic device

30: electronic control unit (ECU) 40: communication line

50: connector

The present invention relates to an anti-collision system and method for diagnosing a terminal during vehicle diagnosis. More particularly, the present invention relates to a vehicle diagnostic service, which is one of the services of a vehicle information terminal such as a telematics terminal mounted in a vehicle, by software. The present invention relates to a control algorithm for preventing a collision with an external diagnostic device.

As the functions of the vehicle become higher, various components mounted on the vehicle are operated through electronic control.

In some electronic control units (ECUs), driving is not possible due to the influence of safe vehicle operation when a failure occurs.

Therefore, in case of failure of various ECUs, it is possible to determine the failure status in real time and inform the risk factor to the user (driver) so that the service can be repaired in advance by finding a repair shop before the risk occurs during the operation of the vehicle. It is being added to vehicle information terminals (eg, telematics terminals, AV terminals, Navi systems).

When implementing a vehicle diagnostic service, for example, one of the services of a telematics terminal among the vehicle information terminals, the same protocol as the diagnostic communication protocol used in the garage is used.

Therefore, the diagnostic device code of the external diagnostic device used in the workshop and the diagnostic device code implemented in the telematics terminal are the same.

In this case, a vehicle equipped with a telematics terminal with a vehicle diagnosis function is connected to an external diagnosis unit at a repair shop, and malfunctions are caused by using the same device ID by using the same network and the same communication protocol when the vehicle is diagnosed. A crash can occur.

However, since the external diagnostic device does not determine that the vehicle information terminal exists, in this case, an external diagnostic device detection method should be provided in the vehicle or the vehicle information terminal, and one of the detection methods is a switch capable of detecting the connection of the external diagnostic device. By connecting to the terminal, it is possible to monitor the external diagnostic device connected to the hardware, but in this case, the additional hardware design must be considered, the production cost increases.

Since the vehicle information terminal (telematics terminal) generally includes an operating system (Operating System), a minimum time (usually 10 seconds to several tens of seconds) is required for booting.

The ECU to be diagnosed can be booted within a few seconds (1-3 sec) after IGN-on, so that a vehicle diagnosis, ECU upgrade, and other service functions can be performed within a few seconds after IGN-on with an external diagnostic device connected.

Therefore, if the vehicle diagnostics, ECU upgrades, and other services using the external diagnostics are executed within a few seconds after the IGN-on, the vehicle information terminal may attempt to connect for diagnostic functions without knowing the communication network status after booting. have.

In this case, unnecessary data is input to the communication network, which may cause an error in the external diagnostic device or the vehicle information terminal, and in the case of upgrading, there may be a problem that may cause a data error of the target ECU.

The present invention has been made to solve the above-described problem, by detecting the connection of the external diagnostic device in software to prevent the collision with the external diagnostic device when implementing the vehicle diagnostic service built in the vehicle information terminal, the connection of the switch which is hardware The purpose of the present invention is to provide a collision avoidance system and method for diagnosing a terminal during a vehicle diagnosis, which can be omitted, which can prevent a cost increase and implement a vehicle diagnostic service function in a vehicle information terminal more efficiently.

In order to achieve the above object, a collision avoidance system of a diagnostic terminal period during vehicle diagnosis according to an embodiment of the present invention is mounted on a vehicle and connected to each other through a communication line, and the ECU is a diagnosis target, and a diagnostic communication protocol embedded in the vehicle. A vehicle information terminal for performing a vehicle diagnostic service of an ECU using an external terminal and an external terminal provided in a repair shop or the like for performing a vehicle diagnostic service of an ECU using the same protocol as the diagnostic communication protocol of the vehicle information terminal. In;

The vehicle information terminal is provided with a diagnostic daemon for performing a vehicle diagnostic service by reading and writing data from a communication line through a communication line driver.

The diagnostic daemon is divided into Read_thread () having only a read function and Request () having only a write function, and the Read_thread () always reads data from a communication line through a communication line driver and detects whether an external diagnostic device is connected. Request () is characterized in that the diagnostic request message of the upper application is set in accordance with the communication line frame and then the diagnosis request is made to the target ECU through the communication line driver.

In addition, the collision avoidance method of the diagnostic terminal period during vehicle diagnosis according to an embodiment of the present invention, reading the data from the communication line and analyzing the data to detect whether the external diagnostic device is connected, when the external diagnostic device is connected to the external diagnostic device Transmitting the connection information and the diagnostic request disable message; and monitoring the occurrence of the DTC on the target ECU when the external diagnostic device is not connected, and analyzing the generated DTC data when the DTC is generated to analyze only the DTC in a specific state. A data read loop comprising: storing and transmitting the DTC in the specific state to a center diagnosis server;

Analyzing the external diagnostic device connection information and the diagnostic request disable message sent from the message and the data read loop of the center diagnostic server to determine whether the diagnostic request is a disable message, and in the case of the diagnostic request disable message If it is not a diagnostic request disable message, determining whether it is a diagnostic request message, requesting a diagnosis to a target ECU in the case of a diagnostic request message, and executing a corresponding message command if the diagnostic request message is not. A message processing loop comprising a step; Include.

Hereinafter, the configuration and operation of the present invention will be described with reference to the accompanying drawings.

1 is a configuration diagram of a vehicle diagnostic system applied to the present invention.

As shown, the vehicle information terminal 10, the external diagnostic device 20, the ECU 30, and comprises a communication line 40.

The ECU 30 grasps and compares various states of the vehicle from sensors mounted on the respective component devices of the vehicle, drives the respective component devices, and is connected through the communication line 40.

The communication line 40 may be a high speed CAN line (eg, 500 kbps) 40a, a low speed CAN line (eg, 10 kbps) 40b, and other non-CAN lines such as FlexRay, L-line, K-Line, and the like. It consists of a communication line 40c.

Each CAN line 40a, 40b has two high and low signals.

For example, the high speed CAN line 40a is composed of a high speed CAN high and a high speed CAN low line.

In the present invention, the diagnostic communication is performed using the high speed CAN line 40a.

The vehicle information terminal 10 refers to any terminal embedded in a vehicle and connected to the ECU 30 and the high speed CAN line 40a to perform a vehicle diagnostic service using the ECU 30 and a diagnostic communication protocol. For example, it may be the telematics terminal 11, the AV terminal 12, the Navi System 13, or the like.

The external diagnostic device 20 is, for example, a terminal provided in a repair shop or the like to implement a vehicle diagnostic service, and uses the same protocol as the diagnostic communication protocol of the vehicle information terminal 10.

Hereinafter, a system for communicating with the ECU 30 using the diagnostic communication protocol through the high speed CAN line 40a will be described as an example.

FIG. 2 is a diagram illustrating a diagnostic software architecture implemented in the vehicle information terminal shown in FIG. 1 according to the present invention.

As illustrated, the application program layer 120, the diagnostic daemon layer 110, and the hardware layer 100 are formed.

The diagnostic daemon 111 of the diagnostic daemon (Diagnosis Daemon) layer 110 performs a vehicle diagnostic service implemented in the vehicle information terminal 10 and is separated into a separate software layer or implemented as a single software CAN driver 112. ).

The diagnostic daemon 111 reads and writes data from the CAN network, which is a hardware layer, through the CAN driver 112.

The diagnostic daemon 111 executes vehicle diagnosis with the ECU 30 through the high speed CAN line 40a, and makes the result available to the upper application layer 120 according to each service.

For example, the vehicle diagnosis service is implemented by transmitting the diagnosis result to an external center diagnosis server through a CDMA modem.

The application program layer 120 is composed of applications (121 ~ 124) implemented in the vehicle information terminal (10), for example, to access the external center diagnostic server to send a DTC, or to receive the center diagnostic server And other service applications are implemented.

FIG. 3 is a diagram illustrating an internal software architecture of the diagnostic daemon shown in FIG. 2.

In the present invention, the read / write two functions are separated and read_thread () 114 and Request () 118 are configured to dedicate the functions of the diagnostic daemon 111.

The read_thread () 114 always reads data from the high speed CAN line 40a through the CAN driver 112 and buffers the diagnostic-related data, and then quick-views to connect the external diagnosis device 20. Detect.

In this case, the read_thread () 114 indicates a case where the diagnostic related data read through the high speed CAN line 40a is a diagnostic request data frame and a diagnostic request in the request daemon 118 of the diagnostic daemon 111. However, in the case of a response data frame, it is detected that the external diagnostic device 20 is connected.

In the case of the data frame requested by the diagnostic daemon 111, the CAN driver 112 cannot read it in the Read_thread () 114. Therefore, in the case of the diagnostic request data frame, the external diagnostic device 20 may request a diagnosis. (20) is connected.

In addition, the diagnosis is not requested by referring to the diagnosis request list of Request () 118. However, when the diagnosis response data frame is read, the diagnosis is made by the external diagnosis unit 20, and thus the external diagnosis unit 20 is connected. It is a state.

The Request () 118 sets the diagnosis request message of the upper application 121 in accordance with the CAN frame by combining the target ECU 30 ID and the diagnostic service ID, and the target ECU 30 through the CAN driver 112. Ask for a diagnosis.

The reason why the read / write two functions are separated and dedicated to the functions as described above is because the diagnostic program embedded in the vehicle information terminal 10 must grasp all the states in software.

That is, since all data that can be obtained internally must be obtained through the high speed CAN line 40a, the diagnostic daemon 111 should always read and analyze all the data in the high speed CAN line 40a. In order to implement read / write efficiently through 112), a thread should be implemented for each function so that each function can efficiently use the system performance. Depending on the state, delays of several tens of ms to several seconds may occur in response to data. Therefore, if the read / write functions are sequentially implemented, in some cases, the waiting time changes aperiodically while waiting for a response, thereby causing a load on the system. Because it gives.

Second, due to the system difference between the ECU 30 and the vehicle information terminal 10, the ECU 30 is composed of MCUs, so that the system booting time is short as 1 to 3 seconds, but the vehicle information terminal 10 is configured as an operating system of the CPU. As a result, the system boot time is relatively long, ranging from 10 to several tens of seconds.

Therefore, even when the external diagnostic apparatus 20 is connected to the high speed CAN line 40a during the time when the vehicle information terminal 10 receives the IGN-On signal and boots, the vehicle information terminal 10 is the high speed CAN line 40a. In other words, it may not be possible to determine the connection status of the external diagnostic device 20. In order for the diagnostic program to connect to the high speed CAN line 40a for the first time after booting, the data is connected to the high speed CAN line 40a with a read function only. Because you have to analyze.

Lastly, the third reason is that the bus-off state should be maintained in software when the connection of the external diagnosis apparatus 20 is detected.

Since the built-in diagnostic program understands all the states in software, when the bus is completely off, the bus state cannot be known. When the connection of the external diagnosis unit 20 is detected, the built-in diagnostic program disables the request () 118 implementing the write function. This is because the software is bus-offed so that the write function is no longer performed.

Read_thread () 114 of the diagnostic daemon 111 is the data from the high-speed CAN line 40a when a diagnostic request is executed by the request () 118, when the connection of the external diagnostic device 20 is not detected It reads and monitors whether the diagnostic failure of ECU 30 occurs.

In the present invention, the diagnostic daemon (DTC: Diagnosis Trouble Code) detected by embedding the DTC analysis DB (116) in the diagnostic daemon (111) to analyze only the DTC message of a specific state The upper application program 121 is transmitted to an external center diagnostic server to be implemented for use in a service.

The DTC in the specific state is a case where the DTC currently occurs and the case where the warning light is turned on.

As such, by embedding the DTC analysis DB 116 in the diagnostic daemon 111, only the DTC in a specific state is used for the service, thereby reducing the amount of load and transmission data generated by analyzing all the DTCs in the center diagnosis server. Can reduce the cost.

4 is a flowchart of a collision avoidance method for diagnosing a vehicle information terminal according to the present invention. The left side shows a data read loop S419 and the right side shows a message processing loop S429.

First, the CAN driver 112 is initialized as the vehicle information terminal 10 is booted after receiving the IGN-On signal (S402), and the Read_thread () 114 and the Msg_thread () 117 are turned on (S404).

Thereafter, as the data read loop S419, the read_thread () 111 first reads data from the high speed CAN line 40a through the CAN driver 112 (S410), and analyzes the read data (S411). It is detected whether the external diagnostic device 20 is connected (S412).

Here, the read_thread () 114 is an external diagnostic device when the read data is a diagnostic request data frame, and when the diagnostic request is not made in the request (118) but is a response response data frame. 20) is detected as connected.

When the external diagnostic device 20 is connected, the external diagnostic device 20 connection information and the diagnostic request disable message are transmitted to the Msg_thread () 117 (S414).

The disable prevents or prevents certain things from happening and controls system functions by inhibiting or inhibiting a specific operation regardless of a failure or malfunction of the vehicle information terminal 10.

When the external diagnostic device 20 is not connected, it is checked whether the DTC has occurred in the ECU 30 (S413). When the DTC occurs, the DTC data is analyzed and stored in the DTC analysis DB 116 (S415). The vehicle information, that is, what failure occurred in which ECU is transmitted to the center diagnosis server by using a telematics or a wireless communication device (S416).

At this time, in the present invention, the currently generated DTC and the warning lamp lighting DTC are stored in the DTC analysis DB 116, and only the DTC is transmitted to the center diagnosis server.

If the DTC does not occur, it indicates that there is no failure by pop-up to the vehicle information terminal 10 (S417).

On the other hand, in the message processing loop (S429), the Msg_thread () 117 receives the external message of the upper application (121) (S420), the external diagnostic device 20 connection information sent from Read_thread () 114 and The diagnostic request disable message is analyzed together with the disabled message (S421), and it is determined whether the diagnostic request disable message is used (S422).

In the case of the diagnosis request disable message, the diagnosis request for the ECU 30 is prohibited, and therefore, the operation returns to step S421. When the diagnosis request disable message is not included, it is determined whether the diagnosis request message is the diagnosis request message (S423).

In the case of the diagnosis request message, Request () 118 sets the diagnosis request message according to the CAN frame in combination with the target ECU 30 ID and the diagnostic service ID, and the target ECU 30 through the CAN driver 112. Request a diagnosis (S424).

If it is not the diagnostic request message, the corresponding message command is executed (S425), and the above steps are repeatedly performed until the system is turned off (S430).

As described above, it is possible to prevent a collision with the external diagnostic apparatus 20 that may occur when the vehicle diagnostic service, which is one of the services of the vehicle information terminal 10 mounted in the vehicle, is implemented in software.

In addition, since the data charge may be transmitted by using a wireless communication device, the data charge that may occur may be reduced by selecting and transmitting only necessary data internally with the DTC analysis DB 116.

As described above, according to the present invention, by detecting the connection of the external terminal in software, and thus do not perform the vehicle diagnostic in the vehicle information terminal, the vehicle information terminal and the external diagnostic device can be generated in the same functional aspect. Problems (for example, malfunction due to using the same ID, data conflict, etc.) can be solved.

Therefore, by adding such software judgment logic, it is possible to determine whether the external diagnosis device is connected in real time without adding additional hardware, and since it is developed as software logic, it is highly compatible and reusable, and it is easily applied to future intelligent vehicle information terminals. This can be done.

Claims (6)

ECU which is mounted on a vehicle and connected to each other via a communication line and is provided with a vehicle information terminal and a vehicle information terminal which is built in the vehicle and performs a vehicle diagnosis service of the ECU by using a diagnostic communication protocol. A vehicle diagnostic system comprising an external terminal for performing a vehicle diagnostic service of an ECU by using the same protocol as the diagnostic communication protocol of the present invention; The vehicle information terminal is provided with a diagnostic daemon for performing a vehicle diagnostic service by reading and writing data from a communication line through a communication line driver. The diagnostic daemon is divided into Read_thread () having only a read function and Request () having only a write function, and the Read_thread () always reads data from a communication line through a communication line driver and detects whether an external diagnostic device is connected. Request () is a collision prevention system of the diagnostic terminal period during the vehicle diagnostics, characterized in that for setting the diagnostic request message of the upper application in accordance with the communication line frame and the diagnostic request to the target ECU through the communication line driver. The method of claim 1, The read_thread () detects that the external diagnostic device is connected when the read data is a diagnostic request data frame and when the diagnostic request is not made in the request () but is a response response data frame. Anti-collision system of the diagnostic terminal period during vehicle diagnosis. The method of claim 1, The diagnostic daemon detects a diagnostic failure code (DTC) with the read data and analyzes the status of the DTC. Among them, only the DTC of a specific state is stored in the diagnostic analysis DB built in the diagnostic daemon and transmitted to the center diagnostic server. Collision prevention system of the diagnostic terminal period during vehicle diagnosis, characterized in that the. The method of claim 3, wherein The specific state of the DTC is a collision prevention system of the diagnostic terminal period when the vehicle diagnosis, characterized in that the DTC and the warning lamp lighting DTC currently generated. The method of claim 1, When the connection of the external diagnostic device is detected, the collision prevention system of the diagnostic terminal period during the vehicle diagnostics, characterized in that only the request () of the write function is inactivated so as to be BUS-Off by software. Reading data from a communication line and analyzing the data to detect whether an external diagnostic device is connected; transmitting external diagnostic device connection information and a diagnostic request disable message when the external diagnostic device is connected; If DTC is not connected, monitor whether DTC occurs in the target ECU, and when DTC occurs, analyzing the generated DTC data and storing only the DTC in a specific state, and transmitting the DTC in the specific state to the center diagnosis server. A data read loop; Analyzing the external diagnostic device connection information and the diagnostic request disable message sent from the message and the data read loop of the center diagnostic server to determine whether the diagnostic request is a disable message, and in the case of the diagnostic request disable message If it is not a diagnostic request disable message, determining whether it is a diagnostic request message, requesting a diagnosis to a target ECU in the case of a diagnostic request message, and executing a corresponding message command if the diagnostic request message is not. A message processing loop comprising a step; Collision prevention method of the diagnostic terminal period when the vehicle diagnostics, including.

Images