Fault diagnosis management method and system and vehicle

By using the interactive management of fault code information between the main controller and the main and secondary controllers in the vehicle fault diagnosis system, the complex signal interaction problem of multi-controllers is solved, the unity and accuracy of fault diagnosis information is achieved, and the development cost is reduced .

CN118938876APending Publication Date: 2024-11-12CHONGQING CHANGAN AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411176572.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-26
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the prior art, the signal interaction between multiple controllers is complex, and the fault information cannot be effectively managed, resulting in a complex fault diagnosis process and redundant controller functions, which increases the waste of development resources and the complexity of signal interaction, and cannot guarantee fault diagnosis information. accuracy and uniqueness.

Method used

The fault diagnosis and management system consisting of the main controller, the main controller and the secondary controller generates fault code information through the main controller and sends a request to the main controller. The fault indicator light is turned on and off, and the fault is solved. After that, clear the fault code information to realize unified information management between controllers.

Benefits of technology

It effectively solves the problem of controller function redundancy, saves costs, and ensures the unity of fault diagnosis information between controllers through interaction, improving the accuracy of fault diagnosis and information uniqueness.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118938876A_ABST
    Figure CN118938876A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of vehicle fault diagnosis, and discloses a fault diagnosis management method and system and a vehicle, and the method comprises the steps: collecting fault signals generated by a main controller and sent by a corresponding auxiliary controller through the main controller, generating fault code information of the main controller, and sending a fault indication lamp lightening request to a main controller; and the master controller is used for lightening a fault indicating lamp and generating fault code information. When the main controller detects that the fault is solved, the main controller updates the fault code information of the main controller and sends a fault indicating lamp extinguishing request to the main controller, and the main controller extinguishes the fault indicating lamp and updates the fault code information of the main controller. In addition, fault code information stored in the main controller and the master controller is cleared through interaction between the main controller and the master controller. According to the invention, the main controller is utilized to uniformly control the on or off of the fault indicating lamps, so that the problem of function redundancy of the controllers is effectively solved, the cost is saved, and the unification of fault diagnosis information between the controllers is ensured through the interaction between the controllers.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle fault diagnosis, and in particular to a fault diagnosis management method, system and vehicle. Background Art

[0002] In conventional fuel vehicles, the On-Board Diagnostics (OBD) controllers that support emission-related functions generally include the Electronic Control Unit (ECU) and the Transmission Control Unit (TCU). With the technological innovation in the automotive field, the control of hybrid vehicles and pure electric vehicles tends to be network-based, with higher functional configuration and control requirements, and the corresponding OBD controllers have increased accordingly. Technical regulations require that these OBD controllers must support fault diagnosis and fault information output, which will undoubtedly lead to redundancy of OBD diagnostic functions and waste of development resources such as time and manpower. It also increases the complexity of controller signal interaction and cannot effectively guarantee the accuracy of the output of each OBD controller and the uniqueness of regulatory characteristic parameters.

[0003] At present, a main control module can be designated among multiple control modules, and the status of the malfunction indicator lamp (MIL) can be arbitrated by the main control module. The instructions or data of other controllers can be managed in a coordinated manner through a main control module. In this process, the OBD controller will generate fault information when a fault is detected and synchronize it to the main control module.

[0004] After the fault is resolved, the fault information of the OBD controller and the main control module must also be cleared to achieve closed-loop control of the diagnostic process. However, the diagnostic system has multiple controllers interacting with each other, and the operations on fault information at different stages of the diagnostic process are also different, which makes the updating and clearing of fault information very complicated. The signal interaction mechanism of traditional methods cannot be well applied in these scenarios, and it is impossible to effectively manage the fault information generated by each controller at different stages of the diagnostic process. Summary of the invention

[0005] In view of this, the present invention provides a fault diagnosis management method, system and vehicle to solve the problem that the related art lacks signal interaction between multiple controllers and cannot effectively manage fault information.

[0006] In a first aspect, the present invention provides a fault diagnosis management method, which is applied to any main controller in a fault diagnosis management system composed of a main controller, multiple main controllers and multiple sub-controllers, wherein each sub-controller corresponds to a main controller, and the multiple main controllers are respectively connected to the main controller, and the method comprises:

[0007] Based on the fault signal generated by itself or sent by the corresponding sub-controller, it generates fault code information stored by itself, and sends a fault indicator light lighting request to the main controller, so that the main main controller lights up the fault indicator light and generates fault code information stored by the main controller;

[0008] When it is detected that the fault has been resolved, the fault code information stored in the system is updated, and a fault indicator light off request is sent to the main controller, so that the main controller turns off the fault indicator light and updates the fault code information stored in the main controller;

[0009] Sending a fault code information clearing request to the master controller so that the master controller clears the stored fault code information, and sending status information indicating that the clearing is completed to the main controller;

[0010] After receiving the status information sent by the main controller, clear the fault code information stored in itself.

[0011] Beneficial effects: The main controller aggregates the fault signals generated by itself and sent by the corresponding sub-controller, generates its own fault code information, and sends a fault indicator light lighting request to the main controller, which lights up the fault indicator light and generates fault code information. When the main controller detects that the fault has been resolved, it updates its own fault code information and sends a fault indicator light extinguishing request to the main controller, which extinguishes the fault indicator light and updates its own fault code information. In addition, the interaction between the main controller and the main controller is used to clear the fault code information stored in both. By using the main controller to uniformly control the lighting or extinguishing of the fault indicator light, the problem of controller function redundancy is effectively solved, costs are saved, and the unified fault diagnosis information between controllers is guaranteed through the interaction between controllers.

[0012] In an optional implementation manner, the fault code information includes pending fault codes, confirmed fault codes and permanent fault codes; based on the fault signal generated by itself or sent by the corresponding sub-controller, the fault code information stored by itself is generated, and a fault indicator light lighting request is sent to the main controller, including:

[0013] When a fault is identified based on a fault signal generated by itself or sent by a corresponding secondary controller, a pending fault code stored by itself is generated;

[0014] After identifying the occurrence of a fault and confirming the fault type based on the fault signal, it generates a confirmed fault code and a permanent fault code stored in itself, and sends a fault indicator light lighting request to the main controller so that the main controller lights up the fault indicator light, and generates a pending fault code, a confirmed fault code and a permanent fault code stored in the main controller.

[0015] Beneficial effect: By summarizing the fault signals of itself and the corresponding sub-controller, a pending fault code is generated when a fault is identified; after further confirming the fault, a confirmed fault code and a permanent fault code are generated, and the main controller is requested to light up the fault indicator light. The main controller uniformly controls the lighting of the fault indicator light, which effectively solves the current controller function redundancy problem and saves time and labor costs for controller function development.

[0016] In an optional implementation manner, the fault indicator light off request includes a first off request; when it is detected that the fault has been resolved, the fault code information stored in the self-stored fault indicator light is updated, and the fault indicator light off request is sent to the main controller, including:

[0017] When no fault is detected within the preset time and the corresponding sub-controller requests the fault indicator light to light up, the pending fault code and permanent fault code stored in itself are cleared, and a first extinguishing request is sent to the main controller to make the main controller extinguish the fault indicator light and clear the permanent fault code stored in the main controller.

[0018] Beneficial effect: When the main controller does not detect a fault within the preset time and the fault indicator light of the corresponding sub-controller is turned on, it clears its own pending fault code and permanent fault code, and requests the main controller to turn off the fault indicator light. When the main controller turns off the fault indicator light, it clears its own permanent fault code, thereby ensuring the unity and accuracy of the information stored by the main controller and the main controller.

[0019] In an optional implementation manner, the fault code information clearing request includes a first clearing request, and the status information includes a first status signal for indicating that the fault code information clearing is completed; sending the fault code information clearing request to the main controller includes:

[0020] Sending a first clearing request to the master controller so that the master controller clears the confirmed fault code and the pending fault code stored in the master controller, and sending a first status signal to the main controller;

[0021] After receiving the status information sent by the main controller, clear the fault code information stored in itself, including:

[0022] After receiving the first status signal sent by the main controller, the confirmed fault code stored in itself is cleared.

[0023] Beneficial effect: The interaction between the main controller and the master controller is utilized to clear the remaining fault codes stored in both, thereby ensuring the unification of fault diagnosis information between the controllers.

[0024] In an optional implementation manner, the fault indicator light off request includes a second off request; when it is detected that the fault has been resolved, the fault code information stored in the self-stored fault indicator light is updated, and a fault indicator light off request is sent to the main controller, including:

[0025] After receiving the fault clearing instruction sent by the external device, the confirmed fault code and pending fault code stored in itself are cleared, and a second extinguishing request is sent to the main controller to make the main controller extinguish the fault indicator light and clear the permanent fault code stored in the main controller.

[0026] Beneficial effect: When the main controller receives the fault clearing instruction sent by the external device, it clears its own confirmed fault code and pending fault code, and requests the master controller to turn off the fault indicator light. When the master controller turns off the fault indicator light, it clears its own permanent fault code, thereby ensuring the unity and accuracy of the information stored in the main controller and the master controller.

[0027] In an optional implementation manner, the fault code information clearing request includes a second clearing request, and the status information includes a second status signal for indicating that the permanent fault code clearing is completed; sending the fault code information clearing request to the main controller includes:

[0028] Sending a second clearing request to the master controller so that the master controller clears the confirmed fault code and the pending fault code stored in the master controller, and sending a second status signal to the main controller;

[0029] After receiving the status information sent by the main controller, clear the fault code information stored in itself, including:

[0030] After receiving the second status signal sent by the main controller, the permanent fault code stored in itself is cleared.

[0031] Beneficial effect: The interaction between the main controller and the master controller is utilized to clear the remaining fault codes stored in both, thereby ensuring the unification of fault diagnosis information between the controllers.

[0032] In an optional embodiment, the method further includes:

[0033] Based on the software calibration identification code and software calibration verification code sent by the corresponding sub-controller, the software version information of the corresponding sub-controller is output or managed.

[0034] Beneficial effect: By aggregating the software calibration identification codes and software calibration verification codes of subordinate sub-controllers, the software version information can be effectively and uniformly managed.

[0035] In an optional embodiment, the method further includes:

[0036] Receive output information sent by the main controller and send the output information to an external device; wherein the output information includes at least one of engine calculated load, engine cooling temperature, engine speed, throttle absolute position, throttle relative position, powertrain running time, powertrain shutdown time, common denominator counter, denominator count, denominator counter effective state, ignition counter, ignition counter effective state, and warm-up cycle.

[0037] Beneficial effect: By using the main controller to receive the output information of the master controller, the accuracy of the output information of each controller and the uniqueness of the parameters are guaranteed.

[0038] In a second aspect, the present invention provides a fault diagnosis management method, which is applied to a master controller in a fault diagnosis management system composed of a master controller, multiple main controllers and multiple sub-controllers, wherein each sub-controller corresponds to a master controller, and the multiple main controllers are respectively connected to the master controller, and the method comprises:

[0039] Receive a fault indicator light lighting request sent by the main controller, light up the fault indicator light, and generate fault code information stored in itself, wherein the fault indicator light lighting request is generated by the main controller based on a fault signal generated by itself or sent by the corresponding sub-controller;

[0040] receiving a fault indicator light off request sent by the main controller, turning off the fault indicator light, and updating the fault code information stored in the main controller, wherein the fault indicator light off request is generated by the main controller when it detects that the fault has been resolved;

[0041] Based on the fault code information clearing request sent by the main controller, the stored fault code information is cleared, and status information indicating the completion of the clearing is sent to the main controller, so that the main controller clears the fault code information stored in the main controller after receiving the status information.

[0042] Beneficial effects: The main controller aggregates the fault signals generated by itself and sent by the corresponding sub-controller, generates its own fault code information, and sends a fault indicator light lighting request to the main controller, which lights up the fault indicator light and generates fault code information. When the main controller detects that the fault has been resolved, it updates its own fault code information and sends a fault indicator light extinguishing request to the main controller, which extinguishes the fault indicator light and updates its own fault code information. In addition, the interaction between the main controller and the main controller is used to clear the fault code information stored in both. By using the main controller to uniformly control the lighting or extinguishing of the fault indicator light, the problem of controller function redundancy is effectively solved, costs are saved, and the unified fault diagnosis information between controllers is guaranteed through the interaction between controllers.

[0043] In an optional implementation manner, generating the fault code information stored in itself includes:

[0044] Generates pending fault codes, confirmed fault codes, and permanent fault codes that are stored by itself.

[0045] Beneficial effect: By using the master controller to aggregate the requests of the main controller and generate fault code information, the current controller function redundancy problem is effectively solved, saving time and labor costs for controller function development.

[0046] In an optional implementation manner, the fault indicator light extinguishing request includes a first extinguishing request; receiving the fault indicator light extinguishing request sent by the main controller, extinguishing the fault indicator light, and updating the fault code information stored in itself, including:

[0047] Based on the first extinguishing request sent by the main controller, the fault indicator light is extinguished and the permanent fault code stored in itself is cleared; wherein, the first extinguishing request is generated when the main controller clears the stored pending fault code and permanent fault code after not generating or receiving a fault signal sent by the corresponding sub-controller within a preset time.

[0048] Beneficial effect: When the main controller does not detect a fault within the preset time and the fault indicator light of the corresponding sub-controller is turned on, it clears its own pending fault code and permanent fault code, and requests the main controller to turn off the fault indicator light. When the main controller turns off the fault indicator light, it clears its own permanent fault code, thereby ensuring the unity and accuracy of the information stored by the main controller and the main controller.

[0049] In an optional implementation manner, the fault code information clearing request includes a first clearing request, and the status information includes a first status signal for indicating that the fault code information clearing is completed; based on the fault code information clearing request sent by the main controller, the stored fault code information is cleared, and the status information for indicating that the clearing is completed is sent to the main controller, including:

[0050] Based on a first clearing request sent by the main controller, the stored confirmed fault code and pending fault code are cleared, and a first status signal is sent to the main controller so that the main controller clears the confirmed fault code stored in the main controller after receiving the first status signal.

[0051] Beneficial effect: The interaction between the main controller and the master controller is utilized to clear the remaining fault codes stored in both, thereby ensuring the unification of fault diagnosis information between the controllers.

[0052] In an optional implementation manner, the fault indicator light extinguishing request includes a second extinguishing request; receiving the fault indicator light extinguishing request sent by the main controller, extinguishing the fault indicator light, and updating the fault code information stored in itself, including:

[0053] Based on the second extinguishing request sent by the main controller, the fault indicator light is extinguished and the permanent fault code stored in the main controller is cleared; wherein the second extinguishing request is generated when the main controller clears the stored confirmed fault code and pending fault code after receiving the fault clearing instruction sent by the external device.

[0054] Beneficial effect: When the main controller receives the fault clearing instruction sent by the external device, it clears its own confirmed fault code and pending fault code, and requests the master controller to turn off the fault indicator light. When the master controller turns off the fault indicator light, it clears its own permanent fault code, thereby ensuring the unity and accuracy of the information stored in the main controller and the master controller.

[0055] In an optional implementation manner, the fault code information clearing request includes a second clearing request, and the status information includes a second status signal for indicating that the permanent fault code clearing is completed; based on the fault code information clearing request sent by the main controller, the stored fault code information is cleared, and the status information for indicating that the clearing is completed is sent to the main controller, including:

[0056] Based on the second clear request sent by the main controller, the stored confirmed fault code and pending fault code are cleared, and a second status signal is sent to the main controller so that the main controller clears the permanent fault code stored in the main controller after receiving the second status signal.

[0057] Beneficial effect: The interaction between the main controller and the master controller is utilized to clear the remaining fault codes stored in both, thereby ensuring the unification of fault diagnosis information between the controllers.

[0058] In a third aspect, the present invention provides a fault diagnosis management system, the system comprising a master controller, a plurality of main controllers and a plurality of sub-controllers, wherein each sub-controller corresponds to a master controller, and the plurality of main controllers are respectively connected to the master controller;

[0059] The main controller generates fault code information stored in itself based on the fault signal generated by itself or sent by the corresponding sub-controller, and sends a request to light up the fault indicator light to the main controller;

[0060] The master controller receives the fault indicator light-up request sent by the main controller, lights up the fault indicator light, and generates fault code information stored in itself;

[0061] When the main controller detects that the fault has been resolved, it updates the fault code information stored in itself and sends a request to turn off the fault indicator light to the main controller;

[0062] The master controller receives the fault indicator light extinguishing request sent by the main controller, extinguishes the fault indicator light, and updates the fault code information stored in itself;

[0063] The main controller sends a fault code information clearing request to the master controller;

[0064] The master controller clears the stored fault code information based on the fault code information clearing request sent by the main controller, and sends status information indicating the completion of clearing to the main controller;

[0065] After receiving the status information sent by the main controller, the main controller clears the fault code information stored in itself.

[0066] In a fourth aspect, the present invention provides a vehicle, comprising the fault diagnosis management system of the third aspect.

[0067] The beneficial effects of the present invention are:

[0068] The main controller aggregates the fault signals generated by itself and sent by the corresponding sub-controller, generates its own fault code information, and sends a fault indicator light lighting request to the main controller, which lights up the fault indicator light and generates fault code information. When the main controller detects that the fault has been resolved, it updates its own fault code information and sends a fault indicator light extinguishing request to the main controller, which extinguishes the fault indicator light and updates its own fault code information. In addition, the main controller sends a fault code information clearing request to the main controller so that the fault code information stored in both can be cleared through the interaction between the main controller and the main controller. By using the main controller to uniformly control the lighting or extinguishing of the fault indicator light, the problem of controller function redundancy is effectively solved, costs are saved, and the unified fault diagnosis information between controllers is guaranteed through the interaction between controllers. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0070] Figure 1 is a structural block diagram of a fault diagnosis management system according to an embodiment of the present invention;

[0071] Figure 2 is a schematic diagram of the architecture of a fault diagnosis management system according to an embodiment of the present invention;

[0072] Figure 3 is a working principle diagram of a fault diagnosis management system according to an embodiment of the present invention;

[0073] Figure 4 is a flow chart of a fault diagnosis management method according to an embodiment of the present invention;

[0074] Figure 5 is a flow chart of another fault diagnosis management method according to an embodiment of the present invention;

[0075] Figure 6 is a flowchart of another fault diagnosis management method according to an embodiment of the present invention;

[0076] Figure 7 is a schematic diagram of a controller request fault management according to an embodiment of the present invention;

[0077] Figure 8 is a schematic diagram of an external device request fault management according to an embodiment of the present invention;

[0078] Fig. 9 Schematic diagram of the hardware structure of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION

[0079] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0080] In conventional fuel vehicles, the On-Board Diagnostics (OBD) controllers that support emission-related functions generally include the Electronic Control Unit (ECU) and the Transmission Control Unit (TCU). With the technological innovation in the automotive field, the control of hybrid vehicles and pure electric vehicles tends to be network-based, with higher functional configurations and control requirements. The corresponding OBD controllers have increased accordingly, such as the Vehicle Control Unit (VCU), Integrated Brake Control Unit (IBCU), Thermal Management System (TMS), Power Electronics Unit (PEU), On-Board Charger (OBC), Battery Management System (BMS), etc. The motor controller can also be divided into front drive motor controller, rear drive motor controller, integrated motor controller, etc. based on domain control.

[0081] Based on the requirements of item J.4.14 of GB18352.6-2016 Light Vehicle Pollutant Emission Limits and Measurement Methods (China Phase VI) (hereinafter referred to as the National VI Regulations), these OBD controllers must support fault diagnosis and fault information output. In order to meet regulatory requirements, each controller needs to develop OBD diagnostic and fault management functions, which will undoubtedly lead to redundancy of OBD diagnostic functions and waste of development resources such as time and manpower, increase the complexity of controller signal interaction, and cannot effectively guarantee the accuracy of each OBD controller output and the uniqueness of regulatory characteristic parameters. On the other hand, each OBD controller works independently and uses different diagnostic IDs in different projects or platforms, resulting in the need to develop various versions of production line electrical inspection and after-sales diagnostic instruments, resulting in poor equipment compatibility. There will also be conflicts in OBD development work during the migration of controller functions for different models.

[0082] Patent "US20070179691A1" discloses a distributed diagnostic architecture, which designates a main control module among multiple control modules to arbitrate MIL status, arbitrate and store OBD freeze frame data, and determine the OBD status flags of the rest of the multiple control modules. The patent focuses on describing the OBD responsibility division of multiple controllers and the functional definition of the main controller and sub-controllers, but does not provide a signal interaction mechanism for each controller, nor does it explain the response scheme of each controller when an external device clears the fault code, and cannot effectively guarantee the unified storage of fault information of the sub-controller and the main controller. In addition, the patent proposes direct interaction between the main controller and the sub-controller, which has the problem of insufficient physical addressing ID of the OBD controller.

[0083] According to an embodiment of the present invention, a fault diagnosis management system 100 is provided. Figure 1 As shown, the fault diagnosis management system 100 includes a master controller 101, multiple main controllers 102 and multiple sub-controllers 103, wherein each sub-controller 103 corresponds to one master controller 102, and multiple main controllers 102 are respectively connected to the master controller 101. For the convenience of description, the master controller in this application may be referred to as the Master controller, the main controller may be referred to as the Primary controller, and the sub-controller may be referred to as the Secondary controller.

[0084] The main controller 102 generates its own stored fault code information based on the fault signal generated by itself or sent by the corresponding sub-controller, and sends a request to light up the fault indicator light to the main controller 101; the main controller 101 receives the request to light up the fault indicator light sent by the main controller 102, lights up the fault indicator light, and generates its own stored fault code information.

[0085] When the main controller 102 detects that the fault has been resolved, it updates the fault code information stored in itself and sends a request to turn off the fault indicator light to the main controller 101; the main controller 101 receives the request to turn off the fault indicator light sent by the main controller 102, turns off the fault indicator light, and updates the fault code information stored in itself.

[0086] The main controller 102 sends a fault code information clearing request to the main controller 101; the main controller 101 clears the stored fault code information based on the fault code information clearing request sent by the main controller 102, and sends status information indicating the completion of the clearing to the main controller 102; after receiving the status information sent by the main controller 101, the main controller 102 clears its own stored fault code information.

[0087] The fault diagnosis management system provided by the embodiment of the present invention uses the main controller 102 to summarize the fault signals generated by itself and sent by the corresponding sub-controller, generate its own fault code information, and send a fault indicator light lighting request to the main controller 101, and the main controller 101 lights up the fault indicator and generates fault code information. When the main controller 102 detects that the fault has been resolved, it updates its own fault code information and sends a fault indicator light extinguishing request to the main controller 101, and the main controller 101 extinguishes the fault indicator and updates its own fault code information. In addition, the main controller 102 sends a fault code information clearing request to the main controller 101, so that the fault code information stored in both is cleared through the interaction between the main controller 102 and the main controller 101. By using the main controller 101 to uniformly control the lighting or extinguishing of the fault indicator, the problem of controller function redundancy is effectively solved, cost is saved, and the unification of fault diagnosis information between controllers is guaranteed through the interaction between controllers.

[0088] In the embodiments of the present application, Figure 2 As shown, the network architecture between the Master controller, each Primary controller and each Secondary controller is defined, and the communication signal interaction between each controller is clarified. Among them, the Master controller and each Primary controller can communicate through the CANFD protocol or the CAN protocol, and the Primary controller and the corresponding Secondary controller can also communicate through the CANFD protocol or the CAN protocol. In addition, the OBD scan tool can communicate with the Master controller and the Primary controller through the gateway, and the communication protocol can be the UDS / OBD protocol.

[0089] For example, see again Figure 2 , based on the network segment communication requirements, the redundant controllers can be attached to the upper-layer Primary controller #1 as Secondary controller #1 and Secondary controller #2; based on the control function requirements, the Secondary controller #3 can be attached to the Primary controller #3. It should be noted that, Figure 2 The defined architectural relationship between the Primary controller #1 and the Secondary controller is only an application example and cannot limit the system architecture of the present invention.

[0090] In some optional embodiments, the Master controller is mainly used to manage fault codes (including fault code storage and clearing), manage fault indicator lights (including the lighting and extinguishing of MIL lights), and calculate and output regulatory information, wherein the output regulatory information includes but is not limited to the following information: drive system activation time, driving cycle, total mileage signal, engine calculated load, engine cooling temperature, engine speed, throttle absolute position, throttle relative position, powertrain running time, powertrain downtime, general denominator counter, denominator count 1, denominator count 2, denominator counter valid state, first ignition counter, second ignition counter, ignition counter valid, warm-up cycle, etc.

[0091] It should be noted that denominator count 1 is the general denominator growth rule of National VI Regulation J.3.4.3.2-(B) / (K), and denominator count 2 is the special denominator growth rule defined in National VI Regulation J.3.4.3.2-(D) / (L). For detailed definitions, please refer to the regulations and will not be repeated here. The first ignition counter is the power drive system activation (starting the engine or high voltage on a hybrid vehicle) count, and the second ignition counter is the engine start count.

[0092] For example, Figure 3 As shown in the figure, the Master controller can collect and summarize the MIL requests of Primary#1-7, and notify the instrument to light up the MIL light through the CAN network. The Master controller supports the communication response of the OBD service (SID01-0A) of the OBD scan tool.

[0093] In some optional embodiments, the main controller 102 is also used to output or manage the software version information of the corresponding sub-controller based on the software calibration identification code and software calibration verification code sent by the corresponding sub-controller, thereby effectively and uniformly managing the software version information by aggregating the software calibration identification codes and software calibration verification codes of the subordinate sub-controllers.

[0094] In some optional embodiments, the main controller 102 is also used to receive output information sent by the master controller and send the output information to an external device; wherein the output information includes at least one of engine calculated load, engine cooling temperature, engine speed, throttle absolute position, throttle relative position, powertrain running time, powertrain downtime, universal denominator counter, denominator count, denominator counter valid state, ignition counter, ignition counter valid state, and warm-up cycle. By using the main controller to receive the output information of the master controller, the accuracy of the output information of each controller and the uniqueness of the parameters are guaranteed.

[0095] Specifically, the Primary controller is mainly used to collect fault signals inside the controller or the Secondary controller and generate a request to turn on or off the MIL light of the Master controller; collect the software calibration identification code (CALID) and software calibration verification code (CVN) of the Secondary controller for data version information output and management of the Secondary controller; and generate a request to clear the fault code information inside the controller.

[0096] For example, see again Figure 3 , Primary controller #1 collects CALID, CVN and fault information of Secondary controller #1 and Secondary controller #2, where fault information can be divided into emission type and non-emission type (MIL light is not lit). Primary controller #1 can also collect regulatory information output by the Master controller. Primary controller #1 supports the communication response of the OBD service (SID01-0A) of the OBD scan tool. Primary controller #1 summarizes the MIL light requests of Primary controller #1, Secondary controller #1 and Secondary controller #2 and sends them to the Master controller via the CAN network. Primary controllers #2-#7 collect regulatory information output by the Master controller and support the communication response of the OBD service (SID01-0A) of the scan tool; support the generation of MIL light requests based on their own fault status and send them to the Master controller via the CAN network.

[0097] In some optional implementations, the Secondary controller has the following functions: collecting fault signals inside the controller and generating a request to light up or turn off the MIL light of the Primary controller, and the Secondary controller has no direct OBD communication with the Master controller; generating a request to clear the fault code information inside the controller; and transmitting the CALID and CVN to the Primary.

[0098] The embodiment of the present invention collects and calculates regulatory information parameters in a unified manner through the Master controller, thereby avoiding confusion in information output by the Primary controller and ensuring the accuracy and uniqueness of the regulatory information output.

[0099] With the increase of vehicle OBD controllers, there is a situation where the number of OBD controllers in the current vehicle exceeds the number defined by the OBD controller addressing ID defined in "ISO 15765-4". The controller in the embodiment of the present invention is mainly an OBD controller. In order to ensure that the UDS / OBD service response IDs of each OBD controller in different projects or platforms do not conflict, and to ensure the compatibility of the production line electrical inspection equipment and diagnostic instruments, a platform protocol diagnostic CANID allocation table is defined to uniformly allocate the physical addressing IDs of each controller. Based on "ISO 15765-4", the present invention provides a physical addressing allocation implementation plan as follows:

[0100] Table 1 Physical addressing allocation scheme

[0101]

[0102]

[0103] In the embodiment of the present application, at the beginning of designing the OBD system architecture, based on the control requirements and the controller interaction network segments (PCAN, HEVCAN), the Primary controls that exceed the definition can be used as Secondary controllers to be hung under the corresponding Primary controllers. For example, the vehicle controller VCU controls thermal management and vehicle charging requirements based on vehicle operating conditions and user needs, so OBC and TMS can be used as Secondary controllers of VCU at the functional level. For another example, OBC and TMS are both in the PCAN network segment, and the remaining Primary controls are all in the HEVCAN network segment, so OBC and TMS can be used as Secondary controllers of VCU at the functional level.

[0104] It should be noted that if the current vehicle has no relevant Primary controller configuration, the physical addressing ID of the control should be reserved and should not be occupied by other controllers.

[0105] The embodiment of the present invention is conducive to promoting product platformization by allocating controller platform IDs. When controller domains of different projects are integrated, the controller development workload is reduced due to the compatibility of OBD system solutions; on the other hand, the electrical inspection and after-sales diagnostic instruments of the OBD controller can be directly borrowed, saving maintenance costs.

[0106] According to an embodiment of the present invention, a fault diagnosis management method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0107] In this embodiment, a fault diagnosis management method is provided. The fault diagnosis management method can be used for example Figure 1 The main controller 101 and the main controller 102 shown, such as MCU, single chip microcomputer, etc., Figure 4 1 is a schematic diagram of the interaction process of the fault diagnosis management system according to an embodiment of the present invention, wherein the main controller 102 is used to execute steps S101 to S104, and the master controller 101 is used to execute steps S201 to S203. The specific interaction process between the master controller 101 and the main controller 102 is as follows:

[0108] Step S101, based on the fault signal generated by itself or sent by the corresponding sub-controller, generate the fault code information stored by itself, and send a request to light up the fault indicator light to the main controller.

[0109] Specifically, any Primary controller can collect fault signals inside the controller or from subordinate Secondary controllers, generate a request to light up the MIL light of the Master controller, and generate corresponding fault code information inside the controller.

[0110] Step S201, receiving a fault indicator light lighting request sent by a main controller, lighting the fault indicator light, and generating fault code information stored in itself.

[0111] Specifically, the Master controller can control the lighting of the MIL light according to the MIL light lighting request of the Primary controller. The Master controller can also summarize the MIL light lighting requests of each Primary controller and notify the instrument to light the MIL light through the CAN network.

[0112] Step S102, when it is detected that the fault has been resolved, the fault code information stored in itself is updated, and a request to turn off the fault indicator light is sent to the main controller.

[0113] Specifically, the fault indicator light off request includes a first off request and a second off request. The Primary controller can generate a fault management request inside the controller. When the controller requests fault management, the Primary controller sends the first off request to the Master controller. The Primary controller can be connected to an external device such as an OBD scanning tool to support communication response of the external device. When the external device requests fault management, the Primary controller sends the second off request to the Master controller.

[0114] Step S202, receiving a fault indicator light extinguishing request sent by the main controller, extinguishing the fault indicator light, and updating the fault code information stored in itself.

[0115] Specifically, the Master controller updates the fault code information in a corresponding manner according to the first extinguishing request or the second extinguishing request sent by the Primary controller, and controls the extinguishing of the MIL light.

[0116] Step S103, sending a fault code information clearing request to the main controller.

[0117] Specifically, the fault code information clearing request includes a first clearing request and a second clearing request. Referring to the description of step S102, when the controller requests fault management, the Primary controller sends the first clearing request to the Master controller; when the external device requests fault management, the Primary controller sends the second clearing request to the Master controller.

[0118] Step S203: based on the fault code information clearing request sent by the main controller, the stored fault code information is cleared, and status information indicating that the clearing is completed is sent to the main controller.

[0119] Specifically, when the Master controller receives a fault code information clearing request, it will clear the fault code stored in itself and generate status information for indicating that the clearing is complete. The status information includes a first status signal for indicating that the fault code information clearing is complete and a second status signal for indicating that the permanent fault code clearing is complete. When the controller requests fault management, the Master controller sends the first status signal to the Primary controller; when the external device requests fault management, the Master controller sends the second status signal to the Primary controller.

[0120] Step S104, after receiving the status information sent by the main controller, clear the fault code information stored in itself.

[0121] Specifically, after receiving the status information from the Master controller, the Primary controller will clear the fault code stored in itself.

[0122] The fault diagnosis management method provided by the embodiment of the present invention uses the main controller to summarize the fault signals generated by itself and sent by the corresponding sub-controller, generate its own fault code information, and send a fault indicator light lighting request to the main controller, and the main controller lights up the fault indicator light and generates fault code information. When the main controller detects that the fault has been resolved, it updates its own fault code information and sends a fault indicator light extinguishing request to the main controller, and the main controller extinguishes the fault indicator light and updates its own fault code information. In addition, the interaction between the main controller and the main controller is used to clear the fault code information stored in both. By using the main controller to uniformly control the lighting or extinguishing of the fault indicator light, the problem of controller function redundancy is effectively solved, costs are saved, and the unification of fault diagnosis information between controllers is guaranteed through the interaction between controllers.

[0123] In this embodiment, a fault diagnosis management method is provided. The fault diagnosis management method can be used for Figure 1 The main controller 101 and the main controller 102 shown, such as MCU, single chip microcomputer, etc., Figure 5 1 is a schematic diagram of the interaction process of the fault diagnosis management system according to an embodiment of the present invention, wherein the main controller 102 is used to execute steps S301 to S305, and the master controller 101 is used to execute steps S401 to S403. The specific interaction process between the master controller 101 and the main controller 102 is as follows:

[0124] Step S301, when a fault is identified based on a fault signal generated by itself or sent by a corresponding sub-controller, a pending fault code stored in itself is generated.

[0125] Specifically, if the Primary controller identifies a fault, it can store a pending fault code within 10 seconds.

[0126] Step S302, after identifying the occurrence of a fault and confirming the fault type based on the fault signal, generates a confirmed fault code and a permanent fault code for storage, and sends a fault indicator light lighting request to the main controller.

[0127] Specifically, after confirming the fault or fault type, the Primary node controller can request the Master controller to light up the MIL light through the CAN signal PrimaryXXX_MILReq=1, and store a confirmed fault code and a permanent fault code. It should be noted that in the signal definition similar to PrimaryXXX_MILReq, XXX represents a Primary controller, and the Primary node controller can manage pending fault codes in accordance with National VI Regulation J.3.2.2.2.

[0128] Step S401, receiving a fault indicator light lighting request sent by a main controller, lighting the fault indicator light, and generating a pending fault code, a confirmed fault code, and a permanent fault code stored in itself.

[0129] Specifically, after receiving the MIL light power request, the Master controller stores a unique fault code (pending fault confirmation, confirmed fault code, and permanent fault are all stored) and turns on the MIL light.

[0130] Therefore, by utilizing the main controller to aggregate its own fault signals and those of the corresponding sub-controller, a pending fault code is generated when a fault is identified; after further confirming the fault, a confirmed fault code and a permanent fault code are generated, and at the same time, the main controller is requested to light up the fault indicator light. The main controller uniformly controls the lighting of the fault indicator light, effectively solving the current problem of controller function redundancy and saving time and labor costs for controller function development.

[0131] Step S303, when no fault is detected within a preset time and the fault indicator light lighting request of the corresponding sub-controller is received, the pending fault code and permanent fault code stored in the self-stored system are cleared, and a first extinguishing request is sent to the main controller.

[0132] Specifically, if the Primary controller detects that the MIL light no longer needs to be lit after at least three consecutive driving cycles, and the fault that caused the MIL light to be lit does not occur again, and no other faults that require the MIL light to be lit are detected, the Primary controller requests to turn off the MIL through the CAN signal PrimaryXXX_MILReq = 0. At the same time, the Primary controller can clear pending fault codes and permanent fault codes.

[0133] Step S402, based on the first extinguishing request sent by the main controller, extinguish the fault indicator light and clear the permanent fault code stored in itself.

[0134] Specifically, the Master controller turns off the MIL light and clears the permanent fault code when receiving the MIL light turning off request. Clearing the permanent fault code and turning off the MIL light can be performed simultaneously, or not later than before the start of the first driving cycle that turns off the MIL.

[0135] In the embodiment of the present invention, when the main controller does not detect a fault within a preset time and responds to the fault indicator light lighting request of the corresponding sub-controller, it clears its own pending fault code and permanent fault code, and requests the main controller to turn off the fault indicator light. When the main controller turns off the fault indicator light, it clears its own permanent fault code, thereby ensuring the unity and accuracy of the information stored by the main controller and the main controller.

[0136] Step S304: Send a first clearing request to the main controller.

[0137] Specifically, the Primary controller may clear the confirmed fault code according to the requirements of Regulation J.3.2.4, and continuously request the Master controller to clear the fault code information through the CAN signal PrimaryXXX_ClearDiagnosticInfo=2.

[0138] Step S403: based on a first clearing request sent by the main controller, clear the stored confirmed fault code and pending fault code, and send a first status signal to the main controller.

[0139] The first status signal is used to indicate that the fault code information has been cleared.

[0140] Specifically, the Master controller receives the first clear request to clear the confirmed fault code and pending fault code, and after completing the clearing of the fault code information, can feedback to the Primary controller that the clearing of the fault code information is completed through the CAN signal Master_ClearXXXDiagnosticInfo=3. It should be noted that in the signal definition similar to Master_ClearXXXDiagnosticInfo, XXX represents a certain Master controller.

[0141] Step S305, after receiving the first status signal sent by the main controller, clear the confirmed fault code stored in itself.

[0142] Specifically, after receiving the first status signal, the Primary controller clears the confirmed fault code and resets the clear request (ie, PrimaryXXX_ClearDiagnosticInfo=0).

[0143] The fault diagnosis management method provided by the embodiment of the present invention uses the main controller to summarize the fault signals generated by itself and sent by the corresponding sub-controller, generate its own pending fault code, confirmed fault code and permanent fault code, and send a fault indicator light lighting request to the main controller, and the main controller lights up the fault indicator and generates pending fault code, confirmed fault code and permanent fault code. When the main controller does not detect the fault and the corresponding sub-controller's fault indicator light lighting request within the preset time, it clears its own pending fault code and permanent fault code, and sends a fault indicator light extinguishing request to the main controller, and the main controller extinguishes the fault indicator and clears its own stored permanent fault code. Finally, the interaction between the main controller and the main controller is used to clear the remaining stored fault codes of both. By using the main controller to uniformly control the lighting or extinguishing of the fault indicator, the problem of controller function redundancy is effectively solved, cost is saved, and the unification of fault diagnosis information between controllers is guaranteed through the interaction between controllers.

[0144] In this embodiment, a fault diagnosis management method is provided. The fault diagnosis management method can be used for Figure 1 The main controller 101 and the main controller 102 shown, such as MCU, single chip microcomputer, etc., Figure 6 1 is a schematic diagram of the interaction process of the fault diagnosis management system according to an embodiment of the present invention, wherein the main controller 102 is used to execute steps S501 to S505, and the master controller 101 is used to execute steps S601 to S603. The specific interaction process between the master controller 101 and the main controller 102 is as follows:

[0145] Step S501: When a fault is identified based on a fault signal generated by itself or sent by a corresponding sub-controller, a pending fault code stored by itself is generated. Figure 5 Step S301 of the illustrated embodiment will not be described in detail here.

[0146] Step S502: after identifying the occurrence of a fault and confirming the fault type based on the fault signal, generate a self-stored confirmed fault code and a permanent fault code, and send a fault indicator light lighting request to the main controller. Figure 5 Step S302 of the illustrated embodiment will not be described in detail here.

[0147] Step S601, receiving a fault indicator light-on request sent by the main controller, lighting the fault indicator light, and generating pending fault codes, confirmed fault codes, and permanent fault codes stored in the system. Figure 5 Step S401 of the illustrated embodiment will not be described in detail here.

[0148] Step S503, after receiving the fault clearing instruction sent by the external device, clear the confirmed fault code and pending fault code stored in itself, and send a second extinguishing request to the main controller.

[0149] Specifically, when the fault code of the controller is cleared by the external device, the Primary controller clears the confirmed fault code and the pending fault code. After the confirmed fault code and the pending fault code are cleared, the MIL light is requested to be turned off through the CAN signal PrimaryXXX_MILReq=0.

[0150] Step S602, based on the second extinguishing request sent by the main controller, extinguish the fault indicator light and clear the permanent fault code stored in itself.

[0151] Specifically, the Master controller immediately turns off the MIL light and clears the permanent fault code after receiving the MIL turning off request.

[0152] In the embodiment of the present invention, when the main controller receives the fault clearing instruction sent by the external device, it clears its own confirmed fault code and pending fault code, and requests the master controller to turn off the fault indicator light. When the master controller turns off the fault indicator light, it clears its own permanent fault code, thereby ensuring the unity and accuracy of the information stored in the main controller and the master controller.

[0153] Step S504: Send a second clearing request to the main controller.

[0154] Specifically, 2s after sending the second extinguishing request to the Master controller, the Primary node continuously requests to clear the Master controller's confirmed fault code and pending fault code through the CAN signal PrimaryXXX_ClearDiagnosticInfo=2. It should be noted that the 2s time is considered to be compatible with the loop difference of the signal calculation of each controller, but the specific time can also be set according to the actual situation.

[0155] Step S603: based on the second clearing request sent by the main controller, the stored confirmed fault code and pending fault code are cleared, and a second status signal is sent to the main controller.

[0156] The second status signal is used to indicate that the permanent fault code has been cleared.

[0157] Specifically, after the Master controller clears the confirmed fault code and pending fault code, it confirms that the fault information has been cleared through the CAN signal MasterXXX_ClearPrimaryXXXDiagnosticInfo=3, and the Primary node CAN signal is reset (i.e. PrimaryXXX_ClearDiagnosticInfo=0). In addition, the Master controller also sends a second status signal to the Primary node to indicate that the permanent fault code has been cleared.

[0158] Step S505, after receiving the second state signal sent by the main controller, clear the permanent fault code stored in itself.

[0159] Specifically, the permanent fault code inside the Primary controller is executed according to the permanent fault code clearing conditions required by the regulation J.3.2.5.2. The permanent fault code of the Primary node cannot be cleared by external devices. The Primary controller can only clear the permanent fault code after the Master controller continuously sends the CAN signal MasterXXX_PFCCCondition=1 (permanent fault code clearing condition) to the Primary controller. After the Primary controller clears the permanent fault code, it is fed back to the Master controller through the CAN signal PrimaryXXX_ClearDiagnosticInfo=3, and the signal is reset (MasterXXX_PFCCCondition=0).

[0160] The fault diagnosis management method provided by the embodiment of the present invention uses the main controller to summarize the fault signals generated by itself and sent by the corresponding sub-controller, generate its own pending fault code, confirmed fault code and permanent fault code, and send a fault indicator light lighting request to the main controller, and the main controller lights up the fault indicator and generates pending fault code, confirmed fault code and permanent fault code. When the main controller receives the fault clearing instruction sent by the external device, it clears its own confirmed fault code and pending fault code, and sends a fault indicator light extinguishing request to the main controller, and the main controller extinguishes the fault indicator and clears the permanent fault code stored in itself. Finally, the interaction between the main controller and the main controller is used to clear the remaining stored fault codes of both. By using the main controller to uniformly control the lighting or extinguishing of the fault indicator light, the problem of controller function redundancy is effectively solved, costs are saved, and the unification of fault diagnosis information between controllers is guaranteed through the interaction between controllers.

[0161] The following are two specific application examples that can ensure the uniformity of diagnostic information of each OBD controller and the uniqueness of regulatory parameters:

[0162] Application example 1:

[0163] like Figure 7 As shown, if the Primary controller identifies a fault, it can store a pending fault code within 10 seconds.

[0164] After confirming the fault or fault type, the Primary node controller can request the Master controller to light up the MIL light (Primary node 1 / 3 step) through the CAN signal PrimaryXXX_MILReq=1, and store a confirmed fault code and a permanent fault code.

[0165] After receiving the MIL light request, the Master controller stores the unique fault code (including pending fault confirmation, confirmed fault, and permanent fault) and turns on the MIL light (Master node 1 / 3 step).

[0166] If the Primary controller detects that the MIL light no longer needs to be lit after at least three consecutive driving cycles, and the fault that caused the MIL light to light up before has not reappeared, and no other faults that require the MIL light to light up are detected, it will request to turn off the MIL through the CAN signal PrimaryXXX_MILReq = 0. At the same time, the Primary controller can clear pending fault codes and permanent fault codes (Primary node 2 / 3 steps).

[0167] The Master controller turns off the MIL light and clears the permanent fault code when receiving the MIL light off request. Clearing the permanent fault code and turning off the MIL light can be performed at the same time, or no later than before the start of the first driving cycle that turns off the MIL (Master node 2 / 3 step).

[0168] The Primary controller can clear the confirmed fault code according to the requirements of Regulation J.3.2.4, and continuously request the Master controller to clear the fault code information through the CAN signal PrimaryXXX_ClearDiagnosticInfo=2 (Primary node 3 / 3 step).

[0169] After receiving the fault clearing request, the Master controller clears the confirmed fault code and pending fault code. After completing the fault code information clearing, it feedbacks the completion of fault code information clearing to the Primary controller through the CAN signal Master_ClearXXXDiagnosticInfo=3. The Primary controller clears the request and resets PrimaryXXX_ClearDiagnosticInfo=0 (Master node 3 / 3 step).

[0170] Application Example 2:

[0171] like Figure 8 As shown, if the Primary controller identifies a fault, it can store a pending fault code within 10 seconds.

[0172] After confirming the fault or fault type, the Primary node controller can request the Master controller to light up the MIL light through the CAN signal PrimaryXXX_MILReq=1, and store a confirmed fault code and a permanent fault code (Primary node 1 / 5 step).

[0173] After receiving the MIL light request, the Master controller stores the unique fault code (pending fault confirmation, confirmed fault, and permanent fault are all stored) and turns on the MIL light (Master node 1 / 4 step).

[0174] The Primary controller keeps the MIL light on through the CAN signal PrimaryXXX_MILReq=1 (Primary node 2 / 5 step).

[0175] When the controller fault code is cleared by an external device, the Primary node clears the confirmed fault code and pending fault code (Primary node step 3 / 5). After the confirmed fault code and pending fault code are cleared, the MIL light is turned off through the CAN signal PrimaryXXX_MILReq=0 (Primary node step 4 / 5).

[0176] Upon receiving the MIL off request, the Master controller immediately turns off the MIL light and clears the permanent fault code (Master node 2 / 4 steps).

[0177] 2 seconds after sending the MIL light off request to the Master controller, the Primary node continuously requests to clear the Master controller's confirmed fault code and pending fault code through the CAN signal PrimaryXXX_ClearDiagnosticInfo=2 (Primary node 5 / 5 step).

[0178] After the Master controller clears the confirmed fault code and pending fault code, it confirms that the fault information has been cleared through the CAN signal MasterXXX_ClearPrimaryXXXDiagnosticInfo=3, and the Primary node CAN signal is reset, that is, PrimaryXXX_ClearDiagnosticInfo=0 (Master node 3 / 4 step).

[0179] The permanent fault code inside the Primary controller is executed according to the permanent fault code clearing conditions required by the regulation J.3.2.5.2. The permanent fault code of the Primary node cannot be cleared by external devices. The Primary controller can only clear the permanent fault code after the Master controller sends the CAN signal MasterXXX_PFCCCondition=1 (permanent fault code clearing condition) to the Primary controller continuously (Master node 4 / 4 step). After the Primary controller clears the permanent fault code, it is fed back to the Master controller through the CAN signal PrimaryXXX_ClearDiagnosticInfo=3, and the signal is reset, that is, MasterXXX_PFCCCondition=0.

[0180] It should be noted that after the Primary controller performs special operations such as data flushing, if the Primary node controller sends a CAN signal to keep PrimaryXXX_MILReq=0, it is necessary to continuously request to clear the Master controller's confirmed fault code and pending fault code through the CAN signal XXX_ClearDiagnosticInfo=2 after 2s. After the Master controller clears the fault code, it confirms that the fault information has been cleared through the CAN signal MasterXXX_ClearPrimaryXXXDiagnosticInfo=3, and the Primary node CAN signal is reset, that is, PrimaryXXX_ClearDiagnosticInfo=0; if the Primary node controller sends a CAN signal XXX_MILReq=1, it runs according to the above normal logic.

[0181] The present invention manages the MIL lights and fault information of each OBD controller through the Master controller, reduces the complexity of controller diagnostic signal interaction, ensures the unification of OBD storage information between the Master controller and the Primary controller, and ensures the accuracy of the OBD scan signal output of each OBD controller and the uniqueness of regulatory parameters.

[0182] The embodiment of the present invention provides a highly integrated, complete and universal vehicle OBD system diagnostic architecture, which is widely applicable to traditional vehicles, hybrid vehicles and pure electric vehicles, effectively solves the current OBD controller function redundancy problem, and saves time and labor costs for the controller OBD function development. It also solves the problem of chaotic physical addressing ID management of each controller, improves the compatibility of production line electrical inspection equipment and diagnostic instruments, and simultaneously improves the compatibility and portability of each control in different projects and different platforms.

[0183] The embodiment of the present invention further provides a vehicle, such as Fig. 9 As shown, with the above Figure 1 The fault diagnosis management system 100 is shown.

[0184] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0185] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0186] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A fault diagnosis management method, It is characterized in that Applied to any main controller in a fault diagnosis management system composed of a main controller, multiple main controllers and multiple sub-controllers, wherein each sub-controller corresponds to a main controller, and multiple main controllers are respectively connected to the main controller, the method comprises: Based on the fault signal generated by itself or sent by the corresponding sub-controller, it generates fault code information stored by itself, and sends a fault indicator light lighting request to the main controller, so that the main main controller lights up the fault indicator light and generates fault code information stored by the main controller; When it is detected that the fault has been resolved, the fault code information stored in the system is updated, and a fault indicator light off request is sent to the main controller, so that the main controller turns off the fault indicator light and updates the fault code information stored in the main controller; Sending a fault code information clearing request to the master controller so that the master controller clears the stored fault code information, and sending status information indicating that the clearing is completed to the main controller; After receiving the status information sent by the main controller, clear the fault code information stored in itself.

2. The method according to claim 1, It is characterized in that The fault code information includes pending fault codes, confirmed fault codes and permanent fault codes; the fault code information stored in the controller is generated based on the fault signal generated by the controller itself or sent by the corresponding sub-controller, and a fault indicator light lighting request is sent to the main controller, including: When a fault is identified based on a fault signal generated by itself or sent by a corresponding secondary controller, a pending fault code stored by itself is generated; After identifying that a fault has occurred and confirming the fault type based on the fault signal, it generates a confirmed fault code and a permanent fault code that are stored in itself, and sends a fault indicator light lighting request to the main controller so that the main controller lights up the fault indicator light, and generates a pending fault code, a confirmed fault code and a permanent fault code that are stored in the main controller.

3. The method according to claim 2, It is characterized in that The fault indicator light off request includes a first off request; when it is detected that the fault has been resolved, the fault code information stored in the device is updated, and a fault indicator light off request is sent to the main controller, including: When no fault is detected within the preset time and the corresponding sub-controller requests the fault indicator light to light up, the pending fault code and permanent fault code stored in itself are cleared, and a first extinguishing request is sent to the main controller to make the main controller extinguish the fault indicator light and clear the permanent fault code stored in the main controller.

4. The method according to claim 3, It is characterized in that The fault code information clearing request includes a first clearing request, and the status information includes a first status signal for indicating that the fault code information clearing is completed; and sending the fault code information clearing request to the main controller includes: Sending a first clearing request to the master controller so that the master controller clears the confirmed fault code and the pending fault code stored in the master controller, and sending a first status signal to the main controller; After receiving the status information sent by the master controller, clearing the fault code information stored in itself includes: After receiving the first status signal sent by the main controller, the confirmed fault code stored in itself is cleared.

5. The method according to claim 2, It is characterized in that The fault indicator light off request includes a second off request; when it is detected that the fault has been resolved, the fault code information stored in the self-stored fault indicator light is updated, and a fault indicator light off request is sent to the main controller, including: After receiving the fault clearing instruction sent by the external device, the confirmed fault code and pending fault code stored in itself are cleared, and a second extinguishing request is sent to the main controller to make the main controller extinguish the fault indicator light and clear the permanent fault code stored in the main controller.

6. The method according to claim 5, It is characterized in that The fault code information clearing request includes a second clearing request, and the status information includes a second status signal for indicating that the permanent fault code clearing is completed; and sending the fault code information clearing request to the main controller includes: Sending a second clearing request to the master controller so that the master controller clears the confirmed fault code and the pending fault code stored in the master controller, and sending a second status signal to the main controller; After receiving the status information sent by the master controller, clearing the fault code information stored in itself includes: After receiving the second status signal sent by the main controller, the permanent fault code stored in itself is cleared.

7. The method according to any one of claims 1 to 6, It is characterized in that The method further comprises: Based on the software calibration identification code and software calibration verification code sent by the corresponding sub-controller, the software version information of the corresponding sub-controller is output or managed.

8. The method according to any one of claims 1 to 6, It is characterized in that The method further comprises: Receive output information sent by the main controller, and send the output information to an external device; wherein the output information includes at least one of engine calculated load, engine cooling temperature, engine speed, throttle absolute position, throttle relative position, powertrain running time, powertrain shutdown time, common denominator counter, denominator count, denominator counter effective state, ignition counter, ignition counter effective state, and warm-up cycle.

9. A fault diagnosis management method, It is characterized in that A method for applying a master controller in a fault diagnosis management system composed of a master controller, multiple main controllers and multiple sub-controllers, wherein each sub-controller corresponds to a master controller, and multiple main controllers are respectively connected to the master controller, comprising: Receiving a fault indicator light lighting request sent by the main controller, lighting the fault indicator light, and generating fault code information stored in itself, wherein the fault indicator light lighting request is generated by the main controller based on a fault signal generated by itself or sent by a corresponding sub-controller; receiving a fault indicator light off request sent by the main controller, turning off the fault indicator light, and updating the fault code information stored in the main controller, wherein the fault indicator light off request is generated by the main controller when it is detected that the fault has been resolved; Based on the fault code information clearing request sent by the main controller, the stored fault code information is cleared, and status information indicating the completion of the clearing is sent to the main controller, so that the main controller clears the fault code information stored in the main controller after receiving the status information.

10. The method according to claim 9, It is characterized in that The generating of the fault code information stored in the self-stored state includes: Generates pending fault codes, confirmed fault codes, and permanent fault codes that are stored by itself.

11. The method according to claim 10, It is characterized in that The fault indicator light extinguishing request includes a first extinguishing request; the receiving the fault indicator light extinguishing request sent by the main controller, extinguishing the fault indicator light, and updating the fault code information stored in itself, includes: Based on the first extinguishing request sent by the main controller, the fault indicator light is extinguished and the permanent fault code stored in the main controller is cleared; wherein, the first extinguishing request is generated when the main controller clears the stored pending fault code and permanent fault code after failing to generate or receive a fault signal sent by the corresponding sub-controller within a preset time.

12. The method according to claim 11, It is characterized in that The fault code information clearing request includes a first clearing request, and the status information includes a first status signal for indicating that the fault code information clearing is completed; the fault code information clearing request sent by the main controller clears the stored fault code information and sends the status information for indicating that the clearing is completed to the main controller, including: Based on a first clearing request sent by the main controller, the stored confirmed fault code and pending fault code are cleared, and a first status signal is sent to the main controller so that the main controller clears the confirmed fault code stored in the main controller after receiving the first status signal.

13. The method according to claim 10, It is characterized in that The fault indicator light extinguishing request includes a second extinguishing request; the receiving the fault indicator light extinguishing request sent by the main controller, extinguishing the fault indicator light, and updating the fault code information stored in itself, includes: Based on the second extinguishing request sent by the main controller, the fault indicator light is extinguished and the permanent fault code stored in the main controller is cleared; wherein, the second extinguishing request is generated when the main controller clears the stored confirmed fault code and pending fault code after receiving the fault clearing instruction sent by the external device.

14. The method according to claim 13, It is characterized in that The fault code information clearing request includes a second clearing request, and the status information includes a second status signal for indicating that the permanent fault code clearing is completed; the fault code information clearing request based on the fault code information sent by the main controller clears the stored fault code information and sends the status information for indicating that the clearing is completed to the main controller, including: Based on a second clear request sent by the main controller, the stored confirmed fault code and pending fault code are cleared, and a second status signal is sent to the main controller so that the main controller clears the permanent fault code stored in the main controller after receiving the second status signal.

15. A fault diagnosis management system, It is characterized in that The system includes a master controller, a plurality of main controllers and a plurality of sub-controllers, wherein each sub-controller corresponds to a master controller, and the plurality of main controllers are respectively connected to the master controller; The main controller generates fault code information stored in itself based on the fault signal generated by itself or sent by the corresponding sub-controller, and sends a request to light up the fault indicator light to the main controller; The master controller receives the fault indicator light-up request sent by the main controller, lights up the fault indicator light, and generates fault code information stored in itself; When the main controller detects that the fault has been resolved, it updates the fault code information stored in itself and sends a request to turn off the fault indicator light to the main controller; The master controller receives the fault indicator light extinguishing request sent by the main controller, extinguishes the fault indicator light, and updates the fault code information stored in the master controller; The main controller sends a fault code information clearing request to the main controller; The master controller clears the stored fault code information based on the fault code information clearing request sent by the main controller, and sends status information indicating that the clearing is completed to the main controller; After receiving the status information sent by the main controller, the main controller clears the fault code information stored in itself.

16. A vehicle, It is characterized in that Includes the fault diagnosis management system as described in claim 15.