Vehicle-mounted controller diagnosis method of vehicle and related equipment

Abstract

The invention belongs to the technical field of automobile control, and discloses a vehicle-mounted controller diagnosis method and related equipment.According to the method, communication protocols are screened based on the type of a to-be-diagnosed vehicle-mounted controller, communication parameters are set, communication connection is established, the problem that communication protocols and data formats of different controllers are different is solved, and the diagnosis accuracy of the vehicle-mounted controller is improved. The development cost and the time cost are greatly reduced, the development efficiency is improved, and the universality of the diagnosis method is enhanced; and analyzing the received response message to obtain the fault code, performing fault information matching based on the preset fault information base, and outputting the fault information corresponding to the successful matching of the fault code, so that the fault existing in the vehicle-mounted controller can be quickly and accurately positioned in the process. Therefore, the problem of work delay caused by the limited number of the diagnostic instruments during centralized detection or maintenance of the vehicle is avoided, the detection and maintenance efficiency is improved, and smooth vehicle diagnosis work is guaranteed.

Description

Technical Field

[0001] The invention belongs to the technical field of automobile control, and in particular relates to a vehicle-mounted controller diagnosis method and related equipment. Background Art

[0002] During the software development process of the vehicle controller application layer and the after-sales maintenance stage, once a vehicle fails, quickly reading and clearing the corresponding fault becomes the key to ensuring the normal operation of the vehicle. At the same time, during the software development period, in order to fully verify the functions of the controller, software updates are essential; during the vehicle offline electrical inspection, accurately writing configuration information and VIN codes is an important step to ensure that the vehicle meets factory standards.

[0003] At present, the host computer method is generally used to update the software for vehicle-mounted controllers. However, due to differences in communication protocols, data formats, etc. between different controllers, corresponding host computer software needs to be developed separately for each controller. This undoubtedly increases development costs and time costs and reduces development efficiency. In reading, clearing fault codes and offline electrical inspection operations, automotive diagnostic instruments are commonly used tools. However, automotive diagnostic instruments are expensive, and for automobile manufacturers and after-sales maintenance companies, purchasing and maintaining a large number of diagnostic instruments will bring a heavy economic burden. In addition, their limited number often cannot meet actual needs when vehicles are centrally inspected or repaired, resulting in delays in inspection and maintenance work.

[0004] It can be seen that the existing diagnostic measures require the development of corresponding host computer software for each vehicle controller, which has poor versatility and low efficiency. Summary of the invention

[0005] The present invention provides a vehicle-mounted controller diagnosis method and related equipment to solve the technical problems that the existing diagnosis measures need to develop corresponding host computer software separately for each vehicle-mounted controller, which has poor versatility and low efficiency.

[0006] In order to achieve the above object, the present invention adopts the following technical solution: A method for diagnosing an onboard controller of a vehicle, comprising: Select the communication protocol and set the communication parameters based on the type of the vehicle controller to be diagnosed, and establish a communication connection; Parse the received response message and obtain the fault code; Based on a preset fault information library, the fault code obtained by the analysis is matched with the fault information, and the fault information corresponding to the successful fault code matching is output; the fault information is used to reflect the fault existing in the vehicle controller.

[0007] Further, the method of selecting a communication protocol based on the type of the vehicle controller to be diagnosed and setting communication parameters to establish a communication connection includes: Filter the CANFD protocol or CANFD protocol according to the type of the vehicle controller to be diagnosed, set the baud rate, and establish a communication connection with the vehicle controller.

[0008] Furthermore, before parsing the received query message to obtain the fault code, the process further includes: The vehicle controller is updated with software based on the acquired new software data.

[0009] Furthermore, the updating of the software of the vehicle controller based on the acquired new software data includes: Read new software data and verify the software version number and part number of the vehicle controller; If the verification is successful, the new software data is parsed to obtain the start address, end address and data segment; The vehicle controller is flashed based on the start address, end address and data segment to implement software update of the vehicle controller.

[0010] Further, the parsing of the received response message to obtain the fault code includes: Sending the query message to the vehicle controller; Receive a response message sent from the vehicle controller; The data bytes in the response message are traversed one by one until the total number of traversals reaches the preset number of traversals, and the data bytes are saved as fault codes in the fault code list.

[0011] Furthermore, the fault information matching of the fault code obtained by the analysis is performed based on the preset fault information library, and the fault information corresponding to the successful matching of the fault code is output, including: For each parsed fault code, match it one by one in the fault information database until all parsed fault codes are matched; If the match is successful, the fault information corresponding to the fault code will be output.

[0012] Furthermore, the method further includes: matching the fault information of the fault code obtained by the analysis based on the preset fault information library, and outputting the fault information corresponding to the successful matching of the fault code, and further includes: After the on-board controller fault is eliminated, a clear fault code message is sent to the on-board controller and the configuration code and VIN code are written into the on-board controller.

[0013] A vehicle-mounted controller diagnostic system for a vehicle, comprising: A communication connection establishment module, used to select a communication protocol and set communication parameters based on the type of the vehicle controller to be diagnosed, and to establish a communication connection; A fault code acquisition module is used to parse the received response message and obtain the fault code; The fault information output module is used to match the fault code obtained by the analysis with the fault information based on the preset fault information library, and output the fault information corresponding to the successful fault code matching; the fault information is used to reflect the fault existing in the vehicle controller.

[0014] A device comprising: Memory for storing computer programs; A processor is used to implement the steps of the above-mentioned vehicle-mounted controller diagnostic method when executing the computer program.

[0015] A computer-readable storage medium stores a computer program, which is used to implement the steps of the vehicle-mounted controller diagnostic method when executed by a processor.

[0016] Compared with the prior art, the present invention has the following beneficial effects: The present invention provides a vehicle-mounted controller diagnosis method. The method overcomes the problem of differences in communication protocols and data formats of different controllers by screening communication protocols and setting communication parameters based on the type of vehicle-mounted controller to be diagnosed, and establishing a communication connection. It is not necessary to develop host computer software for each controller separately, which greatly reduces development costs and time costs, improves development efficiency, and enhances the versatility of the diagnosis method; the received response message is parsed to obtain a fault code, and fault information matching is performed based on a preset fault information library, and the fault information corresponding to the successful fault code matching is output. This process can quickly and accurately locate the faults existing in the vehicle-mounted controller, and can replace the expensive automobile diagnostic instrument to read and analyze the fault code, reducing the economic burden of automobile manufacturers and after-sales maintenance companies to purchase and maintain a large number of diagnostic instruments. At the same time, it avoids the problem of work delays caused by the limited number of diagnostic instruments during centralized vehicle detection or maintenance, improves the efficiency of detection and maintenance, and ensures the smooth progress of vehicle diagnosis.

[0017] Preferably, in the present invention, a communication protocol is selected from the CANFD protocol or the CAN protocol, and the baud rate is set to establish a communication connection, which makes the selection of the communication protocol more specific and operational, can better adapt to the communication requirements of different controllers, ensure the stability and reliability of communication, and provide a stable communication basis for subsequent fault diagnosis and other operations, avoiding problems such as diagnosis failure caused by communication protocol mismatch.

[0018] Preferably, in the present invention, a software update link is added before fault diagnosis, so that the diagnostic method can not only perform fault diagnosis, but also has a software update function. For the software upgrade requirements during vehicle development and maintenance, an integrated solution is provided, without the need for additional software update tools or processes, which improves the efficiency of vehicle maintenance, ensures that the on-board controller software is always in the latest and most stable state, reduces the probability of faults caused by outdated software versions, and also helps to improve the overall performance of the vehicle. Preferably, in the present invention, the new software data is read and the software version number and part number are verified, thereby ensuring the correctness and compatibility of the updated software and avoiding controller failure caused by installing incorrect or incompatible software; the new software data is parsed to obtain the starting address, ending address and data segment, providing necessary information for accurately flashing the software and ensuring the accuracy and completeness of the software update process; software updates are implemented by flashing based on this information, making the software update operation more standardized and reliable, improving the success rate of the software update, and ensuring the smooth progress of the vehicle controller software update. Preferably, in the present invention, by sending query messages, receiving response messages, and traversing data bytes one by one and saving fault codes to a list, the fault code acquisition process is made clearer and more accurate, which can effectively avoid data omissions or errors in the fault code acquisition process, improve the accuracy and reliability of fault code acquisition, and provide a high-quality data foundation for subsequent fault information matching and fault diagnosis.

[0019] Preferably, in the present invention, each parsed fault code is matched one by one in the fault information library until all are completed. If the match is successful, the fault information is output. This method can ensure that all fault codes can be accurately matched with fault information, improves the accuracy and completeness of the fault information output, and enables maintenance personnel to obtain detailed and accurate fault information, which helps to quickly locate and solve faults and improve the efficiency of fault diagnosis and maintenance.

[0020] Preferably, in the present invention, after the fault diagnosis and elimination, the sending of the clear fault code message and the writing of the configuration code and VIN code are added. This makes the diagnostic method cover the complete process from fault diagnosis, fault elimination to vehicle configuration recovery, ensures that the vehicle can be restored to a normal configuration state after maintenance, avoids subsequent problems caused by residual fault codes or inaccurate configuration information, improves the quality and standardization of vehicle maintenance, and ensures that the vehicle runs in the best state. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A functional schematic diagram of the vehicle-mounted controller diagnostic software is provided for an embodiment of the present invention; Figure 2 A schematic diagram of the contents of software update of the vehicle controller diagnostic method provided by an embodiment of the present invention; Figure 3 A flowchart of software update of the vehicle controller diagnostic method provided by an embodiment of the present invention; Figure 4 A schematic diagram of querying fault code data bytes of a vehicle controller diagnostic method provided by an embodiment of the present invention; Figure 5 A fault code analysis flow chart provided by an embodiment of the present invention; Figure 6 A flow chart of a vehicle controller diagnostic method provided by the present invention; Figure 7 A schematic structural diagram of a vehicle-mounted controller diagnostic system provided by the present invention. DETAILED DESCRIPTION

[0022] In order to further understand the content of the present invention, the present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the embodiments are only for explaining the present invention and are not intended to limit it.

[0023] The following is an explanation of the technical terms involved in the present invention: CAN: Controller Area Network, a serial communication protocol widely used in automotive electronics; CANFD: refers to Controller Area Network with Flexible Data Rate, which is an upgraded version of the CAN protocol; VIN: Vehicle Identification Number, which is equivalent to the vehicle's "ID card". It consists of 17 characters and contains information such as the vehicle's manufacturer, year, model, body type and code, engine code, etc. During the vehicle's offline configuration, the VIN code needs to be written into the vehicle controller for vehicle identification, production management, and after-sales tracking. DTC: Abbreviation for Diagnostic Trouble Code. When a fault occurs in the electronic control system of an automobile, the control unit will generate a DTC to mark the type and location of the fault; DID: Data Identifier. It is a code used to uniquely identify specific data during vehicle communication and diagnosis. When parsing freeze frame data, DID can accurately find and obtain the corresponding specific data information.

[0024] As described in the background technology, during the development of the application layer software of the vehicle controller and during the after-sales process, when a vehicle fails, it is necessary to read the fault in time and clear the corresponding fault; during the software development process, the controller software needs to be updated to verify the function; when the vehicle is offline for electrical inspection, the corresponding configuration information and VIN code need to be written. At present, the software is generally updated using the host computer method, and the corresponding host computer needs to be developed for different controllers. When reading, clearing fault codes and offline electrical inspection, the method of automobile diagnostic instrument is generally used, but the price of automobile diagnostic instrument is relatively expensive, the maintenance cost is high, and the quantity is relatively small. It can be seen that the existing diagnostic measures need to develop corresponding host computer software for each type of vehicle controller separately, which has poor versatility and low efficiency.

[0025] Example 1 In order to solve the above problems, this embodiment provides a vehicle-mounted controller diagnosis method. This method can realize the functions of software update, fault code management and offline electrical inspection of the vehicle-mounted controller during vehicle development.

[0026] This diagnostic method includes communicating with the vehicle controller through the PCAN connection line, and can be used to update the software of different controllers of the vehicle, that is, to read the corresponding version number; it can also parse the corresponding fault code and freeze frame, and match the fault code with the corresponding fault, and display the corresponding fault; it can also be used for the offline configuration of the whole vehicle, and has the functions of reading and writing configuration codes, VIN codes and clearing fault codes.

[0027] This embodiment provides a vehicle controller diagnosis method, including: Select the communication protocol and set the communication parameters based on the type of the vehicle controller to be diagnosed, and establish a communication connection; Parse the received response message and obtain the fault code; Based on a preset fault information library, the fault code obtained by the analysis is matched with the fault information, and the fault information corresponding to the successful fault code matching is output; the fault information is used to reflect the fault existing in the vehicle controller.

[0028] The control method provided by this embodiment is further explained below in conjunction with the accompanying drawings: like Figure 1 As shown, this embodiment provides vehicle-mounted controller diagnostic software, including a computer program, wherein when the computer program is executed, the steps of the vehicle-mounted controller diagnostic method can be implemented, and the specific functions are as follows: First, parameter setting: Considering that different controllers may require different communication protocols, this method first develops multiple communication protocol drivers. On the software interface, users can easily select the corresponding communication protocol (such as CAN or CANFD) and controller type according to actual needs. At the same time, the baud rate can also be set according to the requirements of the controller. After completing these parameter settings, the software can establish a stable communication connection with the vehicle controller, preparing for the implementation of subsequent software updates, fault code management, and offline configuration functions.

[0029] Second, update the software: Figure 2 As shown, the software update process uses service 10, service 11, service 31, service 34, service 36 and service 37. In specific operations, the user first imports the software to be updated into the diagnostic software. The software will automatically read all the line contents of the software to be updated, and parse out key information such as the start address, end address, and data segment. Then, the software calls the internal refresh process and writes the new software data accurately into the vehicle controller according to the preset steps and rules to complete the software update operation. In addition, the software has the function of reading the version number. Before and after the update, the user can easily query the software version number, hardware version number and other information to confirm whether the software update is successful and the current version status of the vehicle controller.

[0030] Specific steps to follow: Figure 3 As shown: Start: The update process starts.

[0031] Interface operation: Select the controller type and communication protocol in the software interface, import the S19 file (software update package) and click Start Refresh. If the connection to the controller fails, the refresh is directly judged as failed and the process ends.

[0032] Parse S19 file: Parse the imported S19 file. If the parsing fails, the refresh is directly judged as failed and the process ends.

[0033] Software version number and part number verification: Verify the software version number and part number involved in the parsed file. If the verification fails, the refresh is directly judged to have failed and the process ends.

[0034] Enter the refresh session: Enter the refresh session through 10 service.

[0035] Security verification: Use 27 services for security verification.

[0036] Erase Flash: Erase Flash with the help of 31 service.

[0037] Request transmission: Use 34 service to request transmission.

[0038] Transfer files: Use 36 services to transfer parsed S19 files.

[0039] Request to quit transmission: Request to quit transmission through 37 service.

[0040] Exit the refresh session: Use the 11 service to exit the refresh session.

[0041] Refresh result determination: If the above steps are completed successfully, the refresh is determined to be successful; if abnormal conditions such as negative communication response occur in the above steps, the refresh is determined to have failed.

[0042] The update process is complete.

[0043] Third, fault code management: When querying fault codes, the software sends the query message to be sent to the vehicle controller through the CAN communication protocol or the CANFD communication protocol. For example, use specific message instructions such as 19 02 and 19 04 to read historical fault codes, current fault codes, and freeze frame data. After sending the query message, the software will wait for the vehicle controller to return a response message. After receiving the response message, the software uses a specific parsing method to parse the message.

[0044] The specific analysis process is as follows: Figure 5 As shown, specifically including: Start: The diagnostic process starts.

[0045] Determine the byte length of the received data: Check whether the byte length of the received data is less than 8. If it is less than 8, go to step 3-1; if it is not less than 8, go to step 3-2.

[0046] Step 3-1: Data interception (when the byte length is less than 8): intercept the third byte of the received data to the end.

[0047] Step 3-2: Data interception (when the byte length is not less than 8): intercept the fourth byte of the received data to the end.

[0048] Data traversal and storage: traverse the intercepted data. When the count is less than 3, store each received data byte in a data list and add 1 to the count; when the count is equal to 3, store the received data byte in the discard list, store the data list in the DTC list (fault code list), and then clear the count.

[0049] Forming a fault code list: After the above operations, the DTC list becomes a list containing all fault codes.

[0050] End: The entire fault code extraction process is completed.

[0051] After the analysis is completed, the software will match the fault information according to the analyzed fault code. The specific matching process is: traverse all preset fault codes, and match each analyzed fault code one by one in the fault information library. If matching fault information is found, the fault information is returned. This cycle is repeated until all analyzed fault codes are matched. Finally, based on all the returned fault information, this diagnostic software can clearly display all historical fault information and current fault information of the vehicle. At the same time, the software can also parse the data information corresponding to the DID based on the freeze frame data, providing a more detailed and accurate basis for fault diagnosis.

[0052] Fourth, offline configuration: This function is mainly used for offline configuration of the whole vehicle. During operation, the software will send the fault code clearing message (such as 14 FF FF FF) to the vehicle controller to realize the function of clearing the fault code information. At the same time, the software also has the functions of reading and writing configuration codes and VIN codes. It can accurately write configuration codes and VIN codes into the vehicle controller according to the standard requirements of the vehicle offline, ensuring that all configuration information of the vehicle is accurate before delivery, providing guarantee for the normal use of the vehicle.

[0053] Example 2 This embodiment provides a vehicle on-board controller diagnostic method. This control method is specifically used in the scenario of new energy vehicle controller software update and troubleshooting. When a new energy vehicle manufacturer produces a new electric vehicle, it is necessary to update the on-board controller software to optimize the performance of the battery management system. At the same time, it is found on the production line that the battery management system of some vehicles has a fault prompt, which requires troubleshooting and repair. The specific implementation process of this diagnosis is as follows: Establish communication: The technician opens the vehicle diagnostic software and selects the CANFD communication protocol on the software interface, because the vehicle controller of this new energy vehicle uses the CANFD protocol for communication. Then, select the corresponding battery management system controller type and set the baud rate to 500kbps according to the specifications of the controller. After completing the parameter setting, click the "Connect" button, and the software will establish a communication connection with the vehicle controller through the PCAN cable.

[0054] Update software: The technician imports the optimized battery management system software (stored in S19 file format) into the vehicle diagnostic software. The software automatically reads all the lines of the S19 file, parses the start address of 0x1000, the end address of 0x2000, and the data segment contains a series of instructions and data for optimizing the battery management algorithm. Then, the software calls the refresh process, and executes 10 services to enter the refresh session, 27 services for security verification, 31 services to erase Flash, 34 services to request transmission, 36 services to transmit the parsed S19 file data, 37 services to request to exit transmission, 11 services to exit the refresh session, etc. During the update process, the software displays the update progress in real time. After about 2 minutes of operation, the software prompts "Refresh successful". The technician then uses the software's read version number function to query that the software version number has been updated from the original V1.0 to V1.1, and the hardware version number is H1.2, confirming that the software update is successful.

[0055] Fault code management: After completing the software update, the technicians began to troubleshoot the battery management system. The software sent a 19 02 query message to the vehicle controller through the CANFD communication protocol to read the historical fault code. A moment later, the software received a response message returned by the vehicle controller. The message was parsed using the preset parsing method and the fault code 0x1234 was found. The software traversed the fault information library and matched the fault code 0x1234 with the corresponding fault information, and finally displayed a fault prompt of "Battery temperature sensor failure, which may cause inaccurate battery temperature monitoring." Based on this fault information prompt, the technicians checked the battery temperature sensor and its connection line and found that the sensor's connection line was loose. After reconnecting, the technician used the fault code query function of the software again to confirm that the fault code had been cleared and the battery management system resumed normal operation.

[0056] Offline configuration: After completing the software update and troubleshooting, the vehicle enters the offline configuration phase. The technician uses the offline configuration function of the vehicle diagnostic software to accurately write the vehicle's configuration code (such as model configuration information, production batch, etc.) and VIN code into the vehicle controller. Then, the software sends a 14 FF FF FF clear fault code message to the vehicle controller to ensure that there is no fault code record when the vehicle goes offline. After completing the offline configuration, the vehicle can enter the subsequent vehicle inspection and delivery process.

[0057] Example 3 This embodiment provides a vehicle controller diagnostic method. This control method is specifically applied to the fault diagnosis and processing scenario in the after-sales maintenance of traditional fuel vehicles. Specifically, when the engine fault light of a traditional fuel vehicle comes on during driving, the owner sends the vehicle to an after-sales repair shop for repair. The maintenance personnel use the vehicle diagnostic software of this embodiment to diagnose and repair the vehicle fault. The specific implementation process is as follows: Establish communication: The maintenance personnel open the vehicle diagnostic software, select the CAN communication protocol on the software interface according to the vehicle model and controller information, select the engine controller type, and set the baud rate to 250kbps. After the settings are completed, the software establishes a communication connection with the engine controller through the PCAN connection line.

[0058] Fault code management: The maintenance personnel use the software to send a 19 04 query message to the engine controller to read the current fault code. After receiving the response message, the software parses the fault code 0x5678. After matching the fault information, the software displays the fault prompt "Oxygen sensor failure may cause abnormal engine mixture concentration". According to this fault information prompt, the maintenance personnel tested the oxygen sensor and found that the oxygen sensor was aging and needed to be replaced. After replacing the oxygen sensor, the maintenance personnel used the software to query the fault code again and confirmed that the fault code had been cleared.

[0059] Software update (optional operation): After completing the fault repair, the maintenance personnel decided to use the vehicle diagnostic software to check whether there is any available software update, considering that there may be some room for optimization of the vehicle's engine control software. The software reads the version information of the engine controller and finds that the current software version is older and a new software version is available for update. Therefore, the maintenance personnel imports the new engine control software and successfully updates it to the vehicle's engine controller according to the software update operation process. After the update is completed, the version information is read again to confirm that the software update is successful.

[0060] Offline configuration: After completing the fault repair and software update, the maintenance personnel use the fault code clearing function of the vehicle diagnostic software to ensure that there are no fault codes before the vehicle is delivered to the owner. At the same time, the maintenance personnel can also use the software to check whether the vehicle's configuration information is correct, such as the vehicle's emission standard configuration. After confirmation, the vehicle can be delivered to the owner to complete this after-sales maintenance service.

[0061] It can be seen that the diagnostic method provided in this embodiment can be applied to different vehicle application scenarios, and can efficiently and accurately realize functions such as software updates, fault code management and offline configuration, providing reliable technical support for vehicle research and development, production and after-sales maintenance.

[0062] Example 4 like Figure 6 As shown, this embodiment provides a vehicle controller diagnosis method, comprising the following steps: Select the communication protocol and set the communication parameters based on the type of the vehicle controller to be diagnosed, and establish a communication connection; Parse the received response message and obtain the fault code; Based on a preset fault information library, the fault code obtained by the analysis is matched with the fault information, and the fault information corresponding to the successful fault code matching is output; the fault information is used to reflect the fault existing in the vehicle controller.

[0063] In this embodiment, the steps of selecting a communication protocol based on the type of the vehicle controller to be diagnosed and setting communication parameters to establish a communication connection include: Filter the CANFD protocol or CANFD protocol according to the type of the vehicle controller to be diagnosed, set the baud rate, and establish a communication connection with the vehicle controller.

[0064] In addition, before parsing the received query message and obtaining the fault code, the following steps are also included: The vehicle controller is updated with software based on the acquired new software data.

[0065] Specifically, the software update of the vehicle controller based on the acquired new software data includes: Read new software data and verify the software version number and part number of the vehicle controller; If the verification is successful, the new software data is parsed to obtain the start address, end address and data segment; The vehicle controller is flashed based on the start address, end address and data segment to implement software update of the vehicle controller.

[0066] In this embodiment, the step of parsing the received response message to obtain the fault code includes: Sending the query message to the vehicle controller; Receive a response message sent from the vehicle controller; The data bytes in the response message are traversed one by one until the total number of traversals reaches the preset number of traversals, and the data bytes are saved as fault codes in the fault code list.

[0067] Here, based on the preset fault information library, the fault code obtained by parsing is matched with the fault information, and the fault information corresponding to the successful matching of the fault code is output, including: For each parsed fault code, match it one by one in the fault information database until all parsed fault codes are matched; If the match is successful, the fault information corresponding to the fault code will be output.

[0068] In particular, the method further includes: matching the fault information of the fault code obtained by the analysis based on the preset fault information library, and outputting the fault information corresponding to the successful matching of the fault code. After the on-board controller fault is eliminated, a clear fault code message is sent to the on-board controller and the configuration code and VIN code are written into the on-board controller.

[0069] like Figure 7 As shown, the present embodiment also provides a vehicle-mounted controller diagnostic system, including: a communication connection establishment module, used to filter the communication protocol and set the communication parameters based on the type of the vehicle-mounted controller to be diagnosed, and establish a communication connection; a fault code acquisition module, used to parse the received response message to obtain the fault code; a fault information output module, used to match the fault information of the parsed fault code based on a preset fault information library, and output the fault information corresponding to the successful fault code match; the fault information is used to reflect the fault existing in the vehicle-mounted controller.

[0070] The present invention also provides a device, comprising: a memory for storing a computer program; and a processor for implementing the steps of the vehicle's onboard controller diagnostic method when executing the computer program.

[0071] When the processor executes the computer program, the steps of diagnosing the on-board controller of the above-mentioned vehicle are implemented, for example: based on the type of on-board controller to be diagnosed, the communication protocol is screened and the communication parameters are set to establish a communication connection; the received response message is parsed to obtain the fault code; based on the preset fault information library, the fault code obtained by parsing is matched with the fault information, and the fault information corresponding to the successful fault code match is output; the fault information is used to reflect the fault existing in the on-board controller.

[0072] Alternatively, when the processor executes the computer program, it implements the functions of each module in the above system, for example: a communication connection establishment module, which is used to screen the communication protocol and set the communication parameters based on the type of vehicle controller to be diagnosed, and establish a communication connection; a fault code acquisition module, which is used to parse the received response message to obtain the fault code; a fault information output module, which is used to match the fault information of the parsed fault code based on a preset fault information library, and output the fault information corresponding to the successful fault code match; the fault information is used to reflect the fault existing in the vehicle controller.

[0073] Exemplarily, the computer program can be divided into one or more modules / units, and the one or more modules / units are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments that can complete preset functions, and the instruction segments are used to describe the execution process of the computer program in the vehicle-mounted controller diagnostic device of the vehicle. For example, the computer program can be divided into a communication connection establishment module, a fault code acquisition module and a fault information output module; the specific functions of each module are as follows: a communication connection establishment module, which is used to filter the communication protocol and set the communication parameters based on the type of vehicle-mounted controller to be diagnosed, and establish a communication connection; a fault code acquisition module, which is used to parse the received response message and obtain the fault code; a fault information output module, which is used to match the fault information of the parsed fault code based on the preset fault information library, and output the fault information corresponding to the successful fault code match; the fault information is used to reflect the fault existing in the vehicle-mounted controller.

[0074] The vehicle-mounted controller diagnostic device may be a computing device such as a desktop computer, a notebook, a PDA, and a cloud server. The vehicle-mounted controller diagnostic device may include, but is not limited to, a processor and a memory. Those skilled in the art may understand that the above are examples of vehicle-mounted controller diagnostic devices and do not constitute a limitation on the vehicle-mounted controller diagnostic device. More components than the above may be included, or some components may be combined, or different components may be included. For example, the vehicle-mounted controller diagnostic device may also include input and output devices, network access devices, buses, etc.

[0075] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The processor is the control center of the vehicle-mounted controller diagnosis of the vehicle, and uses various interfaces and lines to connect various parts of the vehicle-mounted controller diagnosis equipment of the entire vehicle.

[0076] The memory can be used to store the computer programs and / or modules, and the processor implements various functions of the vehicle's on-board controller diagnostic device by running or executing the computer programs and / or modules stored in the memory and calling the data stored in the memory.

[0077] The memory may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0078] The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the vehicle on-board controller diagnostic method are implemented.

[0079] The module / unit integrated in the vehicle's onboard controller diagnostic system may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as an independent product.

[0080] Based on such understanding, the present invention implements all or part of the process in the vehicle-mounted controller diagnostic method of the above-mentioned vehicle, and can also be completed by instructing related hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the vehicle-mounted controller diagnostic method of the above-mentioned vehicle can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or preset intermediate form, etc.

[0081] The computer-readable storage medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, etc.

[0082] It should be noted that the content contained in the computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable storage media do not include electrical carrier signals and telecommunication signals.

[0083] The present invention provides a vehicle-mounted controller diagnosis method, which has the following advantages: First, cost reduction: Through unified vehicle diagnostic software and methods, the high cost of developing multiple host computer software for different controllers is avoided, while reducing dependence on expensive automotive diagnostic instruments and reducing hardware purchase and maintenance costs.

[0084] Second, efficiency improvement: The software operation interface is simple and intuitive, and functions such as parameter setting, software update, fault code management and offline configuration are easy to operate, which greatly shortens the operation time during vehicle development, testing and maintenance, and improves overall work efficiency.

[0085] Third, high functional integration: Integrating multiple functions such as software update, fault code management and offline electrical inspection into one software and method, it is convenient for users to perform one-stop operation, avoiding the inconvenience of switching between multiple tools and processes, and improving the continuity and accuracy of work.

[0086] The above embodiment is only one of the implementation methods that can realize the technical solution of the present invention. The scope of protection claimed by the present invention is not limited only to this embodiment, but also includes changes, replacements and other implementation methods that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed by the present invention.

[0087] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A vehicle-mounted controller diagnostic method, characterized in that: include: Select the communication protocol and set the communication parameters based on the type of the vehicle controller to be diagnosed, and establish a communication connection; Parse the received response message and obtain the fault code; Based on the preset fault information library, the fault code obtained by the analysis is matched with the fault information, and the fault information corresponding to the successful fault code matching is output; The fault information is used to reflect the fault existing in the vehicle controller.

2. The vehicle-mounted controller diagnostic method according to claim 1, characterized in that: The method of selecting a communication protocol based on the type of the vehicle controller to be diagnosed and setting communication parameters to establish a communication connection includes: Filter the CANFD protocol or CANFD protocol according to the type of the vehicle controller to be diagnosed, set the baud rate, and establish a communication connection with the vehicle controller.

3. The vehicle-mounted controller diagnostic method according to claim 1, characterized in that: Before parsing the received query message and obtaining the fault code, the method further includes: The vehicle controller is updated with software based on the acquired new software data.

4. The vehicle-mounted controller diagnostic method of claim 3, characterized in that: The updating of the vehicle controller software based on the acquired new software data includes: Read new software data and verify the software version number and part number of the vehicle controller; If the verification is successful, the new software data is parsed to obtain the start address, end address and data segment; The vehicle controller is flashed based on the start address, end address and data segment to implement software update of the vehicle controller.

5. The vehicle-mounted controller diagnostic method according to claim 1, characterized in that: The step of parsing the received response message to obtain the fault code includes: Sending the query message to the vehicle controller; Receive a response message sent from the vehicle controller; The data bytes in the response message are traversed one by one until the total number of traversals reaches the preset number of traversals, and the data bytes are saved as fault codes in the fault code list.

6. The vehicle-mounted controller diagnostic method of claim 1, characterized in that: The method of matching the fault information of the fault code obtained by the analysis based on the preset fault information library and outputting the fault information corresponding to the successful matching of the fault code includes: For each parsed fault code, match it one by one in the fault information database until all parsed fault codes are matched; If the match is successful, the fault information corresponding to the fault code will be output.

7. The vehicle-mounted controller diagnostic method according to claim 1, characterized in that: The method further includes: matching the fault information of the fault code obtained by the analysis based on the preset fault information library, and outputting the fault information corresponding to the successful matching of the fault code; After the on-board controller fault is eliminated, a clear fault code message is sent to the on-board controller and the configuration code and VIN code are written into the on-board controller.

8. A vehicle-mounted controller diagnostic system, characterized in that: include: A communication connection establishment module, used to select a communication protocol and set communication parameters based on the type of the vehicle controller to be diagnosed, and to establish a communication connection; A fault code acquisition module is used to parse the received response message and obtain the fault code; A fault information output module is used to match the fault information of the fault code obtained by the analysis based on a preset fault information library, and output the fault information corresponding to the successful matching of the fault code; The fault information is used to reflect the fault existing in the vehicle controller.

9. A device, characterized in that: include: Memory for storing computer programs; A processor is used to implement the steps of the vehicle-mounted controller diagnostic method of any one of claims 1-7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it is used to implement the steps of the vehicle-mounted controller diagnostic method of any one of claims 1-7.

Images