CN115268396A - Fault data acquisition and analysis method, system, storage medium and electronic equipment - Google Patents

Fault data acquisition and analysis method, system, storage medium and electronic equipment Download PDF

Info

Publication number
CN115268396A
CN115268396A CN202210848174.8A CN202210848174A CN115268396A CN 115268396 A CN115268396 A CN 115268396A CN 202210848174 A CN202210848174 A CN 202210848174A CN 115268396 A CN115268396 A CN 115268396A
Authority
CN
China
Prior art keywords
fault
key data
data
key
acquisition
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210848174.8A
Other languages
Chinese (zh)
Inventor
甘进
李小玲
廖程亮
樊华春
徐炜
邬晶明
袁欣
龚天阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jiangxi Isuzu Motors Co Ltd
Original Assignee
Jiangxi Isuzu Motors Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jiangxi Isuzu Motors Co Ltd filed Critical Jiangxi Isuzu Motors Co Ltd
Priority to CN202210848174.8A priority Critical patent/CN115268396A/en
Publication of CN115268396A publication Critical patent/CN115268396A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
    • G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24065—Real time diagnostics

Abstract

The invention provides a fault data acquisition and analysis method, a fault data acquisition and analysis system, a storage medium and electronic equipment, wherein the method comprises the following steps: monitoring whether a fault signal sent by a CAN bus is received every first preset time; if a fault signal sent by the CAN bus is received, acquiring a fault type according to the fault signal, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type; calling out an acquisition strategy corresponding to each control module name from a preset data acquisition association table according to the control module name; and acquiring the corresponding key data items from the corresponding control modules according to the acquisition strategy, and analyzing the acquired key data items to acquire the fault reasons according to the analysis result. According to the fault data acquisition and analysis method provided by the invention, massive data do not need to be screened and checked one by one after the fault data occurs, the fault checking efficiency can be greatly improved, and the enterprise operation cost is reduced.

Description

Fault data acquisition and analysis method, system, storage medium and electronic equipment
Technical Field
The invention relates to the technical field of vehicle internet, in particular to a fault data acquisition and analysis method, a fault data acquisition and analysis system, a storage medium and electronic equipment.
Background
Along with the promotion of automobile intellectualization, mechanical and software functional fault monitoring and prevention of a vehicle also become a new research hotspot in the automobile industry, through real-time monitoring of the vehicle, when the vehicle breaks down, background customer service personnel can receive the alarm of a platform at the first time, and simultaneously automatically acquire fault related vehicle operation data, help after-sale maintenance personnel to quickly identify fault reasons, provide an accurate rescue and maintenance scheme, and simultaneously help manufacturers to quickly identify fault reasons and optimize parts.
In the prior art, through the vehicle networking platform, the fault monitoring and alarming of the vehicle can be realized, and meanwhile, through the big data acquisition of the vehicle, the state data in the running process of the vehicle can be collected, but the fault alarming and the data acquisition are separated and unrelated, so that after a fault occurs, the fault analysis has obvious hysteresis, the manual work is often required to be arranged to screen and find out effective data from mass data, and further the fault reason is determined, the mode causes the fault finding efficiency to be lower, meanwhile, the requirement on the data analysis capability of after-sales maintenance personnel is higher, the popularization is not facilitated, a large amount of technical training needs to be carried out on the after-sales technicians, and the enterprise operation cost is increased.
Disclosure of Invention
Therefore, the invention aims to provide a fault data acquisition and analysis method, a fault data acquisition and analysis system, a storage medium and electronic equipment, so as to solve the problem of low troubleshooting efficiency caused by the fact that fault alarm and fault data acquisition are not related in the traditional fault monitoring.
The invention provides a fault data acquisition and analysis method, which is applied to a vehicle-mounted terminal and comprises the following steps:
monitoring whether a fault signal sent by a CAN bus is received every first preset time;
if a fault signal sent by a CAN bus is received, acquiring a fault type according to the fault signal, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
respectively acquiring corresponding control module names according to each key data item, and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
and acquiring the corresponding key data item from the corresponding control module according to the acquisition strategy, and analyzing the acquired key data item to acquire a fault reason according to an analysis result.
In conclusion, according to the fault data acquisition and analysis method, faults are monitored in real time, fault data acquisition is triggered by the faults, accurate fault data analysis is provided, accurate fault reasons are obtained, massive data do not need to be screened and investigated one by one after the fault data occur, fault investigation efficiency is greatly improved, and enterprise operation cost is reduced. Specifically, whether a fault signal sent by a CAN bus is received or not is continuously monitored in real time, if the fault signal is monitored, in order to analyze the reason of the fault signal, a corresponding fault type is obtained according to the fault signal, one or more key data items related to the fault are extracted according to the fault type, corresponding control module names, namely data acquisition objects, are locked according to the key data items, acquisition strategies corresponding to the control module names are extracted, data acquisition is carried out on the control modules according to the acquisition strategies in a targeted manner, required key data items are obtained, the specific fault reason is analyzed according to the key data items, manual screening and troubleshooting from mass data are not needed after the fault occurs, the fault troubleshooting efficiency is greatly improved, data are automatically acquired and analyzed after the fault occurs, and the enterprise operation cost is greatly reduced.
Further, if a fault signal sent by a CAN bus is received, the step of obtaining a fault type according to the fault signal and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type includes:
acquiring a plurality of known fault types, and defining at least one key data item according to the fault characteristics of each fault type, wherein the key data item comprises control vehicle condition data, engine state data and controller state data;
and associating any one known fault type with the key data item corresponding to each known fault type, and summarizing all association results to obtain the preset fault key mapping table.
Further, the step of respectively obtaining the corresponding control module names according to each key data item, and calling out the acquisition strategies respectively corresponding to each control module name from the preset data acquisition association table according to the control module names includes:
respectively acquiring data sensitivities of vehicle condition data, engine state data and controller state data so as to acquire a corresponding error range according to the sensitivity of each key data item;
and respectively defining corresponding acquisition cycles according to the error range corresponding to each key data item, and formulating an acquisition strategy according to the key data items and the acquisition cycles corresponding to each key data item.
Further, the step of acquiring the corresponding key data item from the corresponding control module according to the acquisition policy, and analyzing the acquired key data item to acquire the fault cause according to the analysis result includes:
calling out reissue time corresponding to the fault type from a preset reissue time table according to the fault type, and acquiring various key data items before the fault occurs according to the receiving time of the fault signal and the reissue time corresponding to the fault type;
and acquiring real fault key index values at all moments according to various key data items before the fault occurs and various key data items after the fault occurs, and judging whether the real fault key index value at each moment exceeds an error standard range.
Further, the step of obtaining the real fault key index values at all times according to various key data items before and after the occurrence of the fault, and determining whether the real fault key index value at each time exceeds the error standard range includes:
respectively configuring corresponding standard fault key index values and error standard values for each known fault type to obtain a fault checking data table;
calling out a corresponding standard fault key index value and a corresponding error standard value from the fault checking data table according to the fault type corresponding to the fault signal;
and acquiring a real error value according to the real fault key index value at each moment and the corresponding standard fault key index value, and judging whether the real error value is greater than an error standard value or not.
Further, the step of monitoring whether a fault signal sent by the CAN bus is received every first preset time includes:
acquiring a vehicle running state message sent by a CAN bus every a first preset time, and acquiring current fault state bit information according to the vehicle running state message;
and judging whether the vehicle has a fault according to the fault state bit information.
Further, the step of obtaining a real error value according to the real fault key index value at each moment and the corresponding standard fault key index value, and determining whether the real error value is greater than an error standard value further includes:
and if the real error value is larger than the error standard value, determining each key data item at the moment as fault data, and uploading all fault data to a cloud service monitoring platform.
The fault data acquisition and analysis system according to the embodiment of the invention is applied to a vehicle-mounted terminal, and comprises:
the fault signal receiving module is used for monitoring whether a fault signal sent by the CAN bus is received or not at intervals of first preset time;
the key data item calling module is used for acquiring a fault type according to a fault signal sent by a CAN bus if the fault signal is received, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
the acquisition strategy acquisition module is used for respectively acquiring corresponding control module names according to each key data item and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
and the fault analysis module is used for acquiring the corresponding key data items from the corresponding control module according to the acquisition strategy and analyzing the acquired key data items so as to acquire fault reasons according to analysis results.
In another aspect, the present invention further provides a storage medium, which includes one or more programs stored in the storage medium, and when the programs are executed, the method for collecting and analyzing fault data as described above is implemented.
Another aspect of the present invention also provides an electronic device, which includes a memory and a processor, wherein:
the memory is used for storing computer programs;
the processor is used for realizing the fault data acquisition and analysis method when executing the computer program stored in the memory.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a flowchart of a fault data collection and analysis method according to a first embodiment of the present invention;
FIG. 2 is a flow chart of a fault data collection and analysis method according to a second embodiment of the present invention;
FIG. 3 is a detailed diagram of step S106 in the second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a fault data collection and analysis system according to a third embodiment of the present invention.
The following detailed description will further illustrate the invention in conjunction with the above-described figures.
Detailed Description
To facilitate an understanding of the invention, the invention will now be described more fully with reference to the accompanying drawings. Several embodiments of the invention are shown in the drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
Referring to fig. 1, a flowchart of a fault data collection and analysis method according to a first embodiment of the present invention is shown, and is applied to a vehicle-mounted terminal, where the method includes steps S01 to S04, where:
step S01: monitoring whether a fault signal sent by a CAN bus is received every first preset time;
it should be noted that, in the starting process of the entire vehicle, the vehicle-mounted terminal starts to be powered on, that is, whether a fault signal sent by the CAN bus exists is monitored in real time, that is, whether a fault occurs is monitored so as to trigger subsequent fault data acquisition and analysis.
The purpose of setting the first preset time is to continuously monitor whether a fault signal exists in real time by the vehicle-mounted terminal as long as the vehicle is in the whole process from starting to flameout, so as to trigger subsequent work at the first time, and in the embodiment, the first preset time is generally set to be 5-30s, so that the vehicle-mounted terminal keeps high-frequency monitoring.
Step S02: if a fault signal sent by a CAN bus is received, acquiring a fault type according to the fault signal, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
it can be understood that, after the vehicle-mounted terminal monitors that a fault signal exists, the corresponding fault type is judged according to the fault signal, and then one or more key data items completely corresponding to the fault trigger are extracted based on the fault type.
Step S03: respectively acquiring corresponding control module names according to each key data item, and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
it should be noted that, in order to accurately analyze the cause of the occurrence of the fault, at least one key data item is defined for each fault under normal conditions, and multiple control modules are involved to comprehensively and accurately analyze the cause of the fault.
Step S04: and acquiring the corresponding key data items from the corresponding control modules according to the acquisition strategy, and analyzing the acquired key data items to acquire fault reasons according to analysis results.
In conclusion, according to the fault data acquisition and analysis method, faults are monitored in real time, fault data acquisition is triggered by the faults, accurate fault data analysis is provided, accurate fault reasons are obtained, massive data do not need to be screened and investigated one by one after the fault data occur, fault investigation efficiency is greatly improved, and enterprise operation cost is reduced. Specifically, whether a fault signal sent by a CAN bus is received or not is continuously monitored in real time, if the fault signal is monitored, in order to analyze the reason of the fault signal, a corresponding fault type is obtained according to the fault signal, one or more key data items related to the fault are extracted according to the fault type, corresponding control module names, namely data acquisition objects, are locked according to the key data items, acquisition strategies corresponding to the control module names are extracted, data acquisition is carried out on the control modules according to the acquisition strategies in a targeted manner, required key data items are obtained, the specific fault reason is analyzed according to the key data items, manual screening and troubleshooting from mass data are not needed after the fault occurs, the fault troubleshooting efficiency is greatly improved, data are automatically acquired and analyzed after the fault occurs, and the enterprise operation cost is greatly reduced.
Referring to fig. 2, a flowchart of a fault data collecting and analyzing method according to a second embodiment of the present invention is shown, the method includes steps S101 to S106, wherein:
step S101: acquiring a vehicle running state message sent by a CAN bus every a first preset time, and acquiring current fault state bit information according to the vehicle running state message;
step S102: judging whether the vehicle has a fault according to the fault state bit information;
it should be noted that, when a vehicle has a fault, the corresponding fault status bit of the CAN bus may be changed, and the vehicle-mounted terminal acquires the fault status change, thereby triggering event data acquisition.
For example, but not limited to, if the fault state bit information in the vehicle running state message sent by the normal alarm-free CAN is 0, after an alarm occurs, the state bit changes to 1, the vehicle-mounted terminal catches the change from 0 to 1, and it is determined that the vehicle generates the fault alarm, so that a fault time data acquisition process is triggered.
Step S103: if a fault signal sent by a CAN bus is received, acquiring a fault type according to the fault signal, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
it should be noted that if it is determined that the vehicle has a fault, that is, a fault signal with a fault status bit of 0 is received, the corresponding key data item is automatically triggered and retrieved, specifically:
the method comprises the steps that a plurality of known fault types are obtained before the vehicle-mounted terminal detects, at least one key data item is defined according to the fault characteristics of each fault type, the key data items comprise control vehicle condition data, engine state data and controller state data, the vehicle condition data generally comprise data such as vehicle speed, accelerator opening and brake opening, the transmitter state data generally comprise operation parameters such as transmitter rotating speed, and the controller state data generally comprise state data of each ECU of each controller of the vehicle;
and then associating any one known fault type with the key data items corresponding to each known fault type, summarizing all association results to obtain the preset fault key mapping table, and pre-storing the fault key mapping table, so that the vehicle-mounted terminal can obtain the key data items corresponding to the fault signal according to the fault key mapping table.
Step S104: respectively acquiring corresponding control module names according to each key data item, and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
it can be understood that after obtaining the key data items, the special acquisition is started, but before the acquisition, the frequency requirements for the data may be different due to different fault types, such as a fault of an engine controller module ECM, which is usually a message period of 20-50ms, a fault of a vehicle body controller BCM, which is usually a message period of 100-200ms, based on which, before the acquisition, data sensitivities of vehicle condition data, engine state data, and controller state data need to be respectively obtained to obtain a corresponding error range according to the sensitivity of each key data item; in this embodiment, the data sensitivity refers to the data magnitude of the key data item, that is, a corresponding data valid range is obtained according to the data magnitude of the key data item, and if the data valid range exceeds or is lower than the data valid range, it indicates that the data cannot be analyzed even if the data is collected.
And then respectively defining corresponding acquisition cycles according to the error range corresponding to each key data item, and formulating an acquisition strategy according to the key data items and the acquisition cycles corresponding to each key data item. The acquisition cycle is the acquisition frequency, and the acquisition cycle of each key data item is accurately defined to further ensure that the key data items acquired in a targeted manner are really effective and can be used for analyzing data, so that the condition that the key data items are incomplete due to too large error of the acquisition frequency is prevented.
Step S105: calling out reissue time corresponding to the fault type from a preset reissue time table according to the fault type, and acquiring various key data items before the fault occurs according to the receiving time of the fault signal and the reissue time corresponding to the fault type;
it should be noted that, since the acquisition of the key data items is triggered based on the fault signal, the cause of the fault may be caused by the previous abnormality, and based on this, the vehicle-mounted terminal needs to acquire various key data items before the fault occurs.
Step S106: acquiring real fault key index values at all moments according to various key data items before and after the fault occurs, and judging whether the real fault key index value at each moment exceeds an error standard range;
further, please refer to fig. 3, which shows a detailed diagram of step S106 in the present embodiment, wherein step S106 includes steps S1061 to S106, wherein:
step S1061: respectively configuring corresponding standard fault key index values and error standard values for each known fault type to obtain a fault checking data table;
step S1062: calling out a corresponding standard fault key index value and a corresponding error standard value from the fault checking data table according to the fault type corresponding to the fault signal;
step S1063: acquiring a real error value according to the real fault key index value at each moment and the corresponding standard fault key index value, and judging whether the real error value is greater than an error standard value or not;
step S1064: and if the real error value is larger than the error standard value, determining each key data item at the moment as fault data, and uploading all fault data to a cloud service monitoring platform.
It should be noted that, in order to analyze the key data items at each time to determine that those data are fault data, that is, abnormal data, first, a corresponding standard key index value and a corresponding error standard value are configured for all known fault types, and then when analyzing the key data items at any time, a true error value of the key data item is calculated, so as to determine whether the error standard is exceeded, if yes, the key data item is determined to be abnormal data, at this time, the vehicle-mounted terminal encodes all the abnormal data, and after the analysis is completed, all the fault data is uploaded to the cloud service monitoring platform according to the codes, so as to accurately obtain the reason for triggering the fault signal this time.
By way of example and not limitation, for a transmission ratio, the calculation is:
i0＝0.377*r*n/(ig*v)
wherein i0Expressing the transmission ratio of the main speed reducer, namely representing the transmission ratio as a real key fault index value; r represents the radius of the wheel, v represents the speed of the vehicle, and belongs to the vehicle condition data, and n represents the rotating speed of the engine, namely belongs to the engine state data; i.e. igIs the transmission ratio of the transmission, i.e. belongs to the controller state data.
By collecting the key data and calculating according to a formula, the transmission ratio of the vehicle main reducer at each moment can be obtained, and is compared with a standard key fault index value configured at the background, the transmission ratio is normal within a certain error range, and the transmission ratio is fault data if the transmission ratio exceeds the error range.
If the transmission ratio of the corresponding gear of a certain vehicle type is as follows: the standard value corresponding to the first gear is 5.979; the standard value corresponding to the second gear is 3.434; the standard value corresponding to the third gear is 1.862; the standard value corresponding to the fourth gear is 1.297; the standard value corresponding to the fifth gear is 1; the standard value corresponding to the sixth gear is 0.759, and the standard value corresponding to the R gear is 5.701; the error standard value is 5%, and if the data contrast exceeds 5%, it is determined to be abnormal.
In conclusion, according to the fault data acquisition and analysis method, faults are monitored in real time, the faults are triggered to acquire the fault data, accurate fault data analysis is provided, accurate fault reasons are obtained, massive data do not need to be screened and checked one by one after the fault data occur, the fault checking efficiency is greatly improved, and the enterprise operation cost is reduced. Specifically, whether a fault signal sent by a CAN bus is received or not is continuously monitored in real time, if the fault signal is monitored, in order to analyze the reason of the fault signal, a corresponding fault type is obtained according to the fault signal, one or more key data items related to the fault are extracted according to the fault type, corresponding control module names, namely data acquisition objects, are locked according to the key data items, acquisition strategies corresponding to the control module names are extracted, data acquisition is carried out on the control modules according to the acquisition strategies in a targeted manner, required key data items are obtained, the specific fault reason is analyzed according to the key data items, manual screening and troubleshooting from mass data are not needed after the fault occurs, the fault troubleshooting efficiency is greatly improved, data are automatically acquired and analyzed after the fault occurs, and the enterprise operation cost is greatly reduced.
Referring to fig. 4, a schematic structural diagram of a fault data collecting and analyzing system according to a third embodiment of the present invention is shown, where the system includes:
the fault signal receiving module 10 is used for monitoring whether a fault signal sent by the CAN bus is received every first preset time;
further, the fault signal receiving module 10 further includes:
the state message receiving unit is used for acquiring vehicle running state messages sent by the CAN bus at intervals of first preset time and acquiring current fault state bit information according to the vehicle running state messages;
and the fault signal judging unit is used for judging whether the vehicle has a fault or not according to the fault state bit information.
The key data item retrieving module 20 is configured to, if a fault signal sent by a CAN bus is received, obtain a fault type according to the fault signal, and retrieve one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
the acquisition strategy acquisition module 30 is used for respectively acquiring corresponding control module names according to each key data item, and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
and the fault analysis module 40 is configured to collect the corresponding key data item from the corresponding control module according to the collection policy, and analyze the obtained key data item to obtain a fault cause according to an analysis result.
Further, the fault analysis module 40 further includes:
the key data reissue unit is used for calling reissue time corresponding to the fault type from a preset reissue time table according to the fault type and acquiring various key data items before the fault occurs according to the receiving time of the fault signal and the reissue time corresponding to the fault type;
and the fault data detection unit is used for acquiring real fault key index values at all moments according to various key data items before the fault occurs and various key data items after the fault occurs, and judging whether the real fault key index value at each moment exceeds an error standard range.
Further, the fault data detection unit further includes:
the checking data table constructing subunit is used for configuring corresponding standard fault key index values and error standard values for each known fault type to obtain a fault checking data table;
the standard data calling subunit is used for calling out a corresponding standard fault key index value and a corresponding error standard value from the fault checking data table according to the fault type corresponding to the fault signal;
the real error value detection subunit is used for obtaining a real error value according to the real fault key index value at each moment and the corresponding standard fault key index value and judging whether the real error value is greater than the error standard value or not;
and the fault data uploading subunit is used for judging each key data item at the moment as fault data if the real error value is greater than the error standard value, and uploading all fault data to the cloud service monitoring platform.
Further, in some optional embodiments of the present invention, the system further comprises:
the fault definition module is used for acquiring a plurality of known fault types and defining at least one key data item according to the fault characteristics of each fault type, wherein the key data item comprises control vehicle condition data, engine state data and controller state data;
and the key data item binding module is used for associating any one known fault type with the key data item corresponding to each known fault type, and summarizing all association results to obtain the preset fault key mapping table.
Further, in some optional embodiments of the present invention, the system further comprises:
the error range acquisition module is used for respectively acquiring the data sensitivities of the vehicle condition data, the engine state data and the controller state data so as to acquire a corresponding error range according to the sensitivity of each key data item;
and the acquisition cycle configuration module is used for respectively defining corresponding acquisition cycles according to the error ranges corresponding to each key data item and formulating an acquisition strategy according to the key data items and the acquisition cycles corresponding to each key data item.
In conclusion, according to the fault data acquisition and analysis system, faults are monitored in real time, fault data acquisition is triggered by the faults, accurate fault data analysis is provided, accurate fault reasons are obtained, massive data do not need to be screened and checked one by one after the fault data occur, fault checking efficiency is greatly improved, and enterprise operation cost is reduced. The method comprises the steps of firstly, continuously monitoring whether a fault signal sent by a CAN bus is received in real time, obtaining a corresponding fault type according to the fault signal if the fault signal is monitored, taking out one or more key data items related to the fault through the fault type, locking corresponding control module names, namely data acquisition objects, according to the key data items, and then taking out acquisition strategies corresponding to the control module names respectively, so that data acquisition is carried out on each control module according to the acquisition strategies in a targeted manner, required various key data items are obtained, the specific fault reason is analyzed according to the key data items, manual screening and troubleshooting from mass data are not required to be arranged after the fault occurs, the fault troubleshooting efficiency is greatly improved, and data are automatically acquired and analyzed through triggering once the fault occurs, so that the enterprise operation cost is greatly reduced.
In another aspect, the present invention further provides a storage medium, on which one or more programs are stored, and the programs, when executed by a processor, implement the fault data collection and analysis method described above.
In another aspect of the present invention, an electronic device is further provided, which includes a memory and a processor, where the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so as to implement the above fault data collection and analysis method.
Those of skill in the art will understand that the logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be viewed as implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following technologies, which are well known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is specific and detailed, but not to be understood as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A fault data acquisition and analysis method is applied to a vehicle-mounted terminal and is characterized by comprising the following steps:
monitoring whether a fault signal sent by a CAN bus is received every first preset time;
if a fault signal sent by a CAN bus is received, acquiring a fault type according to the fault signal, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
respectively acquiring corresponding control module names according to each key data item, and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
and acquiring the corresponding key data items from the corresponding control modules according to the acquisition strategy, and analyzing the acquired key data items to acquire fault reasons according to analysis results.
2. The method according to claim 1, wherein the step of acquiring a fault type according to the fault signal and retrieving one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type if the fault signal sent by the CAN bus is received comprises:
acquiring a plurality of known fault types, and defining at least one key data item according to the fault characteristics of each fault type, wherein the key data item comprises control vehicle condition data, engine state data and controller state data;
and associating any one known fault type with the key data item corresponding to each known fault type, and summarizing all association results to obtain the preset fault key mapping table.
3. The method according to claim 2, wherein the step of obtaining the corresponding control module name according to each key data item and calling out the collection strategy corresponding to each control module name from the preset data collection association table according to the control module name comprises:
respectively acquiring data sensitivities of vehicle condition data, engine state data and controller state data so as to acquire a corresponding error range according to the sensitivity of each key data item;
and respectively defining corresponding acquisition cycles according to the error range corresponding to each key data item, and formulating an acquisition strategy according to the key data items and the acquisition cycles corresponding to each key data item.
4. The method according to claim 3, wherein the step of acquiring the corresponding key data item from the corresponding control module according to the acquisition policy and analyzing the acquired key data item to acquire the cause of the fault according to the analysis result comprises:
calling out reissue time corresponding to the fault type from a preset reissue time table according to the fault type, and acquiring various key data items before the fault occurs according to the receiving time of the fault signal and the reissue time corresponding to the fault type;
and acquiring real fault key index values at all moments according to various key data items before the fault occurs and various key data items after the fault occurs, and judging whether the real fault key index value at each moment exceeds an error standard range.
5. The method according to claim 4, wherein the step of obtaining the actual fault key index values at all times according to the various key data items before the occurrence of the fault and the various key data items after the occurrence of the fault and determining whether the actual fault key index value at each time exceeds the error criterion range includes:
respectively configuring corresponding standard fault key index values and error standard values for each known fault type to obtain a fault checking data table;
calling out a corresponding standard fault key index value and a corresponding error standard value from the fault checking data table according to the fault type corresponding to the fault signal;
and acquiring a real error value according to the real fault key index value at each moment and the corresponding standard fault key index value, and judging whether the real error value is greater than an error standard value or not.
6. The method for collecting and analyzing fault data according to claim 1, wherein the step of monitoring whether a fault signal transmitted by a CAN bus is received every first preset time comprises:
acquiring a vehicle running state message sent by a CAN bus at intervals of a first preset time, and acquiring current fault state bit information according to the vehicle running state message;
and judging whether the vehicle has a fault according to the fault state bit information.
7. The method according to claim 5, wherein the step of obtaining a true error value according to the true fault key index value and the corresponding standard fault key index value at each time, and determining whether the true error value is greater than the error standard value further comprises:
and if the real error value is larger than the error standard value, determining each key data item at the moment as fault data, and uploading all fault data to a cloud service monitoring platform.
8. The utility model provides a trouble data acquisition and analytic system, is applied to vehicle mounted terminal, its characterized in that, the system includes:
the fault signal receiving module is used for monitoring whether a fault signal sent by the CAN bus is received or not at intervals of first preset time;
the key data item calling module is used for acquiring a fault type according to a fault signal sent by a CAN bus if the fault signal is received, and calling one or more key data items corresponding to the fault type from a preset fault association mapping table according to the fault type;
the acquisition strategy acquisition module is used for respectively acquiring corresponding control module names according to each key data item and calling out acquisition strategies respectively corresponding to each control module name from a preset data acquisition association table according to the control module names;
and the fault analysis module is used for acquiring the corresponding key data items from the corresponding control module according to the acquisition strategy and analyzing the acquired key data items so as to acquire fault reasons according to analysis results.
9. A storage medium, comprising: the storage medium stores one or more programs which, when executed by a processor, implement the fault data collection and analysis method of any one of claims 1-7.
10. An electronic device, comprising a memory and a processor, wherein:
the memory is used for storing computer programs;
the processor is configured to implement the fault data collection and analysis method according to any one of claims 1 to 7 when executing the computer program stored in the memory.
CN202210848174.8A 2022-07-19 2022-07-19 Fault data acquisition and analysis method, system, storage medium and electronic equipment Pending CN115268396A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210848174.8A CN115268396A (en) 2022-07-19 2022-07-19 Fault data acquisition and analysis method, system, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210848174.8A CN115268396A (en) 2022-07-19 2022-07-19 Fault data acquisition and analysis method, system, storage medium and electronic equipment

Publications (1)

Publication Number Publication Date
CN115268396A true CN115268396A (en) 2022-11-01

Family

ID=83767604

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210848174.8A Pending CN115268396A (en) 2022-07-19 2022-07-19 Fault data acquisition and analysis method, system, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN115268396A (en)

Similar Documents

Publication Publication Date Title
US11978291B2 (en) Method and apparatus for remote vehicle diagnosis
US6862504B2 (en) System and method for detecting alternator condition
US10281909B2 (en) Signal measuring/diagnosing system, and method for applying the same to individual devices
EP2166422B1 (en) Method of alarm mask generation and condition monitoring of wind turbines
CN109901555B (en) Vehicle fault diagnosis method, equipment and storage medium
CN112946485A (en) Vehicle battery detection method, storage medium and device
US20100049473A1 (en) Validation process for fault detection of a device
CN113763592B (en) Vehicle feed detection method, system, readable storage medium and computer device
CN114839949A (en) Vehicle fault online diagnosis method and system
CN114548437A (en) Intelligent operation and maintenance system and method for rotating equipment based on industrial Internet of things
CN111267756B (en) Vehicle speed limit control method, vehicle and medium
CN115268396A (en) Fault data acquisition and analysis method, system, storage medium and electronic equipment
CN111198540B (en) Equipment monitoring method and device
WO2012027733A1 (en) Method and apparatus for remote vehicle diagnosis
CN116775464A (en) Whole vehicle testing method and system
CN113448301A (en) Fault diagnosis method and system based on OBD system
CN113300918A (en) Fault detection method of intelligent lamp pole, terminal device and storage medium
CN113172764A (en) Mixing station monitoring method and system
CN108561226B (en) Intelligent engine shutdown monitoring system and monitoring method thereof
CN111741042A (en) Oil consumption, driving track and safe driving integrated remote monitoring system
JP2021096616A (en) Vehicle data classification method and vehicle data classification device
CN116449794A (en) Monitoring method and device for ring automatic test, electronic equipment and storage medium
CN113419513A (en) Data processing method and device
CN117872199A (en) Battery health diagnosis method, diagnosis device, system and storage medium
CN117472033A (en) Abnormality determination method, device, equipment and medium for vehicle data stream

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination