Vehicle fault warning method, device, equipment and medium

Abstract

The invention discloses a vehicle fault warning method and device, equipment and a medium. The invention belongs to the technical field of Internet of Vehicles. The method comprises the following steps: acquiring component monitoring data obtained by coding a component unit according to a preset coding rule; analyzing the component monitoring data to obtain monitoring information; when it is identified that the monitoring information comprises fault code information, determining fault information of the component unit according to the fault code information; and sending the fault information to a trip computer so as to display the fault information through the trip computer. By adopting the technical scheme, the purposes of monitoring the running condition of the vehicle in real time and automatically identifying the vehicle fault can be achieved, and the efficiency of analyzing the vehicle fault and the timeliness of fault warning are improved.

Description

Technical Field

[0001] This application belongs to the field of vehicle networking technology, specifically relating to a vehicle fault alarm method, device, equipment, and medium. Background Technology

[0002] With the continuous development of the automotive industry, automatic fault diagnosis and fault reporting have gradually become the development trend of in-vehicle systems. Timely reporting of vehicle faults to the owner and remote monitoring terminal can greatly improve the safety of vehicles during use.

[0003] In related technologies, the vehicle owner or vehicle status monitoring personnel usually send a vehicle status check request through the vehicle terminal. Then, the various component nodes in the vehicle upload the monitored data to the vehicle's back-end server or cloud based on the check request. The back-end server or cloud performs data analysis and fault statistics to achieve remote fault diagnosis, and the diagnosed fault information is fed back to the vehicle terminal.

[0004] However, the relevant technologies cannot directly read vehicle fault information and require fault analysis through a backend server or cloud, which results in low efficiency in vehicle fault analysis and untimely fault reporting. Summary of the Invention

[0005] The purpose of this application is to provide a vehicle fault alarm method, device, equipment, and medium that can solve the problems of low efficiency in vehicle fault analysis and untimely fault reporting. By analyzing component monitoring data, monitoring information is obtained. When fault code information is identified in the monitoring information, the fault information of the component unit is determined based on the fault code information. This can achieve the purpose of real-time monitoring of vehicle operation and automatic identification of vehicle faults, thereby improving the efficiency of vehicle fault analysis and the timeliness of fault alarm.

[0006] In a first aspect, embodiments of this application provide a vehicle fault alarm method, the method being executed by a microcontroller connected to at least one component unit of the vehicle; the method includes:

[0007] Obtain component monitoring data obtained by encoding component units according to pre-set encoding rules;

[0008] The component monitoring data is parsed to obtain monitoring information;

[0009] If the monitoring information includes fault code information, the fault information of the component unit is determined based on the fault code information;

[0010] The fault information is sent to the vehicle's computer so that the fault information can be displayed on the vehicle's computer.

[0011] This solution addresses the issues of low efficiency in vehicle fault analysis and untimely fault reporting. By analyzing component monitoring data, monitoring information is obtained. When fault code information is identified in the monitoring information, the fault information of the component unit is determined based on the fault code information. This achieves the goal of real-time monitoring of vehicle operation and automatic identification of vehicle faults, improving the efficiency of vehicle fault analysis and the timeliness of fault alarms.

[0012] Optionally, the fault information of the component unit can be determined based on the fault code information, including:

[0013] Identify the faulty component in the component unit based on the fault code information;

[0014] Obtain the correlation between preset fault codes and fault information, and determine the fault information of the faulty component based on the fault code information and the correlation.

[0015] The beneficial effect of this solution is that by identifying the faulty component in the component unit, and determining the fault information of the faulty component based on the fault code information and the correlation between the preset fault codes and the fault information, the goal of directly determining the fault information based on the fault code can be achieved, which improves the efficiency of component fault identification and helps vehicle repair personnel quickly find the cause of the fault, and helps vehicle repair centers quickly locate the fault and repair it.

[0016] Optionally, before determining the faulty component in the component unit based on the fault code information, the method further includes:

[0017] Delete component monitoring data;

[0018] Send a cycle monitoring command to the component unit to obtain the cycle monitoring data of the component unit;

[0019] The cyclic monitoring data is analyzed to obtain cyclic monitoring information;

[0020] If the fault code information in the cyclic monitoring information is the same, the faulty component in the component unit is determined based on the fault code information.

[0021] The beneficial effect of this solution is that by deleting component monitoring data, the cyclic monitoring information of the component unit is obtained. When the fault code information in the cyclic monitoring information is the same, the fault component in the component unit is determined based on the fault code information. This achieves the purpose of verifying the accuracy of the fault code information before determining the fault component in the component unit based on the fault code information, and further improves the accuracy of subsequent determination of the fault component.

[0022] Optionally, the component monitoring data can be parsed, including:

[0023] Obtain the code element output format of the inspection tool in the component unit;

[0024] Generate symbol mapping relationships based on symbol output format and preset symbol readable format;

[0025] Based on the symbol mapping relationship, the component monitoring data is mapped to a preset symbol readable format to obtain monitoring information.

[0026] The beneficial effect of this solution is that by obtaining the symbol output format of the inspection tool in the component unit, generating a symbol mapping relationship based on the symbol output format and the preset symbol readable format, and mapping the component monitoring data to the preset symbol readable format based on the symbol mapping relationship, the monitoring information can be obtained. This can ensure the readability of the component unit monitoring data, thereby improving the accuracy of subsequent component fault determination based on the monitoring information.

[0027] Optionally, the microcontroller is also connected to the vehicle's T-BOX;

[0028] After determining the fault information of the component unit based on the fault code information, the process includes:

[0029] The fault information is sent to the T-BOX so that the fault information can be forwarded to the cloud controller via the T-BOX.

[0030] The beneficial effect of this solution is that it enables remote display and control of vehicle fault information, thereby improving the timeliness of vehicle status monitoring and fault handling.

[0031] Optionally, after parsing the component monitoring data to obtain monitoring information, the method also includes:

[0032] Identify voltage monitoring data in the monitoring information;

[0033] Determine whether there are any anomalies in the voltage monitoring data based on a preset standard voltage threshold;

[0034] In the event of abnormal voltage monitoring data, historical voltage monitoring data within a preset time period is obtained.

[0035] Based on historical voltage monitoring data, voltage monitoring data, and preset standard voltage thresholds, the system predicts the circuit faults of the vehicle and sends the prediction results to the vehicle's computer for display.

[0036] The beneficial effects of this solution are that by identifying voltage monitoring data in the monitoring information, determining whether there are any abnormalities in the voltage monitoring data based on a preset standard voltage threshold, and in the event of abnormalities, obtaining historical voltage monitoring data within a preset time period, and predicting the circuit fault prediction results of the vehicle based on the historical voltage monitoring data, the current voltage monitoring data, and the preset standard voltage threshold, the circuit fault prediction results are sent to the vehicle's computer for display. This achieves the purpose of early warning and timely diagnosis of circuit faults in the vehicle, promptly issuing warnings to the driver or vehicle maintenance personnel for early handling, preventing more serious problems from occurring, reducing vehicle maintenance costs and expenses, and improving the intelligence level of vehicle fault diagnosis.

[0037] Optionally, based on historical voltage monitoring data, voltage monitoring data, and preset standard voltage thresholds, the predicted circuit fault results for the vehicle include:

[0038] Identify the changing patterns in voltage monitoring data and historical voltage monitoring data;

[0039] When the change pattern is the same as the change pattern before the voltage fault, the circuit fault prediction result is that a fault will occur, and the time when the fault will occur is predicted.

[0040] The beneficial effects of this solution are that by identifying the changing patterns of voltage monitoring data and historical voltage monitoring data, and when the changing patterns are the same as those before the voltage fault, the circuit fault prediction result is obtained as a fault that will occur, and the time of the fault is predicted. This can reduce the amount of calculation required for circuit fault prediction and improve prediction efficiency. Based on the accumulation of long-term fault monitoring data, the fault time is determined according to the actual changing patterns of the data before the fault, which improves the accuracy of circuit fault prediction and is conducive to predictive maintenance and product improvement of vehicles.

[0041] Optionally, the fault information includes at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault, and at least one of the following fault conditions in each of the above component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

[0042] The beneficial effects of this solution are that by monitoring the faults of each component unit and setting fault information including at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault, and the presence of at least one of the following fault conditions in each of the above component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating, the scope of vehicle fault monitoring can be expanded, further improving the comprehensiveness of vehicle fault monitoring. It can monitor the data of various ECUs in the vehicle system in real time, ensuring that the vehicle operates in the best condition, timely detects and repairs potential faults, reduces the occurrence of traffic accidents, and improves the safety of vehicle driving.

[0043] Secondly, embodiments of this application provide a vehicle fault alarm device, the device being equipped with a microcontroller connected to at least one component unit of the vehicle; the device includes:

[0044] The component monitoring data acquisition module is used to acquire component monitoring data obtained by encoding component units according to pre-set encoding rules.

[0045] The monitoring information parsing module is used to parse the component monitoring data to obtain monitoring information;

[0046] The fault information determination module is used to determine the fault information of the component unit based on the fault code information when the monitoring information, including the fault code information, is identified.

[0047] The fault information display module is used to send fault information to the vehicle's computer so that the fault information can be displayed on the vehicle's computer.

[0048] This solution addresses the issues of low efficiency in vehicle fault analysis and untimely fault reporting. By analyzing component monitoring data, monitoring information is obtained. When fault code information is identified in the monitoring information, the fault information of the component unit is determined based on the fault code information. This achieves the goal of real-time monitoring of vehicle operation and automatic identification of vehicle faults, improving the efficiency of vehicle fault analysis and the timeliness of fault alarms.

[0049] Optional, the fault information determination module is specifically used for:

[0050] Identify the faulty component in the component unit based on the fault code information;

[0051] Obtain the correlation between preset fault codes and fault information, and determine the fault information of the faulty component based on the fault code information and the correlation.

[0052] The beneficial effect of this solution is that by identifying the faulty component in the component unit, and determining the fault information of the faulty component based on the fault code information and the correlation between the preset fault codes and the fault information, the goal of directly determining the fault information based on the fault code can be achieved, which improves the efficiency of component fault identification and helps vehicle repair personnel quickly find the cause of the fault, and helps vehicle repair centers quickly locate the fault and repair it.

[0053] Optionally, the device also includes:

[0054] The data deletion module is used to delete component monitoring data;

[0055] The cycle monitoring module is used to send cycle monitoring commands to the component units in order to obtain cycle monitoring data from the component units.

[0056] The loop monitoring data parsing module is used to parse the loop monitoring data to obtain loop monitoring information;

[0057] The fault information determination module is used to determine the fault component in the fault code information determination component unit when the fault code information is found to be the same in the cyclic monitoring information.

[0058] The beneficial effect of this solution is that by deleting component monitoring data, the cyclic monitoring information of the component unit is obtained. When the fault code information in the cyclic monitoring information is the same, the fault component in the component unit is determined based on the fault code information. This achieves the purpose of verifying the accuracy of the fault code information before determining the fault component in the component unit based on the fault code information, and further improves the accuracy of subsequent determination of the fault component.

[0059] Optional, a monitoring information parsing module, specifically used for:

[0060] Obtain the code element output format of the inspection tool in the component unit;

[0061] Generate symbol mapping relationships based on symbol output format and preset symbol readable format;

[0062] Based on the symbol mapping relationship, the component monitoring data is mapped to a preset symbol readable format to obtain monitoring information.

[0063] The beneficial effect of this solution is that by obtaining the symbol output format of the inspection tool in the component unit, generating a symbol mapping relationship based on the symbol output format and the preset symbol readable format, and mapping the component monitoring data to the preset symbol readable format based on the symbol mapping relationship, the monitoring information can be obtained. This can ensure the readability of the component unit monitoring data, thereby improving the accuracy of subsequent component fault determination based on the monitoring information.

[0064] Optionally, the microcontroller is also connected to the vehicle's T-BOX;

[0065] After determining the fault information of the component unit based on the fault code information, the process includes:

[0066] The fault information is sent to the T-BOX so that the fault information can be forwarded to the cloud controller via the T-BOX.

[0067] The beneficial effect of this solution is that it enables remote display and control of vehicle fault information, thereby improving the timeliness of vehicle status monitoring and fault handling.

[0068] Optionally, the device also includes:

[0069] The voltage monitoring data identification module is used to identify voltage monitoring data in the monitoring information;

[0070] The voltage anomaly detection module is used to determine whether there are anomalies in the voltage monitoring data based on a preset standard voltage threshold.

[0071] The historical voltage data acquisition module is used to acquire historical voltage monitoring data within a preset time period when there are abnormalities in the voltage monitoring data.

[0072] The circuit fault prediction module is used to predict the circuit fault prediction results of the vehicle based on historical voltage monitoring data, voltage monitoring data and preset standard voltage thresholds, and send the circuit fault prediction results to the vehicle computer for display.

[0073] The beneficial effects of this solution are that by identifying voltage monitoring data in the monitoring information, determining whether there are any abnormalities in the voltage monitoring data based on a preset standard voltage threshold, and in the event of abnormalities, obtaining historical voltage monitoring data within a preset time period, and predicting the circuit fault prediction results of the vehicle based on the historical voltage monitoring data, the current voltage monitoring data, and the preset standard voltage threshold, the circuit fault prediction results are sent to the vehicle's computer for display. This achieves the purpose of early warning and timely diagnosis of circuit faults in the vehicle, promptly issuing warnings to the driver or vehicle maintenance personnel for early handling, preventing more serious problems from occurring, reducing vehicle maintenance costs and expenses, and improving the intelligence level of vehicle fault diagnosis.

[0074] Optional, a circuit fault prediction module, specifically used for:

[0075] Identify the changing patterns in voltage monitoring data and historical voltage monitoring data;

[0076] When the change pattern is the same as the change pattern before the voltage fault, the circuit fault prediction result is that a fault will occur, and the time when the fault will occur is predicted.

[0077] The beneficial effects of this solution are that by identifying the changing patterns of voltage monitoring data and historical voltage monitoring data, and when the changing patterns are the same as those before the voltage fault, the circuit fault prediction result is obtained as a fault that will occur, and the time of the fault is predicted. This can reduce the amount of calculation required for circuit fault prediction and improve prediction efficiency. Based on the accumulation of long-term fault monitoring data, the fault time is determined according to the actual changing patterns of the data before the fault, which improves the accuracy of circuit fault prediction and is conducive to predictive maintenance and product improvement of vehicles.

[0078] Optionally, the fault information includes at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault, and at least one of the following fault conditions in each of the above component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

[0079] The beneficial effects of this solution are that by monitoring the faults of each component unit and setting fault information including at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault, and the presence of at least one of the following fault conditions in each of the above component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating, the scope of vehicle fault monitoring can be expanded, further improving the comprehensiveness of vehicle fault monitoring. It can monitor the data of various ECUs in the vehicle system in real time, ensuring that the vehicle operates in the best condition, timely detects and repairs potential faults, reduces the occurrence of traffic accidents, and improves the safety of vehicle driving.

[0080] Thirdly, embodiments of this application provide an electronic device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the first aspect.

[0081] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, and when the program or instructions are executed by a processor, they implement the steps of the method as described in the first aspect.

[0082] Fifthly, embodiments of this application provide a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect.

[0083] In this embodiment, component monitoring data is obtained by encoding component units according to a pre-set encoding rule; the component monitoring data is parsed to obtain monitoring information; if the monitoring information includes fault code information, the fault information of the component unit is determined based on the fault code information; the fault information is sent to the vehicle computer for display. This vehicle fault alarm method solves the problems of low efficiency in vehicle fault analysis and untimely fault reporting. By parsing component monitoring data to obtain monitoring information, and determining the fault information of the component unit based on the fault code information when the monitoring information includes fault code information, the method achieves real-time monitoring of vehicle operation and automatic identification of vehicle faults, improving the efficiency of vehicle fault analysis and the timeliness of fault alarms. Attached Figure Description

[0084] Figure 1 This is a flowchart illustrating the vehicle fault alarm method provided in the embodiments of this application;

[0085] Figure 2 This is a schematic diagram of the vehicle component monitoring system provided in this application;

[0086] Figure 3 This is a schematic diagram of the process for parsing monitoring data provided in an embodiment of this application;

[0087] Figure 4 This is a schematic diagram of the symbol mapping structure provided in this application;

[0088] Figure 5 This is a schematic diagram of the symbol bit field conversion provided in this application;

[0089] Figure 6 This is a flowchart illustrating another vehicle fault alarm method provided in an embodiment of this application;

[0090] Figure 7 This is a schematic diagram of the vehicle fault alarm device provided in the embodiments of this application;

[0091] Figure 8 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0092] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0093] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0094] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0095] The vehicle fault alarm method, device, equipment, and medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0096] In existing technologies, vehicle owners or vehicle status monitoring personnel typically send vehicle status check requests via an in-vehicle terminal. Based on these requests, various component nodes within the vehicle upload the monitored data to the vehicle's backend server or cloud. The backend server or cloud then performs data analysis and fault statistics to achieve remote fault diagnosis, and the diagnosed fault information is fed back to the in-vehicle terminal. However, these technologies cannot directly read vehicle fault information; they require fault analysis through a backend server or cloud, resulting in low efficiency in fault analysis and untimely fault reporting.

[0097] In this embodiment of the invention, by parsing the component monitoring data to obtain monitoring information, and when the monitoring information includes fault code information, the fault information of the component unit is determined based on the fault code information. This can solve the problems of low efficiency in vehicle fault analysis and untimely fault reporting, and can achieve the purpose of real-time monitoring of vehicle operation and automatic identification of vehicle faults, thereby improving the efficiency of vehicle fault analysis and the timeliness of fault alarms.

[0098] Figure 1 This is a flowchart illustrating the vehicle fault alarm method provided in this application. The method is executed by a microcontroller, which is connected to at least one component unit of the vehicle; such as Figure 1 As shown, the specific steps include the following:

[0099] S101, Obtain component monitoring data obtained by encoding the component unit according to the pre-set encoding rules.

[0100] First, this solution can be used in scenarios where vehicle faults are monitored and diagnosed in real time, especially in scenarios where vehicle faults are remotely monitored or displayed on the vehicle's computer.

[0101] Based on the above usage scenarios, it is understood that the executing entity of this application can be a microcontroller connected to at least one component unit of the vehicle. This microcontroller has functions such as fault monitoring, data processing, fault identification, and fault reporting for the connected component unit.

[0102] A microcontroller is an embedded device that integrates computing capabilities. It integrates a central processing unit (CPU), memory, timers, input / output interfaces, and other functional units, and is typically used to control and monitor various electronic devices and systems. In this solution, the microcontroller primarily receives and processes data stored in connected component units, performs component fault analysis based on the data processing results, and uploads the analysis results to the vehicle's computer and remote monitoring terminals such as T-BOX. This microcontroller enables real-time monitoring and diagnosis of vehicle operating status and identification of vehicle faults, improving driving safety, reducing repair time and maintenance costs, and enhancing overall vehicle performance.

[0103] A component unit can be a combination of components obtained by dividing the various components in a vehicle according to their functions or types. A component unit may include one or more vehicle components.

[0104] Figure 2 This is a schematic diagram of the vehicle component monitoring system provided in this application.

[0105] like Figure 2 As shown, the component unit may include: a display component unit, an antenna component unit, an audio component unit, an imaging component unit, a USB voltage monitoring unit, and a B+ voltage monitoring unit. The display component unit includes: a central control display screen, an instrument panel display screen, a HUD, a passenger-side display screen, a rear-seat display screen, a rearview mirror, a transparent A-pillar, a streaming media display, and an armrest screen. The antenna component unit includes an AM / FM antenna, a DAB antenna, a GPS antenna, a BT / WIFI antenna, and a V2X antenna. The imaging component unit includes: an AVM camera, an OMS camera, a DMS camera, a DVR camera, and a rearview camera. The microcontroller reads the register status of the display component unit, antenna component unit, audio component unit, and imaging component unit via, but not limited to, I2C, I3C, or SPI communication protocols, collects the component monitoring data detected by each component unit, converts it according to preset rules, and reports it to the vehicle computer via CAN messages and / or to the T-BOX networking component via the CAN bus. After collecting monitoring data from various component units, the microcontroller needs to identify and process the fault information of each component unit, and then report the fault information to the vehicle's computer or send it to the T-BOX networking component to achieve remote display and monitoring of the vehicle's operating status. The T-BOX networking component forwards the received fault information to the cloud controller to enable remote control of the vehicle. Fault information in each component unit includes, but is not limited to, short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

[0106] In this solution, the controller analyzes monitoring data to provide suggestions to vehicle maintenance or monitoring personnel to optimize vehicle performance and fuel economy. Users can remotely monitor vehicle status and obtain maintenance suggestions through the vehicle's computer or device terminal, increasing driving convenience and comfort. They can also monitor vehicle status through the in-vehicle display or mobile application, receive maintenance reminders, and understand the causes of malfunctions. Vehicle owners or service centers can remotely monitor vehicle status and perform timely troubleshooting. For large-scale vehicle operation companies, the vehicle component monitoring system in this solution can monitor each vehicle in the fleet in real time, improving operational efficiency and reducing maintenance costs.

[0107] Encoding rules can be used by component units to convert the monitored operational status data of each component into a unified format or a rule of the same type. Encoding the operational status data of each component ensures the correctness, stability, readability, and maintainability of the data. Component monitoring data can be the data obtained after encoding the operational status data of each component. Component monitoring data includes operational data under normal component conditions as well as operational data when a component malfunctions. Component monitoring data can be obtained through inspection tools pre-set in each component unit and can be stored in the registers of each component unit. The microcontroller can obtain the monitoring data of each component by reading the register status in real time.

[0108] In one embodiment, component monitoring data obtained by reading the register status of each component unit in real time, and encoding the component unit according to a pre-set encoding rule, can be obtained.

[0109] S102, parse the component monitoring data to obtain monitoring information.

[0110] Among them, monitoring information can be information representing the operating status of each component at each monitoring time.

[0111] In one embodiment, component monitoring data can be parsed using preset mapping rules to map it into readable data. This readable data can then be categorized by data type or format to obtain monitoring information. For example, when a component malfunctions, its monitoring data is a fault code. Parsing this data yields fault code format data and regular format data for normal component operation. Classifying the data based on its format allows determination of the monitoring information for each component state.

[0112] S103, if the monitoring information includes fault code information, determine the fault information of the component unit based on the fault code information.

[0113] Fault code information can represent the fault condition of a component. Different fault types of components, and different faults within the same fault type, correspond to different fault codes. The fault code information can determine the fault condition of the component. Fault information can describe the component's fault problem. Fault information corresponds to fault code information; different fault information corresponds to different fault codes. Fault information can include the identity information of the faulty component and a description of the fault. For example, which component has a fault of what degree. The component's identity information can be numbers or identifiers used to distinguish each component and locate its position within the vehicle. For example, the component's ID.

[0114] Tables 1 and 2 below show the fault descriptions for different faults within each fault type. Different fault types may contain the same fault or have the same or different descriptions, but different faults within the same fault type will have different fault codes, and the same fault will also have different fault codes across different fault types.

[0115] The table below only provides examples of two types of vehicle malfunctions; other malfunction types will not be discussed here.

[0116]

[0117]

[0118] Table 1

[0119]

[0120]

[0121] Table 2

[0122] In one embodiment, it can be determined whether the monitoring information includes fault code information by identifying whether the monitoring information includes data in the fault code format. If the monitoring information includes fault code information, the fault information of the component unit can be determined according to the preset correspondence between the fault code information and the fault information.

[0123] In one embodiment, optionally, determining the fault information of the component unit based on the fault code information includes:

[0124] Identify the faulty component in the component unit based on the fault code information;

[0125] Obtain the correlation between preset fault codes and fault information, and determine the fault information of the faulty component based on the fault code information and the correlation.

[0126] The faulty component can be one that fails to operate normally or whose operating parameters exceed standard operating thresholds. The association between preset fault codes and fault information can be a pre-defined correspondence between fault codes and fault information based on the fault type and description of each component. The association between fault codes and fault information is fixed and stored in the microprocessor.

[0127] In one embodiment, the faulty component in a component unit can be determined based on the component identity information in the fault code information. For example, when the component unit performs component inspection or data monitoring using a preset inspection tool, the monitored data and the identity IDs of each component can be stored together in the component unit's register. If the monitored data is fault data, the component can be determined as the faulty component in the component unit based on the component identity ID stored in the fault code information. The association between preset fault codes and fault information is obtained, and the fault information corresponding to the fault code information in the association is searched, thus identifying the fault information as the fault information of the faulty component.

[0128] This solution identifies the faulty component within the component unit and determines the fault information of the faulty component based on fault code information and the correlation between preset fault codes and fault information. This achieves the goal of directly determining fault information based on fault codes, improving the efficiency of component fault identification. It is beneficial for vehicle repair personnel to quickly find the cause of the fault and for vehicle repair centers to quickly locate and repair the fault.

[0129] In one embodiment, optionally, before determining the faulty component in the component unit based on the fault code information, the method further includes:

[0130] Delete component monitoring data;

[0131] Send a cycle monitoring command to the component unit to obtain the cycle monitoring data of the component unit;

[0132] The cyclic monitoring data is analyzed to obtain cyclic monitoring information;

[0133] If the fault code information in the cyclic monitoring information is the same, the faulty component in the component unit is determined based on the fault code information.

[0134] The cyclic monitoring instruction can be a notification used to instruct a component unit to perform multiple checks on its internal components. Cyclic monitoring data can be the data obtained during each check by the component unit. Cyclic monitoring information can be the information on the operating status of each component obtained after parsing the check data from each check.

[0135] In one embodiment, after identifying that the monitoring information includes fault code information, the component monitoring data in the component unit can be deleted, and a cyclic monitoring instruction can be sent to the component unit to cause the component unit to cyclically monitor each internal component according to the number of times specified in the cyclic monitoring instruction. The cyclic monitoring data of the component unit is obtained by reading the register status of the component unit. The cyclic monitoring data is decoded to obtain cyclic monitoring information. The fault code information in the cyclic monitoring information is compared to see if they are the same. If they are the same, it means that the multiple monitoring results of the component are consistent and the fault code information is accurate. At this time, the operation of determining the faulty component in the component unit based on the fault code information can be performed. If they are different, it means that the multiple monitoring results of the component are inconsistent and the fault code information is incorrectly judged. At this time, the operation of determining the faulty component in the component unit based on the fault code information is not performed.

[0136] This solution obtains the cyclic monitoring information of the component unit by deleting component monitoring data. When the fault code information in the cyclic monitoring information is the same, it performs the determination of the faulty component in the component unit based on the fault code information. This achieves the purpose of verifying the accuracy of the fault code information before determining the faulty component in the component unit, and further improves the accuracy of subsequent determination of the faulty component.

[0137] S104 sends the fault information to the vehicle's computer so that the fault information can be displayed on the vehicle's computer.

[0138] The vehicle's onboard computer is a device used to monitor, locate, display, and issue fault alarms for the vehicle's operating status. It can store fault information, helping maintenance personnel quickly and accurately determine the nature and location of the fault.

[0139] In one embodiment, a fault message can be generated based on fault information and sent to the vehicle computer via the CAN bus so that the fault information can be displayed on the vehicle computer.

[0140] In one embodiment, optionally, the microcontroller is also connected to the vehicle's T-BOX;

[0141] After determining the fault information of the component unit based on the fault code information, the following is included:

[0142] The fault information is sent to the T-BOX so that the fault information can be forwarded to the cloud controller via the T-BOX.

[0143] The T-BOX (Telematics Box) can be a networked component used for data collection and forwarding. In this solution, the T-BOX is primarily used to collect and forward vehicle fault information processed by the microcontroller. The cloud controller is a device used to process and store data from vehicle sensors and actuators, and to communicate with a cloud server. The cloud controller enables remote monitoring and intelligent scheduling of the vehicle, allowing vehicle owners or remote monitoring personnel to monitor the vehicle's location, driving status, fault information, and other key data in real time via a mobile app or onboard control platform, and to perform remote diagnostics and maintenance. In this solution, the cloud controller is primarily used to process and store fault information forwarded by the T-BOX.

[0144] In one embodiment, the microcontroller can connect to the vehicle's T-BOX via a CAN bus and exchange data, sending the processed fault information to the T-BOX so that the fault information can be forwarded to the cloud controller via the T-BOX.

[0145] This solution sends fault information to the T-BOX, which then forwards the fault information to the cloud controller. This enables remote display and control of vehicle fault information, improving the timeliness of vehicle status monitoring and fault handling.

[0146] The technical solution provided in this application embodiment obtains component monitoring data encoded by component units according to a pre-set encoding rule; parses the component monitoring data to obtain monitoring information; when the monitoring information includes fault code information, determines the fault information of the component unit based on the fault code information; and sends the fault information to the vehicle computer for display. This vehicle fault alarm method solves the problems of low efficiency in vehicle fault analysis and untimely fault reporting. By parsing component monitoring data to obtain monitoring information, and determining the fault information of the component unit based on the fault code information when the monitoring information includes fault code information, it achieves real-time monitoring of vehicle operation and automatic identification of vehicle faults, improving the efficiency of vehicle fault analysis and the timeliness of fault alarms.

[0147] Figure 3 This is a schematic diagram of the process for parsing monitoring data provided in an embodiment of this application. For example... Figure 3 As shown, the specific steps include the following:

[0148] S301, Obtain the symbol output format of the inspection tool in the component unit.

[0149] The inspection tool can be a device used to check the operational status of each component in the component unit. The inspection tool can automatically check for component faults and generate a fault code corresponding to the fault if a fault is found. The code element output format can be the format of the data output by the inspection tool. The code element output format of the inspection tool can be fixed.

[0150] In one embodiment, the symbol output format of the inspection tool can be determined based on the tool parameters of the inspection tool in the component unit.

[0151] S302 generates symbol mapping relationships based on symbol output format and preset symbol readable format.

[0152] The preset code element readable format can be a data format that the microprocessor can recognize. The code element mapping relationship can be the conversion relationship between the code element output format and the preset code element readable format.

[0153] In one embodiment, a symbol mapping relationship can be generated based on the symbol output format and a preset symbol readable format.

[0154] Figure 4 This is a schematic diagram of the symbol mapping structure provided in this application.

[0155] Figure 5 This is a schematic diagram of the symbol bit field conversion provided in this application.

[0156] like Figure 4-5 As shown, UDS 3-byte DTC data is mapped to J1939 DM1 DTC data. UDS 3-byte fault codes refer to fault codes in modern automotive electronic control units (ECUs) that follow the UDS (Unified Diagnostic Services) standard and are typically represented by three bytes. These three bytes represent different information: .RootDTC (Basic Fault Code): The first two bytes are called the RootDTC, which is an OBD diagnostic fault code, usually a five-digit fault code 1; .FTB (Fault Type Byte): The last byte is called the FTB, representing the specific type of fault information. J1939 DM1 is a diagnostic message in the SAE J1939 protocol used to report fault codes of the current active state. The DM1 message is defined by SAE J1939-73. The main function of the DM1 message is to report fault codes of the current active state. It periodically sends these fault codes via the CAN bus so that the system can monitor and control the status of the controller. The DM1 message can trigger the MIL (Malfunction Indicator) light and the red stop light to alert the driver or maintenance personnel that a malfunction has occurred.

[0157] The inspection tool in this solution can use UDS for diagnosis, and the microprocessor can define all CANIDs through J1939. By defining the arrangement and mapping relationship of the output codes of the inspection tool and the codes readable by the microprocessor, abnormal fault codes can be distinguished. Based on Figure 5 The bit field conversion in the process maps the 3-byte data output by the inspection tool into binary code, thus obtaining the final code data that the microcontroller can recognize.

[0158] The following is a code example for mapping UDS 3-byte DTC data to J1939 DM1 DTC data:

[0159] Example of UDS 3byte DTC according to SPN and FMI defined by SAE J1939:"SPN=1045(Trailer Brake Lamp)"FMI=14(Special Instructions)UDS 3byte DTC=0x15040E Example of complete UDS positive response CAN message with one DTC=CAN id 0x18DAFxYY(Fx=OffBoard tool Tester Address,YY=OnBoard generic ECUaddress)DLC 8Data field 0x07 0x59 0x02 0xFF 0x15 0x040x0E 0xSS(SS=specificDTC status bitfield)Example of complete DM1 CAN message with one DTC=CAN id0x18FECAYY(YY=OnBoard generic ECU address)DLC 8Data field 0xLL 0xLL(firsttwo bytes for Lamps Statuses)0x150x04 0x0E 0xOO(OO=specific DTCoccurenceCount>1).

[0160] S303 maps component monitoring data to a preset code element readable format based on the code element mapping relationship to obtain monitoring information.

[0161] In one embodiment, component monitoring data can be mapped to a preset readable code format according to the code mapping relationship, so that the component monitoring data can be read and parsed, and monitoring information can be obtained by parsing the component monitoring data in the readable format.

[0162] The technical solution provided in this application obtains the code output format of the inspection tool in the component unit, generates a code mapping relationship based on the code output format and a preset code readable format, and maps the component monitoring data to the preset code readable format based on the code mapping relationship to obtain monitoring information. This can ensure the readability of the component unit monitoring data and improve the accuracy of subsequent component fault determination based on monitoring information.

[0163] Figure 6 This is a flowchart illustrating another vehicle fault alarm method provided in an embodiment of this application. The method is executed by a microcontroller, which is connected to at least one component unit of the vehicle, such as... Figure 6 As shown, the specific steps include the following:

[0164] S601, Obtain component monitoring data obtained by encoding the component unit according to the pre-set encoding rules.

[0165] S602, the monitoring data of the component is parsed to obtain monitoring information.

[0166] S60311, if the monitoring information includes fault code information, determine the fault information of the component unit based on the fault code information.

[0167] S60312, the fault information is sent to the vehicle computer so that the fault information can be displayed on the vehicle computer.

[0168] S60321 identifies voltage monitoring data in the monitoring information.

[0169] The voltage monitoring data can represent the vehicle's voltage status under its current operating conditions. This includes B+ voltage monitoring data and USB voltage monitoring data.

[0170] In one embodiment, voltage monitoring data in the monitoring information can be identified based on the data characteristics in the monitoring information and the data characteristics of the voltage monitoring data.

[0171] S60322 determines whether there are any abnormalities in the voltage monitoring data based on a preset standard voltage threshold.

[0172] The preset standard voltage threshold can be a pre-set standard range of voltage values ​​under normal vehicle operating conditions.

[0173] In one embodiment, it can be determined whether there is an anomaly in the voltage monitoring data by identifying whether the voltage monitoring data meets a preset standard voltage threshold.

[0174] For example, if the monitored voltage is B+ voltage monitoring data, and the normal range of B+ voltage monitoring data is [9V, 16V], then the preset standard voltage threshold can be [8.5V, 16.5V]. If the voltage detection data is lower than 8.5V, it is determined that the voltage monitoring data is abnormal, and the current vehicle's B+ voltage is in an undervoltage state; if the voltage detection data is higher than 16.5V, it is determined that the voltage monitoring data is abnormal, and the current vehicle's B+ voltage is in a high-voltage state. If the monitored voltage is USB voltage monitoring data, and the normal range of USB voltage monitoring data is [4.75V, 5.25V], then the preset standard voltage threshold can be [4.5V, 5.5V]. If the voltage detection data is lower than 4.5V, it is determined that the voltage monitoring data is abnormal, and the current vehicle's USB voltage is in an undervoltage state; if the voltage detection data is higher than 5.5V, it is determined that the voltage monitoring data is abnormal, and the current vehicle's USB voltage is in a high-voltage state.

[0175] S60323: In the event of abnormal voltage monitoring data, acquire historical voltage monitoring data within a preset time period.

[0176] Historical voltage monitoring data can be voltage data acquired in real time or at regular intervals before the current moment.

[0177] In one embodiment, if there is an anomaly in the voltage monitoring data, historical voltage monitoring data within a preset time period can be obtained by reading the voltage data stored in the register.

[0178] S60324, based on historical voltage monitoring data, voltage monitoring data and preset standard voltage threshold, predicts the circuit fault prediction results of the vehicle, and sends the circuit fault prediction results to the vehicle computer so that the circuit fault prediction results can be displayed on the vehicle computer.

[0179] The circuit fault prediction result can be information about impending faults in the vehicle's electrical system. This result includes the type of circuit fault and the component causing the fault. Fault types include, but are not limited to, high or low B+ voltage and high or low USB voltage.

[0180] In one embodiment, the voltage change trend can be determined based on historical voltage monitoring data, and the voltage data of the vehicle at the next moment can be predicted by combining the voltage monitoring data and the change trend. Based on the relationship between the predicted voltage data and the preset standard voltage threshold, the circuit fault that will occur in the vehicle at the next moment or after a preset time period can be predicted. The circuit fault prediction result is sent to the vehicle computer so that the circuit fault prediction result can be displayed on the vehicle computer.

[0181] In one embodiment, optionally, predicting the vehicle's circuit fault prediction results based on historical voltage monitoring data, voltage monitoring data, and a preset standard voltage threshold includes:

[0182] Identify the changing patterns in voltage monitoring data and historical voltage monitoring data;

[0183] When the change pattern is the same as the change pattern before the voltage fault, the circuit fault prediction result is that a fault will occur, and the time when the fault will occur is predicted.

[0184] The variation patterns of voltage monitoring data and historical voltage monitoring data can be the trends of actual voltage monitoring data over a preset period of time, both at the current moment and prior to the current moment. The variation patterns prior to a voltage fault can be the trends of voltage monitoring data over a preset period of time prior to the occurrence of the voltage fault, summarized in advance based on voltage monitoring data from previous voltage faults. Different fault types correspond to different variation patterns prior to the voltage fault.

[0185] In one embodiment, the change curves of voltage monitoring data and historical voltage monitoring data as a function of monitoring time can be plotted. The change patterns of voltage monitoring data and historical voltage monitoring data can be identified by an image recognition algorithm. If the change pattern is the same as the change pattern before the voltage fault, the circuit fault prediction result is determined to be a fault that will occur. Based on the fault type and fault time corresponding to the change pattern before the voltage fault, the type of fault that will occur in the vehicle's circuit system and the time of occurrence of the fault are predicted.

[0186] This solution identifies the changing patterns of voltage monitoring data and historical voltage monitoring data. When the changing patterns are the same as those before a voltage fault, it predicts that a circuit fault will occur and forecasts the time of occurrence. This reduces the computational load for circuit fault prediction and improves prediction efficiency. Based on the accumulation of long-term fault monitoring data, it determines the fault time according to the actual changing patterns of the data before the fault, thus improving the accuracy of circuit fault prediction. This is beneficial for predictive maintenance of vehicles and product improvement.

[0187] In one embodiment, optionally, the fault information includes at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault, and at least one of the following fault conditions in each of the above component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

[0188] Among these, display component unit failures can manifest as the display unit's inability to properly display vehicle information. Examples include: the display screen not lighting up, flickering, and interlaced display. Antenna component unit failures can manifest as the vehicle's antenna failing to communicate properly or the radar system malfunctioning. Examples include: physical damage and loose connections. Audio component unit failures can manifest as the audio equipment failing to properly record or process audio data. Examples include: microphone malfunction. Camera component unit failures can manifest as the camera equipment failing to focus, record, or save video or image data properly. Examples include: the camera failing to capture images inside the vehicle. A short circuit to the power supply can cause current to flow directly through the positive and negative terminals of the power supply without passing through the load. A short circuit to ground can cause a part of the circuit to be directly connected to the ground (or the power supply's grounding terminal), causing current to bypass the entire circuit and flow directly to the ground. Overvoltage can cause the voltage to exceed the equipment's rated value, exceeding the normal voltage fluctuation range. Overcurrent can cause the current in the circuit to exceed its rated current value. Overheating can cause the motor's temperature to exceed the design-specified upper temperature limit during normal operation.

[0189] In one embodiment, the fault information may include a fault in at least one of the following components: a display component unit fault, an antenna component unit fault, an audio component unit fault, and a camera component unit fault, and at least one of the following fault conditions in the aforementioned component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

[0190] This solution expands the scope of vehicle fault monitoring by monitoring the faults of various component units and setting fault information including at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault. Furthermore, it addresses the presence of at least one fault condition in each of the aforementioned component units, such as short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating. This enhances the comprehensiveness of vehicle fault monitoring, enables real-time monitoring of data from various ECUs in the vehicle system, ensures optimal vehicle operation, timely detection and repair of potential faults, reduces traffic accidents, and improves vehicle safety during driving.

[0191] The technical solution provided in this application identifies voltage monitoring data in the monitoring information, determines whether there is an anomaly in the voltage monitoring data based on a preset standard voltage threshold, and if there is an anomaly in the voltage monitoring data, obtains historical voltage monitoring data within a preset time period, and predicts the circuit fault prediction result of the vehicle based on the historical voltage monitoring data, the voltage monitoring data, and the preset standard voltage threshold. The circuit fault prediction result is sent to the vehicle computer so that the circuit fault prediction result can be displayed on the vehicle computer. This can achieve the purpose of early warning and timely diagnosis of circuit faults in the vehicle, and issue a timely warning to the driver or vehicle maintenance personnel so as to deal with it in advance, prevent more serious problems from occurring, reduce vehicle maintenance costs and expenses, and improve the intelligence of vehicle fault diagnosis.

[0192] Figure 7 This is a schematic diagram of the vehicle fault alarm device provided in an embodiment of this application. The device is equipped with a microcontroller, which is connected to at least one component unit of the vehicle, such as... Figure 7 As shown, it specifically includes the following:

[0193] The component monitoring data acquisition module 701 is used to acquire component monitoring data obtained by encoding component units according to a pre-set encoding rule;

[0194] The monitoring information parsing module 702 is used to parse the monitoring data of the component to obtain monitoring information;

[0195] The fault information determination module 703 is used to determine the fault information of the component unit based on the fault code information when the monitoring information is identified to include fault code information.

[0196] The fault information display module 704 is used to send the fault information to the vehicle computer so that the fault information can be displayed on the vehicle computer.

[0197] Optionally, the fault information determination module 703 is specifically used for:

[0198] Based on the fault code information, the faulty component in the component unit is determined;

[0199] Obtain the association between preset fault codes and fault information, and determine the fault information of the faulty component based on the fault code information and the association.

[0200] Optionally, the device also includes:

[0201] The data deletion module is used to delete the monitoring data of the component;

[0202] A loop monitoring module is used to send loop monitoring instructions to the component unit in order to obtain loop monitoring data of the component unit;

[0203] The cyclic monitoring data parsing module is used to parse the cyclic monitoring data to obtain cyclic monitoring information;

[0204] The fault information determination module 703 is used to determine the faulty component in the component unit based on the fault code information when the fault code information in the cyclic monitoring information is the same.

[0205] Optionally, the monitoring information parsing module 702 is specifically used for:

[0206] Obtain the code element output format of the inspection tool in the component unit;

[0207] Generate a symbol mapping relationship based on the symbol output format and the preset symbol readable format;

[0208] Based on the symbol mapping relationship, the component monitoring data is mapped to the preset symbol readable format to obtain monitoring information.

[0209] Optionally, the microcontroller is also connected to the vehicle's T-BOX;

[0210] The device also includes:

[0211] The fault information forwarding module is used to send the fault information to the T-BOX, so that the fault information can be forwarded to the cloud controller through the T-BOX.

[0212] Optionally, the device also includes:

[0213] A voltage monitoring data identification module is used to identify voltage monitoring data in the monitoring information;

[0214] A voltage anomaly determination module is used to determine whether there is an anomaly in the voltage monitoring data based on a preset standard voltage threshold.

[0215] The historical voltage data acquisition module is used to acquire historical voltage monitoring data within a preset time period when the voltage monitoring data is abnormal.

[0216] The circuit fault prediction module is used to predict the circuit fault prediction result of the vehicle based on the historical voltage monitoring data, the voltage monitoring data and the preset standard voltage threshold, and send the circuit fault prediction result to the vehicle computer so that the circuit fault prediction result can be displayed on the vehicle computer.

[0217] Optionally, the circuit fault prediction module is specifically used for:

[0218] Identify the changing patterns of the voltage monitoring data and the historical voltage monitoring data;

[0219] When the change pattern is the same as the change pattern before the voltage fault, the circuit fault prediction result is that a fault will occur, and the time when the fault will occur is predicted.

[0220] Optionally, the fault information includes at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and photography component unit fault, and at least one of the following fault conditions in each of the above component units: short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

[0221] The technical solution provided in this application includes a component monitoring data acquisition module for acquiring component monitoring data encoded according to a pre-set encoding rule; a monitoring information parsing module for parsing the component monitoring data to obtain monitoring information; a fault information determination module for determining the fault information of a component unit based on the fault code information when the monitoring information includes fault code information; and a fault information display module for sending the fault information to the vehicle computer for display. This vehicle fault alarm device solves the problems of low efficiency in vehicle fault analysis and untimely fault reporting. By parsing the component monitoring data to obtain monitoring information, and determining the fault information of a component unit based on the fault code information when the monitoring information includes fault code information, it achieves real-time monitoring of vehicle operation and automatic identification of vehicle faults, improving the efficiency of vehicle fault analysis and the timeliness of fault alarms.

[0222] The vehicle fault alarm device in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, mobile electronic devices can be mobile phones, tablets, laptops, PDAs, in-vehicle electronic devices, wearable devices, ultra-mobile personal computers (UMPCs), netbooks, or personal digital assistants (PDAs), etc., while non-mobile electronic devices can be servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc. This application embodiment does not impose specific limitations.

[0223] The vehicle fault alarm device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0224] The vehicle fault alarm device provided in this application embodiment can realize the various processes implemented in the above method embodiments. To avoid repetition, it will not be described again here.

[0225] Figure 8 This is a schematic diagram of the structure of the electronic device provided in an embodiment of this application. For example... Figure 8 As shown, this application embodiment also provides an electronic device 800, including a processor 801, a memory 802, and a program or instructions stored in the memory 802 and executable on the processor 801. When the program or instructions are executed by the processor 801, they implement the various processes of the above-described vehicle fault alarm method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0226] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0227] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described vehicle fault alarm method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0228] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0229] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described vehicle fault alarm method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0230] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0231] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0232] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0233] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0234] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the claims.

Claims

1. A vehicle fault alarm method, characterized in that, The method is executed by a microcontroller connected to at least one component unit of the vehicle; the method includes: Obtain component monitoring data obtained by encoding component units according to pre-set encoding rules; The monitoring data of the components is parsed to obtain monitoring information; If the monitoring information includes fault code information, the fault information of the component unit is determined based on the fault code information; The fault information is sent to the vehicle's computer so that the fault information can be displayed on the vehicle's computer.

2. The method according to claim 1, characterized in that, The fault information of the component unit is determined based on the fault code information, including: Based on the fault code information, the faulty component in the component unit is determined; Obtain the association between preset fault codes and fault information, and determine the fault information of the faulty component based on the fault code information and the association.

3. The method according to claim 2, characterized in that, Before determining the faulty component in the component unit based on the fault code information, the method further includes: Delete the monitoring data of the component; Send a cyclic monitoring command to the component unit to obtain the cyclic monitoring data of the component unit; The cyclic monitoring data is parsed to obtain cyclic monitoring information; If the fault code information in the cyclic monitoring information is found to be the same, the faulty component in the component unit is determined based on the fault code information.

4. The method according to claim 1, characterized in that, The parsing of the component monitoring data includes: Obtain the code element output format of the inspection tool in the component unit; Generate a symbol mapping relationship based on the symbol output format and the preset symbol readable format; Based on the symbol mapping relationship, the component monitoring data is mapped to the preset symbol readable format to obtain monitoring information.

5. The method according to claim 1, characterized in that, The microcontroller is also connected to the vehicle's T-BOX; After determining the fault information of the component unit based on the fault code information, the process includes: The fault information is sent to the T-BOX so that the fault information can be forwarded to the cloud controller via the T-BOX.

6. The method according to claim 1, characterized in that, After parsing the component monitoring data to obtain monitoring information, the method further includes: Identify the voltage monitoring data in the monitoring information; Determine whether the voltage monitoring data is abnormal based on a preset standard voltage threshold; If the voltage monitoring data is abnormal, acquire historical voltage monitoring data within a preset time period; Based on the historical voltage monitoring data, the voltage monitoring data, and the preset standard voltage threshold, the predicted circuit fault result of the vehicle is sent to the vehicle computer for display.

7. The method according to claim 6, characterized in that, The prediction of the vehicle's circuit fault prediction result based on the historical voltage monitoring data, the voltage monitoring data, and the preset standard voltage threshold includes: Identify the changing patterns of the voltage monitoring data and the historical voltage monitoring data; When the change pattern is the same as the change pattern before the voltage fault, the circuit fault prediction result is that a fault will occur, and the time when the fault will occur is predicted.

8. The method according to claim 1, characterized in that, The fault information includes at least one of the following: display component unit fault, antenna component unit fault, audio component unit fault, and camera component unit fault; and, in each of the above component units, there is at least one fault condition among short circuit to power supply, short circuit to ground, overvoltage, overcurrent, and overheating.

9. A vehicle malfunction alarm device, characterized in that, The device is equipped with a microcontroller connected to at least one component unit of the vehicle; the device includes: The component monitoring data acquisition module is used to acquire component monitoring data obtained by encoding component units according to pre-set encoding rules. The monitoring information parsing module is used to parse the monitoring data of the components to obtain monitoring information; The fault information determination module is used to determine the fault information of the component unit based on the fault code information when the monitoring information is identified to include fault code information. The fault information display module is used to send the fault information to the vehicle computer so that the fault information can be displayed on the vehicle computer.

10. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the vehicle fault alarm method as described in any one of claims 1-8.

11. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the vehicle fault alarm method as described in any one of claims 1-8.

Images