Cross-platform diagnostic software configuration management and real-time data analysis system and method

Abstract

The invention relates to a cross-platform diagnostic software configuration management and real-time data analysis method, which comprises the following steps of: judging whether updating is needed or not, if so, issuing an updating file and updating a version, otherwise, confirming a vehicle diagnostic demand; if the diagnosis demand comes from the diagnosis instrument, the diagnosis instrument reads the vehicle VIN code and sends the vehicle VIN code to the cross-end diagnosis background server, otherwise, the vehicle machine diagnosis software reads the vehicle VIN code and sends the vehicle VIN code to the cross-end diagnosis background server; various parameters of the vehicle are obtained; preparing all diagnosis demand files; initializing communication, and issuing a diagnosis protocol file; if the diagnostic apparatus is operated, a diagnosis demand is manually input, a related diagnosis file is issued, and automatic operation is performed, otherwise, a Web end diagnosis instruction is sent; related diagnosis files are issued, and automatic operation is performed; if the parts are replaced, judging whether a diagnosis demand exists or not, if yes, returning to confirm the vehicle diagnosis demand, and otherwise, returning vehicle fault information; and generating a diagnostic test report. The method has the beneficial effects of short diagnosis process period and high efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of automotive fault diagnosis, and particularly to a cross-platform diagnostic software configuration management and real-time data analysis method and system. Background Art

[0002] With the continuous development of automotive electronics technology, the complexity of automotive functions has been increasing day by day, resulting in more and more onerous tasks for vehicle diagnostic system development and testing. During the vehicle development process, it is necessary to adjust the in-vehicle diagnostic module configuration file according to current market requirements, regulatory requirements, in-vehicle system configurations, etc. After the vehicle enters the market, in response to changes in diagnostic requirements, customer usage feedback, and the emergence of new faults, etc., it is necessary to rewrite the configuration of the in-vehicle diagnostic module. Thus, the development of automotive diagnostic systems faces huge challenges.

[0003] Most traditional diagnostic instruments and their configured diagnostic software write the configuration parameters and diagnostic protocol files of many vehicle models into the diagnostic program uniformly. This method not only has low efficiency but also is prone to the situation where the diagnostic results do not match the actual faults, so that fault diagnosis relies more on manual experience, which undoubtedly increases the labor cost for after-sales.

[0004] In addition, the current automotive fault diagnosis process is that the in-vehicle diagnostic module monitors and records fault data, and then the handheld diagnostic instrument reads the monitored fault data, mainly fault codes, and then the fault location and cause are found out through manual analysis. This diagnostic process has a long cycle and low efficiency, and fails to effectively utilize the large amount of vehicle driving data collected.

[0005] Ensuring to meet vehicle diagnostic requirements while reducing labor costs and time costs is the general trend of the current development direction of automotive fault diagnosis. Thus, it is of practical significance to study diagnostic software configuration management methods and diagnostic data real-time analysis methods. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a cross-platform diagnostic software configuration management and real-time data analysis method and system to solve the problem that the existing automotive fault diagnosis process is that the in-vehicle diagnostic system monitors and records fault data, and then the handheld diagnostic instrument reads the monitored fault data, mainly fault codes, and then the fault location and cause are found out through manual analysis. This diagnostic process has a long cycle and low efficiency, and fails to effectively utilize the large amount of vehicle driving data collected.

[0007] The technical solution of the present invention to solve the above technical problem is as follows:

[0008] A cross-platform diagnostic software configuration management and real-time data analysis method includes the following steps:

[0009] S01. Build a diagnostic configuration database in the cross-terminal diagnostic background server;

[0010] The SO2 cross - terminal diagnostic background server determines whether the diagnostic instrument or in - vehicle diagnostic software needs to be updated. If so, it proceeds to S03; if not, it proceeds to S04;

[0011] S03. Trigger an update prompt. After confirmation, send the update file and update the version of the diagnostic instrument or in - vehicle diagnostic software;

[0012] S04. Confirm the vehicle diagnostic requirements, read the vehicle identification number and the vehicle configuration information corresponding to this vehicle identification number, and transmit them to the cross - terminal diagnostic background server;

[0013] S05. Determine whether the diagnostic requirement comes from the diagnostic instrument. If so, it proceeds to S06; if not, it proceeds to S07;

[0014] S06. The diagnostic instrument reads the vehicle VIN code and gives it to the cross - terminal diagnostic background server, and then proceeds to S08;

[0015] S07. The in - vehicle diagnostic software reads the vehicle VIN code and gives it to the cross - terminal diagnostic background server;

[0016] S08. The cross - terminal diagnostic background server queries in the production system data with this VIN code to obtain various parameters of this vehicle;

[0017] S09. Prepare all diagnostic requirement files according to the vehicle configuration parameters;

[0018] S10. Initialize the communication between the diagnostic instrument or in - vehicle diagnostic software and the vehicle module, and send the diagnostic protocol file;

[0019] S11. Determine whether it is an operation of the diagnostic instrument. If so, it proceeds to S12; if not, it proceeds to S16;

[0020] S12. Manually input the diagnostic requirements;

[0021] S13. Feed back the diagnostic requirements to the cross - terminal diagnostic background server;

[0022] S14. According to the diagnostic requirements, the cross - terminal diagnostic background server sends relevant diagnostic files to the diagnostic instrument;

[0023] S15. The diagnostic instrument performs automated operations according to the relevant diagnostic files and then proceeds to S19;

[0024] S16. Send the Web - end diagnostic instruction;

[0025] S17. According to the diagnostic requirements, the cross - terminal diagnostic background server sends relevant diagnostic files to the vehicle diagnostic software;

[0026] S18. The vehicle diagnostic software performs automated operations and then proceeds to S19;

[0027] S19. Determine whether the parts need to be replaced. If yes, go to S20; if no, go to S21.

[0028] S20. Replace the relevant parts according to the version number of the parts, and check whether the diagnostic requirements still exist. If yes, go to S04; if no, go to S21.

[0029] S21. Transmit the vehicle fault information back.

[0030] S22. Generate a diagnostic test report.

[0031] S23. End.

[0032] Based on the above technical solutions, the present invention can also be improved as follows.

[0033] Further, the diagnostic configuration database at least includes: files for maintaining the diagnostic communication protocols of all vehicles, configuration parameter files, flashing file packages, flashing software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files.

[0034] Further, the files for diagnostic communication protocols, configuration parameter files, flashing file packages, flashing software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files are internally managed by different sections, including: module configuration parameter section, module software flashing section, module calibration and self-learning section, and diagnostic instrument software management section.

[0035] Further, the specific process for determining whether the diagnostic instrument or the in-vehicle diagnostic software needs to be updated is as follows: The cross-terminal diagnostic background server obtains the version number information of the in-vehicle diagnostic software or the diagnostic instrument, and compares this version number information with the latest released version number in the background configuration management system to determine whether an update is required.

[0036] Further, the vehicle configuration information at least includes: vehicle identification number, vehicle production date, vehicle model, module hardware information, and part number structure, and this part number structure includes assembly number, hardware number, software number, and network number.

[0037] Further, preparing all diagnostic requirement files according to the vehicle configuration parameters specifically means: The cross-terminal diagnostic background server matches the diagnostic communication protocol file and sets the diagnostic communication parameters according to the vehicle identification number and the vehicle configuration information corresponding to this vehicle identification number, and queries the configuration parameter file, flashing file package, flashing software package, calibration file package, calibration software package, and self-learning program package.

[0038] Further, the relevant diagnostic files issued meet the module parameter configuration requirements, module software flashing requirements, module calibration requirements, and module self-learning requirements.

[0039] Furthermore, the vehicle fault information transmitted back includes but is not limited to: vehicle fault time and location information, vehicle mileage information, vehicle internal communication message information, freeze frames and fault code information saved in vehicle internal modules, and the modification status of current vehicle configuration parameters.

[0040] Furthermore, generating a diagnostic test report specifically means that the cross - end diagnostic background server generates a diagnostic test report composed of the transmitted - back data, and conducts fault analysis based on this diagnostic test report, forming fault diagnosis experience and saving it in the diagnostic experience database.

[0041] Based on the above technical solutions, the present invention also provides a cross - platform diagnostic software configuration management and real - time data analysis system for implementing the above - mentioned cross - platform diagnostic software configuration management and real - time data analysis method, including: a cross - end diagnostic background server and a diagnostic instrument. The cross - end diagnostic background server establishes data interactions with the diagnostic instrument and the in - vehicle diagnostic module in the target vehicle respectively. The diagnostic instrument establishes a data interaction with the in - vehicle diagnostic module in the target vehicle, and the in - vehicle diagnostic module runs the vehicle diagnostic software.

[0042] The beneficial effects of the present invention are as follows:

[0043] By completely decoupling the management and application of diagnostic files, it can more flexibly meet the increasingly complex diagnostic requirements of in - vehicle electronic modules. When a diagnostic requirement arises, it can configure and manage the diagnostic instrument and vehicle diagnostic software in real - time and efficiently. By means of real - time issuing of diagnostic files, the storage space occupied by the installation program and update package of the diagnostic instrument is reduced, creating conditions for the use of vehicle diagnostic software. At the same time, by canceling the way of embedding the main core diagnostic files in the diagnostic instrument and vehicle diagnostic software, the privacy and confidentiality of diagnostic data are improved, the frequency of data interaction within the enterprise and the data backup volume are reduced. All files related to vehicle diagnosis are managed through different management sections in the same system, simplifying the management solution. Meanwhile, a method for real - time data analysis and use is provided, which can obtain vehicle fault data in real - time and conduct data analysis in the diagnostic background server to form diagnostic experience for engineers to learn and use;

[0044] The cross - end diagnostic background server obtains the vehicle configuration information and part information through data synchronization with other production systems, but does not save the relevant information, reducing local memory consumption and facilitating efficient management;

[0045] Diagnostic communication protocol files, configuration parameter files, flashing file packages, flashing software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files in the diagnostic configuration database are internally managed by different sections, including: module configuration parameter section, module software flashing section, module calibration and self-learning section, and diagnostic instrument software management section, which can quickly and flexibly provide diagnostic files when the handheld diagnostic instrument issues a diagnostic requirement;

[0046] By developing in-vehicle diagnostic software, remote upload of diagnostic data and real-time operation fault data of the vehicle can be achieved. Diagnostic experience can be formed through diagnostic cases, providing a data basis for subsequent development and support for maintenance cases for maintenance technicians and engineers. Brief Description of the Drawings

[0047] Figure 1 It is a flowchart of the cross-platform diagnostic software configuration management and real-time data analysis method in the present invention;

[0048] Figure 2 It is a structural diagram of the cross-platform diagnostic software configuration management and real-time data analysis system in the present invention. Detailed Embodiment

[0049] The principles and features of the present invention will be described below in conjunction with the accompanying drawings. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0050] Embodiment 1

[0051] As Figure 1 shown, a cross-platform diagnostic software configuration management and real-time data analysis method includes the following steps:

[0052] S01. Build a diagnostic configuration database in the cross-terminal diagnostic background server;

[0053] S02. The cross-terminal diagnostic background server determines whether the diagnostic instrument or in-vehicle diagnostic software needs to be updated. If yes, go to S03; if no, go to S04;

[0054] S03. Trigger an update prompt, and after confirmation, send the update file and update the version of the diagnostic instrument or in-vehicle diagnostic software;

[0055] S04. Confirm the vehicle diagnostic requirement, read the vehicle identification number and the vehicle configuration information corresponding to the vehicle identification number and transmit them to the cross-terminal diagnostic background server;

[0056] S05. Determine whether the diagnostic requirement comes from a diagnostic instrument. If yes, go to S06; if no, go to S07;

[0057] S06, the diagnostic instrument reads the vehicle VIN code and sends it to the cross-end diagnostic backend server, and then enters S08;

[0058] S07, the vehicle diagnostic software reads the vehicle VIN code and sends it to the cross-end diagnostic backend server;

[0059] S08, the cross-end diagnosis backend server uses the VIN code to query the production system data to obtain various parameters of the vehicle;

[0060] S09. Prepare all diagnostic requirement files according to vehicle configuration parameters;

[0061] S10, the diagnostic instrument or vehicle diagnostic software is initialized to communicate with the vehicle module, and the diagnostic protocol file is issued;

[0062] S11, determine whether it is a diagnostic instrument operation, if yes, go to S12, if no, go to S16;

[0063] S12, manual input of diagnostic requirements;

[0064] S13, the diagnosis demand is fed back to the cross-end diagnosis backend server;

[0065] S14, sending relevant diagnostic files to the diagnostic instrument through the cross-end diagnostic backend server according to the diagnostic requirements;

[0066] S15, the diagnostic instrument performs automatic operation according to the relevant diagnostic files and enters S19;

[0067] S16, Web-side diagnostic instructions are sent;

[0068] S17, sending relevant diagnostic files to the vehicle diagnostic software through the cross-end diagnostic backend server according to the diagnostic requirements;

[0069] S18, the vehicle diagnostic software performs automatic operation according to the relevant diagnostic files and enters S19;

[0070] S19, determine whether the parts need to be replaced, if yes, proceed to S20, if no, proceed to S21;

[0071] S20, replace relevant parts according to the version number of the parts, and check whether the diagnosis requirement still exists. If yes, go to S04, if not, go to S21;

[0072] S21, transmitting vehicle fault information;

[0073] S22. Generate a diagnostic test report.

[0074] All the diagnostic instruments mentioned in the present invention are handheld diagnostic instruments. By completely decoupling the management and application of diagnostic files, the present invention can more flexibly meet the increasingly complex diagnostic requirements of in-vehicle electronic modules. When a diagnostic requirement arises, it can configure and manage the diagnostic instrument and in-vehicle diagnostic software in real time and efficiently. By issuing diagnostic files in real time, the storage space occupied by the installation program and update package of the diagnostic instrument is reduced, creating conditions for the use of in-vehicle diagnostic software. At the same time, the way of embedding the main core diagnostic files in the diagnostic instrument and in-vehicle diagnostic software is cancelled, improving the privacy and confidentiality of diagnostic data, reducing the frequency of data interaction and the amount of data backup within the enterprise. All files related to vehicle diagnosis are managed by different management sections in the same system, simplifying the management solution. At the same time, a method for real-time data analysis and use is provided, obtaining vehicle fault data in real time and performing data analysis on the diagnostic background server to form diagnostic experience for engineers to learn and use;

[0075] The cross-terminal diagnostic background server obtains the vehicle configuration information and part information by synchronizing data with other production systems, but does not save the relevant information, reducing local memory consumption and facilitating efficient management;

[0076] The diagnostic communication protocol files, configuration parameter files, flashing file packages, flashing software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files in the diagnostic configuration database are internally managed by different sections, including: module configuration parameter section, module software flashing section, module calibration and self-learning section, and diagnostic instrument software management section, which can quickly and flexibly provide diagnostic files when the handheld diagnostic instrument issues a diagnostic requirement;

[0077] By developing in-vehicle diagnostic software, the remote upload of diagnostic data and vehicle real-time operation fault data can be realized, forming diagnostic experience through diagnostic cases, providing a data basis for subsequent development, and providing maintenance case support for maintenance technicians and engineers.

[0078] Embodiment 2

[0079] This embodiment is a further optimization based on Embodiment 1, and the specific content is as follows:

[0080] The diagnostic configuration database at least includes: maintaining diagnostic communication protocol files, configuration parameter files, flashing file packages, flashing software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files for all vehicles.

[0081] Furthermore: The diagnostic communication protocol file, configuration parameter file, flashing file package, flashing software package, calibration software package, calibration file package, self-learning program package, diagnostic software upgrade file package, and diagnostic software upgrade program file are internally managed by different sections, including: the module configuration parameter section, the module software flashing section, the module calibration and self-learning section, and the diagnostic instrument software management section, which can quickly and flexibly provide diagnostic files when the diagnostic instrument issues a diagnostic requirement.

[0082] Embodiment 3

[0083] This embodiment is a further optimization based on Embodiment 1 or 2, and its specific content is as follows:

[0084] The specific process for determining whether the diagnostic instrument or in-vehicle diagnostic software needs to be updated is as follows:

[0085] The cross-terminal diagnostic background server obtains the version number information of the in-vehicle diagnostic software or diagnostic instrument, and compares this version number information with the latest released version number in the background configuration management system to determine whether an update is required.

[0086] The vehicle configuration information includes at least: vehicle identification number, vehicle production date, vehicle model, module hardware information, and part number structure, which includes assembly number, hardware number, software number, and network number.

[0087] Preparing all diagnostic requirement files based on vehicle configuration parameters specifically means: The cross-terminal diagnostic background server matches the diagnostic communication protocol file and sets diagnostic communication parameters according to the vehicle identification number and the vehicle configuration information corresponding to the vehicle identification number, and queries the configuration parameter file, flashing file package, flashing software package, calibration file package, calibration software package, and self-learning program package.

[0088] The relevant diagnostic files issued meet the module parameter configuration requirements, module software flashing requirements, module calibration requirements, and module self-learning requirements.

[0089] The vehicle fault information transmitted back includes but is not limited to: vehicle fault time and location information, vehicle mileage information, vehicle internal communication message information, freeze frame and fault code information saved in the vehicle internal module, and the modification status of the current vehicle configuration parameters.

[0090] Embodiment 4

[0091] This embodiment is a further optimization based on Embodiment 1 or 2 or 3, and its specific content is as follows:

[0092] Generating a diagnostic test report specifically means: The cross-terminal diagnostic background server generates a diagnostic test report composed of the transmitted-back data, and performs fault analysis based on this diagnostic test report to form fault diagnosis experience and save it in the diagnostic experience database.

[0093] Example 5

[0094] As Figure 2 shown, a cross-platform diagnostic software configuration management and real-time data analysis system, which is used to execute the cross-platform diagnostic software configuration management and real-time data analysis method described in any one of Embodiments 1 to 4, includes: a cross-terminal diagnostic background server and a diagnostic instrument. The cross-terminal diagnostic background server establishes data interaction with the diagnostic instrument and the in-vehicle diagnostic module in the target vehicle respectively. The diagnostic instrument establishes data interaction with the in-vehicle diagnostic module in the target vehicle, and the in-vehicle diagnostic module runs the vehicle machine diagnostic software.

[0095] For the embodiments of the present invention, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

Claims

1. A cross-platform diagnostic software configuration management and real-time data analysis method, characterized in that: The steps include: S01. Construct a diagnostic configuration database in the cross-end diagnostic backend server; S02, the cross-end diagnosis backend server determines whether the diagnostic instrument or the vehicle computer diagnostic software needs to be updated, if yes, then enters S03, if no, then enters S04; S03, triggering the update prompt, issuing the update file after confirmation and updating the version of the diagnostic instrument or vehicle computer diagnostic software; S04, confirming the vehicle diagnosis requirement, reading the vehicle identification number and the vehicle configuration information corresponding to the vehicle identification number, and transmitting them to the cross-end diagnosis backend server; S05, determining whether the diagnostic demand comes from the diagnostic instrument, if yes, proceeding to S06, if no, proceeding to S07; S06, the diagnostic instrument reads the vehicle VIN code and sends it to the cross-end diagnostic backend server, and then enters S08; S07, the vehicle diagnostic software reads the vehicle VIN code and sends it to the cross-end diagnostic backend server; S08, the cross-end diagnosis backend server uses the VIN code to query the production system data to obtain various parameters of the vehicle; S09. Prepare all diagnostic requirement files according to vehicle configuration parameters; S10, the diagnostic instrument or vehicle diagnostic software is initialized to communicate with the vehicle module, and the diagnostic protocol file is issued; S11, determine whether it is a diagnostic instrument operation, if yes, go to S12, if no, go to S16; S12, manual input of diagnostic requirements; S13, the diagnosis demand is fed back to the cross-end diagnosis backend server; S14, sending relevant diagnostic files to the diagnostic instrument through the cross-end diagnostic backend server according to the diagnostic requirements; S15, the diagnostic instrument performs automatic operation according to the relevant diagnostic files and enters S19; S16, Web-side diagnostic instructions are sent; S17, sending relevant diagnostic files to the vehicle diagnostic software through the cross-end diagnostic backend server according to the diagnostic requirements; S18, the vehicle diagnostic software performs automatic operation according to the relevant diagnostic files and enters S19; S19, determine whether the parts need to be replaced, if yes, proceed to S20, if no, proceed to S21; S20, replace relevant parts according to the version number of the parts, and check whether the diagnosis requirement still exists. If yes, go to S04, if not, go to S21; S21, transmitting vehicle fault information; S22. Generate a diagnostic test report.

2. The cross-platform diagnostic software configuration management and real-time data analysis method according to claim 1, characterized in that: The diagnostic configuration database at least includes: diagnostic communication protocol files, configuration parameter files, flash file packages, flash software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files for maintaining all vehicles.

3. The cross-platform diagnostic software configuration management and real-time data analysis method according to claim 2, characterized in that: Diagnostic communication protocol files, configuration parameter files, flash file packages, flash software packages, calibration software packages, calibration file packages, self-learning program packages, diagnostic software upgrade file packages, and diagnostic software upgrade program files are internally managed by different sections, including: module configuration parameter section, module software flash section, module calibration and self-learning section diagnostic instrument software management section.

4. The cross-platform diagnostic software configuration management and real-time data analysis method according to claim 1, characterized in that: The specific process for determining whether the diagnostic instrument or vehicle diagnostic software needs to be updated is as follows: the cross-end diagnostic background server obtains the version number information of the vehicle diagnostic software or diagnostic instrument, and compares the version number information with the latest released version number of the background configuration management system to determine whether an update is needed.

5. The cross-platform diagnostic software configuration management and real-time data analysis method according to claim 2 or 3, characterized in that: The vehicle configuration information includes at least: vehicle identification number, vehicle production date, vehicle model, module hardware information, and part numbering structure, which includes assembly number, hardware number, software number, and network number.

6. The cross-platform diagnostic software configuration management and real-time data analysis method according to any one of claims 1 to 5, characterized in that: All diagnostic requirement files are prepared according to the vehicle configuration parameters: the cross-end diagnostic background server matches the diagnostic communication protocol file and sets the diagnostic communication parameters according to the vehicle identification number and the vehicle configuration information corresponding to the vehicle identification number, and queries the configuration parameter file, flash file package, flash software package, calibration file package, calibration software package, and self-learning program package.

7. The cross-platform diagnostic software configuration management and real-time data analysis method according to any one of claims 1 to 5, characterized in that: The relevant diagnostic files issued meet the module parameter configuration requirements, module software flashing requirements, module calibration requirements, and module self-learning requirements.

8. The cross-platform diagnostic software configuration management and real-time data analysis method according to any one of claims 1 to 5, characterized in that: The returned vehicle fault information includes but is not limited to: vehicle fault time and location information, vehicle mileage information, vehicle internal communication message information, freeze frame and fault code information saved by the vehicle's internal module, and modification status of the current vehicle configuration parameters.

9. The cross-platform diagnostic software configuration management and real-time data analysis method according to any one of claims 1 to 5, characterized in that: Generating a diagnostic test report specifically includes: the cross-end diagnostic backend server generates a diagnostic test report consisting of the returned data, and performs fault analysis based on the diagnostic test report to form fault diagnosis experience and save it in a diagnostic experience database.

10. A cross-platform diagnostic software configuration management and real-time data analysis system, characterized in that: Used to execute the cross-platform diagnostic software configuration management and real-time data analysis method as described in any one of claims 1 to 9, including: a cross-end diagnostic background server and a diagnostic instrument, the cross-end diagnostic background server establishes data interaction with the diagnostic instrument and the on-board diagnostic module in the target vehicle respectively, the diagnostic instrument establishes data interaction with the on-board diagnostic module in the target vehicle, and the on-board diagnostic module runs the vehicle diagnostic software.

Images