CN115695149A - Fault management method, device, equipment and storage medium of vehicle controller - Google Patents
Fault management method, device, equipment and storage medium of vehicle controller Download PDFInfo
- Publication number
- CN115695149A CN115695149A CN202211352460.1A CN202211352460A CN115695149A CN 115695149 A CN115695149 A CN 115695149A CN 202211352460 A CN202211352460 A CN 202211352460A CN 115695149 A CN115695149 A CN 115695149A
- Authority
- CN
- China
- Prior art keywords
- fault
- information
- state
- activation
- controllers
- 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
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
- Y02T10/00—Road transport of goods or passengers
- Y02T10/10—Internal combustion engine [ICE] based vehicles
- Y02T10/40—Engine management systems
Landscapes
- Testing And Monitoring For Control Systems (AREA)
Abstract
The invention discloses a fault management method, a device, equipment and a storage medium of a vehicle controller, wherein the method comprises the following steps: analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers; calculating a flag bit of a fault through the source address and fault code information of the rest controllers, and determining the activation state of the fault through the flag bit of the fault; and storing the fault information according to the activation state of the fault, and prompting the fault. This application can avoid other a plurality of controllers to the repeated development of fault management module, reduces the input of research and development expense, also can manage the trouble simultaneously, makes things convenient for maintenance personal to carry out troubleshooting maintenance, improves maintenance efficiency.
Description
Technical Field
The invention relates to the technical field of vehicle electric control, in particular to a fault management method, a fault management device, fault management equipment and a storage medium of a vehicle controller.
Background
With the continuous development of the automobile industry, the requirement on the safety of the vehicle is higher and higher, and in order to improve the safety of the vehicle, the functions, the component states and the like of the automobile need to be monitored and fault-diagnosed in real time.
At present, a plurality of controllers are arranged on a vehicle, a fault management system is developed for each controller, resources are wasted due to repeated development, and when faults of the controllers are reported, the alarm prompt of the instrument is required, so that the instrument is inconvenient to manage the faults of the controllers.
Therefore, how to reduce the repeated development of the fault management modules of different controllers is a technical problem which needs to be solved at present.
Disclosure of Invention
The invention mainly aims to provide a fault management method, a device, equipment and a storage medium for a vehicle controller, which can avoid repeated development of other multiple controllers on a fault management module, reduce the input of research and development cost, manage faults, facilitate troubleshooting and maintenance of maintenance personnel and improve the maintenance efficiency.
In a first aspect, the present application provides a method of fault management for a vehicle controller, the method comprising the steps of:
analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers;
calculating a flag bit of a fault through the source address and fault code information of the rest controllers, and determining the activation state of the fault through the flag bit of the fault;
and storing the fault information according to the activation state of the fault, and prompting the fault.
With reference to the first aspect, as an optional implementation manner, the calculating a flag bit of the fault occurrence through the source address and the fault code information of each of the other controllers includes:
determining controllers corresponding to the current fault information through the source addresses of the rest controllers obtained by analyzing the preset main controller;
and comparing the fault code information defined by the controller corresponding to the fault information with the fault code information obtained by analysis to obtain a flag bit of the fault.
With reference to the first aspect, as an optional implementation manner, when the flag bit activated by fault confirmation is 1, it is determined that the controller has a fault and the fault is in an activated state;
and when the fault confirms that the activated flag bit is 0, determining that the controller is in an inactivated state.
With reference to the first aspect, as an optional implementation manner, when it is determined that a fault occurs, the fault is stored as a confirmed and activated fault before the next engine start;
when it has been confirmed that the activation failure is not detected during the engine start-to-stop process, the failure is set to a historical activation state before the next engine start.
With reference to the first aspect, as an optional implementation manner, the fault warning light state is calculated according to the fault activation state, and the fault information and the fault warning light state are sent to the CAN bus through the preset main controller,
and when the vehicle instrument receives the fault information on the CAN bus and the state of the fault alarm lamp, the alarm lamp is turned on and fault information prompt is carried out.
With reference to the first aspect, as an optional implementation manner, if the flag bit of the fault occurrence is 1, the timer starts to accumulate from zero by a set step length, and when the timer exceeds a set threshold, the fault state is a confirmed activation state;
if the fault is in the activation confirmation state and the flag bit of the fault is 0, the timer starts to decrement from the threshold value by the set step length, and when the timer decrements to 0, the flag bit of the fault is detected to be 0, and the fault state is in the non-activation state.
With reference to the first aspect, as an optional implementation manner, when the fault state is determined and activated, the preset main controller records fault information and a freeze frame at the moment of the fault occurrence, and sends the recorded fault information and the freeze frame at the moment of the fault occurrence to the CAN bus;
and the Tbox acquires the fault information and the freeze frame information through the CAN bus, uploads the fault information and the freeze frame information to the networking platform, and inquires the fault vehicle information through the networking platform so as to lock the fault reason.
In a second aspect, the present application provides a fault management apparatus of a vehicle controller, the apparatus comprising:
the analysis module is used for analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers;
the calculation module is used for calculating a fault occurring zone bit through the source address and the fault code information of the rest controllers, and determining the fault activation state through the fault occurring zone bit;
and the storage module is used for storing the fault information according to the activation state of the fault and carrying out fault prompt.
In a third aspect, the present application further provides an electronic device, including: a processor; a memory having computer readable instructions stored thereon which, when executed by the processor, implement the method of any of the first aspects.
In a fourth aspect, the present application also provides a computer readable storage medium storing computer program instructions which, when executed by a computer, cause the computer to perform the method of any of the first aspects.
The application provides a fault management method, a fault management device, equipment and a storage medium of a vehicle controller, wherein the method comprises the following steps: analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers; calculating a flag bit of a fault through the source address and fault code information of the rest controllers, and determining the activation state of the fault through the flag bit of the fault; and storing the fault information according to the activation state of the fault, and prompting the fault. This application can avoid other a plurality of controllers to the repeated development of fault management module, reduces the input of research and development expense, also can manage the trouble simultaneously, makes things convenient for maintenance personal to carry out troubleshooting maintenance, improves maintenance efficiency.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a flow chart of a method for managing a fault of a vehicle controller provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of a fault management device of a vehicle controller provided in an embodiment of the present application;
fig. 3 is a schematic diagram of an electronic device provided in an embodiment of the present application;
fig. 4 is a schematic diagram of a computer-readable program medium provided in an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities.
The embodiment of the application provides a fault management method, a fault management device, equipment and a storage medium for a vehicle controller, which can avoid repeated development of other multiple controllers on a fault management module, reduce the input of research and development cost, manage faults, facilitate troubleshooting and maintenance of maintenance personnel and improve the maintenance efficiency.
It is understood that the vehicle has a plurality of controllers, and the failure of each of the other control systems is managed by one of the controllers, and the other controllers can no longer develop the failure management module, thereby reducing the development cost and shortening the development period.
In order to achieve the technical effects, the general idea of the application is as follows:
a method of fault management for a vehicle controller, the method comprising the steps of:
s101: and analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers.
S102: and calculating the flag bit of the fault occurrence through the source address and fault code information of the other controllers, and determining the activation state of the fault through the flag bit of the fault occurrence.
S103: and storing the fault information according to the activation state of the fault, and prompting the fault.
Embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a flowchart illustrating a fault management method for a vehicle controller according to the present invention, and as shown in fig. 1, the method includes the steps of:
and S101, analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers.
Specifically, a main controller is set in a plurality of controllers, diagnosis messages of the other controllers are defined in a unified manner, namely, a message source address is distributed to each controller, a fault code is defined for each fault, and the diagnosis messages of the other controllers except the main controller are analyzed through a CAN bus according to the set main controller to obtain source addresses and fault code information of the other controllers. It should be noted that, according to the uniformly defined diagnostic message, each controller has a source address SA, and the rest of the controllers send fault information DTCs to the CAN bus through the diagnostic message. .
In one embodiment, the unified CAN bus is provided with an instrument, a Tbox terminal and three controllers, one controller is selected to be set as a main controller, wherein all fault code information of the other controllers is stored in the main controller, and when the other controllers have faults, the fault information of the other controllers is received and processed by setting the main controller. In addition, it should be noted that whether the main controller fails or not is determined and set in a self-checking manner, when a failure occurs, the failure information is transmitted to the failure management module in the main controller, the failure signals of the main controller diagnostic controller are all directly led to the main controller through a wire harness, and the main controller directly processes and diagnoses the acquired signals to determine whether the failure occurs or not.
In one embodiment, according to the definition of the J1939 message, each controller has a source address SA, and each controller sends fault information DTCs to the CAN bus through a diagnostic message, and analyzes the diagnostic message of each controller of the CAN bus through a set master controller to obtain the source address SA and the fault code information DTCs.
And S102, calculating a fault occurring zone bit through the source address and fault code information of the other controllers, and determining the fault activation state through the fault occurring zone bit.
Specifically, a set main controller analyzes a diagnosis message of each controller of the CAN bus to obtain a source address SA and fault code information DTCs, the set main controller judges which controller the current fault information comes from according to the obtained source address SA, and then compares and judges the analyzed DTCs and a fault code information list of the controller to calculate a flag bit DF whether the fault occurs or not. Note that, the flag bit: is a flag indicating the occurrence of a certain event. Flag bit of whether failure occurs: namely, the fault occurs, and if the fault is detected, the mark DF representing the fault occurrence is 1; if no fault occurs and no fault is detected, the flag indicating the occurrence of the fault is 0.
Optionally, when the fault flag DF =1, it represents that a fault is detected, and when the fault flag DF =0, it represents that a fault is not detected, it is understood that a fault is determined to be present when the fault flag DF =1, and when the fault flag DF =0, it is determined that a fault is not present.
Alternatively, the configured master controller may select whether to turn on or off the detection of faults in multiple controllers.
In an embodiment, the fault occurrence flag DF is output to the fault anti-shake module, and if DF =1, the fault anti-shake module starts timing accumulation with a set step size from 0, and when the timer exceeds a threshold, the fault state is a confirmed activation, and the fault confirmed activation flag CF =1.
When the fault is in a confirmed activation state CF =1 and the fault is repaired DF =0, the timer of the fault anti-shake module is decreased from the threshold value by a set step length, and when the value of the timer is 0, the fault confirmed activation flag CF =0; when the fault anti-shake module timer is in the process of accumulation, the fault repaired DF =0, the timer starts to decrement from the threshold value by the set step length. When a fault occurs, the counter is increased from 0 to the threshold value; the fault is repaired and the counter is decremented from the threshold to 0.
It can be understood that after a fault is detected, the time for reporting the fault is prolonged, the fault is prevented from being reported by mistake, if the fault is detected, the fault management module cannot report the fault immediately, and the fault is reported again only when the fault continuously occurs for more than a certain time.
For example, when a certain sensor is in poor contact with the wire harness, the control system detects that the sensor is opened (DF = 1) at a moment, but then the poor contact of the wire harness is immediately repaired, and the fault is not generated (DF = 0). The fault occurs in a short time, and the fault cannot be reported if the fault anti-shake time is not exceeded.
And S103, storing the fault information according to the activation state of the fault, and performing fault prompt.
Specifically, the failure storage is performed based on the failure confirmation activation flag CF. When the fault is determined to be in an activated state, namely the confirmed activation flag bit CF =1 of the fault, the fault is stored as the confirmed and activated fault before the end of the next operation process, and when the confirmed activation fault is not detected to be CF =0 in a complete operation process, the fault is set to be in a historical activated state before the start of the next operation process, and stored fault information is sent to the CAN bus in real time. It should be noted that, the operation process: refers to the time course consisting of engine start, engine run, engine shutdown, and until the next engine start. Including engine start, running, shutdown, and the time until the next engine start.
In one embodiment, when a certain fault state is confirmed and activated, the set main controller records a freeze frame and environmental information at the moment of fault occurrence, such as ambient temperature, vehicle speed, engine speed, accelerator pedal position and the like, and sends the recorded information to the CAN bus through a message.
Optionally, when a certain fault state is confirmed and activated, the fault lamp states, such as an MI lamp, a maintenance warning lamp, and a STOP lamp, are calculated, and each fault lamp state is sent to the CAN bus. The malfunction alerting lamp includes an MIL lamp, a STOP lamp, a water temperature alerting lamp, an oil pressure lamp, etc.
In one embodiment, when a fault affects vehicle safety and requires engine shutdown, a message is sent to the meter and the meter lights up a STOP light.
Optionally, when the water temperature of the engine is detected to be higher than the alarm threshold, a message is sent to the meter, and the water temperature lamp is turned on by the meter.
Optionally, when a certain confirmed and activated fault affects the safety of the vehicle or a driver, a degraded operation flag is output, so that the purpose of limiting the torque of the engine or the speed of the vehicle is achieved, and the driving safety is ensured.
In one embodiment, the instrument acquires the stored fault information and the calculated fault information and the state of the fault warning lamp through the CAN bus, displays the fault information according to requirements, and lights up the warning lamp so as to remind a driver of maintenance. The Tbox acquires fault information, freeze frame information and the like through the CAN bus and uploads the fault information, the freeze frame information and the like to the networking platform, and research and development and service personnel CAN inquire fault vehicle information through the networking platform so as to lock fault reasons. The diagnostic equipment can communicate with a set main controller through a specific protocol, read all fault information and obtain a maintenance suggestion according to the fault information so that maintenance personnel can conveniently carry out troubleshooting and maintenance.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating a fault management apparatus for a vehicle controller according to the present invention, and as shown in fig. 2, the apparatus includes:
the analysis module 201: the method is used for analyzing the diagnosis messages of the other controllers according to the set main controller to obtain the source addresses and fault code information of the other controllers.
The calculation module 202: the fault detection method is used for calculating the zone bit of the fault through the source address and the fault code information of the other controllers, and determining the activation state of the fault through the zone bit of the fault.
The storage module 203: the fault information storage device is used for storing fault information and carrying out fault prompt according to the activation state of the fault.
Further, in a possible implementation manner, the calculation module 202 is further configured to determine a controller corresponding to the current fault information through the source addresses of the other controllers obtained by analyzing by the preset main controller;
and comparing the fault code information defined by the controller corresponding to the fault information with the fault code information obtained by analysis to obtain a flag bit of the fault.
Further, in one possible implementation, the calculation module 202 is further configured to,
when the flag bit of the fault confirmation activation is 1, determining that the controller has a fault and the fault is in an activation state;
and when the fault confirms that the activated flag bit is 0, determining that the controller is in an inactivated state.
Further, in one possible implementation, the calculation module 202 is further configured to, when it is determined that a fault has occurred, store the fault as a confirmed and activated fault before the next engine start;
when it has been confirmed that the activation failure is not detected during the engine start-to-stop process, the failure is set to a historical activation state before the next engine start.
Further, in a possible implementation manner, the calculating module 202 is further configured to calculate a status of the malfunction warning lamp according to the malfunction activated status, and send the malfunction information and the status of the malfunction warning lamp to the CAN bus through the preset main controller,
and when the vehicle instrument receives the fault information on the CAN bus and the state of the fault alarm lamp, the alarm lamp is turned on and fault information prompt is carried out.
Further, in one possible implementation, the calculation module 202 is further configured to,
if the flag bit of the fault occurrence is 1, the timer starts to accumulate from zero by a set step length, and when the timer exceeds a set threshold value, the fault state is a confirmed activation state;
if the fault is in the activation confirmation state and the flag bit of the fault is 0, the timer starts to decrement from the threshold value by the set step length, and when the timer decrements to 0, the flag bit of the fault is detected to be 0, and the fault state is in the non-activation state.
Further, in a possible implementation manner, the storage module 203 is further configured to, when the fault state is determined and activated, record the fault information and the freeze frame at the moment of the fault occurrence by the preset main controller, and send the recorded fault information and the freeze frame at the moment of the fault occurrence to the CAN bus;
and the Tbox acquires the fault information and the freeze frame information through the CAN bus, uploads the fault information and the freeze frame information to the networking platform, and inquires the fault vehicle information through the networking platform so as to lock the fault reason.
An electronic device 300 according to this embodiment of the invention is described below with reference to fig. 3. The electronic device 300 shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 3, electronic device 300 is embodied in the form of a general purpose computing device. The components of electronic device 300 may include, but are not limited to: the at least one processing unit 310, the at least one memory unit 320, and signal lines 330 connecting different system components (including the memory unit 320 and the processing unit 310).
Wherein the storage unit stores program code that can be executed by the processing unit 310, such that the processing unit 310 performs the steps according to various exemplary embodiments of the present invention described in the section "example methods" above in this specification.
The storage unit 320 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM) 321 and/or a cache memory unit 322, and may further include a read only memory unit (ROM) 323.
The storage unit 320 may also include a program/utility 324 having a set (at least one) of program modules 325, such program modules 325 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 300 may also communicate with one or more external devices (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 300, and/or with any device (e.g., router, modem, etc.) that enables the electronic device 300 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 350. Also, the electronic device 300 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 360. As shown, network adapter 360 communicates with the other modules of electronic device 300 over bus 330. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
According to an aspect of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 4, a program product 400 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
In summary, the present application provides a method, an apparatus, a device and a storage medium for managing a fault of a vehicle controller, where the method includes: analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers; calculating a flag bit of a fault occurrence through the source address and fault code information of the other controllers, and determining the activation state of the fault through the flag bit of the fault occurrence; and storing the fault information according to the activation state of the fault, and prompting the fault. This application can avoid other a plurality of controllers to the repeated development of fault management module, reduces the input of research and development expense, also can manage the trouble simultaneously, makes things convenient for maintenance personal to carry out troubleshooting maintenance, improves maintenance efficiency.
The above description is merely exemplary of the present application and is presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Claims (10)
1. A fault management method for a vehicle controller, characterized by an envelope:
analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers;
calculating a flag bit of a fault through the source address and fault code information of the rest controllers, and determining the activation state of the fault through the flag bit of the fault;
and storing the fault information according to the activation state of the fault, and prompting the fault.
2. The method of claim 1, wherein calculating the flag bit of the fault occurrence through the source address and fault code information of the remaining controllers comprises:
determining a controller corresponding to the current fault information through the source addresses of the rest controllers obtained by analyzing the preset main controller;
and comparing the fault code information defined by the controller corresponding to the fault information with the fault code information obtained by analysis to obtain a flag bit of the fault.
3. The method of claim 1, wherein determining the activation status of the fault via the flag bit of the fault occurrence comprises:
when the flag bit of the fault confirmation activation is 1, determining that the controller has a fault and the fault is in an activation state;
and when the flag bit of the fault confirmation activation is 0, determining that the controller fault is in an inactivated state.
4. The method of claim 1, wherein storing the fault information according to the activation status of the fault comprises:
when it is determined that a fault occurs, storing the fault as a confirmed and activated fault before the next engine start;
when it has been confirmed that the activation failure is not detected during the engine start-to-stop process, the failure is set to a historical activation state before the next engine start.
5. The method of claim 1, wherein:
calculating the state of a fault alarm lamp according to the fault activation state, and sending fault information and the state of the fault alarm lamp to a CAN bus through the preset main controller;
and when the vehicle instrument receives the fault information on the CAN bus and the state of the fault alarm lamp, the alarm lamp is turned on and fault information prompt is carried out.
6. The method of claim 1, wherein before storing the fault information according to the activation status of the fault, the method comprises:
if the flag bit of the fault is 1, the timer starts accumulation from zero by a set step length, and when the timer exceeds a set threshold, the fault state is a confirmed activation state;
if the fault is in the activation confirmation state and the flag bit of the fault is 0, the timer starts to decrement from the threshold value by the set step length, and when the timer decrements to 0, the flag bit of the fault is detected to be 0, and the fault state is in the non-activation state.
7. The method of claim 1,
when the fault state is confirmed and activated, the preset main controller records fault information and a freeze frame at the moment of fault occurrence, and sends the recorded fault information and the freeze frame at the moment of fault occurrence to the CAN bus;
and the Tbox acquires the fault information and the freeze frame information through the CAN bus, uploads the fault information and the freeze frame information to the networking platform, and inquires the fault vehicle information through the networking platform so as to lock the fault reason.
8. A fault management device of a vehicle controller, characterized by comprising:
the analysis module is used for analyzing the diagnosis messages of the rest controllers according to the set main controller to obtain the source addresses and fault code information of the rest controllers;
the calculation module is used for calculating a fault occurring zone bit through the source address and the fault code information of the rest controllers, and determining the fault activation state through the fault occurring zone bit;
and the storage module is used for storing the fault information according to the activation state of the fault and carrying out fault prompt.
9. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of any of claims 1 to 7.
10. A computer-readable storage medium, characterized in that it stores computer program instructions which, when executed by a computer, cause the computer to perform the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211352460.1A CN115695149A (en) | 2022-10-31 | 2022-10-31 | Fault management method, device, equipment and storage medium of vehicle controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211352460.1A CN115695149A (en) | 2022-10-31 | 2022-10-31 | Fault management method, device, equipment and storage medium of vehicle controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115695149A true CN115695149A (en) | 2023-02-03 |
Family
ID=85047697
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211352460.1A Pending CN115695149A (en) | 2022-10-31 | 2022-10-31 | Fault management method, device, equipment and storage medium of vehicle controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115695149A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116560347A (en) * | 2023-06-27 | 2023-08-08 | 江铃汽车股份有限公司 | New energy automobile fault management method and system |
-
2022
- 2022-10-31 CN CN202211352460.1A patent/CN115695149A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116560347A (en) * | 2023-06-27 | 2023-08-08 | 江铃汽车股份有限公司 | New energy automobile fault management method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10127093B1 (en) | Method and apparatus for monitoring a message transmission frequency in a robot operating system | |
| WO2023125852A1 (en) | Remote diagnosis method and apparatus, and electronic device and storage medium | |
| CN110103931B (en) | Method and device for detecting abnormal braking of vehicle | |
| CN114490161B (en) | Fault diagnosis method and device, vehicle and storage medium | |
| CN110928271A (en) | Automobile self-service diagnosis method and system | |
| CN115695149A (en) | Fault management method, device, equipment and storage medium of vehicle controller | |
| WO2020173304A1 (en) | Method and device for detecting fault in vehicle, and vehicle | |
| CN113341923B (en) | Low-voltage wire harness fault detection method of vehicle, signal diagnosis unit and vehicle | |
| CN111830927A (en) | Vehicle fault monitoring method and device and vehicle-mounted diagnosis equipment | |
| CN100498733C (en) | Method for implementing control of computer fault alarm | |
| CN113942394B (en) | Range extender abnormality monitoring method and device and electronic equipment | |
| US20160080223A1 (en) | Dynamic management of notifications | |
| KR100505692B1 (en) | Fail diagnostics service system and method for disc drive | |
| WO2023226952A1 (en) | Vehicle state feedback method and apparatus, electronic device, and storage medium | |
| CN116009510A (en) | Vehicle-mounted control system abnormality processing method and device and vehicle | |
| WO2014027558A1 (en) | Vehicle control device, and vehicle control system | |
| CN113309605B (en) | Method for monitoring cooling efficiency of vehicle intercooler | |
| CN114691633A (en) | Log management method, device and storage medium for rail transit signal system | |
| CN109474478B (en) | Method, device and system for monitoring transmission data abnormity | |
| CN113992530B (en) | Baud rate identification method, baud rate identification device, electronic equipment and storage medium | |
| CN110519558A (en) | The processing method and its Baseboard Management Controller of video data | |
| CN116488988A (en) | Automatic overhaul method and device, electronic equipment and storage medium | |
| CN115731689A (en) | Unmanned vehicle control method, system, device and storage medium | |
| CN116533875A (en) | Vehicle fault reminding method and device, electronic equipment and storage medium | |
| CN114167164A (en) | High-side power supply detection method and device, electronic equipment and storage medium |
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 |