A method and system for externally transmitting fault codes of a brake system controller

Abstract

The present invention discloses a method and system for externally transmitting fault codes of a brake system controller. The method comprises the following steps: setting a fault code external transmission state; numbering the fault codes to obtain a fault code number; prioritizing the fault codes; and when a fault code is generated, transmitting the fault code number and priority corresponding to the fault code via CAN, while setting the fault code external transmission state to a predefined state. According to the solution proposed by the present invention, after the fault code number is sent to CAN, data can be recorded remotely or on a real vehicle through a specific device in order to lock the fault. In addition, the recorded data can accurately confirm the time when the fault occurred, the state of other related signals when the fault occurred, and the working conditions when the fault occurred, which is conducive to troubleshooting.

Description

Technical Field

[0001] The present invention relates to the field of automobile technology, and more particularly to a method and system for externally transmitting fault codes of a brake system controller. Background Art

[0002] Under normal circumstances, when the brake system fails, the instrument alarm will sound. We use diagnostic tools to read the current fault or historical fault through the vehicle's OBD diagnostic port.

[0003] Technical solution of prior art 1:

[0004] Currently, when a brake system fault occurs (such as a wheel speed sensor fault or brake switch fault), the fault code can only be read afterwards through diagnostic instructions. This method cannot accurately obtain the time when the fault code was generated. For example, some faults caused by poor wiring harness contact will recover quickly after the fault occurs and then become historical faults, making fault troubleshooting and identification extremely difficult. In addition, due to some unconventional power-off operations, some faults cannot be stored, increasing the difficulty of troubleshooting the problem.

[0005] Therefore, how to provide a method and system for externally transmitting fault codes of a brake system controller has become a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0006] The purpose of the present invention is to provide a method and system for externally transmitting fault codes of a brake system controller.

[0007] A first aspect of the present invention discloses a method for externally transmitting fault codes of a brake system controller, the method comprising:

[0008] Step S1, setting the fault code outgoing status;

[0009] Step S2: number the fault code to obtain the fault code number;

[0010] Step S3: Prioritize the fault codes;

[0011] Step S4: When a fault code is generated, it is sent out through CAN according to the fault code number and priority corresponding to the fault code, and the fault code sending state is set to a predefined state.

[0012] According to the method of the first aspect of the present invention, in step S1, the fault code external transmission state is set to four states, specifically:

[0013] 0x0: no fault code;

[0014] 0x1: Send fault codes according to the current fault code number and priority;

[0015] 0x2: There are fault code recovery and new fault codes;

[0016] 0x3: Fault code sending function failure.

[0017] According to the method of the first aspect of the present invention, in step S3, the method of prioritizing fault codes includes:

[0018] Prioritize fault codes based on criticality, impact scope, and fault type.

[0019] According to the method of the first aspect of the present invention, in step S4, when the fault code is generated, the method of sending the fault code to the outside via CAN according to the fault code number and priority corresponding to the fault code, and setting the fault code sending state to a predefined state includes:

[0020] When sending the first fault code in the current priority sequence, the fault code outgoing status is set to 0x1 until all fault codes in the current priority sequence are sent. When the sending cycle of all fault codes in the current priority sequence ends, if the current fault code still exists, the fault code outgoing status jumps to 0x2, and all fault codes in the current priority sequence are sent cyclically according to the current priority sequence.

[0021] If all fault codes in the current priority order are restored, the fault code outgoing status is set to jump from 0x1 or 0x2 to 0x0.

[0022] According to the method of the first aspect of the present invention, in step S4, when the fault code is generated, the method further includes sending the fault code to the outside via CAN according to the fault code number and priority corresponding to the fault code, and setting the fault code sending state to a predefined state.

[0023] If one or more fault codes in the current priority sorting are restored, after the sending cycle of all fault codes in the current priority sorting is completed, the fault code outgoing state jumps to 0x2, the restored priority sorting is generated, and then the fault codes are sent according to the restored priority sorting.

[0024] According to the method of the first aspect of the present invention, in step S4, when the fault code is generated, the method further includes sending the fault code to the outside via CAN according to the fault code number and priority corresponding to the fault code, and setting the fault code sending state to a predefined state.

[0025] If a new fault code is generated within the current priority sending cycle, after the current priority sending cycle is completed, the fault code outgoing status jumps to 0x2, the priority ranking of the new fault code is generated, and then the fault code is sent according to the priority ranking of the new fault code.

[0026] According to the method of the first aspect of the present invention, in step S4, when no fault code is generated, the fault code external status is set to 0x0;

[0027] When the fault code sending function fails, the fault code sending status is set to 0x3.

[0028] A second aspect of the present invention discloses a brake system controller fault code externalization system; the system comprises:

[0029] The first processing module is configured to set a fault code external transmission state;

[0030] The second processing module is configured to number the fault code to obtain a fault code number;

[0031] A third processing module is configured to prioritize the fault codes;

[0032] The fourth processing module is configured to, when a fault code is generated, send it externally via CAN according to the fault code number and priority corresponding to the fault code, and at the same time set the fault code external transmission state to a predefined state.

[0033] A third aspect of the present invention discloses an electronic device comprising a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the steps of any one of the methods for externally transmitting a brake system controller fault code according to the first aspect of the present disclosure.

[0034] A fourth aspect of the present invention discloses a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any one of the methods for externally transmitting a brake system controller fault code according to the first aspect of the present disclosure.

[0035] According to the technical content disclosed in the present invention, the following beneficial effects are achieved: the controller sends the current diagnostic fault code number to the outside in an agreed form through CAN according to a specific protocol. After the fault code number is sent to CAN, data can be recorded remotely or on the actual vehicle through specific equipment, so that the time when the fault occurs, the status of other related signals when the fault occurs, and the working conditions when the fault occurs can be accurately obtained, which is conducive to fault troubleshooting.

[0036] Further features and advantages of the present invention will become apparent from the following detailed description of exemplary embodiments of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

[0038] Figure 1 This is a flow chart of a method for externally transmitting fault codes of a brake system controller according to an embodiment;

[0039] Figure 2 This is a schematic diagram of a method for sending a fault code to an external device via CAN according to the fault code number and priority corresponding to the fault code when a fault code is generated according to an embodiment, and setting the fault code sending state to a predefined state.

[0040] Figure 3 This is a structural diagram of a brake system controller fault code outbound system according to an embodiment of the present invention;

[0041] Figure 4 FIG. 4 is a structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0042] Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention.

[0043] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.

[0044] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.

[0045] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0046] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0047] Example 1:

[0048] The invention discloses a method for externally transmitting fault codes of a brake system controller. Figure 1 FIG. 1 is a flow chart of a method for sending fault codes of a brake system controller according to an embodiment of the present invention. Figure 1 As shown, the method includes:

[0049] Step S1, setting the fault code outgoing status;

[0050] Step S2: number the fault code to obtain the fault code number;

[0051] Step S3: Prioritize the fault codes;

[0052] Step S4: When a fault code is generated, it is sent out through CAN according to the fault code number and priority corresponding to the fault code, and the fault code sending state is set to a predefined state.

[0053] In step S1, the fault code outgoing state is set.

[0054] In some embodiments, in step S1, the fault code outgoing state is set to four states, specifically:

[0055] 0x0: no fault code;

[0056] 0x1: Send fault codes according to the current fault code number and priority;

[0057] 0x2: There are fault code recovery and new fault codes;

[0058] 0x3: Fault code sending function failure.

[0059] Specifically, as shown in Table 1.

[0060] Table 1

[0061]

[0062] In step S2, the fault codes are numbered to obtain fault code numbers.

[0063] Specifically, as shown in Table 2.

[0064] Table 2

[0065]

[0066] In step S3, the fault codes are prioritized.

[0067] In some embodiments, in step S3, the method for prioritizing fault codes includes:

[0068] Prioritize fault codes based on criticality, impact scope, and fault type.

[0069] Specifically, the faults are ranked according to the degree of danger they cause, with the most dangerous ones taking priority;

[0070] If the degree of danger is the same, priority will be given to the one with the largest impact range;

[0071] When the danger level and impact range are the same, the diagnosis controller fault takes priority, followed by the associated controller;

[0072] After following the above principles, random sorting is sufficient.

[0073] In step S4, when a fault code is generated, it is sent out through CAN according to the fault code number and priority corresponding to the fault code, and the fault code sending state is set to a predefined state.

[0074] In some embodiments, in step S4, when the fault code is generated, the method of sending the fault code to the outside via CAN according to the fault code number and priority corresponding to the fault code, and setting the fault code sending state to a predefined state includes:

[0075] When sending the first fault code in the current priority sequence, the fault code outgoing status is set to 0x1 until all fault codes in the current priority sequence are sent. When the sending cycle of all fault codes in the current priority sequence ends, if the current fault code still exists, the fault code outgoing status jumps to 0x2, and all fault codes in the current priority sequence are sent cyclically according to the current priority sequence.

[0076] If all fault codes in the current priority order are restored, the fault code outgoing status is set to jump from 0x1 or 0x2 to 0x0.

[0077] If one or more fault codes in the current priority sorting are restored, after the sending cycle of all fault codes in the current priority sorting is completed, the fault code outgoing state jumps to 0x2, the restored priority sorting is generated, and then the fault codes are sent according to the restored priority sorting.

[0078] If a new fault code is generated within the current priority sending cycle, after the current priority sending cycle is completed, the fault code outgoing status jumps to 0x2, the priority ranking of the new fault code is generated, and then the fault code is sent according to the priority ranking of the new fault code.

[0079] When no fault code is generated, the fault code outgoing status is set to 0x0;

[0080] When the fault code sending function fails, the fault code sending status is set to 0x3.

[0081] In summary, the solution proposed in the present invention enables the controller to send the current diagnostic fault code number to the outside in an agreed form through CAN according to a specific protocol. After the fault code number is sent to CAN, data can be recorded remotely or on the actual vehicle through specific equipment, so as to accurately obtain the time when the fault occurred, the status of other related signals when the fault occurred, and the working conditions when the fault occurred, which is conducive to fault troubleshooting.

[0082] Example 2:

[0083] like Figure 2 As shown, when the fault code is generated, the method of sending the fault code to the outside through CAN according to the fault code number and priority corresponding to the fault code, and setting the fault code sending state to a predefined state includes:

[0084] When no fault code is generated, DTC is set to 0 and DTCSendSts is set to 0x0: no DTC; see Figure 2 T1 to T3 interval;

[0085] When the fault code is sent out for a functional fault, DTCSendSts is set to 0x3:error; if there is no functional fault, the error state may not be set;

[0086] When multiple fault codes are generated at the same time, the fault codes need to be sorted in order of priority. When the first fault code in the current priority is sent, DTCSendSts is set to 0x1: DTC sending until all fault codes in the current priority are sent. When the sending cycle of all fault codes in the current priority is completed, if the current fault code still exists, DTCSendSts jumps to 0x2: DTC sending switchover, and all fault codes in the current priority are sent cyclically according to the current priority. For details, see Figure 2 T4-T9 and T18-T23 intervals;

[0087] When a fault code changes from zero to present, DTCSendSts always sets to 0x1: DTC sending first. When a fault code is being sent, DTCSendSts needs to switch between 0x1: DTC sending and 0x2: DTC sending switchover. The switch always occurs between the end of a fault code sending cycle and the start of a new fault code sending cycle.

[0088] When the fault code changes from being present to not present, DTCSendSts can change from 0x1: DTC sending or 0x2: DTC sending switchover to 0x0: no DTC;

[0089] If a new fault code is generated in the current fault code sending cycle, the current fault code sending cycle remains unchanged. The new fault code needs to be prioritized with the existing fault codes to generate a priority ranking for the newly added fault code, which can only be reflected in the new fault code sending cycle. For details, see Figure 2 T7 to T13 interval;

[0090] If the current fault is recovered or converted into a historical fault during the current fault code sending cycle, the current fault code sending cycle remains unchanged and the priority ranking after recovery is generated. The disappeared fault code can only be reflected in the new fault code sending cycle; see Figure 2 The T14 to T19 interval.

[0091] Example 3:

[0092] The invention discloses a brake system controller fault code external transmission system. Figure 3 FIG. 1 is a structural diagram of a brake system controller fault code outgoing system according to an embodiment of the present invention; FIG. Figure 3 As shown, the system 100 includes:

[0093] The first processing module 101 is configured to set a fault code external transmission state;

[0094] The second processing module 102 is configured to number the fault code to obtain a fault code number;

[0095] The third processing module 103 is configured to prioritize the fault codes;

[0096] The fourth processing module 104 is configured to, when a fault code is generated, send it externally via CAN according to the fault code number and priority corresponding to the fault code, and simultaneously set the fault code external transmission state to a predefined state.

[0097] According to the system of the second aspect of the present invention, the first processing module 101 is specifically configured to set the fault code external transmission state to four states, specifically:

[0098] 0x0: no fault code;

[0099] 0x1: Send fault codes according to the current fault code number and priority;

[0100] 0x2: There are fault code recovery and new fault codes;

[0101] 0x3: Fault code sending function failure.

[0102] Specifically, as shown in Table 1.

[0103] Table 1

[0104]

[0105] According to the system of the second aspect of the present invention, the second processing module 102 is specifically configured as shown in Table 2.

[0106] Table 2

[0107]

[0108]

[0109] According to the system of the second aspect of the present invention, the third processing module 103 is specifically configured as follows:

[0110] Prioritize fault codes based on criticality, impact scope, and fault type.

[0111] Specifically, the faults are ranked according to the degree of danger they cause, with the most dangerous ones taking priority;

[0112] If the degree of danger is the same, priority will be given to the one with the largest impact range;

[0113] When the danger level and impact range are the same, the diagnosis controller fault takes priority, followed by the associated controller;

[0114] After following the above principles, random sorting is sufficient.

[0115] According to the system of the second aspect of the present invention, the fourth processing module 104 is specifically configured to, when the fault code is generated, send it externally via CAN according to the fault code number and priority corresponding to the fault code, and at the same time set the fault code external transmission state to a predefined state. The method includes:

[0116] When sending the first fault code in the current priority sequence, the fault code outgoing status is set to 0x1 until all fault codes in the current priority sequence are sent. When the sending cycle of all fault codes in the current priority sequence ends, if the current fault code still exists, the fault code outgoing status jumps to 0x2, and all fault codes in the current priority sequence are sent cyclically according to the current priority sequence.

[0117] If all fault codes in the current priority order are restored, the fault code outgoing status is set to jump from 0x1 or 0x2 to 0x0.

[0118] If one or more fault codes in the current priority sorting are restored, after the sending cycle of all fault codes in the current priority sorting is completed, the fault code outgoing state jumps to 0x2, the restored priority sorting is generated, and then the fault codes are sent according to the restored priority sorting.

[0119] If a new fault code is generated within the current priority sending cycle, after the current priority sending cycle is completed, the fault code outgoing status jumps to 0x2, the priority ranking of the new fault code is generated, and then the fault code is sent according to the priority ranking of the new fault code.

[0120] When no fault code is generated, the fault code outgoing status is set to 0x0;

[0121] When the fault code sending function fails, the fault code sending status is set to 0x3.

[0122] Example 4:

[0123] This invention discloses an electronic device. The electronic device includes a memory and a processor. The memory stores a computer program. When the processor executes the computer program, it implements the steps of any one of the methods for externally transmitting fault codes of a brake system controller in Embodiment 1 of the present invention.

[0124] Figure 4 FIG. 1 is a structural diagram of an electronic device according to an embodiment of the present invention. Figure 4 As shown, the electronic device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the electronic device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, near field communication (NFC) or other technologies. The display screen of the electronic device can be a liquid crystal display or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the electronic device housing, or an external keyboard, touchpad or mouse.

[0125] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a structural diagram of the part related to the technical solution of the present disclosure, and does not constitute a limitation on the electronic device to which the solution of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0126] Example 5:

[0127] The present invention discloses a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program implements the steps of any one of the methods for externally transmitting fault codes of a brake system controller in embodiment 1 of the present invention.

[0128] Please note that the technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification. The above embodiments only express several implementation methods of the present application. The description is relatively specific and detailed, but it cannot be understood as a limitation on the scope of the invention patent. It should be pointed out that for ordinary technicians in this field, without departing from the concept of this application, several variations and improvements can be made, which all fall within the scope of protection of this application. Therefore, the scope of protection of the patent in this application shall be based on the attached claims.

[0129] Embodiments of the subject matter and functional operations described in this specification may be implemented in the following: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. Embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier to be executed by a data processing device or to control the operation of the data processing device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information and transmit it to a suitable receiver device for execution by the data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

[0130] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform the corresponding functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0131] Computers suitable for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of central processing unit. Typically, the central processing unit will receive instructions and data from a read-only memory and / or random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or the computer will be operably coupled to such mass storage devices to receive data from them or to transmit data to them, or both. However, a computer does not necessarily have such devices. In addition, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0132] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0133] Although this specification includes many specific implementation details, these should not be interpreted as limiting the scope of any invention or the scope of protection claimed, but are mainly used to describe the features of specific embodiments of specific inventions. Certain features described in multiple embodiments within this specification may also be implemented in combination in a single embodiment. On the other hand, the various features described in a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may work in certain combinations as described above and even initially claimed as such, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may point to a sub-combination or a variation of the sub-combination.

[0134] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or performed sequentially, or that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product, or packaged into multiple software products.

[0135] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the particular order shown or sequential sequence to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.

[0136] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

[0137] Although some specific embodiments of the present invention have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present invention. It should be understood by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the present invention. The scope of the present invention is defined by the appended claims.

Claims

1. A method for sending fault codes of a brake system controller, characterized in that: The method comprises: Step S1: Set the fault code outgoing status, including the following four states: 0x0: no fault code; 0x1: Send fault codes according to the current fault code number and priority; 0x2: There are fault code recovery and new fault codes; 0x3: Fault code sending function failure; Step S2: number the fault code to obtain the fault code number; Step S3: Prioritize the fault codes; Step S4: When a fault code is generated, it is sent externally via CAN according to the fault code number and priority corresponding to the fault code, and the fault code external transmission state is set to a predefined state, which at least includes: if one or more fault codes in the current priority ranking are restored, after the transmission cycle of all fault codes in the current priority ranking is completed, the fault code external transmission state jumps to 0x2, the restored priority ranking is generated, and then the fault code is sent according to the restored priority ranking; and further includes: If a new fault code is generated within the current priority sending cycle, after the current priority sending cycle is completed, the fault code outgoing status jumps to 0x2, the priority ranking of the new fault code is generated, and then the fault code is sent according to the priority ranking of the new fault code.

2. A method for externally transmitting fault codes of a brake system controller according to claim 1, characterized in that: In step S3, the method for prioritizing fault codes includes: Prioritize fault codes based on criticality, impact scope, and fault type.

3. The method for externally transmitting fault codes of a brake system controller according to claim 1, characterized in that: In step S4, when the fault code is generated, the method further includes sending the fault code to the outside via CAN according to the fault code number and priority corresponding to the fault code, and setting the fault code sending state to a predefined state. When sending the first fault code in the current priority sequence, the fault code outgoing status is set to 0x1 until all fault codes in the current priority sequence are sent. When the sending cycle of all fault codes in the current priority sequence ends, if the current fault code still exists, the fault code outgoing status jumps to 0x2, and all fault codes in the current priority sequence are sent cyclically according to the current priority sequence. If all fault codes in the current priority order are restored, the fault code outgoing status is set to jump from 0x1 or 0x2 to 0x0.

4. A method for externally transmitting fault codes of a brake system controller according to claim 1, characterized in that: In step S4, when no fault code is generated, the fault code external status is set to 0x0; When the fault code sending function fails, the fault code sending status is set to 0x3.

5. A brake system controller fault code externalization system, characterized in that: The system comprises: The first processing module is configured to set the fault code outgoing state, including the following four states: 0x0: no fault code; 0x1: Send fault codes according to the current fault code number and priority; 0x2: There are fault code recovery and new fault codes; 0x3: Fault code sending function failure; The second processing module is configured to number the fault code to obtain a fault code number; A third processing module is configured to prioritize the fault codes; The fourth processing module is configured to, when a fault code is generated, send it externally through CAN according to the fault code number and priority corresponding to the fault code, and at the same time set the fault code external transmission state to a predefined state, which at least includes: if one or more fault codes in the current priority sorting are restored, after the sending cycle of all fault codes in the current priority sorting is completed, the fault code external transmission state jumps to 0x2, the restored priority sorting is generated, and then the fault code is sent according to the restored priority sorting; and also includes: if a new fault code is generated within the sending cycle of all fault codes in the current priority sorting, after the sending cycle of all fault codes in the current priority sorting is completed, the fault code external transmission state jumps to 0x2, the priority sorting of the newly added fault code is generated, and then the fault code is sent according to the priority sorting of the newly added fault code.

6. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the steps in the method for externally transmitting fault codes of a brake system controller according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of the method for externally transmitting fault codes of a brake system controller according to any one of claims 1 to 4 are implemented.

Images