KR102246322B1 - Diagnostic system and method for vehicle - Google Patents

Abstract

The present invention relates to a vehicle diagnostic system and method, the system comprising: a communication unit for communicating with an external diagnostic device; When programs for operating the vehicle are installed, the diagnostic control unit performs an operation for diagnosing the programs through communication with the diagnostic device; And a diagnosis and comparison unit that determines whether or not to set security for the programs when diagnosis of the programs is completed. Accordingly, it is possible to improve productivity by reducing the time required to release security when diagnosing each program.

Description

Vehicle diagnostic system and method {DIAGNOSTIC SYSTEM AND METHOD FOR VEHICLE}

The present invention relates to a vehicle diagnosis system and method, and more particularly, after initially installing programs for operation of a vehicle, diagnosing each program in a state in which security is not set, and setting security when the diagnosis is completed. By doing so, it relates to a vehicle diagnosis system and method for improving productivity by reducing the time required to release security when diagnosing each program.

An ECU (Electronic Control Unit) is a control device having a function of controlling and managing major assemblies of a vehicle, and a number of ECUs are installed in the vehicle according to the assembly to control each assembly.

Programs for controlling each assembly are installed in each of these ECUs. When programs are initially installed in the ECU, a diagnostic process using a diagnostic device is performed to test whether the programs work properly. At this time, among the programs, programs that have information requiring security are already set up for security. Accordingly, in order to diagnose a program for which security is set in the diagnostic device, the security must first be released using a security algorithm.

In order to pass the security algorithm, the diagnostic device transmits a signal requesting information for security release to the ECU. The ECU provides first security information for the request signal to a diagnostic device, and the diagnostic device generates second security information using the first security information and transmits it to the ECU. The ECU compares the second security information provided from the diagnostic device with the second security information possessed by the ECU and, if they match, releases the security.

Since it takes several seconds to tens of seconds to perform the unlocking process of such a security algorithm, if the security algorithm is performed for several programs, the overall time required for the diagnosis process is lengthened. In addition, when the security information of the diagnostic device and the security information of the ECU are inconsistent during the security algorithm release process, the security release process fails, and if the number of failures exceeds a preset number, a predetermined time must be waited. In addition, since the security algorithm is set and delivered by each manufacturer, if the security algorithm cannot be released, it is difficult to solve it in the process line, so you must ask the manufacturer for help. Therefore, the entire production process is lengthened by the wait due to the release and failure of the security algorithm, which leads to a decrease in productivity, which leads to an increase in cost.

The present invention diagnoses each program in a state in which security is not set after initial installation of programs for operation of a vehicle, and sets security when the diagnosis is completed, in order to release security when diagnosing each program. A vehicle diagnosis system and method are proposed that reduce the time required to improve productivity.

The object is a communication unit that communicates with an external diagnostic device; When programs for operation of the vehicle are installed, the diagnosis control unit performs an operation for diagnosis of the programs through communication with the diagnosis device; And a diagnosis comparison unit that determines whether or not to set security for the programs when diagnosis of the programs is completed.

The object is to install programs for operation of the vehicle; A diagnostic step of performing an operation for diagnosing the programs; And a security decision step of determining whether or not to set security for the programs when the diagnosis of the programs is completed.

In the present invention, after installation of initial programs, a diagnostic process for diagnosing the operation of each program is performed in a state in which security is not set, and security is set when the diagnostic process is performed according to a preset pattern. Accordingly, since there is no security program during the diagnosis process, it does not take a separate time for security release, so the production process including the diagnosis process can be quickly performed, and cost increase can be prevented. have.

1 is a block diagram of a vehicle diagnosis system according to the present invention;
FIG. 2 is a block diagram showing a configuration for comparing an implementation diagnosis pattern and a reference diagnosis pattern in the vehicle diagnosis system of FIG. 1;
FIG. 3 is a flowchart illustrating a process of diagnosing a vehicle and setting security at the initial stage of program installation in the vehicle diagnosis system of FIG. 1.

Hereinafter, some embodiments of the present invention will be described in detail through exemplary drawings. In adding reference numerals to elements of each drawing, it should be noted that the same elements are assigned the same numerals as possible, even if they are indicated on different drawings. In addition, in describing the present invention, when it is determined that a detailed description of a related known configuration or function may obscure the subject matter of the present invention, a detailed description thereof will be omitted.

In addition, in describing the constituent elements of the present invention, terms such as first, second, A, B, (a) and (b) may be used. These terms are for distinguishing the constituent element from other constituent elements, and the nature, order, or order of the constituent element is not limited by the term. When a component is described as being "connected", "coupled" or "connected" to another component, the component may be directly connected or connected to that other component, but another component between each component It will be understood that elements may be “connected”, “coupled” or “connected”.

1 is a block diagram of a vehicle diagnosis system according to the present invention.

In the vehicle diagnosis system 1 according to the present invention, after installing programs for the operation of the vehicle, it diagnoses whether the programs normally operate in a state in which security is not set to generate an execution diagnosis pattern, and the execution diagnosis pattern is set in advance. Determine whether or not to set security according to whether or not it matches the standard diagnosis pattern.

The vehicle diagnosis system 1 may include a diagnosis device 50 and an ECU 10 of a vehicle.

The diagnostic device 50 is an equipment used in the final diagnosis process in the production process of a vehicle or a single product, and checks whether programs installed in the ECU 10 operate normally by communicating with the ECU 10 using a vehicle diagnosis protocol.

The ECU 10 of the vehicle is stored in the communication unit 15 that communicates with the external diagnosis unit 50, the temporary storage unit 20 temporarily storing the diagnosis information generated by the diagnosis unit 50, and the temporary storage unit 20. A diagnosis result storage unit 25 storing diagnosis information, a reference pattern storage unit 30 storing a reference diagnosis pattern, a diagnosis control unit 35 performing a diagnosis operation according to a request from the diagnosis device 50, a reference diagnosis pattern, and A diagnosis comparison unit 40 that compares diagnosis information performed by the diagnosis device 50 to determine whether to set security, and a security control unit 45 that sets and releases security.

The communication unit 15 may communicate with an external diagnostic device 50 using one of vehicle communication protocols CAN (Controller Area Network), LIN (Local Interconnect Network), and Flexray, and the ECU 10 and the diagnostic device 50 ) To support the exchange of information.

The temporary storage unit 20 is formed of a volatile memory, and temporarily stores execution diagnosis patterns and diagnosis results generated by diagnosing programs installed in the vehicle by the diagnosis device 50.

Each program installed in the vehicle is diagnosed according to a unique diagnosis pattern to check whether the program is operating normally, and the diagnosis device 50 diagnoses each program according to its own diagnosis pattern to generate an implementation diagnosis pattern and diagnosis result. . Since each program has a different function, each program has a respective implementation diagnosis pattern. Accordingly, when N programs are installed in the vehicle, N implementation diagnosis patterns may be generated when each program is diagnosed by the diagnostic device 50.

Accordingly, when one diagnosis process is performed in the temporary storage unit 20, N implementation diagnosis patterns are sequentially stored. The N execution diagnosis patterns and past results stored in the temporary storage unit 20 are transferred to and stored in the diagnosis result storage unit 25.

The diagnosis result storage unit 25 is formed of a nonvolatile memory, and may receive and store N execution diagnosis patterns and diagnosis results temporarily stored in the temporary storage unit 20.

The diagnosis result storage unit 25 may receive N execution diagnosis patterns for a diagnosis process completed with one routine, and may collect and store the N execution diagnosis patterns as a single file. That is, when the diagnosis process is performed several times, the diagnosis result storage unit 25 stores a plurality of files in which N implementation diagnosis patterns generated in each diagnosis process are grouped into one file. At this time, since the diagnosis process may be performed several times on the same day or on different days, it is preferable to store the diagnosis process separately according to the date and the number of trials. In this way, the implementation diagnosis pattern and the diagnosis result stored in the diagnosis result storage unit 25 form a diagnosis history of the vehicle, and can be retrieved at any time to check the diagnosis history of the vehicle.

The reference pattern storage unit 30 is formed of a nonvolatile memory, and stores a plurality of reference diagnosis patterns preset for each program during the diagnosis process. Each reference diagnosis pattern includes contents for diagnosing each program installed in the vehicle, and one reference diagnosis pattern is generated for one program. Each reference diagnosis pattern may be compared with an implementation diagnosis pattern generated by the diagnosis device 50 to serve as a criterion for determining whether diagnosis for each program is properly performed when the diagnosis process is performed. Each reference diagnosis pattern may be changed by a designer, and a diagnosis pattern performed by the diagnosis device 50 must also be changed according to the changed reference diagnosis pattern.

The diagnosis control unit 35 may control the operation of each program according to a diagnosis request signal from the diagnosis unit 50 and transmit the controlled result to the diagnosis unit 50. In this case, when the diagnostic device 50 receives control results performed in each of the programs from the diagnostic control unit 35, it is possible to determine whether each program is operating properly.

For example, if the diagnosis control unit 35 requests that the diagnosis unit 50 control the operation of the motor, the diagnosis control unit 35 controls the operation of the motor and transmits the control result to the diagnosis unit 50. At this time, the diagnosis device 50 requests the diagnosis control unit 35 to control the operation of the motor using the implementation diagnosis pattern. The diagnostic device 50 receives the control result of the motor performed by the diagnostic control unit 35 according to the diagnostic pattern implemented and determines whether the motor is operating properly. As a result of the determination, if the motor is properly controlled, the diagnosis device 50 transmits a diagnosis request signal for the next object to the diagnosis control unit 35. On the other hand, if the motor is not properly controlled, the diagnostic device 50 displays a message requesting processing of the motor because the motor has not been properly operated.

As shown in FIG. 2, the diagnosis and comparison unit 40 retrieves each implementation diagnosis pattern stored in the temporary storage unit 20 and each reference diagnosis pattern stored in the reference pattern storage unit 30, and compares them with each other. Depending on the result, it is possible to decide whether to set security or not.

The diagnosis and comparison unit 40 determines to set security when each implementation diagnosis pattern and each reference diagnosis pattern match, and when each implementation diagnosis pattern and each reference diagnosis pattern do not match, the diagnosis and comparison unit 40 transmits a command signal to the diagnosis device 50. Can be communicated and requested to re-do the diagnosis.

When the diagnosis and comparison unit 40 starts diagnosis in the diagnosis unit 50, diagnosis of one program is completed, one execution diagnosis pattern is generated, and the execution diagnosis pattern is stored in the temporary storage unit 20, a temporary The implementation diagnosis pattern stored in the storage unit 20 and the reference diagnosis pattern for the corresponding program are retrieved from the reference pattern storage unit 30. Then, the diagnosis comparison unit 40 may compare the implementation diagnosis pattern and the reference diagnosis pattern to determine whether the two are identical.

When the diagnosis and comparison unit 40 determines that all the implementation diagnosis patterns and all the reference diagnosis patterns match, the diagnosis and comparison unit 40 may provide a signal to the security control unit 45 to set security.

The security control unit 45 may set security only for programs that require security among programs installed in the vehicle, or may set security for all programs.

The security control unit 45 may release the security through a preset security release process when performing a diagnostic service on a program for which security is set later.

When the diagnostic device 50 requests a random seed from the security control unit 45, the security control unit 45 checks whether the request is legitimate by using the information included in the request, and generates a seed if it is legitimate. Then, it is transmitted to the diagnostic device 50. The diagnostic device 50 and the security control unit 45 respectively calculate a key value using the generated seed, and the diagnostic device 50 transmits the key value to the security control unit 45. The security control unit 45 releases the security when the key value generated by the diagnostic device 50 and the key value generated by the security control unit 45 are the same.

A process of initially diagnosing a vehicle and setting security in the vehicle diagnosis system 1 having such a configuration will be described below with reference to FIG. 3.

Initially, if programs for controlling the operation of motors and sensors are installed in the ECU 10 of the vehicle (S300), the diagnostic device 50 is connected to the ECU 10 in order to perform a diagnostic process for the programs to operate properly. do.

When the diagnostic device 50 is connected to the ECU 10 and the diagnostic process starts (S310), the diagnostic device 50 transmits a signal requesting the operation of each program to the ECU 10, and the diagnostic control unit of the ECU 10 In (35), each program is operated as requested by the diagnostic device 50, and then the execution result is transmitted to the diagnostic device 50. Then, the diagnostic device 50 may determine whether the program is operating properly using the execution result. The ECU 10 stores operations requested for diagnosis of a program from the diagnosis device 50 in the temporary storage unit 20 as information on an execution diagnosis pattern (S320).

If the program does not operate properly (S330), the diagnostic device 50 displays a message indicating that the program needs to be modified on the screen of the diagnostic device 50 (S335), and transmits the message to the ECU 10 to obtain a diagnosis result. It is to be stored in the storage unit 25. In addition, the diagnostic device 50 stops the diagnostic process until the corresponding program is modified.

When the program is properly operated and the execution diagnosis pattern and the diagnosis result are stored in the temporary storage unit 20, the diagnosis comparison unit 40 includes the execution diagnosis pattern and reference pattern storage unit 30 for the program stored in the temporary storage unit 20. The reference diagnostic pattern stored in the is compared (S340). If the implementation diagnosis pattern and the reference diagnosis pattern match, the diagnosis and comparison unit 40 transmits a message to the security control unit 45 to set security. The security control unit 45 sets security through a preset security process (S350).

On the other hand, if the implementation diagnosis pattern and the reference diagnosis pattern do not match, the diagnosis comparison unit 40 transmits a message indicating that the diagnosis order is wrong to the diagnosis unit 50 so that the diagnosis process is performed again (S345).

Then, the diagnosis comparison unit 40 checks whether the diagnosis for all programs is completed (S360). When the diagnosis for all programs is completed, the diagnosis process is completed.

If security is set for each program after completion of the diagnosis process, if the diagnosis process is required later, the process of canceling the security must be preceded.

As described above, in the present invention, after installation of the initial programs, the diagnostic process of diagnosing the operation of each program is performed by connecting the diagnostic device 50 in a state in which security is not set, and then the diagnostic process in the diagnostic device 50 is performed. If it is performed according to a preset pattern, security is set. Accordingly, since there is no security program during the diagnosis process, it does not take a separate time for canceling the security program, so the production process including the diagnosis process can be quickly performed, and the cost increase can be prevented. can do.

The standard contents or standard documents mentioned in the above-described embodiments are omitted to simplify the description of the specification and constitute a part of the present specification. Accordingly, it should be construed as falling within the scope of the present invention to add the contents of the standard contents and some of the standard documents to the present specification or to describe in the claims.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains will be able to make various modifications and variations without departing from the essential characteristics of the present invention. Accordingly, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain the technical idea, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

1: vehicle diagnostic system 10: ECU
15: communication unit 20: temporary storage unit
25: diagnosis result storage unit 30: reference pattern storage unit
35: control unit 40: diagnosis and comparison unit
45: security control unit 50: diagnostic device

Claims (10)

A communication unit that communicates with an external diagnostic device;
A diagnostic control unit configured to perform an operation for diagnosing the programs through communication with the diagnostic device in a state in which security is not set when programs for operating the vehicle are installed; And
When the diagnosis of the programs is completed, a diagnosis comparison unit that determines whether or not to set security for the programs; Including,
The diagnostic comparison unit is a vehicle diagnostic system, characterized in that for comparing the execution diagnostic pattern, which is generated when each program is diagnosed and includes the diagnostic contents of each program, and a reference diagnostic pattern set in advance for each program. delete ◈ Claim 3 was abandoned upon payment of the set registration fee.◈ The method of claim 1,
And the diagnostic comparison unit determines security for each program when the implementation diagnosis pattern and the reference diagnosis pattern match for each program. ◈ Claim 4 was abandoned upon payment of the set registration fee. The method of claim 1,
The diagnosis comparing unit, when the implementation diagnosis pattern and the reference diagnosis pattern do not match, requesting a re-diagnosis by the diagnosis system. The method of claim 1,
And a temporary storage unit for temporarily storing an implementation diagnosis pattern for each program, and a reference pattern storage unit in which the reference diagnosis pattern is stored. The method of claim 1,
And a security control unit configured to set the security of each program according to a decision from the diagnosis and comparison unit. Installing programs for operation of the vehicle;
A diagnosis step of performing an operation for diagnosing the programs in a state in which security is not set; And
When the diagnosis of the programs is completed, a security decision step of determining whether to set security for the programs; Including,
The security determination step includes comparing an implementation diagnosis pattern that is generated at the time of diagnosis of each program and includes diagnosis contents of each program and a reference diagnosis pattern set in advance for each program. Way. delete The method of claim 7,
And the step of determining security includes determining security for the programs when the implementation diagnosis pattern and the reference diagnosis pattern are identical for each of the programs. The method of claim 7,
And the step of determining security comprises requesting a re-diagnosis when the implementation diagnosis pattern and the reference diagnosis pattern do not match.

Images