Vehicle fault diagnosis system and method capable of configuring and modifying fault judgment rules

By introducing rule maintenance modules and fault level division into the vehicle fault diagnosis system, the problem of inflexible fault judgment in the prior art is solved, and more accurate and safe fault judgment is achieved.

CN114859871BActive Publication Date: 2024-11-22CHONGQING CHANGAN TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202210589397.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-05-27
Publication Date
2024-11-22
Estimated Expiration
2042-05-27

AI Technical Summary

Technical Problem

The existing vehicle fault diagnosis system has fewer diagnostic basis, and the fault determination rules cannot be flexibly adjusted according to the real-time situation of the vehicle, resulting in insufficient diagnosis.

Method used

A vehicle fault diagnosis system including data processing module, fault judgment module, rule maintenance module and alarm notification module is designed. The fault judgment rules are adjusted according to the real-time situation of the vehicle through the rule maintenance module, and the rules are ensured through fault level classification and audit processing. Rationality and effectiveness.

Benefits of technology

It realizes the flexibility and accuracy of fault judgment, and can dynamically adjust fault judgment rules based on different models and fault conditions, reduce the burden of manual review, and improve the accuracy and safety of fault judgment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114859871B_ABST
    Figure CN114859871B_ABST
Patent Text Reader

Abstract

This invention discloses a vehicle fault diagnosis system and method with configurable and modifiable fault judgment rules. The system includes a data processing module, a fault judgment module, a rule maintenance module, and an alarm notification module. The data processing module uploads vehicle-side signals to the cloud in real time and caches fault-related data according to the configuration required for fault diagnosis. The fault judgment module listens for and receives fault-related data and performs fault judgment based on the fault judgment rules in the rule maintenance module. The rule maintenance module adds or modifies fault judgment rules and fault notification rules. The alarm notification module receives the fault judgment results, determines the fault level and fault information sending method according to the fault notification rules, and outputs the fault judgment results to the front end, which is a vehicle-mounted terminal and / or a web page and / or a mobile phone terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of vehicle fault monitoring, and in particular relates to a vehicle fault diagnosis system and method capable of configuring and modifying fault judgment rules. Background Art

[0002] With the development and maturity of Internet of Vehicles technology, traditional vehicle diagnostic technology, that is, after a vehicle breaks down, it goes to a 4S shop, where maintenance staff use local diagnostic equipment to diagnose the fault and then repair it. Such a maintenance process takes time and money to make it difficult for car owners to be satisfied.

[0003] At present, most of the vehicle fault diagnosis schemes are based on vehicle-side module calculations, and the calculation results are directly output in the form of DTC fault codes, signal lights, fault information, etc., and then corresponding processing measures are made according to these result data. For example, the Chinese patent with publication number 113821875 discloses a real-time prediction method and system for intelligent vehicle faults based on end-cloud collaboration; the method includes: step 1, collecting the original data of n systems of the intelligent vehicle during operation; step 2, performing real-time prediction training through the CNN-LSTM prediction model deployed in the cloud, obtaining a single system remaining service life prediction model corresponding to each system, and sending it to the vehicle side; step 3, through the trained single system remaining service life prediction model, the vehicle side obtains the predicted remaining service life of the kth system in real time, k=1...,n; step 4, according to the predicted remaining service life corresponding to each of the k systems, the remaining service life of the whole vehicle is obtained through the series-parallel system remaining service life prediction model.

[0004] The above vehicle fault prediction mainly obtains real-time data of the vehicle from multiple systems on the vehicle side through the cloud, and then performs prediction training through the cloud to determine the service life of each system, and obtains the predicted remaining service life based on the service life. This kind of diagnosis is only based on the system life, with less diagnostic basis, and the fault judgment rules cannot be changed according to the real-time situation of the vehicle, and the judgment method is not flexible enough. Summary of the invention

[0005] In view of the above-mentioned deficiencies in the prior art, the technical problem to be solved by the present invention is: how to provide a vehicle fault diagnosis system and method with flexible fault determination and simple determination method.

[0006] In order to solve the above technical problems, the present invention adopts the following technical solutions:

[0007] A vehicle fault diagnosis system capable of configuring and modifying fault judgment rules, characterized in that it comprises a data processing module, a fault judgment module, a rule maintenance module and an alarm notification module, wherein the data processing module is used to cache fault-related data according to the configuration required for fault diagnosis after uploading the vehicle-side signal to the cloud in real time; the fault judgment module is used to monitor and receive fault-related data, and perform fault judgment in combination with the fault judgment rules in the rule maintenance module; the rule maintenance module is used to: set fault groups according to the relevance of fault rules, and modify and / or add fault judgment rules, and after modifying and / or adding fault judgment rules, review and process the modified and / or added fault judgment rules, use the new fault judgment rules formed after processing as subsequent fault judgment rules, and send corresponding fault information to the fault judgment module after any fault judgment rule in the fault group is triggered; the alarm notification module is used to receive fault judgment results, and output the fault judgment results to the front end after determining the fault level and fault information sending method according to the fault notification rules.

[0008] In this way, the added rule maintenance module can be adjusted according to the specific real-time situation of the vehicle, and different fault judgment rules can be configured for different models, different signals, and different fault codes. If the real-time situation of the vehicle has a significant change, the fault judgment rules can be adjusted according to the real-time situation of the vehicle, making the vehicle fault diagnosis more accurate. The set fault group is convenient for integrating related faults. When adding and / or modifying rules, the fault rules added and / or modified are quickly determined and reviewed to ensure that after the fault rules are modified and / or added, there will be no unreasonable judgment rules due to the modification, effectively ensuring that after adding and / or modifying the rules, the judgment rules are reasonable and the judgment results are valid.

[0009] Furthermore, the rule maintenance module is also used to classify the fault groups according to their impact on driving, and the fault levels are 0, 1, 2, and 3, where level 0 means no fault, level 1 means a fault that does not affect the normal driving of the vehicle, level 2 means a fault that affects the vehicle performance and requires the driver to limit driving; and level 3 means a fault that the driver should immediately stop the vehicle for processing or request rescue. In this way, after setting the level of the fault rule according to the severity of the impact of the fault on vehicle driving, it is convenient for the rule maintenance module to formulate processing measures when modifying and / or adding fault rules according to the fault level. Low fault levels are faults that do not affect user driving. The processing of these faults can be postponed, and the notification cycle can be set longer to reduce the burden on the program. High-level faults affect driving. If the driver insists on driving under this level of fault, safety accidents are likely to occur. Correspondingly, according to its severity, you can choose to send a fault warning immediately to avoid dangerous driving by the user.

[0010] Furthermore, when the modified and / or added fault judgment rules are reviewed and processed, the added and / or modified fault judgment rules are processed according to the set fault level line and the processing method corresponding to the fault level line. In this way, by setting level lines for fault rules of different levels, different processing methods can be used to reduce the burden of subsequent manual review.

[0011] Furthermore, the fault level line is set to 2, the fault level less than 2 is a low-level fault, and the fault level greater than or equal to 2 is a high-level fault. In this way, the faults are divided into high-level faults and low-level faults according to the fault level line. Since high-level faults will affect driving, all processing methods and rules are highly correlated, and more careful processing is required. Simple code review cannot meet the requirements of fault rationality. Low-level faults will not affect driving, and the processing process is more simplified.

[0012] Further, the specific method for processing the added and / or modified fault judgment rules according to the set fault level line and the processing method corresponding to the fault level line is as follows: if the fault level is a low-level fault, a new fault group is automatically generated through the code according to the modified fault judgment rule, and the code is audited and verified before the code is automatically generated. After the verification is qualified, the new fault group is used as the subsequent fault judgment rule; if the fault level is a high-level fault, all fault rules in the fault group are audited after the fault is modified and / or added, and after the audit is qualified, the audited fault group is used as the subsequent fault judgment rule. In this way, when the fault level is low, it is not easy for the fault rules to interfere with each other, or affect driving after modification, and there is no need for manual review. Only the code needs to be automatically reviewed and verified, which reduces the waiting time for fault processing. However, high-level fault rules are prone to influence and conflict with each other after modification or addition, and these rules directly correspond to driving safety after modification. Therefore, sending and processing after manual review can effectively ensure the rationality of rule setting.

[0013] Furthermore, the rule maintenance module includes a relational database MySql, and the relational database MySql maintains rules through the Web framework Spring Boot.

[0014] Furthermore, the fault judgment rules mainly include the name of the fault group and each fault rule in the fault group, the fault rule expression, the duration, and the fault level; the duration refers to how long the expression must be satisfied at the same time to determine that the fault has occurred; the fault notification rules mainly include the fault notification form and the fault notification cycle; the fault notification form is divided into enterprise WeChat notification, email notification, and SMS notification, and the fault notification cycle is divided into immediate notification and scheduled notification. In this way, the background or user can directly determine the fault situation based on the fault name, fault level, and duration. The forms of fault notification are diverse, and users can choose the appropriate notification form according to their needs.

[0015] Furthermore, the vehicle-side signals received by the data processing module include DTC fault code data, CAN transparent transmission vehicle condition data, vehicle buried point data, and vehicle basic data; wherein DTC fault code data changes are uploaded, that is, once the vehicle generates a DTC fault code, it is immediately uploaded to the cloud in real time; CAN transparent transmission vehicle condition data is divided into two forms: periodic upload and change upload, and the signal data of both upload forms are uploaded to the cloud in real time; vehicle buried points and vehicle basic data changes are uploaded to the cloud. In this way, the data received by the data processing module includes not only real-time vehicle data, but also basic vehicle data, making the data received by the fault judgment module more comprehensive, so that when performing fault diagnosis, historical data and real-time data can be combined for simultaneous judgment, and the signal duration, fault code duration reporting times, etc. can be used as one of the judgment factors, effectively improving the fault judgment ability.

[0016] Furthermore, the data processing module includes a Flink stream processing program, a Redis database, and a first Kafka publish-subscribe system. After the vehicle-side signal is uploaded to the cloud in real time, the original vehicle-side data is associated and filtered through the Flink stream processing program to obtain fault-related data. The fault-related data is stored in the Redis database in real time on the one hand, and output to the first Kafka publish-subscribe system on the other hand, as a trigger condition for the judgment logic. In this way, the data processing module can first associate and filter the received real-time data with the original vehicle-side data, and then obtain the fault-related data. This processing process can effectively ensure the accuracy and timeliness of the fault data sent.

[0017] Furthermore, the fault judgment module includes a Spring Boot application, a rule judgment engine Drools, and a second Kafka publish-subscribe system. The Spring Boot application monitors fault-related data from the Kafka publish-subscribe system, and combines fault judgment rules to call all data within the duration of the relevant signal in the Redis database when a signal that meets the fault triggering conditions appears, and sends all the called data into an object to the rule judgment engine Drools. The rule engine performs calculations and judgments based on the rules and data to determine whether the judgment result is a real fault, and sends the real fault that meets the rules to the second Kafka publish-subscribe system.

[0018] A vehicle fault diagnosis method capable of configuring and modifying fault judgment rules, characterized in that it comprises the following steps: Step 1, presetting fault judgment rules, fault notification rules, setting fault rule levels, and setting related fault rules as a fault group through a rule maintenance module; at the same time, when the existing fault rules do not meet the fault judgment requirements of the current vehicle, modifying and / or adding the fault rules through the rule maintenance module, after modifying and / or adding the fault judgment rules, reviewing and processing the modified and / or added fault judgment rules, using the new fault judgment rules formed after the processing as subsequent fault judgment rules, and in the fault group After any fault judgment rule is triggered, the corresponding fault information is sent to the fault judgment module; Step 2, the vehicle-side signal is uploaded to the cloud through the data processing module, and the fault-related data is cached according to the configuration required for fault diagnosis; Step 3, the fault judgment module monitors and receives the fault-related data, and performs fault judgment in combination with the fault judgment rules to obtain the fault judgment result; Step 4, the fault judgment result is received through the alarm notification module, and after determining the fault level and the fault information sending method according to the fault notification rule, the fault judgment result is output to the front end, which is the vehicle terminal and / or the web page terminal and / or the mobile phone terminal. In this way, when the vehicle situation changes and the previous fault judgment rules are not suitable for the fault judgment of the vehicle under the existing vehicle conditions, the rules can be edited in real time by modifying and adding the rules, so that the rules are adapted to the existing vehicle situation. The fault judgment rules are configurable, which greatly reduces the development of fault judgment code. The configuration module can configure different fault judgment rules according to different vehicle models, different signals, and different fault codes, and they are effective in real time.

[0019] Furthermore, in step 2, the data of the vehicle-side signal are uploaded to the first Kafka publish-subscribe system in the cloud, and then the original data on the vehicle side is associated and filtered through the Flink stream processing program to obtain fault-related data. The fault-related data is stored in the Redis database in real time on the one hand, and output to the first Kafka publish-subscribe system on the other hand to provide trigger conditions for the judgment logic.

[0020] Furthermore, in step 3, the fault judgment module monitors fault-related data from the Kafka publish-subscribe system through the Spring Boot application, and combines the fault judgment rules. When a signal that meets the fault triggering conditions appears, all data within the duration of the relevant signal in the Redis database is called, and all the called data are composed of objects and sent to the rule judgment engine Drools. The rule engine calculates and judges according to the rules and data to determine whether the judgment result is a real fault, and sends the real fault that meets the rules to the second Kafka publish-subscribe system. In this way, combined with the configuration of fault judgment rules and fault push strategies, the fault judgment rules can be tested and verified. Due to the instability of the vehicle-side signal to the cloud, there are omissions and mistransmissions. The fault judgment threshold and push strategy can be dynamically adjusted to ensure that the data is stable before being pushed to the car owner or dealer to reduce user complaints.

[0021] Compared with the prior art, the vehicle fault diagnosis system and method with configurable and modifiable fault judgment rules obtained by the present invention have the following advantages: 1) The fault judgment rules are configurable, which greatly reduces the development of fault judgment codes. The configuration module can configure different fault judgment rules according to different vehicle models, different signals, and different fault codes, and they take effect in real time; 2) The fault push rules are configurable, and the push strategies are changed dynamically in real time to provide different fault push strategies for car owners, dealers and OEMs, so as to provide personalized services for car owners; 3) In combination with the configuration of fault judgment rules and fault push strategies, the fault judgment rules can be tested and verified to a certain extent. Due to the instability of the vehicle-side signal to the cloud, there are omissions and mistransmissions. The fault judgment threshold and push strategy can be dynamically adjusted to ensure that the data is stable before being pushed to the car owner or dealer, reducing user complaints; 4) The fault judgment ability is strong, and it can combine historical data and real-time data for simultaneous judgment, and the signal duration, the number of fault code duration reports, etc. can be used as one of the judgment factors. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a flow chart of the data processing module in the embodiment.

[0023] Figure 2 It is a flow chart of the fault judgment module in the embodiment.

[0024] Figure 3 It is a flow chart of the rule maintenance module in the embodiment.

[0025] Figure 4 This is a flow chart of the alarm notification module in the embodiment;

[0026] Figure 5 This is a flow chart for adding / or modifying fault judgment rules in the embodiment. DETAILED DESCRIPTION

[0027] The present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0028] Example:

[0029] like Figure 1-Figure 4 As shown, this embodiment provides a vehicle fault diagnosis system capable of configuring and modifying fault judgment rules, including a data processing module, a fault judgment module, a rule maintenance module and an alarm notification module. The data processing module is used to upload the vehicle-side signal to the cloud in real time, and then cache the fault-related data according to the configuration required for fault diagnosis; the fault judgment module is used to monitor and receive the fault-related data, and perform fault judgment in combination with the fault judgment rules in the rule maintenance module; the rule maintenance module is used to: set fault groups according to the relevance of fault rules, and classify the fault groups according to the degree of influence on driving; and to modify and / or add faults Judgment rules, and after modifying and / or adding fault judgment rules, the added and / or modified fault judgment rules are reviewed and processed according to the set fault level line and the processing method corresponding to the fault level line, and after the review is qualified, the reviewed fault group is used as the subsequent fault judgment rule, and at the same time, after any rule in the fault group is triggered, the corresponding fault information is sent to the fault judgment module; the alarm notification module is used to receive the fault judgment result, and after determining the fault level and the fault information sending method according to the fault notification rule, the fault judgment result is output to the front end, which is the vehicle terminal and / or the web page terminal and / or the mobile phone terminal. Specifically, the data processing module includes a Flink stream processing program, a Redis database, and a first Kafka publish-subscribe system. The fault judgment module includes a Spring Boot application, a rule judgment engine Drools, and a second Kafka publish-subscribe system. The rule maintenance module includes a relational database MySql, and the relational database MySql maintains rules through the Web framework Spring Boot.

[0030] When modifying and / or adding fault judgment rules, if the fault level is low, a new fault group is automatically generated according to the modified fault judgment rules, and the new fault group is directly used as the subsequent fault judgment rules. When any rule in the fault group is triggered, the corresponding fault information is sent to the fault judgment module; if the fault level is high, all fault rules in the fault group are reviewed after the fault is modified and / or added.

[0031] The data on the vehicle side includes DTC fault code data, CAN transparent vehicle condition data, vehicle tracking data, vehicle basic data, etc. Among them, DTC fault code data changes are uploaded, that is, once a DTC fault code is generated on the vehicle side, it is immediately uploaded to the cloud in real time; CAN transparent vehicle condition data is divided into two forms: periodic upload and change upload. The signal data of both upload forms are uploaded to the cloud in real time; vehicle tracking points and vehicle basic data changes are uploaded to the cloud.

[0032] According to the actual business scenario, multiple interrelated fault rules are set as a fault group, and the fault level of the fault group is divided into four levels: 0, 1, 2, and 3 ("0" means: no fault; "1" means: level 1 fault, which refers to a fault that does not affect the normal driving of the vehicle; "2" means: level 2 fault, which refers to a fault that affects the vehicle performance and requires the driver to limit driving; "3" means: level 3 fault, which is the highest level fault and refers to a fault for which the driver should stop the vehicle immediately or request rescue).

[0033] If any fault rule in the fault group is triggered, it means that the fault group is triggered. When a fault with a fault level of 3 is triggered, the car owner and after-sales service will be notified in real time to provide protection for the car owner's car safety. When a fault with a fault level of 2 is triggered, only the after-sales service will be notified, and the after-sales service will determine whether it is necessary to contact the car owner or do corresponding work based on the actual situation. When a fault with a fault level of 1 or 0 is triggered, it will not be pushed in real time. At 9 o'clock every morning, a fault occurrence report of the previous day will be actively generated and pushed to after-sales, who will conduct manual analysis of the previous day's faults.

[0034] The fault level line set in this embodiment is 2, a fault level less than 2 is a low-level fault, and a fault level greater than or equal to 2 is a high-level fault. The specific method for processing the added and / or modified fault judgment rules according to the set fault level line and the processing method corresponding to the fault level line is as follows: if the fault level is a low-level fault, a new fault group is automatically generated through the code according to the modified fault judgment rule, and before the code is automatically generated, the code is audited and verified, and after the verification is qualified, the new fault group is used as a subsequent fault judgment rule; if the fault level is a high-level fault, after the fault is modified and / or added, all fault rules in the fault group are audited, and after the audit is qualified, the audited fault group is used as a subsequent fault judgment rule.

[0035] Specifically, when the fault rules in fault groups of different fault levels are modified, different processes need to be involved. The modification of fault rules of fault levels 3 and 2 requires the review of the relevant business manager, and it will take effect only after the review is passed; after the fault rules of fault levels 1 and 0 are modified, no manual review is required; secondly, after modifying any fault rule in a fault group, the fault rules of the entire fault group will automatically regenerate a new fault rule group through the code according to the modified rules. Finally, to ensure the correctness of the code, it is necessary to set up a code field library, and extract the fields of the code automatically generated by the rules and match them with the corresponding codes in the code field library to determine the correctness of the modified code fields. At the same time, it is necessary to verify and review the relationship between the codes through regular expressions. After confirming that the automatically generated code is correct, the reviewed fault group is used as the new fault judgment basis.

[0036] Specifically, based on the above system, the present embodiment also provides a vehicle fault diagnosis method that can configure and modify fault judgment rules, including the following steps: Step 1, preset fault judgment rules, fault notification rules, set fault rule levels, and set related fault rules as a fault group through a rule maintenance module; and when the existing fault rules do not meet the fault judgment requirements of the current vehicle, modify and / or add the fault rules through the rule maintenance module. When modifying and / or adding fault rules, if the modified and / or added fault level is low, then a new fault group is automatically generated according to the modified fault judgment rules, and the new fault group is directly used as a subsequent fault judgment rule. When any rule in the fault group is triggered, the corresponding fault information is sent to the fault judgment module; if the fault level is high, then After the fault is modified and / or added, all fault rules in the fault group are reviewed, and after the review is qualified, the reviewed fault group is used as the subsequent fault judgment rule. At the same time, after any rule in the fault group is triggered, the corresponding fault information is sent to the fault judgment module; Step 2, the vehicle-side signal is uploaded to the cloud through the data processing module, and the fault-related data is cached according to the configuration required for fault diagnosis; Step 2, the fault judgment module monitors and receives the fault-related data, and performs fault judgment in combination with the fault judgment rules to obtain the fault judgment result; Step 3, the fault judgment result is received through the alarm notification module, and after determining the fault level and the fault information sending method according to the fault notification rules, the fault judgment result is output to the front end, which is the vehicle machine end and / or the web page end and / or the mobile phone end.

[0037] Figure 1This is the flow chart of the data processing module. The cloud forwards all data through Kafka, that is, all the original data on the vehicle side are uploaded to the first Kafka publish-subscribe system on the cloud, and then the original data on the vehicle side is associated and filtered through a Flink stream processing program. The filtering conditions are all signals related to the rules, that is, only the signal data used in the fault judgment rules are retained, and irrelevant data are filtered out to avoid wasting storage space and computing resources. The filtered data is fault-related data. On the one hand, the fault-related data is sent to Redis for storage in real time to provide a data source for fault judgment. The data TTL time is the longest duration in the rule, which saves storage space and meets computing needs; on the other hand, it is output to the first Kafka publish-subscribe system of the message queue to provide trigger conditions for the judgment logic.

[0038] Figure 2 This is the processing flow chart of the fault judgment module. The fault judgment module listens to fault-related data from the Kafka publish-subscribe system through the Spring Boot application, and combines the fault judgment rules. When a signal that meets the fault triggering conditions appears, all data within the duration of the relevant signal in the Redis database is called, and all the called data are composed of objects and sent to the rule judgment engine Drools. The rule engine calculates and judges according to the rules and data to determine whether the judgment result is a real fault, and sends the real fault that meets the rules to the second Kafka publish-subscribe system to prepare data for alarm notification. For example, the rule expression configured for fault F is: A<=5& B>=10& C==1, keep=30, and the fault level is level 1 (the fault level is divided into four levels: 0, 1, 2, and 3); in another table, A and B signals are configured as periodic signals, and C signal is a non-periodic signal. This rule can be interpreted as when the periodic upload signal A meets A<=5, the periodic upload signal B meets B>=10, and the change upload signal C meets C==1 and the duration reaches 30 seconds, it is judged that a level 1 fault F occurs. The judgment process is that when the periodic signal A<=5 is monitored, all data of the A, B, and C signals in the last 30 seconds, the signal value and time of the last upload of signal C are queried in Redis. The change of uploaded signal C needs to be processed as follows: if signal C has not uploaded a signal in the last 30 seconds, signal C uses the most recent signal value; if it has been uploaded, it means that signal C has changed and does not meet the conditions, and the current judgment process ends directly. If signal C is not uploaded, signals A, B, and C are combined into an object and sent to the judgment engine Drools for judgment: if the result is False, it means that the fault condition is not met, and the current process ends directly; if the result is True, it means that fault F is established, and fault F and fault level 1 are output to the second Kafka publishing and subscription system.

[0039] Figure 3 This is a flowchart of the rule maintenance module. Specifically, in the rule maintenance module, we can maintain fault judgment rules and fault notification rules. Both rules are stored in the relational database MySql. The rules are maintained through the Web framework Spring Boot, so that all rules can be configured visually. Among them, the fault judgment rules mainly include fault group and fault name, fault rule expression, duration, fault level, etc. The fault name is the name customized by the engineer for the fault. It is best to express the fault content and make it clear at a glance, such as abnormal left front tire pressure, abnormal ESM controller voltage, etc. The fault expression is mainly a regular expression, and it also supports custom expressions in Drools. The duration refers to how long the expression satisfies the same condition at the same time to determine that the fault has occurred, avoiding false alarms caused by vehicle-side signal jumps; the fault level is 0, 1, 2, 3. When defining a fault, a level is defined for the fault according to the severity of the fault. The fault notification rules mainly include the fault notification form, fault notification cycle, etc. The fault notification form is divided into enterprise WeChat notification, email notification, and SMS notification. The fault notification cycle is divided into immediate notification and scheduled notification. Fault notification form configuration can be configured at the fault level or on a specific fault, and can be upward compatible, that is, start by checking the fault notification rules based on the specific fault. If no results are found, then query the notification rules based on the fault level. In this way, notification rules can be configured for the fault level, and only the faults that require special treatment can be configured separately, thus achieving both personalized and unified configuration.

[0040] Figure 4 This is a flowchart of the alarm notification module. Specifically, the alarm notification module monitors fault result data through Spring Boot, and performs fault notification processing according to the fault name and fault level, combined with the configuration of fault notification rules. For real-time notification faults, the relevant message notification module is immediately called to notify the fault. For scheduled notification faults, they are cached and the message notification module is called regularly to notify all faults.

[0041] Figure 5 This is a flow chart for modifying and / or adding higher-level fault rules. When adding and / or modifying fault judgment rules, it is necessary to first verify whether the rules are legal. If not, they will be directly passed to the rule editor. If the fault judgment rules are legal, the background will determine whether manual review is required. If necessary, the fault rules will be applied after manual review and verification. If the rules are determined to be unreasonable after manual verification, the rule editor will be notified to re-edit the fault rules until the modified and / or added fault judgment rules are reasonable.

[0042] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit the technical solution. Although the applicant has described the present invention in detail with reference to the preferred embodiments, ordinary technicians in this field should understand that those modifications or equivalent substitutions of the technical solution of the present invention without departing from the purpose and scope of the technical solution should be included in the scope of the claims of the present invention.

Claims

1. A vehicle fault diagnosis system capable of configuring and modifying fault judgment rules, characterized in that: It includes data processing module, fault judgment module, rule maintenance module and alarm notification module. The data processing module is used to cache fault-related data according to the configuration required for fault diagnosis after uploading the vehicle-side signal to the cloud in real time; The fault judgment module is used to monitor and receive fault-related data, and perform fault judgment in combination with the fault judgment rules in the rule maintenance module; The rule maintenance module is used to: set up fault groups according to the relevance of fault rules, and modify and / or add fault judgment rules, and after modifying and / or adding fault judgment rules, review and process the modified and / or added fault judgment rules, use the new fault judgment rules formed after processing as subsequent fault judgment rules, and send corresponding fault information to the fault judgment module after any fault judgment rule in the fault group is triggered; The alarm notification module is used to receive the fault judgment result, and after determining the fault level and the fault information sending method according to the fault notification rule, output the fault judgment result to the front end; The rule maintenance module is also used to classify the fault groups according to their impact on driving, and the fault levels are 0, 1, 2, and 3, where level 0 means no fault, level 1 means a fault that does not affect the normal driving of the vehicle, level 2 means a fault that affects the vehicle performance and requires the driver to limit driving; level 3 means a fault that the driver should stop immediately or request rescue; when reviewing and processing the modification and / or addition of fault judgment rules, the added and / or modified fault judgment rules are processed according to the set fault level line and the processing method corresponding to the fault level line; the set fault level line is 2, and a fault level less than 2 is a low-level fault, and a fault level greater than or equal to 2 is a low-level fault. 2 is a high-level fault; the specific method for processing the added and / or modified fault judgment rules according to the set fault level line and the processing method corresponding to the fault level line is as follows: if the fault level is a low-level fault, a new fault group is automatically generated through the code according to the modified fault judgment rule, and the code is reviewed and verified before the code is automatically generated. After the verification is qualified, the new fault group is used as the subsequent fault judgment rule; if the fault level is a high-level fault, all fault rules in the fault group are reviewed after the fault is modified and / or added, and after the review is qualified, the reviewed fault group is used as the subsequent fault judgment rule.

2. The vehicle fault diagnosis system capable of configuring and modifying fault judgment rules according to claim 1, characterized in that: The rule maintenance module includes a relational database MySql, and the relational database MySql maintains rules through a Web framework SpringBoot.

3. The vehicle fault diagnosis system capable of configuring and modifying fault judgment rules according to claim 1 or 2, characterized in that: The fault judgment rules mainly include the name of the fault group and each fault rule in the fault group, the fault rule expression, the duration, and the fault level; The duration refers to how long the expression must be satisfied simultaneously to determine that a fault has occurred; the fault notification rules mainly include the fault notification form and the fault notification cycle; the fault notification form is divided into enterprise WeChat notification, email notification, and SMS notification, and the fault notification cycle is divided into immediate notification and scheduled notification.

4. The vehicle fault diagnosis system capable of configuring and modifying fault judgment rules according to claim 3, characterized in that: The vehicle-side signals received by the data processing module include DTC fault code data, CAN transparent vehicle condition data, vehicle buried point data, and vehicle basic data; among them, DTC fault code data change upload, that is, once the vehicle-side generates a DTC fault code, it is immediately uploaded to the cloud in real time; CAN transparent vehicle condition data is divided into two forms: periodic upload and change upload, and the signal data of both upload forms are uploaded to the cloud in real time; vehicle buried points and vehicle basic data changes are uploaded to the cloud.

5. The vehicle fault diagnosis system capable of configuring and modifying fault judgment rules according to claim 1, 2 or 4, characterized in that: The data processing module includes a Flink stream processing program, a Redis database, and a first Kafka publish-subscribe system. After the vehicle-side signal is uploaded to the cloud in real time, the Flink stream processing program is used to associate and filter the vehicle-side original data to obtain fault-related data. The fault-related data is stored in the Redis database in real time on the one hand, and is output to the first Kafka publish-subscribe system on the other hand to provide trigger conditions for the judgment logic.

6. The vehicle fault diagnosis system capable of configuring and modifying fault judgment rules according to claim 5, characterized in that: The fault judgment module includes a Spring Boot application, a rule judgment engine Drools, and a second Kafka publish-subscribe system. The Spring Boot application monitors fault-related data from the Kafka publish-subscribe system, and combines fault judgment rules to call all data within the duration of the relevant signal in the Redis database when a signal that meets the fault triggering conditions appears, and sends all the called data into the form of an object to the rule judgment engine Drools. The rule engine calculates and judges based on the rules and data to determine whether the judgment result is a real fault, and sends the real fault that meets the rules to the second Kafka publish-subscribe system.

7. A vehicle fault diagnosis method capable of configuring and modifying fault judgment rules, characterized in that: The method comprises the following steps: Step 1, presetting fault judgment rules, fault notification rules, setting fault rule levels, and setting related fault rules as a fault group through a rule maintenance module; at the same time, when the existing fault rules do not meet the fault judgment requirements of the current vehicle, modifying and / or adding the fault rules through the rule maintenance module, and after modifying and / or adding the fault judgment rules, reviewing and processing the modified and / or added fault judgment rules, using the new fault judgment rules formed after processing as subsequent fault judgment rules, and sending corresponding fault information to the fault judgment module after any fault judgment rule in the fault group is triggered; Step 2, upload the vehicle-side signal to the cloud through the data processing module, and cache the fault-related data according to the configuration required for fault diagnosis; Step 3, monitor and receive the fault-related data through the fault judgment module, and make a fault judgment in combination with the fault judgment rules to obtain the fault judgment result; Step 4, receive the fault judgment result through the alarm notification module, and after determining the fault level and the fault information sending method according to the fault notification rules, output the fault judgment result to the front end, which is the vehicle-side and / or web page and / or mobile phone side; The fault levels are 0, 1, 2, and 3, among which level 0 means no fault, level 1 means a fault that does not affect the normal driving of the vehicle, level 2 means a fault that affects the vehicle performance and requires the driver to limit driving; level 3 means a fault that the driver should stop immediately or request rescue; When reviewing and processing the modification and / or addition of fault judgment rules, according to the The set fault level line and the processing method corresponding to the fault level line are used to process the added and / or modified fault judgment rules; the set fault level line is 2, a fault level less than 2 is a low-level fault, and a fault level greater than or equal to 2 is a high-level fault; the specific method for processing the added and / or modified fault judgment rules according to the set fault level line and the processing method corresponding to the fault level line is as follows: if the fault level is a low-level fault, a new fault group is automatically generated through the code according to the modified fault judgment rule, and the code is reviewed and verified before the code is automatically generated. After the verification is qualified, the new fault group is used as a subsequent fault judgment rule; if the fault level is a high-level fault, all fault rules in the fault group are reviewed after the fault is modified and / or added, and after the review is qualified, the reviewed fault group is used as a subsequent fault judgment rule.

8. The vehicle fault diagnosis method capable of configuring and modifying fault judgment rules according to claim 7, characterized in that: In step 2, the data of the vehicle-side signal are uploaded to the first Kafka publish-subscribe system in the cloud, and then the original data on the vehicle side is associated and filtered through the Flink stream processing program to obtain fault-related data. The fault-related data is stored in the Redis database in real time on the one hand, and output to the first Kafka publish-subscribe system on the other hand to provide trigger conditions for the judgment logic.

9. The vehicle fault diagnosis method capable of configuring and modifying fault judgment rules according to claim 7 or 8, characterized in that: In step 3, the fault judgment module listens to fault-related data from the Kafka publish-subscribe system through the Spring Boot application, and combines the fault judgment rules. When a signal that meets the fault trigger conditions appears, it calls all data within the duration of the relevant signal in the Redis database, and sends all the called data into the form of an object to the rule judgment engine Drools. The rule engine calculates and judges based on the rules and data to determine whether the judgment result is a real fault, and sends the real fault that meets the rules to the second Kafka publish-subscribe system.

Citation Information

Patent Citations

  • Airborne real-time fault diagnosis method

    CN102998996A

  • Automatic parking fault diagnosis and monitoring system and method, vehicle and storage medium

    CN112037564A

  • Multi-user collaborative interactive navigation and emergency control system

    CN113763694A

  • Vehicle alarm method and device, and computer readable storage medium

    CN113793134A

  • Configurable fault diagnosis method and fault diagnosis system based on real-time vehicle condition

    CN114279718A