Interactive diagnostic system, diagnostic method and storage medium
Through the design of an interactive diagnostic system, combined with data acquisition, analysis and logical reasoning modules, the problems of insufficient diagnostic accuracy and cross-system fault monitoring capabilities in the existing technology are solved, and efficient and accurate fault diagnosis and software configuration management are achieved. Reduces the risk of human operational errors.
Patent Information
- Application Number
- CN202210910432.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-29
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2042-07-29
AI Technical Summary
Existing automotive diagnostic equipment has shortcomings in diagnostic accuracy and cross-system fault monitoring and analysis capabilities, especially the location and description of systemic complex faults are not accurate enough, and there is a risk of miswrite or misbrushing operations based on human operations.
An interactive diagnostic system was designed, including diagnostic equipment, data conversion box, security gateway, electronic control unit and diagnostic backend server. Through data acquisition, data analysis, logical reasoning and human-computer interaction modules, the fault information is achieved in all aspects. Three-dimensional, multi-dimensional analysis and judgment, combined with historical fault diagnosis and recording and probability calculation, provides diagnostic results and solutions, and has software verification and matching and configuration management functions.
It improves the accuracy and efficiency of complex cross-system function fault diagnosis, reduces the diagnostic error rate, ensures the correctness of software configuration and data security, and enhances the independent analysis capabilities and user rights management of the diagnostic system.
Smart Images

Figure CN115373366B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of automobile fault diagnosis, and more specifically, relates to an interactive diagnosis system, a diagnosis method and a storage medium. Background Art
[0002] As the degree of automobile electrification and intelligent networking increases, the complexity of automobile functions increases day by day. How to ensure the normal use of various functions of the automobile throughout its life cycle has always been a problem that automobile companies pay close attention to and a difficult problem. Modern diagnostic technology is also developing rapidly with the strong demand of customers and manufacturers. From the early days of relying entirely on the experience accumulation of maintenance technicians or engineers, to the current experience and test verification methods, to the future of fully intelligent diagnosis, the comprehensive application of various technologies such as personnel experience, logical strategies, and big data, and continuous learning and training iterations, the development goal of modern diagnostic technology is to make the diagnostic process efficient and convenient, and the diagnostic results accurate, to create worry-free car services for customers, to realize modern system capabilities for manufacturers, efficient after-sales guarantee teams, and low-cost market maintenance expenses.
[0003] There are now vehicle diagnostic equipment or devices for market models or professional brands on the market, which are usually called decoders in the industry. It has shown great advantages over the relatively single-function instruments such as multimeters and oscilloscopes in the early days. It can interact with the electronic control unit on the vehicle through communication protocol data based on CAN bus, Ethernet, LIN bus, etc., and read the fault information and status data stored in the self-diagnosis system of each electronic control unit of the vehicle; it makes the past fuzzy description of fault phenomena progress to intuitive and visible fault information and real-time readable key status data. However, through actual usage feedback, it still has the problem of low diagnostic accuracy. Its biggest shortcoming is the lack of analysis and judgment of the logic at the vehicle architecture level. It still takes the self-diagnosis system of each ECU as the core monitoring scope. The diagnostic accuracy of its own small cycle area is relatively high, and the monitoring and analysis ability of cross-system functional fault failure is obviously insufficient. The description of fault information, especially for systemic complex faults, is still based on the phenomenon monitoring feedback of a local feature, which is the fundamental reason that cannot be located. Therefore, there is a saying in the industry that states the helplessness and defects of the current situation: the presence of a fault code does not necessarily mean that there is a real fault.
[0004] The current diagnostic equipment has three limitations. First, it completely relies on the self-diagnosis capability of each electronic control unit. The stronger the self-diagnosis capability of each electronic control unit, the higher the diagnostic accuracy of its own system and the higher the coverage of the diagnosable capability. The weaker the self-diagnosis capability, the poorer the diagnostic accuracy and the lower the coverage of the diagnostic function. Second, it is independent of each other, lacks related interaction, and lacks logical verification analysis. The main diagnostic equipment in the current industry is at best what everyone calls a decoder, which only serves as a tool, similar to the role of a radio station. It only directly translates the telegram, and still requires very experienced translators to annotate, analyze, judge and solve according to experience and event background. Third, the diagnostic equipment and diagnostic system are relatively closed, and mainly rely on manual operation, including writing relevant configuration data, flashing execution operations, etc. There is a lack of management and judgment on the accuracy of the written content and the correctness evaluation of the test content, and there is a certain risk of wrong writing and wrong flashing operations. Summary of the invention
[0005] In view of the above defects or improvement needs of the prior art, the present invention provides an interactive diagnostic system and a diagnostic method, which make the system verification logic visualized and have responsive feedback, while greatly ensuring the accuracy of write refresh data and the accuracy of fault analysis and judgment.
[0006] To achieve the above-mentioned object, according to one aspect of the present invention, there is provided an interactive diagnostic system, comprising a diagnostic device, a data conversion box, a security gateway, an electronic control unit, and a diagnostic background server, wherein the diagnostic device is communicatively connected to the data conversion box, the data conversion box is communicatively connected to the security gateway, the security gateway is connected to the electronic control unit, and the diagnostic background server is communicatively connected to the diagnostic device;
[0007] The diagnostic equipment includes a data acquisition module, a data analysis module, a logic reasoning module, a human-computer interaction module, and a log management module, wherein:
[0008] The data acquisition module is used to collect fault information recorded by each electronic control unit of the vehicle and send it to the data analysis module;
[0009] The data analysis module is used to query and retrieve historical fault diagnosis records in the fault diagnosis database, calculate the fault similarity probability, sort the fault diagnosis records according to the fault similarity probability, and push them to the logic reasoning module in sequence;
[0010] The logic reasoning module is used to analyze and evolve the fault diagnosis record until the actual fault cause is determined, and send the fault cause and solution to the human-computer interaction module;
[0011] The human-computer interaction module is used to receive user input information and display fault diagnosis results;
[0012] The log management module is used to record fault diagnosis records, generate diagnostic logs, store and manage them by vehicle type classification, and update the fault diagnosis database.
[0013] Furthermore, the log management module includes a special vehicle log storage unit and a civilian vehicle log storage unit, the special vehicle log storage unit is provided with a local data interface, and the special vehicle log storage unit is used to store the diagnostic log of the special vehicle diagnostic operation; the civilian log storage unit is communicatively connected to the diagnostic background server, and the civilian vehicle log storage unit is used to store the diagnostic log of the civilian vehicle diagnostic operation.
[0014] Furthermore, the diagnostic device also includes a software verification and matching module for verifying and matching the software version of the automobile-associated electronic control unit.
[0015] Furthermore, the diagnostic device also includes an offline diagnostic configuration module, which is communicatively connected to the MES system of the manufacturing enterprise, and is used to associate the configuration content with the vehicle model and write the configuration information according to the offline configuration requirements of the associated vehicle model.
[0016] According to another aspect of the present invention, an interactive diagnosis method is provided, which is implemented by using the above-mentioned interactive diagnosis system, and the method comprises the following steps:
[0017] S100: Establishing a communication connection between the diagnostic device and the vehicle safety gateway, and logging into the diagnostic system;
[0018] S200: The data acquisition module collects the fault information recorded by each electronic control unit of the vehicle through the security gateway and sends it to the data analysis module;
[0019] S300: The data analysis module retrieves historical fault diagnosis records of similar vehicle models in the fault diagnosis database according to the fault information, calculates the fault similarity probability, and sorts the historical fault diagnosis records according to the fault similarity probability;
[0020] S400: The data analysis module pushes the historical fault diagnosis record with the highest probability of fault similarity in the sorting to the logic reasoning module, and removes it from the sorting;
[0021] S500: the logic reasoning module analyzes and evolves the pushed historical fault diagnosis records to determine whether the pushed fault cause is the actual fault cause. If so, the fault cause and solution are sent to the human-computer interaction module. If not, return to S400.
[0022] S600: The log management module records the fault diagnosis record, generates a diagnostic log, stores and manages it by vehicle type, and updates the fault diagnosis database.
[0023] Furthermore, the process of logging into the diagnostic system in S100 also includes the security gateway verifying the identity information of the diagnostic device, and entering the diagnostic system after successful verification.
[0024] Furthermore, S100 also includes, after entering the diagnostic system, selecting a diagnostic level, wherein the diagnostic level is conventional diagnosis or advanced diagnosis; when conventional diagnosis is selected, starting conventional diagnostic operations; when advanced diagnosis is selected, verifying the user's authority level, and starting advanced diagnostic operations if the verification is successful.
[0025] Furthermore, the calculation of the fault similarity probability in S300 adopts the following calculation formula:
[0026] Similarity probability = vehicle model similarity + controller similarity + cause DTC similarity + associated DTC similarity + mileage similarity
[0027] Furthermore, updating the fault diagnosis database in S600 includes correcting the pushed historical fault diagnosis records according to the matching degree between the pushed historical fault diagnosis records and the actual fault causes.
[0028] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the interactive diagnosis method as described above is implemented.
[0029] In general, the above technical solutions conceived by the present invention can achieve the following beneficial effects compared with the prior art:
[0030] 1. The present invention parameterizes the logic analysis function, connects the related data, and accumulates each successful analysis case in a parameterized manner. When performing fault diagnosis, an interactive analysis method is used to analyze and judge step by step. Through all-round, three-dimensional, and multi-dimensional reasoning analysis and logical judgment, the accuracy and efficiency of complex cross-system functional fault diagnosis are effectively improved.
[0031] 2. The present invention has the functions of evolutionary learning and evolution database and probability calculation guidance. It can automatically query and retrieve the historical fault diagnosis database according to the fault information of the vehicle, sort it according to the similarity of the fault information, and provide the final diagnosis result and maintenance plan as a reference. The past maintenance cases, the same type of faults, and the fault cases of the same model are truly and effectively utilized, and the probability is sorted through a series of calculations, and the solution is actively pushed, which greatly improves the efficiency of diagnosis, analysis and positioning. After the diagnosis is completed, the database is also updated, enriched, and continuously upgraded to improve the accuracy of fault diagnosis.
[0032] 3. The present invention solves the compatibility problem between special off-road vehicles and civilian vehicles, and develops different API interface applications. The special vehicle diagnostic data storage only has an internal storage API interface, and all operation trace data is stored in the local disk; the civilian vehicle API interface connects to the background server and the enterprise remote diagnosis client, and can perform remote data retrieval and data transmission support. The two are independent of each other in diagnostic data transmission and log management, while ensuring the data confidentiality requirements of special vehicles and the remote diagnosis needs of civilian vehicles.
[0033] 4. The diagnostic system of the present invention has a cross-system software matching and verification function, which solves the problems of version mismatch, function loss or function abnormality that occur during the software flashing process in the current industry, and ensures that the flashing is safe and reliable.
[0034] 5. The diagnostic system of the present invention is connected with the production management system, and by integrating the vehicle hardware configuration list and software function configuration business requirements, strong correlation management is achieved, and the configuration task management component is automatically generated. The configuration operation process is completed with one click. After the configuration job is completed, the configuration operation completion list is automatically printed and generated. The database storage can be traced back at any time, and an associated mutually exclusive configuration checking function is provided to prevent configuration errors.
[0035] 6. The diagnostic system of the present invention has an identity authentication function. The security gateway verifies the identity of the diagnostic device during the login process, and verifies the user's permission level when performing advanced diagnostic operations, thereby ensuring the legitimacy of the user of the diagnostic device and the equivalence of the permission level. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 It is a structural schematic diagram of an interactive diagnostic system in a specific implementation mode of the present invention;
[0037] Figure 2 It is an internal architecture diagram of an interactive diagnostic system in a specific implementation mode of the present invention;
[0038] Figure 3 It is a workflow diagram of the log management module in a specific implementation manner of the present invention;
[0039] Figure 4 It is a working flow chart of the offline diagnosis configuration module in a specific implementation mode of the present invention;
[0040] Figure 5 It is a flow chart of an interactive diagnosis method in a specific implementation manner of the present invention. DETAILED DESCRIPTION
[0041] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.
[0042] like Figure 1 As shown, the present invention provides an interactive diagnostic system, which is divided into three parts as a whole. The terminal includes a diagnostic device and a data conversion box. The vehicle end includes various electronic control units and a security gateway. The cloud end includes a diagnostic background server and a manufacturing enterprise MES system. The diagnostic device has the following external communication interfaces: WiFi, Bluetooth, Ethernet, 5G, and 4G. The diagnostic device is connected to the data conversion box VCI via Bluetooth, WiFi, and Ethernet. The diagnostic device is connected to the diagnostic background server via 4G and 5G links. The data conversion box VCI is communicatively connected to the security gateway, and the security gateway is connected to each electronic control unit via a CAN bus. The internal architecture diagram of the interactive diagnostic system is shown in FIG. Figure 2 shown.
[0043] The diagnostic equipment includes a data acquisition module, a data analysis module, a logic reasoning module, a human-computer interaction module, a log management module, a software verification and matching module, and an offline diagnosis configuration module.
[0044] The data acquisition module is used to exchange data with the vehicle's electronic control unit through the security gateway, collect fault information recorded by each electronic control unit of the vehicle, and send it to the data analysis module.
[0045] The data analysis module is used to retrieve historical fault diagnosis records of similar vehicle models in the fault diagnosis database according to the fault information, calculate the fault similarity probability, sort the fault diagnosis records according to the fault similarity probability, and push them to the logical reasoning module in sequence.
[0046] The logic reasoning module is used to analyze and evolve the pushed fault diagnosis record until the actual fault cause is determined and sent to the human-computer interaction module.
[0047] The human-computer interaction module is used to receive user input information, including login information and query information, and display fault diagnosis results.
[0048] The log management module is used to record fault diagnosis records, generate diagnostic logs, store and manage them according to the categories of special vehicles and civilian vehicles, and update the fault diagnosis database.
[0049] The log management module is divided into a special vehicle log storage unit and a civilian vehicle log storage unit, which are independent of each other. This is to make the two systems compatible. Special vehicles are the enterprise's door-to-door maintenance service system. Due to confidentiality requirements, local storage requirements must be strictly implemented; civilian vehicles are mainly vehicle in-station maintenance service systems. In order to improve maintenance efficiency and reduce after-sales maintenance operating costs, remote diagnosis technology support and other scenarios are widely used. Figure 3 As shown, the special vehicle log storage unit reserves a local USB data collection port, and the local USB interface uses a whitelist verification method for authentication, which is convenient for local transfer and centralized analysis and processing of diagnostic data. For civilian models, the remote diagnosis needs and the accumulation of big data diagnostic analysis require high timeliness, so the civilian vehicle log storage unit is connected to the diagnostic background server, and the diagnostic background server is used to capture and analyze big data, and the cloud synchronization module is used to achieve fast data synchronization.
[0050] The software verification and matching module is used to verify and match the software version of the electronic control unit of the automobile-related system.
[0051] There are usually very extensive connections between the automotive instrument system and other systems, and there are extensive software and communication signal connections in applications such as status display, warning light indication, and function switching.
[0052] In the actual vehicle development process, or even after the vehicle is launched on the market, functional failures caused by software adaptation often occur. The software matching relationship of the related systems is very important. Due to the cumbersomeness of software management, new functional failures are often caused by flashing the wrong software version.
[0053] The function of the software verification and matching module is to ensure the correctness of the flash software upgrade by sorting out the associations between the systems.
[0054] Take the following subsystem as an example:
[0055] BCM: body system controller; IC: instrument; IVI: intelligent information multimedia system; TPMS: tire pressure monitoring system;
[0056] There are three rules for software versions between subsystems:
[0057] One is that they completely match each other, one is that they do not match and are mutually exclusive, and one is that the higher version is compatible with the lower version and can be used universally.
[0058] Based on the above three relationships, the following mapping table is established:
[0059] Serial number / controller name BCM IC TPMS IVI Software version 1 V1.1_BCM V1.2_IC V1.2_TPMS V1.3_IVI Software version 2 V1.2_BCM V1.3_IC V1.3_TPMS V1.4_IVI Software version 3 / / V1.4_TPMS V1.5_IVI
[0060] Define the same-generation version characteristic code TQBB, and verify the same-generation version characteristic code when performing software upgrade on any of the above controllers.
[0061] For example, by reading the same period version of BCM at this stage, the code is TQBB=1;
[0062] Flash IVI and select the IVI version as V1.3_IVI;
[0063] For example, by reading the same period version of BCM at this stage, the code is TQBB=2;
[0064] Flash IVI and select the IVI version as V1.4_IVI;
[0065] For example, if the software version of the TPMS read is the synchronous software version 3, then when performing IVI flashing, it will remind that the flashing version is V1.5_IVI, which is a detailed compatible version. If the flashing fails, it can be returned to the synchronous software version 2 for dimensionality reduction flashing.
[0066] When performing diagnostic operations for software upgrades, the diagnostic system ensures the integrity and correctness of the application software data package by performing application data package signature verification on the security gateway end.
[0067] The offline diagnostic configuration module is connected to the manufacturing enterprise MES system for managing the association between configuration content and vehicle models, and writing configuration information according to the offline configuration requirements of the associated vehicle models. The offline diagnostic configuration module formulates a list of offline diagnostic work tasks based on the offline configuration and monitoring requirements of the production, automatically binds the configuration content with the vehicle model configuration, writes it with one click and reads it back for verification, and eliminates errors caused by manual item-by-item click operations.
[0068] like Figure 4 As shown in the figure, the offline diagnosis configuration process is as follows: the manufacturing enterprise MES system allocates the VIN code information of the daily production model, allocates the model information association database, allocates the model offline configuration business operation requirement database, and provides the model VIN code to the offline diagnosis configuration module; the offline diagnosis configuration module reads the model information QR code, retrieves the associated model configuration information, generates the model configuration business requirement, writes the configuration information, sends the configuration information back to the manufacturing enterprise MES system for verification, and generates the offline diagnosis configuration work log.
[0069] The following is an example of vehicle configuration differences:
[0070] Software Configuration Configuration 1# Configuration 2# Configuration 3# Configuration 4# Configuration 5# Configuration 6# Fuel tank configuration Main + Secondary Main tank only Main tank only Main tank only Main + Secondary Main + Secondary Braking system configuration ABS ABS ABS ESC ABS ABS 360-degree view none none have have have none FWCU none none have have have none Night Vision System none none have have have none Whether it has a power generation system none none none none have have Door configuration Single row Single row Single row Single row Single row Single row Fuel heating have none none none none none
[0071] The corresponding offline diagnostic configuration operation requirement mapping table is as follows:
[0072]
[0073]
[0074] like Figure 5 As shown, the present invention also provides an interactive diagnosis method for fault diagnosis using the above interactive diagnosis system, comprising the following steps:
[0075] 1. Establish a communication connection between the diagnostic device and the vehicle safety gateway, and log in to the diagnostic system.
[0076] The diagnostic device establishes a communication connection with the vehicle safety gateway through the data conversion box. The user enters the login information through the human-computer interaction module. The diagnostic device sends a login request with identity information to the safety gateway. The safety gateway verifies the identity information of the diagnostic device. If the verification is successful, the user successfully logs into the diagnostic system. Otherwise, the user is denied login. The authentication process of the diagnostic device by the safety gateway ensures the legitimacy of the user of the diagnostic system.
[0077] In order to ensure the equality of the user authority levels of the diagnostic system, the diagnostic system manages user authority in a hierarchical manner. After the user logs in to the diagnostic system, he / she selects the diagnostic level. When the user needs to perform ordinary diagnosis, he / she can directly perform the diagnostic operation by selecting conventional diagnosis; when the user needs to perform high-level diagnostic operations such as action testing and software upgrades, he / she can select advanced diagnosis. The security gateway will verify the user's authority level. Only when the user has the authority to perform advanced diagnostic operations can he / she perform advanced diagnostic operations.
[0078] 2. The data acquisition module collects the fault information recorded by each electronic control unit of the vehicle through the security gateway and sends it to the data analysis module.
[0079] Each diagnostic operation will scan the entire vehicle system for fault codes (DTCs) and collect fault information recorded by each electronic control unit of the vehicle.
[0080] 1) When performing diagnostic operations on a vehicle coded as A1, the results of scanning the vehicle fault information are as follows:
[0081] DTC list: P1XXX87, P1XXX35, P1XXX34, P1XXX11, etc.
[0082] 2) When performing diagnostic operations on a vehicle coded as A2, the results of the vehicle fault information scan are as follows:
[0083] DTC list: P1XXX87, P1XXX35, P1XXX34, P1XXX14, etc.
[0084] 3) When performing diagnostic operations on a vehicle coded as A3, the results of the vehicle fault information scan are as follows:
[0085] DTC list: P1XXX87, P1XXX35, P1XXX34, P1XXX14, etc.
[0086] -------Data accumulation;
[0087] Similarity List overlap / maximum number of DTC lists
[0088] 3. The data analysis module retrieves the historical fault diagnosis records of similar models in the fault diagnosis database based on the fault information, calculates the fault similarity probability, and sorts the fault diagnosis records according to the fault similarity probability.
[0089] The fault diagnosis database stores fault diagnosis records of the historical diagnosis process, including fault causes and solutions, etc., which are sorted and classified according to categories such as fault information of the same model, fault information of the same controller, and multiple occurrences of the same model.
[0090] After each diagnostic process is completed, the fault causes in the fault diagnosis database are correlated and weighted. If the actual fault cause matches a certain DTC description very well, it is defined as a causal DTC. If the DTC deviates from the actual fault cause, the DTC is a general associated DTC. The causal DTC takes a weighting coefficient of K1, and the general associated DTC takes a weighting coefficient of K2.
[0091] DTC correlation degree ∮=Cause DTC*K1+Related DTC*K2
[0092] Statistical compensation is calculated for the frequency of failures and the first mileage time of failures. For failures with high frequency, the probability coefficient is weighted by K1.
[0093] The probability of each failure factor is calculated according to the following formula:
[0094] Fault cause probability = vehicle model characteristics + controller characteristics + cause DTC*K1 + related DTC*K2 + mileage regularity characteristics + frequency characteristics
[0095] The data analysis module retrieves the historical fault diagnosis records of similar models in the fault diagnosis database, including the vehicle's own historical diagnosis records, based on the vehicle fault code DTC reading scan results and fault phenomenon keywords (such and such system failure or fault light on), and calculates the fault similarity probability using the following formula:
[0096] Similarity probability = vehicle model similarity + controller similarity + cause DTC similarity + related DTC similarity + mileage similarity.
[0097] 4. The data analysis module sends the fault diagnosis record with the highest probability of fault similarity in the sorting to the logical reasoning module and removes it from the sorting.
[0098] 5. The logical reasoning module analyzes and evolves the pushed historical fault diagnosis records to determine whether the pushed fault cause is the actual fault cause. If so, the fault cause and solution are sent to the human-computer interaction module for display. If not, return to the previous step.
[0099] The data analysis module exchanges information with the logic reasoning module. The data analysis module actively pushes historical fault diagnosis records to the logic reasoning module according to the probability of fault similarity. That is, the historical fault diagnosis record with the highest probability of fault similarity is pushed first, including the cause of the fault and the solution. The logic reasoning module receives the historical fault diagnosis record with the highest similarity probability and implements the solution. If the fault is eliminated, the pushed fault cause is determined to be the actual fault cause. Otherwise, it is fed back to the data analysis module that it is not the fault cause. The data analysis module then pushes the historical fault diagnosis record with the next highest similarity probability, and so on, until the actual fault cause is determined.
[0100] After the actual cause of the fault is determined, the logic reasoning module sends the cause of the fault and the solution to the human-computer interaction module, which displays it.
[0101] 6. The log management module records the fault diagnosis record, generates a diagnostic log, and stores and manages it according to the categories of special vehicles and civilian vehicles, and updates the fault diagnosis database.
[0102] In order to be compatible with the data security requirements and actual characteristics of special vehicles and civilian vehicles, users have separated special vehicles from civilian vehicles when selecting models. When diagnosing special vehicles, for example, when entering the J-use model diagnostic operation for a model code J-001, the diagnostic log will be transmitted through the internal database storage area interface associated with the model diagnostic software APK. All diagnostic data will be stored in the local EPROM, following the first-in-first-out principle. When the storage space exceeds the upper limit, the earliest historical data will be erased and overwritten. For civilian models M-001, 002, 003, etc., independent APK access channels are used, and the diagnostic logs of all diagnostic operations will be stored in another local EPROM through the internal database storage area interface associated with the model APK, fundamentally isolating the physical data from the J-use model.
[0103] The log management module synchronizes the fault diagnosis record to the fault diagnosis database and performs reverse verification based on the final diagnosis result, that is, the pushed historical fault diagnosis record is corrected according to the matching degree between the pushed historical fault diagnosis record and the actual fault cause. If it matches the fault diagnosis record pushed by similarity probability 1, the fault diagnosis record pushed by similarity probability 1 is corrected by positive compensation %Δt; if the fault diagnosis record pushed by similarity probability 1 has a certain correlation with the actual fault cause but the correlation is not strong, the reverse reduction probability correction -%Δt is taken; if the fault diagnosis record pushed by similarity probability 1 has almost no correlation with the actual fault cause, the reverse reduction probability correction -%2Δt is taken.
[0104] The present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, all or part of the steps of the interactive diagnostic method described above are implemented. The computer-readable storage medium includes a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), and other media that can carry computer program codes.
[0105] Embodiment 1
[0106] The interactive diagnostic method of the present invention is used to diagnose the following faults:
[0107] Fault phenomenon: The instrument shows that the vehicle speed signal is an idle value, and the ABS system fault warning light is not on.
[0108] The diagnostic system automatically retrieves the fault information recorded by each electronic control unit of the vehicle. Only the instrument records the ABS signal loss fault, and there is no fault information recorded for the ABS and gateway.
[0109] In response to the above information, the system automatically feeds back the following information: vehicle CAN bus network architecture topology diagram, ABS controller signal list and signal flow diagram.
[0110] The user enters the key words of the fault phenomenon: the instrument does not display the vehicle speed value, the ABS fault warning light is not on; other information is displayed normally. Select the characteristics of the fault phenomenon: occurs after long-term use, occasionally, and on continuous rainy days.
[0111] The system analyzes the speed message from the instrument to the ABS. The speed message is forwarded to the instrument through the body network segment gateway. The instrument parses it. If there is no display, it is prioritized according to the connection of the ABS bus harness, gateway harness, ABS controller, instrument, and gateway controller.
[0112] The cause of the fault was determined through step-by-step deduction: the ABS warning light did not light up, and the problem with the ABS controller itself was preliminarily ruled out; clicking on the data stream query, the ABS vehicle speed data stream was normal; the virtual action test instrument speedometer, the instrument tachometer feedback was normal; the fault reappeared, clicking on the vehicle body CAN bus data monitoring, it was found that the vehicle speed message was missing; it was determined to be a problem with the wiring harness connection from the gateway to the instrument end. After investigation, the root wiring harness of the connector at the gateway CAN bus connection was cracked and accompanied by obvious water stains.
[0113] After repairing the wiring harness, the fault disappeared immediately.
[0114] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. An interactive diagnostic system, It is characterized in that It includes a diagnostic device, a data conversion box, a security gateway, an electronic control unit, and a diagnostic background server. The diagnostic device is connected to the data conversion box in communication, the data conversion box is connected to the security gateway in communication, the security gateway is connected to the electronic control unit, and the diagnostic background server is connected to the diagnostic device in communication; The diagnostic equipment includes a data acquisition module, a data analysis module, a logic reasoning module, a human-computer interaction module, and a log management module, wherein: The data acquisition module is used to collect fault information recorded by each electronic control unit of the vehicle and send it to the data analysis module; The data analysis module is used to retrieve historical fault diagnosis records of similar models in the fault diagnosis database according to the fault information, calculate the fault similarity probability, sort the fault diagnosis records according to the fault similarity probability, and push them to the logic reasoning module in sequence; The similarity probability = vehicle model similarity + controller similarity + cause DTC similarity + associated DTC similarity + mileage similarity, After each diagnosis process, the fault causes in the fault diagnosis database are weighted. If the actual fault cause has a high matching degree with a certain DTC description, it is defined as the cause DTC. If the DTC deviates from the actual fault cause, the DTC is the associated DTC. The cause DTC takes the weight coefficient K1, and the associated DTC takes the weight coefficient K2. DTC correlation degree ∮=cause DTC*K1+related DTC*K2; The logic reasoning module is used to analyze and evolve the pushed fault diagnosis records until the actual fault cause is determined, and send the fault cause and solution to the human-computer interaction module. Otherwise, it feeds back to the data analysis module a fault diagnosis record that is not the fault cause, and the data analysis module pushes the historical fault diagnosis record with the next highest similarity probability, and so on, until the actual fault cause is determined; The human-computer interaction module is used to receive user input information and display fault diagnosis results; The log management module is used to record fault diagnosis records, generate diagnostic logs, store and manage them by vehicle type classification, and update the fault diagnosis database.
2. The interactive diagnostic system according to claim 1, Features: The log management module includes a special vehicle log storage unit and a civilian vehicle log storage unit. The special vehicle log storage unit is provided with a local data interface, and the special vehicle log storage unit is used to store the diagnostic log of the special vehicle diagnostic operation; the civilian vehicle log storage unit is communicatively connected to the diagnostic background server, and the civilian vehicle log storage unit is used to store the diagnostic log of the civilian vehicle diagnostic operation.
3. The interactive diagnostic system according to claim 1, Features: The diagnostic device also includes a software verification and matching module, which is used to verify and match the software version of the automobile-related electronic control unit.
4. An interactive diagnostic system according to any one of claims 1 to 3, Features: The diagnostic device also includes an offline diagnostic configuration module, which is communicatively connected to the manufacturing enterprise's MES system and is used to associate configuration content with vehicle models and write configuration information according to offline configuration requirements of the associated vehicle models.
5. An interactive diagnostic method, It is characterized in that The interactive diagnostic system according to any one of claims 1 to 4 is used to implement the method, wherein the method comprises the following steps: S100: Establishing a communication connection between the diagnostic device and the vehicle safety gateway, and logging into the diagnostic system; S200: The data acquisition module collects the fault information recorded by each electronic control unit of the vehicle through the security gateway and sends it to the data analysis module; S300: The data analysis module retrieves historical fault diagnosis records of similar vehicle models in the fault diagnosis database according to the fault information, calculates the fault similarity probability, and sorts the historical fault diagnosis records according to the fault similarity probability; S400: The data analysis module pushes the historical fault diagnosis record with the highest probability of fault similarity in the sorting to the logic reasoning module, and removes it from the sorting; S500: the logic reasoning module analyzes and evolves the pushed historical fault diagnosis records to determine whether the pushed fault cause is the actual fault cause. If so, the fault cause and solution are sent to the human-computer interaction module. If not, return to S400. S600: The log management module records the fault diagnosis record, generates a diagnostic log, stores and manages it by vehicle type, and updates the fault diagnosis database.
6. The interactive diagnostic method according to claim 5, Features: The process of logging into the diagnostic system in S100 also includes the security gateway verifying the identity information of the diagnostic device, and entering the diagnostic system after successful verification.
7. The interactive diagnostic method according to claim 6, Features: S100 also includes, after entering the diagnostic system, selecting a diagnostic level, wherein the diagnostic level is conventional diagnosis or advanced diagnosis; when conventional diagnosis is selected, starting conventional diagnostic operation; when advanced diagnosis is selected, verifying the user's authority level, and starting advanced diagnostic operation if the verification is successful.
8. The interactive diagnostic method according to claim 5, Features: The calculation of the fault similarity probability in S300 adopts the following calculation formula: Similarity probability = vehicle model similarity + controller similarity + cause DTC similarity + associated DTC similarity + mileage similarity.
9. The interactive diagnostic method according to claim 5, Features: The updating of the fault diagnosis database in S600 includes correcting the pushed historical fault diagnosis records according to the matching degree between the pushed historical fault diagnosis records and the actual fault causes.
10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the interactive diagnostic method according to any one of claims 5 to 9 is implemented.
