WO2021143387A1

WO2021143387A1 - Adas system processing method and automobile diagnostic device

Info

Publication number: WO2021143387A1
Application number: PCT/CN2020/133784
Authority: WO
Inventors: 黄允彦
Original assignee: 深圳市道通科技股份有限公司
Priority date: 2020-01-14
Filing date: 2020-12-04
Publication date: 2021-07-22
Also published as: CN111190413A

Abstract

Provided are an ADAS system processing method and automobile diagnostic device. The method comprises: according to vehicle information of a vehicle, obtaining ADAS system information of the vehicle, the ADAS system information comprising a subsystem contained by the ADAS system (S11); displaying the information of the subsystem contained by the ADAS system, the information of the subsystem comprising the identification of the subsystem and the status of the subsystem (S12); receiving a user instruction, and performing one of fault identification, fault handling, and calibration on the subsystem indicated by the user instruction (S13). The provided ADAS system processing method and automobile diagnostic device can detect ADAS system faults more conveniently, and improve the efficiency of fault detection.

Description

A processing method of ADAS system and automobile diagnostic equipment

This application claims the priority of the Chinese patent application filed with the Chinese Patent Office on January 14, 2020, the application number is 202010037053.6, and the application name is "A processing method of ADAS system and automobile diagnostic equipment", the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of automobile technology, and in particular to an ADAS system processing method and automobile diagnostic equipment.

Background technique

With the development of the automotive industry and the advancement of technology, people have higher requirements for the safety and comfort of car driving. Unmanned driving is an important direction for the development of current automotive technology. Advanced Driver Assistance Systems (Advanced Driver Assistance Systems, ADAS) is the early stage of the development of unmanned driving technology, and it is also a necessary stage. As more and more attention is paid to automobile safety, more and more vehicles are equipped with ADAS systems. In the near future, ADAS systems will become standard configurations on all automobiles. When the ADAS system fails or is abnormal, it is necessary Repair the fault of the ADAS system before the ADAS system can be used normally and safely.

The current method of detecting ADAS system failures is generally to simply enter a system to perform the calibration function. After the calibration function is completed, enter the diagnosis menu to perform the fault code query of the system. If there is still a problem, return to the calibration function menu to continue the calibration function. Repeat the process to complete the fault detection of the system.

In the process of implementing the present invention, the inventor found that the related technology has at least the following problems: when detecting ADAS system faults, the operation is cumbersome and inefficient, and users cannot easily diagnose ADAS system faults.

Summary of the invention

The technical problem to be solved by the present invention is to provide an ADAS system processing method and automobile diagnostic equipment, and solve the technical problems of complicated operation and low efficiency in the detection of ADAS system faults in related technologies.

In one aspect of the embodiments of the present invention, there is provided a processing method of an ADAS system, which is applied to an automobile diagnostic equipment, and the automobile diagnostic equipment is connected to an ADAS system in a vehicle, and the method includes:

Acquiring ADAS system information of the vehicle according to the vehicle information of the vehicle, where the ADAS system information includes the subsystems included in the ADAS system;

Display information of the subsystems included in the ADAS system, the information of the subsystems including the identifier of the subsystem and the state of the subsystem;

Receive a user instruction, and perform one of fault identification, fault processing or calibration on the subsystem indicated by the user instruction.

Optionally, the status of the subsystem includes at least one of the following:

Whether the failure of the sub-system has been identified, whether the failure of the sub-system has been cleared, whether the sub-system can be calibrated, and whether the sub-system has been calibrated.

Optionally, the displaying the information of the subsystems included in the ADAS system includes: displaying the information of all or part of the subsystems included in the ADAS system.

Optionally, the receiving a user instruction and performing a fault identification operation on the subsystem indicated by the user instruction includes: after receiving the user's fault code acquisition instruction, sending an acquiring fault code to the subsystem indicated by the user instruction Request; determine whether the fault code of the subsystem is obtained from the subsystem; if so, display the fault code.

Optionally, the method further includes: displaying the meaning of the fault corresponding to the fault code.

Optionally, the method further includes: determining whether the equipment in the subsystem needs to be calibrated according to the fault code; if so, prompting the user to calibrate the equipment in the subsystem.

Optionally, the receiving a user instruction and performing a fault handling operation on the subsystem indicated by the user instruction includes: after receiving the user's fault handling instruction, determining the fault corresponding to the fault code of the subsystem indicated by the user instruction Processing plan; display the fault processing plan to guide the user to perform maintenance operations on the subsystem.

Optionally, the method further includes: displaying the fault handling solution on a page displaying the information of the subsystems included in the ADAS system; or jumping to another page to display the fault handling solution.

Optionally, the method further includes: receiving a fault code clearing instruction from the user, and determining whether the fault code in the subsystem indicated by the fault code clearing instruction has been cleared; if so, updating the fault code of the subsystem state.

Optionally, the receiving a user instruction and performing a calibration operation on the subsystem indicated by the user instruction includes: jumping to a calibration guide operation page of the subsystem.

In another aspect of the embodiments of the present invention, there is provided an automobile diagnostic equipment, the automobile diagnostic equipment includes: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores the The instructions executed by the at least one processor are executed by the at least one processor, so that the at least one processor can execute the processing method of the ADAS system as described above.

Different from the prior art, the processing method of the ADAS system and the automobile diagnostic equipment provided by the embodiments of the present invention obtain the ADAS system information of the vehicle through the vehicle information. The ADAS system information includes the subsystems included in the ADAS system, and displays the sub-systems. With the identification of the system and the state of the subsystem, when a user instruction is received, one operation of fault identification, fault processing or calibration is performed on the subsystem indicated by the user instruction. The processing method of the ADAS system and the automobile diagnostic equipment provided by the embodiments of the present invention integrate the ADAS system of the entire vehicle so that the system information can be reflected in one menu, so that the ADAS system failure can be detected more conveniently, and the failure detection efficiency is improved. .

Description of the drawings

One or more embodiments are exemplified by the pictures in the corresponding drawings. These exemplified descriptions do not constitute a limitation on the embodiments. The elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the attached drawings do not constitute a scale limitation.

FIG. 1 is a flowchart of a processing method of an ADAS system provided by an embodiment of the present invention;

2 is a flowchart of a method for performing fault identification operations on the subsystem indicated by the user instruction according to an embodiment of the present invention;

3 is a flowchart of a method for performing fault handling operations on the subsystem indicated by the user instruction according to an embodiment of the present invention;

4a to 4i are schematic diagrams of software interfaces for realizing the processing method of the ADAS system provided by the embodiments of the present invention;

FIG. 5 is a schematic structural diagram of a processing device of an ADAS system provided by an embodiment of the present invention;

Fig. 6 is a schematic structural diagram of an automobile diagnostic equipment provided by an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present invention clearer, the following further describes the present invention in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, but not used to limit the present invention.

It should be noted that if there is no conflict, the various features in the embodiments of the present invention can be combined with each other, and all fall within the protection scope of the present invention. In addition, although the functional modules are divided in the schematic diagram of the device, and the logical sequence is shown in the flowchart, in some cases, the module division in the schematic diagram of the device may be different from the module division in the schematic diagram, or the sequence in the flowchart may be executed. Steps shown or described.

The embodiment of the present invention provides a processing method and device of an ADAS system and automobile diagnostic equipment. This method can obtain the ADAS system information of the vehicle according to the vehicle information of the vehicle, and integrate the ADAS system of the entire vehicle, so that the ADAS system information of the entire vehicle can be reflected in a menu.

Through this method, maintenance personnel can clearly understand the overall overview of the entire vehicle's ADAS system in one operation interface, perform corresponding functions according to the software prompt information, solve the ADAS system failure problem, and finally output a detailed maintenance report.

Specifically, please refer to FIG. 1, which is a flowchart of a processing method of an ADAS system according to an embodiment of the present invention. The method can be applied to automobile diagnostic equipment, which is connected to the ADAS system in the vehicle, and the method includes:

S11. Obtain ADAS system information of the vehicle according to the vehicle information of the vehicle, where the ADAS system information includes the subsystems included in the ADAS system.

Among them, the corresponding relationship between the vehicle and the ADAS system can be preset in the vehicle diagnostic equipment, that is, vehicle information, such as vehicle model, vehicle model, production year, etc., can be obtained, and the vehicle's ADAS system can be correspondingly learned which subsystems are included in the ADAS system .

The ADAS system information of the vehicle is composed of all the subsystems included in the ADAS system of the vehicle. For example, the subsystems included in the ADAS system include an adaptive cruise system, a lane departure warning system, a lane keeping system, a lane change assist system, a blind spot monitoring system, a night vision system, a panoramic 3600 surround system, a rear-view camera system, and a large Light system, head-up display system, pre-collision system, automatic braking system, pedestrian protection system, traffic indication recognition system, etc. Vehicles with different configurations have different numbers and types of ADAS systems, and the ways to calibrate ADAS systems may be different. However, there will also be associations between different ADAS systems, and different systems can pass the same ADAS The sensor performs the corresponding work. For example, the lane keeping system, pedestrian protection system, and traffic indication recognition system can all be realized by the front camera; the adaptive cruise system and the pre-collision system are all realized by the adaptive cruise radar.

Wherein, the vehicle information may specifically be the VIN code of the vehicle. According to the vehicle information of the vehicle, obtaining the ADAS system information of the vehicle includes: obtaining the model information of the vehicle according to the VIN code of the vehicle; query The database is used to obtain ADAS system information matching the vehicle type information.

Wherein, the VIN code of the vehicle refers to the vehicle identification code, which is composed of seventeen English characters and numbers. According to the VIN code, other data such as the manufacturer, engine, and chassis serial number of the car can be identified. In this embodiment, after the user inputs the VIN code of the vehicle, the automobile diagnostic equipment that executes the method reads the VIN code, and obtains vehicle information based on the VIN code, such as vehicle type, vehicle year, and vehicle model. Model, engine model, etc. By analyzing the vehicle type information, a preset database is searched to obtain ADAS system information matching the vehicle type information.

Wherein, the ADAS system information matching the vehicle model information includes the corresponding relationship between the vehicle model information and the ADAS system, and which ADAS subsystems are specifically included in the current vehicle model can be obtained through the corresponding relationship. The ADAS system information of the current vehicle model also includes the fault solution of the ADAS system corresponding to the vehicle model information, and the fault analysis can be performed on the malfunctioning ADAS system and the fault can be resolved through the fault solution. The ADAS system information of the current vehicle model further includes historical diagnostic information corresponding to the vehicle model information, and the historical diagnostic information includes historical fault information of the ADAS system and historical fault solutions, and so on.

It should be noted that in addition to obtaining the ADAS system information of the automobile according to the VIN code of the automobile, other methods may also be used to obtain the ADAS system information of the automobile.

S12. Display the information of the subsystems included in the ADAS system, where the information of the subsystem includes the identifier of the subsystem and the state of the subsystem.

Wherein, the information of the subsystems included in the ADAS system can be displayed on the display interface of the automobile diagnostic equipment. The information of the subsystem may be preset in the automobile diagnostic equipment, or obtained from the vehicle, or may be preset in the automobile diagnostic equipment and obtained from the vehicle. acquired. The identifier of the subsystem refers to information used to identify the subsystem, and the subsystem can be uniquely identified through the identifier of the subsystem. The status of the subsystem includes whether the failure of the subsystem has been identified, whether the failure of the subsystem has been cleared, whether the subsystem can be calibrated, whether the subsystem has been calibrated, and so on. Wherein, when the status of the subsystem corresponds to whether the fault of the subsystem has been identified, it can display "unscanned" (which is used to indicate an unidentified fault) in the fault column, or display "normal" or " Fault” (it is used to indicate that a fault has been identified). When the status of the subsystem corresponds to whether the fault of the subsystem has been cleared, "normal" (which is used to indicate that the fault of the subsystem has been cleared) or "fault" can be displayed in the fault column. It is used to indicate that the fault of the subsystem has not been cleared). When the status of the subsystem corresponds to whether the subsystem can be calibrated, the “calibration” identification information (which is used to indicate that the subsystem can be calibrated) can be displayed in the calibration column, or “calibration” is not displayed. "Identification information (which is used to indicate that the subsystem cannot be calibrated), and the "calibration" identification information can specifically be represented by one or more of pictures, texts, animations, etc. When the status of the subsystem corresponds to whether the subsystem has been calibrated, it can be determined whether the calibration has been completed according to the display status of the fault column, for example, the corresponding to the fault column changes from "fault" to "normal", It means that the calibration of the subsystem has been completed.

Wherein, when displaying the information of the subsystems included in the ADAS system, the information of all or part of the subsystems included in the ADAS system may be displayed. For example, the identifier of each subsystem can correspond to the status of all or part of the subsystem.

The information of the subsystems can be displayed according to a certain rule, for example, the information of the subsystems of the same category is displayed together, or the information of the subsystems that have an association relationship are displayed together. An association relationship refers to a connection relationship or a functional association relationship.

Wherein, when displaying the information of the subsystems included in the ADAS system, the information of the subsystems included in the ADAS system may be displayed in at least one of text, graphics, icons, animation, video, and audio.

It should be noted that the above step S11 and step S12 can be performed alternately. For example, when at least two subsystems included in the ADAS system are obtained, the information of the subsystems included in the ADAS system can be displayed.

When at least two subsystems included in the ADAS system are acquired, the information of at least two subsystems can be displayed at the same time, or the information of each of the at least two subsystems can be displayed successively, that is, the information of only one subsystem is displayed on a display page. Information, or display information of at least two subsystems in a display interface.

S13. Receive a user instruction, and perform one of fault identification, fault processing, or calibration on the subsystem indicated by the user instruction.

The user instruction may be a character instruction or a touch instruction input to the car diagnostic device by a user through a keyboard or a sliding screen, or a voice instruction input to the car diagnostic device by voice, or a voice instruction to the car diagnostic device through a camera. Input gesture commands, etc. The subsystem indicated by the user instruction may be all subsystems included in the ADAS system, or may be one or more subsystems included in the ADAS system.

The fault identification refers to whether there is a fault in the subsystem indicated by the scan. The fault handling is to perform maintenance operations such as calibration on the faulty subsystem to remove the fault. The calibration is the process of calibrating the subsystem. When performing a calibration operation, the calibrated subsystem can be a subsystem that has been identified as having a fault, or it can be a normal subsystem.

Wherein, as shown in FIG. 2, the receiving a user instruction and performing a fault identification operation on the subsystem indicated by the user instruction includes:

S201: After receiving the fault code acquisition instruction of the user, send a fault code acquisition request to the subsystem indicated by the user instruction.

S202: Determine whether the fault code of the subsystem is obtained from the subsystem.

If yes, execute the following step S203.

S203. Display the fault code.

In this embodiment, the user instruction is a fault code acquisition instruction, and the fault code acquisition instruction is used to acquire a fault code. The fault code refers to a code identifier used to identify the meaning of a subsystem fault, which can be translated into identifiable symbols such as numbers and letters. The corresponding relationship between the meaning of the subsystem failure and the failure code can be set in advance. A subsystem can include at least one fault code. When the faults of different subsystems are the same, they can display the same fault code. In some embodiments, it is also possible to preset a corresponding fault code for each subsystem, and different subsystems contain different fault codes. In addition, the fault code can also be associated with the device (such as a sensor, etc.) corresponding to the subsystem, and the fault information of the device, the device identification code (which is used to uniquely identify the device), and the fault code are associated with each other. The fault code can be used to obtain the faulty equipment in the subsystem and the specific fault problem.

Among them, the entire vehicle ADAS system scan can be performed to detect whether all the subsystems of the ADAS are faulty, and display the fault code corresponding to the faulty subsystem. It is also possible to scan only the subsystem indicated by the user instruction, so as to obtain whether the subsystem has a fault, and display the fault code of the faulty subsystem.

If the fault code is not obtained, or the information that the subsystem is normal is obtained, it can be displayed that the subsystem is normal.

In some embodiments, referring also to FIG. 2, the method further includes:

S204. Display the meaning of the fault corresponding to the fault code.

The meaning of the fault can be displayed in various ways. For example, when the mouse arrow operated by the user is placed at the position of the fault code, the meaning of the fault can be displayed in text, or the meaning of the fault can be played by sound. When the arrow moves away from the fault code, it will not be displayed. For another example, the meaning of the fault code is displayed on the page displaying the information of the subsystems included in the ADAS system, or the meaning of the fault code is displayed on another page.

When there are multiple fault codes, the meaning of each fault code can be displayed separately.

In some embodiments, referring also to FIG. 2, the method further includes:

S205: Determine whether the equipment in the subsystem needs to be calibrated according to the fault code.

If calibration is required, the following step S206 is executed.

S206: Prompt the user to calibrate the equipment in the subsystem.

The automobile diagnostic equipment that executes the method can obtain the corresponding fault information according to the fault code, and determine whether the equipment corresponding to the subsystem needs to be calibrated according to the fault information, that is, to determine whether to calibrate the faulty equipment. The fault level can be preset according to the fault information, for example, the first level is a fault that needs to be dealt with urgently, the second level is a fault that can be dealt with later, and the third level is a fault that can be ignored. Different levels correspond to different fault codes, and the corresponding fault level is determined according to the fault code, so as to determine whether the equipment in the subsystem needs to be calibrated. If it is the first level and the second level, it means that the calibration needs to be performed Operation, at this time, the user can be reminded to calibrate the equipment of the subsystem.

Wherein, calibrating the devices in the sub-system includes calibrating all devices in the sub-system or calibrating the devices indicated by the fault code.

Among them, the way of prompting the user to perform calibration includes, but is not limited to: prompting the user to perform calibration by highlighting or with obvious color characteristics; prompting the user to perform calibration by means of sounds and/or indicator lights; etc.

In some embodiments, the user instruction may also be a fault handling instruction. As shown in FIG. 3, the receiving a user instruction and performing a fault handling operation on the subsystem indicated by the user instruction includes:

S301: After receiving the user's fault handling instruction, determine the fault handling plan corresponding to the fault code of the subsystem indicated by the user instruction.

S302. Display the fault handling plan to guide the user to perform maintenance operations on the subsystem.

The fault handling plan may be stored in a preset database, and the database includes fault information of various vehicle models and fault handling plans corresponding to the fault information.

Wherein, when the fault handling solution is displayed, the fault handling solution may be displayed on a page displaying the information of the subsystems included in the ADAS system; or, the fault handling solution may be displayed by jumping to another page.

The fault handling solution may be displayed in at least one of text, graphics, icons, animation, video, and audio.

In some embodiments, after performing maintenance operations on the faulty subsystem, please also refer to FIG. 3, and the method further includes:

S303. Receive a fault code clearing instruction from the user, and determine whether the fault code in the subsystem indicated by the fault code clearing instruction has been cleared.

If yes, execute the following step S304.

S304. Update the state of the subsystem.

After the faulty subsystem is calibrated, the fault code clearing operation can be performed. For the recovered subsystem, the fault code displayed can be automatically cleared according to the user's clear fault code instruction, and the status of the subsystem is indicated as normal. .

In some embodiments, the user instruction may also be a calibration instruction, and the receiving the user instruction and performing the calibration operation on the subsystem indicated by the user instruction includes: jumping to the calibration guide operation page of the subsystem. The calibration guide operation page refers to the page used to guide the user to perform the calibration operation, which includes the calibration tools that need to be prepared, the calibration precautions, the calibration preparation work, the specific process of the calibration process, the verification process of the calibration result, etc.

The content in the calibration guide operation page may be embodied in at least one of text, graphics, icons, animation, video, and audio.

It should be noted that the above step S13 may be applied when the above steps S11 and S12 are executed, or it may be applied after the above steps S11 and S12 are executed.

The following examples illustrate the detailed process of the above steps. It should be noted that the following examples are only used to illustrate the processing method of the ADAS system provided by the embodiment of the present invention, and are not used to limit the method.

For example: please refer to Fig. 4a to Fig. 4i, Fig. 4a to Fig. 4i are schematic diagrams of the software interface for realizing the processing method of the ADAS system. You can use a highly stable Linux system as the software development platform, which supports all automotive communication protocols and most automotive bus standards, such as ISO15765, J1850, J2610, ISO9141, ISO14230, J2740, J1939, J1962, J2610, J1979, J2610, etc. The software has a high degree of integration (supports single and dual-wire CAN, PWM, VPW, SCI, UART, etc.), and can simultaneously support the programming of three-protocol automotive computers, and realize any pin multiplexing function on the same connected device And high stability.

Wherein, as shown in Figures 4a and 4b, the VIN code of the car is first obtained, and the model information of the car is obtained according to the VIN code, or the user is prompted to manually enter the model information. After the model information is determined, the query The database, thereby obtaining the ADAS system information matching the vehicle type information as shown in FIG. 4c.

The interface shown in Figure 4c displays all ADAS subsystems matching the vehicle model information, and displays multiple functional options, including automatic scanning options, control unit options, ADAS calibration options, and vehicle information options. Select the operation to select the corresponding function option, and then display the function interface under the function option. Among them, the ADAS system information that matches (ie corresponds to) the vehicle type information is displayed on the function interface under the ADAS calibration option. Here, the ADAS system information includes the information of the ADAS system including the subsystem, the identifier of the subsystem, and the status of the subsystem. The identifier of the subsystem shown in Fig. 4c includes the number and name of the subsystem, and the sub-system shown in Fig. 4c The status of the system is not scanned, and some subsystems are correspondingly displayed with calibration buttons, indicating that this part of the subsystem can be calibrated. The interface shown in Figure 4c also displays a fault scan button, a clear fault code button and a back button. By selecting the fault scan button, the user can scan the ADAS subsystem to determine whether the ADAS subsystem is faulty and clear the fault. The current gray value of the code button indicates that it cannot be selected. It is used to process the fault after scanning the ADAS subsystem. Backward indicates that the previous interface can be displayed.

As shown in Figure 4d and Figure 4e, it is a schematic diagram of the software interface after the ADAS system is scanned. In Figure 4e, the scanned and unscanned ADAS subsystems can be displayed, and faulty and normal ADAS subsystems can be identified. The ADAS subsystem, where the number of fault codes can be displayed for the faulty ADAS subsystem, for example, the number of fault codes corresponding to "13-vehicle distance control" is "1", and the diagnostic equipment can identify the fault type according to the fault code And the fault content, and then analyze the fault type and fault content, so as to find an overall solution to the fault code.

As shown in Figure 4e and Figure 4f, it is a schematic diagram of the software interface after the ADAS system scan is completed. It displays the overall information of the ADAS system of the entire vehicle, and identifies the faulty ADAS subsystem and the specific ADAS subsystem failure Code and fault meaning, you can judge whether the calibration function needs to be performed according to the fault code and fault meaning. The meaning of the fault can be hidden and displayed, and the meaning of the fault can be expanded or hidden according to the user's expand or hide operation. The meaning of the fault includes a detailed explanation or a short explanation of the fault code. For example, as seen in Figure 4f, ADAS subsystem 6C-Reverse There is one fault code in the camera system, the fault code number is C11007, and the fault meaning is calibration (static). Wherein, when the ADAS subsystem has a calibration function, the ADAS subsystem includes a calibration button, the calibration button is displayed in the menu item corresponding to the ADAS subsystem, and the user can perform corresponding operations on the calibration button For example, by "clicking" the calibration button, the calibration function of the ADAS subsystem corresponding to the calibration button can be executed. The calibration function of the ADAS subsystem refers to performing a calibration operation on the ADAS subsystem so that the ADAS can be used normally. For example, the ADAS subsystem can be calibrated by using a diagnostic instrument and a dedicated calibration tool. It is required to place the special calibration tool in the corresponding position of the car, and use the diagnostic instrument to drive the vehicle ADAS subsystem into the calibration mode to complete the function calibration, so as to ensure that the equipment corresponding to the ADAS subsystem can be used safely and normally. It should be noted that the calibration function is usually performed on the ADAS subsystem corresponding to the fault code that needs to be calibrated. If the fault code is not related to the calibration function, the calibration function may not be required. However, in some embodiments, each ADAS subsystem may have its corresponding calibration button, that is, the calibration function can be performed on all ADAS subsystems of the vehicle, not just when the ADAS subsystem fails. Function. In addition, users can choose the ADAS subsystem that needs to perform the calibration function according to their own wishes.

As shown in Figure 4g and Figure 4h, the faulty ADAS subsystem also includes a guide button, which is displayed in the menu item corresponding to the ADAS subsystem, and each faulty ADAS subsystem corresponds to a guide button The guide button is used to help the user complete the calibration function of the ADAS subsystem according to the preset prompt mode. For example, the positioning of the calibration auxiliary tool can be completed step by step through the graphic prompt of the software. In some embodiments, the display interface further includes a quick code clearing button, such as the "Clear Fault Code" button as shown in Figure 4h. After performing the calibration function operation on the faulty ADAS subsystem, the user can receive the According to the operation of the quick code clearing button, the fault code of the ADAS subsystem of the entire vehicle is cleared according to the operation, that is, the fault code is automatically processed by the diagnostic device to clear the fault.

As shown in Figure 4i, after the calibration function and the fault code guidance function are executed, the diagnosis and maintenance report of the ADAS subsystem of the whole vehicle can be output finally.

It should be noted that FIGS. 4a to 4i are only an example of the processing method of the ADAS system. In addition to showing the flow of the ADAS system processing method through diagrams, other methods such as animation, video, and Audio and other ways to show the processing method of the ADAS system.

The embodiment of the present invention provides a processing method of an ADAS system. The method obtains ADAS system information of a vehicle through vehicle information. The ADAS system information includes the subsystems included in the ADAS system, and displays the identifier of the subsystem and the status of the subsystem. State, when a user instruction is received, one operation of fault identification, fault processing or calibration is performed on the subsystem indicated by the user instruction. The processing method of the ADAS system provided by the embodiment of the present invention, in the first aspect, can accurately provide the current vehicle system information and troubleshooting method, which can greatly improve the maintenance efficiency of the user; in the second aspect, it can make the software prompt integration more High, the maintenance operation guidelines for different ADAS subsystems are more unified and concise, allowing users to more easily master the maintenance methods; third, users can easily grasp the current status of the entire vehicle’s ADAS subsystems and display faults Information and function guidelines can easily complete ADAS maintenance and output maintenance reports.

Please refer to FIG. 5, which is a schematic structural diagram of a processing device of an ADAS system according to an embodiment of the present invention. The device 40 can be applied to an automobile diagnostic equipment which is connected to an ADAS system in a vehicle. The device 40 includes: an acquisition module 41, a display module 42 and a processing module 43.

Wherein, the acquisition module 41 is used to acquire ADAS system information of the vehicle according to the vehicle information of the vehicle, the ADAS system information includes the subsystems included in the ADAS system; the display module 42 is used to display all The information of the subsystems included in the ADAS system includes the identifier of the subsystem and the status of the subsystem; the processing module 43 is configured to receive user instructions and respond to information indicated by the user instructions. The subsystem performs one of fault identification, fault handling, or calibration.

Wherein, the status of the subsystem includes at least one of the following:

Wherein, said displaying the information of the subsystems included in the ADAS system includes:

Display the information of all or part of the subsystems included in the ADAS system.

Wherein, the processing module 43 is specifically configured to: after receiving a user's fault code acquisition instruction, send a fault code acquisition request to the subsystem indicated by the user instruction; Fault code; if yes, display the fault code.

Optionally, the processing module 43 is further configured to display the meaning of the fault corresponding to the fault code.

Optionally, the processing module 43 is further configured to determine whether the equipment in the subsystem needs to be calibrated according to the fault code; if so, prompt the user to calibrate the equipment in the subsystem.

Wherein, the processing module 43 is specifically configured to: after receiving the user's fault handling instruction, determine the fault handling plan corresponding to the fault code of the subsystem indicated by the user instruction; display the fault handling plan to guide the user to The described subsystem performs maintenance operations.

Wherein, the fault handling solution may be displayed on a page displaying the information of the subsystems included in the ADAS system; or, the fault handling solution may be displayed by jumping to another page.

Optionally, the processing module 43 is further configured to: receive a fault code clearing instruction from the user, and determine whether the fault code in the subsystem indicated by the fault code clearing instruction has been cleared; if so, update the fault code The status of the subsystem.

Wherein, the processing module 43 is specifically configured to: jump to the calibration guide operation page of the subsystem.

It is worth noting that the information interaction between the modules and units in the above-mentioned device, the execution process, etc., are based on the same concept as the method embodiment of the present invention. For specific content, please refer to the description in the method embodiment of the present invention. No longer.

6 is a schematic diagram of the hardware structure of an automobile diagnostic equipment provided by an embodiment of the present invention. The automobile diagnostic equipment 50 is used to execute the processing method of the ADAS system as described above. The automobile diagnostic equipment 50 and the ADAS system in the vehicle Connected, as shown in Fig. 6, the car diagnostic equipment 50 includes:

One or more processors 51 and a memory 52. One processor 51 is taken as an example in FIG. 6.

The processor 51 and the memory 52 may be connected by a bus or in other ways. In FIG. 6, the connection by a bus is taken as an example.

The memory 52, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, as corresponding to the processing method of the ADAS system in the embodiment of the present invention. Program instructions/modules (for example, the acquisition module 41, the display module 42, and the processing module 43 shown in FIG. 5). The processor 51 executes various functional applications and data processing of the automobile diagnostic equipment by running the non-volatile software programs, instructions, and modules stored in the memory 52, that is, realizes the processing method of the ADAS system in the above method embodiment.

The memory 52 may include a program storage area and a data storage area. The program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the processing device of the ADAS system. In addition, the memory 52 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some embodiments, the memory 52 may optionally include a memory remotely provided with respect to the processor 51, and these remote memories may be connected to a processing device of the ADAS system through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The one or more modules are stored in the memory 52, and when executed by the one or more processors 51, the processing method of the ADAS system in any of the foregoing method embodiments is executed, for example, the above-described diagram is executed. 1. The method steps in Fig. 2 and Fig. 3, and the functions of the modules in Fig. 5 are realized.

The above-mentioned products can execute the methods provided in the embodiments of the present invention, and have corresponding functional modules and beneficial effects for executing the methods. For technical details that are not described in detail in this embodiment, refer to the method provided in the embodiment of the present invention.

The embodiment of the present invention provides a non-volatile computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more processors, for example, as shown in FIG. 6 A processor 51 of, can enable the one or more processors to execute the processing method of the ADAS system in any of the above method embodiments, for example, to execute the method steps in Figure 1, Figure 2 and Figure 3 described above, and Realize the function of the module in Figure 5.

The embodiment of the present invention provides a computer program product, which includes a calculation program stored on a non-volatile computer-readable storage medium. The computer program includes program instructions. When the program instructions are executed by a computer, the The computer executes the processing method of the ADAS system in any of the foregoing method embodiments, for example, executes the method steps in FIGS. 1, 2 and 3 described above, and realizes the functions of the modules in FIG. 5.

The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

Through the description of the above implementation manners, a person of ordinary skill in the art can clearly understand that each implementation manner can be implemented by means of software plus a general hardware platform, and of course, it can also be implemented by hardware. A person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by instructing relevant hardware through a computer program. The program can be stored in a computer readable storage medium, and the program can be stored in a computer readable storage medium. When executed, it may include the procedures of the above-mentioned method embodiments. Wherein, the storage medium can be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, not to limit them; under the idea of the present invention, the technical features of the above embodiments or different embodiments can also be combined. The steps can be implemented in any order, and there are many other variations of the different aspects of the present invention as described above. For the sake of brevity, they are not provided in the details; although the present invention has been described in detail with reference to the foregoing embodiments, it is common in the art The skilled person should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or equivalently replace some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the implementations of the present invention. Examples of the scope of technical solutions.

Claims

A processing method of an ADAS system, applied to a car diagnostic equipment, and the car diagnostic equipment is connected to an ADAS system in a vehicle, characterized in that the method includes:

Acquiring ADAS system information of the vehicle according to the vehicle information of the vehicle, where the ADAS system information includes the subsystems included in the ADAS system;

Display information of the subsystems included in the ADAS system, the information of the subsystems including the identifier of the subsystem and the state of the subsystem;

Receive a user instruction, and perform one of fault identification, fault processing or calibration on the subsystem indicated by the user instruction.
The processing method of the ADAS system according to claim 1, wherein the state of the subsystem includes at least one of the following:

Whether the failure of the sub-system has been identified, whether the failure of the sub-system has been cleared, whether the sub-system can be calibrated, and whether the sub-system has been calibrated.
The processing method of the ADAS system according to claim 1 or 2, wherein the displaying the information of the subsystems included in the ADAS system comprises:

Display the information of all or part of the subsystems included in the ADAS system.
The processing method of the ADAS system according to any one of claims 1 to 3, wherein the receiving a user instruction and performing a fault identification operation on the subsystem indicated by the user instruction comprises:

After receiving the fault code acquisition instruction of the user, send a fault code acquisition request to the subsystem indicated by the user instruction;

Determine whether the fault code of the subsystem is obtained from the subsystem;

If yes, display the fault code.
The processing method of the ADAS system according to claim 4, wherein the method further comprises:

Display the meaning of the fault corresponding to the fault code.
The processing method of the ADAS system according to claim 4 or 5, wherein the method further comprises:

Determine whether the equipment in the subsystem needs to be calibrated according to the fault code;

If yes, prompt the user to calibrate the equipment in the subsystem.
The processing method of the ADAS system according to any one of claims 1-6, wherein the receiving a user instruction and performing a fault processing operation on the subsystem indicated by the user instruction comprises:

After receiving the fault handling instruction from the user, determine the fault handling plan corresponding to the fault code of the subsystem indicated by the user instruction;

Display the fault handling plan to guide the user to perform maintenance operations on the subsystem.
The processing method of the ADAS system according to claim 7, wherein the method further comprises:

Display the fault handling solution on the page displaying the information of the subsystems included in the ADAS system; or,

Jump to another page to display the troubleshooting solution.
The processing method of the ADAS system according to claim 7 or 8, wherein the method further comprises:

Receiving a fault code clearing instruction from the user, and determining whether the fault code in the subsystem indicated by the fault code clearing instruction has been cleared;

If yes, update the state of the subsystem.
The processing method of the ADAS system according to any one of claims 1-9, wherein the receiving a user instruction and performing a calibration operation on the subsystem indicated by the user instruction comprises:

Jump to the calibration guide operation page of the subsystem.
An automobile diagnostic equipment, characterized in that, the automobile diagnostic equipment includes:

At least one processor;

And a memory communicatively connected with the at least one processor;

Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute any one of claims 1 to 10 The method described.