Fault management method and related equipment

Abstract

The invention provides a fault management method and related equipment. The fault management method comprises the following steps: acquiring a fault type of the vehicle and a fault state corresponding to the fault type; determining a fault state mark corresponding to the fault state based on the fault state and a preset calibration state rule; and generating a fault management strategy based on the fault state mark, the fault type of the vehicle and preset calibration data. In different scenes, different fault state diagnosis can be realized by adjusting the preset calibration state rule, and different fault management strategies can be realized by adjusting the preset calibration data.

Description

Technical Field

[0001] The present application relates to the field of vehicles, and in particular to a fault management method and related equipment. Background Art

[0002] The vehicle is a complex system involving motors, controllers, shift mechanisms, electro-hydraulic control modules, oil pumps and other components. Vehicle fault diagnosis is diverse, ranging from mechanical diagnosis to electrical diagnosis, from minor sensor failure to serious power system failure. Each fault may require different fault suppression strategies and treatment measures, including limiting functions, entering safe mode, etc. In order to implement different suppression strategies and treatment measures, it is usually necessary to modify the software logic of the diagnostic fault suppression management system. This will not only increase the workload of software developers and testers and reduce software development efficiency, but may also lead to vulnerabilities and other problems due to continuous modification of software logic. Summary of the invention

[0003] In order to solve the problems in the prior art, the present application provides a fault management method and related equipment to achieve flexible adjustment of fault management strategies.

[0004] The present application provides a fault management method, which is applied to a vehicle. The fault management method includes:

[0005] Acquire a fault type of the vehicle and a fault state corresponding to the fault type;

[0006] Based on the fault state and a preset calibration state rule, determining a fault state flag corresponding to the fault state;

[0007] A fault management strategy is generated based on the fault status flag, the fault type of the vehicle and preset calibration data.

[0008] In one embodiment, determining a fault state flag corresponding to the fault state based on the fault state and a preset calibration state rule includes:

[0009] If the fault state is consistent with the preset calibration state, determining that the fault state flag is a first flag value;

[0010] If the fault state is inconsistent with the preset calibration state, the fault state flag is determined to be a second flag value.

[0011] In one embodiment, the preset calibration data includes a plurality of fault types and a preset value of a fault status flag corresponding to each fault type, and the generating of a fault management strategy based on the fault status flag, the fault type of the vehicle and the preset calibration data includes:

[0012] If the fault status flag is consistent with a preset value of the fault status flag corresponding to the fault type of the vehicle, one or more of restricted function management, safe mode management, and suppressed function management are performed based on the fault type of the vehicle.

[0013] In one embodiment, the performing one or more of limited function management, safe mode management, and inhibited function management based on the fault type of the vehicle includes:

[0014] If the fault type is a limited function fault, executing the limited function management;

[0015] If the fault type is a safety mode fault, executing the safety mode management;

[0016] If the fault type is a suppression function fault, the suppression function management is performed.

[0017] In one embodiment, the fault management method further includes:

[0018] A fault status table is generated based on the multiple fault types; in the fault status table, each fault type corresponds to a fault status flag.

[0019] In one embodiment, the preset calibration data includes a plurality of limited function fault types and limited function management strategies corresponding to different fault status flags under each limited function fault type, and the generating of the fault management strategy based on the fault status flag, the fault type of the vehicle and the preset calibration data includes:

[0020] If the fault type is a limiting function fault and the fault status flag is a first flag value, the first type of limiting function management is performed; if the fault type is a limiting function fault and the fault status flag is a second flag value, the second type of limiting function management is performed.

[0021] In one embodiment, the preset calibration data includes a plurality of safety mode fault types and safety mode management strategies corresponding to different fault status flags under each safety mode fault type, and the generating of the fault management strategy based on the fault status flag, the fault type of the vehicle and the preset calibration data includes:

[0022] If the fault type is a safety mode fault and the fault status flag is a first flag value, the first type of safety mode management is performed; if the fault type is a safety mode fault and the fault status flag is a second flag value, the second type of safety mode management is performed.

[0023] In one embodiment, the preset calibration data includes a plurality of inhibition function fault types and inhibition function management strategies corresponding to different fault status flags under each inhibition function fault type, and the generating of the fault management strategy based on the fault status flag, the fault type of the vehicle and the preset calibration data includes:

[0024] If the fault type is a suppression function fault and the fault status flag is a first flag value, the first type of suppression function management is performed; if the fault type is a suppression function fault and the fault status flag is a second flag value, the second type of suppression function management is performed.

[0025] The present application also proposes a vehicle, comprising:

[0026] A state acquisition module, used to acquire the fault type of the vehicle and the fault state corresponding to the fault type;

[0027] A flag determination module, used to determine a fault state flag corresponding to the fault state based on the fault state and a preset calibration state rule;

[0028] A strategy generation module is used to generate a fault management strategy based on the fault status flag, the fault type of the vehicle and preset calibration data.

[0029] The present application also proposes an electronic device, which includes a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call the instructions in the memory so that the electronic device executes the above-mentioned fault management method.

[0030] The present application also proposes a storage medium, comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned fault management method.

[0031] This application obtains the fault state corresponding to the fault type, determines the fault state flag according to the preset calibration state rules, and generates a fault management strategy according to the fault state flag, fault type and preset calibration data. In different scenarios, different fault state diagnoses can be achieved by adjusting the preset calibration state rules, and different fault management strategies can be achieved by adjusting the preset calibration data. The modification of the preset calibration state rules and the preset calibration data changes the software logic more conveniently. In this way, in the face of complex vehicle control systems, the development cycle of the vehicle control system can be reduced and the software development efficiency and quality can be improved by changing the preset calibration state rules and preset calibration data according to actual applications. It is also convenient for developers to adjust the fault management strategy in time according to different faults, and improve the accuracy of fault diagnosis and the safety performance of the whole vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1This is a schematic diagram of the module structure of a vehicle embodiment of the present application.

[0033] Figure 2 This is a schematic diagram of the module structure of an embodiment of a strategy generation module of the present application.

[0034] Figure 3 This is a flow chart of an embodiment of a fault management method of the present application.

[0035] Figure 4 The present invention is a flowchart of an embodiment of determining a fault status flag corresponding to a fault status of the present invention.

[0036] Figure 5 This is a flow chart of an embodiment of generating a fault management strategy of the present application.

[0037] Figure 6 This is a flow chart of an embodiment of generating a fault management strategy of the present application.

[0038] Figure 7 The flowchart of another embodiment of generating a fault management strategy of the present application.

[0039] Figure 8 The flowchart of another embodiment of generating a fault management strategy of the present application.

[0040] Fig. 9 The flowchart of another embodiment of generating a fault management strategy of the present application.

[0041] Fig.10 The flowchart of another embodiment of generating a fault management strategy of the present application.

[0042] Main component symbols

[0043] Vehicle 100 State acquisition module 110 Flag determination module 120 Policy generation module 130 Restriction function management module 131 Safety mode management module 132 Fault suppression management module 133

[0045] The following specific implementation methods will further illustrate the present application in conjunction with the above-mentioned drawings. DETAILED DESCRIPTION

[0046] The following description will refer to the accompanying drawings to more fully describe the content of the present application. Shown in the accompanying drawings are exemplary embodiments of the present application. However, the present application can be implemented in many different forms and should not be interpreted as being limited to the exemplary embodiments set forth herein. These exemplary embodiments are provided to make the present application thorough and complete, and to fully convey the scope of the present application to those skilled in the art. Similar reference numerals represent identical or similar components.

[0047] The terms used herein are only used for the purpose of describing specific exemplary embodiments and are not intended to limit the present application. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to also include the plural forms. In addition, when used herein, "including" and / or "comprising" and / or "having", integers, steps, operations, components and / or components, but do not exclude the existence or addition of one or more other features, regions, integers, steps, operations, components and / or groups thereof.

[0048] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which this application belongs. In addition, unless explicitly defined herein, terms such as those defined in general dictionaries should be interpreted as having a meaning consistent with their meaning in the relevant technology and the content of this application, and will not be interpreted as an idealized or overly formal meaning.

[0049] The following will describe exemplary embodiments in conjunction with the accompanying drawings. It should be noted that the components depicted in the reference drawings are not necessarily shown to scale; and the same or similar components will be given the same or similar reference numerals or similar technical terms.

[0050] Reference Figure 1 The present application proposes a vehicle 100, comprising a state acquisition module 110, a sign determination module 120 and a strategy generation module 130. The state acquisition module 110 is used to acquire the fault type of the vehicle 100 and the fault state corresponding to the fault type. The sign determination module 120 is used to determine the fault state sign corresponding to the fault state based on the fault state and a preset calibration state rule. The strategy generation module 130 is used to generate a fault management strategy based on the fault state sign, the fault type of the vehicle 100 and preset calibration data.

[0051] In this embodiment, the vehicle 100 may include an electric vehicle and a hybrid vehicle. The faults of the vehicle 100 may include mechanical faults (e.g., gear shift failure faults, abnormal gear shift faults) and electrical faults (e.g., sensor failure faults, transistor switch faults, etc.). The state acquisition module 110 may determine the fault type and the fault state corresponding to the fault type by communicating with the electronic devices in the vehicle 100. For example, the fault code of the oil temperature sensor is 02184B, and the state acquisition module 110 determines the fault state of the oil temperature sensor by reading the voltage value output by the oil temperature sensor. If the voltage value is within the preset voltage range, the fault state of 02184B is determined to be passed; if the voltage value is not within the preset voltage range, the fault state of 02184B is determined to be failed; if the fault state determination is not completed, the fault state of 02184B is not completed.

[0052] The flag determination module 120 can compare the fault state of the vehicle 100 according to the preset calibration state rules and generate a fault state flag. The preset calibration state rules can be set according to actual needs to achieve fault diagnosis and fault management in different scenarios.

[0053] In one embodiment, the flag determination module 120 determines that the fault state flag is a first flag value when the fault state is consistent with the preset calibration state; and determines that the fault state flag is a second flag value when the fault state is inconsistent with the preset calibration state.

[0054] For example, the preset calibration status of 02184B is set to Failure. When the fault status of 02184B is Failure, the generated fault status flag is 1; when the fault status of 02184B is Pass or Incomplete, the generated fault status flag is 0. Alternatively, the preset calibration status of 02184B is set to Failure or Incomplete. When the fault status of 02184B is Failure or Incomplete, the generated fault status flag is 1; when the fault status of 02184B is Pass, the generated fault status flag is 0. In this way, users can set calibration status rules according to their needs to achieve fault status diagnosis in different scenarios.

[0055] The strategy generation module 130 can generate a fault management strategy based on the fault status flag, the fault type of the vehicle 100 and the preset calibration data. The preset calibration data may include the fault type that needs to be faulted or managed and the preset value of the fault status flag corresponding to each fault type. If the fault type of the vehicle 100 actually obtained is in the preset calibration data, and the fault status flag of the fault type is consistent with the preset value of the fault status flag, the corresponding fault management is performed. The preset calibration data can increase / decrease the fault type according to actual needs, or modify the preset value of the fault status flag to achieve fault diagnosis and fault management in different scenarios.

[0056] In one embodiment, the preset calibration data includes multiple fault types and a preset value of a fault status flag corresponding to each fault type. If the fault status flag is consistent with the preset value of the fault status flag corresponding to the fault type of the vehicle 100, the strategy generation module 130 is used to execute one or more of restricted function management, safe mode management, and suppressed function management based on the fault type of the vehicle 100.

[0057] For example, in the preset calibration data, the preset value of the fault status flag of 02184B is 1. If the strategy generation module 130 actually obtains that the fault status flag of 02184B is 1, the restricted function management is executed.

[0058] Reference Figure 2In one embodiment, the policy generation module 130 further includes a restricted function management module 131, a safe mode management module 132 and a fault suppression management module 133. If the fault type is a restricted function fault, the restricted function management module 131 performs the restricted function management; if the fault type is a safe mode fault, the safe mode management module 132 performs the safe mode management; if the fault type is a suppressed function fault, the fault suppression management module 133 performs the suppressed function management.

[0059] In this embodiment, the preset calibration data of the limiting function management module 131 may include the fault types that need to be limited, such as vehicle speed sensor fault (fault code is 02184C), oil temperature sensor fault (fault code is 02184D), battery temperature sensor fault (fault code is 02184E), etc. When the vehicle speed is too high, the limiting function management module 131 obtains that the fault state flag corresponding to 02184C is 1, indicating that the vehicle speed in this state may affect the normal operation of the vehicle 100, then the limiting function management module 131 sets the limiting function flag to 1 and outputs it to the drive motor of the wheel to limit the output torque of the drive motor, thereby limiting the vehicle speed.

[0060] The preset calibration data of the safety mode management module 132 may include the fault types that require entering the safety mode, such as the failure of the switch tube in the motor controller (fault code is 02184F), the shift system jamming fault (fault code is 03184A), etc. When the switch tube in the motor controller fails, the safety mode management module 132 obtains that the fault state flag corresponding to 02184F is 1, indicating that the fault state may affect the safe operation of the vehicle 100, then the safety mode management module 132 sets the safety mode flag to 1 and outputs it to the vehicle controller to control the vehicle 100 to enter the safety mode. After entering the safety mode, the vehicle 100 can drive to the repair shop at a lower speed.

[0061] The preset calibration data of the fault suppression management module 133 may include the types of faults that need to be suppressed, such as vehicle speed sensor fault (fault code is 02184C), abnormal battery voltage fault (fault code is 03184B), etc. If the battery voltage is too low, it may cause abnormal communication of the whole vehicle, and electrical components such as sensors may not work properly, and the fault will also be reported. Therefore, when the battery voltage is too low, it is necessary to suppress the reporting of communication faults and sensor faults, so as to avoid the occurrence of secondary faults, guide maintenance personnel to find the real cause of the problem, and facilitate the maintenance of the vehicle 100. When the battery voltage is too low, the fault suppression management module 133 obtains the fault state flag corresponding to 03184B as 1, indicating that the fault state may cause the suppression of communication faults and sensor faults, then the fault suppression management module 133 sets the fault suppression flag to 1, and outputs it to the relevant communication device and sensor to suppress the communication fault and sensor fault from being reported.

[0062] In actual applications, the preset calibration data in the restricted function management module 131, the safe mode management module 132 and the fault suppression management module 133 can be changed according to actual needs to adjust the fault management mode and realize restricted function management, safe mode management and fault suppression management in different scenarios.

[0063] In one embodiment, the preset calibration data includes multiple limiting function fault types and limiting function management strategies corresponding to different fault status flags under each limiting function fault type. If the fault type is a limiting function fault and the fault status flag is a first flag value, the limiting function management module 131 executes the first type of limiting function management; if the fault type is a limiting function fault and the fault status flag is a second flag value, the limiting function management module 131 executes the second type of limiting function management.

[0064] In this embodiment, the preset calibration data of the limiting function management module 131 may include the fault type to be limited, the preset value of the fault status flag, and the limiting function flags corresponding to different preset values ​​of the fault status flag, as shown in Table 1, for example.

[0065] Table 1

[0066]

[0067] For example, when the vehicle speed is too high, the limiting function management module 131 obtains the fault state flag corresponding to 02184C as 1, then the limiting function management module 131 sets the limiting function flag to 2 and outputs it to the drive motor of the wheel to limit the output torque of the drive motor to 80%, thereby limiting the vehicle speed to the first vehicle speed. When the vehicle speed is normal, the limiting function management module 131 obtains the fault state flag corresponding to 02184C as 0, then the limiting function management module 131 sets the limiting function flag to 1 and outputs it to the drive motor of the wheel to limit the output torque of the drive motor to 50%. After determining that the running state of the vehicle 100 is normal, the torque limit is released to avoid multiple occurrences of the same fault in a short period of time to trigger multiple limiting fault management. In addition, when the fault state flag corresponding to 02184C is set to 0, the limiting function flag is set to 0 to limit the output torque of the drive motor to 0%. Among them, the specific value of limiting the output torque of the drive motor can be set according to the actual application (such as the running state of the vehicle 100). The limiting function flag can also be set to other flags for fault management according to the actual application, which is not limited here.

[0068] In one embodiment, the preset calibration data includes multiple safety mode failure types and safety mode management strategies corresponding to different failure status flags under each safety mode failure type. If the failure type is a safety mode failure and the failure status flag is a first flag value, the safety mode management module 132 performs a first type of safety mode management; if the failure type is a safety mode failure and the failure status flag is a second flag value, the safety mode management module 132 performs a second type of safety mode management.

[0069] In this embodiment, the preset calibration data of the safety mode management module 132 may include the fault type that requires entering the safety mode, the preset value of the fault status flag, and the restricted function flag corresponding to different preset values ​​of the fault status flag, as shown in Table 2, for example.

[0070] Table 2

[0071]

[0072] For example, when the switch tube in the motor controller fails, the safety mode management module 132 obtains the fault state flag corresponding to 02184F as 1, then the safety mode management module 132 sets the safety mode flag to 2 and outputs it to the vehicle controller, so that the vehicle 100 enters the safety mode. When the switch tube in the motor controller works normally, the safety mode management module 132 obtains the fault state flag corresponding to 02184F as 0, then the safety mode management module 132 sets the restriction function flag to 1, and outputs it to the vehicle controller, so that the power circuit and other modules in the vehicle 100 exit the safety mode, and the main fault modules such as the drive motor still remain in the safety mode. After determining that the operating state of the vehicle 100 is normal, all modules of the vehicle exit the safety mode to avoid multiple occurrences of the same fault in a short period of time triggering multiple safety mode management. In addition, when the fault state flag corresponding to 02184F is set to 0, the safety mode flag is set to 0 to exit the safety mode of the vehicle. The safety mode flag can also be set to other flags for fault management according to actual applications, which is not limited here.

[0073] In one embodiment, the preset calibration data includes multiple suppression function fault types and suppression function management strategies corresponding to different fault status flags under each suppression function fault type. If the fault type is a suppression function fault and the fault status flag is a first flag value, the fault suppression management module 133 executes a first type of suppression function management; if the fault type is a suppression function fault and the fault status flag is a second flag value, the fault suppression management module 133 executes a second type of suppression function management.

[0074] In this embodiment, the preset calibration data of the fault suppression management module 133 may include the fault type that needs to be suppressed, the preset value of the fault status flag, and the restriction function flag corresponding to different preset values ​​of the fault status flag, as shown in Table 3, for example.

[0075] Table 3

[0076]

[0077] For example, when the battery voltage is too low, the fault suppression management module 133 obtains the fault status flag corresponding to 03184B as 1, then the fault suppression management module 133 sets the fault suppression flag to 2 and outputs it to the relevant communication devices and sensors to suppress the communication type fault and sensor type fault from being reported. When the battery voltage is normal, the fault suppression management module 133 obtains the fault status flag corresponding to 03184B as 0, then the fault suppression management module 133 sets the fault suppression flag to 1 and outputs it to the vehicle controller to release the fault suppression of the relevant sensor and maintain the fault suppression of the relevant communication device. After determining that the operating state of the vehicle 100 is normal, the fault suppression of the relevant communication device is released to avoid the same fault from occurring multiple times in a short period of time and triggering multiple fault suppression management. In addition, when the fault status flag corresponding to 03184B is set to 0, the fault suppression flag is set to 0 to release the fault suppression of the relevant communication device and sensor. The fault suppression flag can also be set to other flags for fault management according to actual applications, which is not limited here.

[0078] In one embodiment, in the preset calibration data of the fault limit management module, the fault limit flag may also be set to be determined by a plurality of fault types and fault status flag preset values, as shown in Table 4, for example.

[0079] Table 4

[0080]

[0081]

[0082] When the fault limit management module obtains that the fault status flag of 02184C is 1 and the fault status flag of 03184C is 1, the fault limit flag is set to 1 to limit the output torque of the drive motor to 80% and the vehicle speed to the first vehicle speed. When the fault limit management module obtains that the fault status flags of 02184C, 03184D, and 03184B are all 1, it means that the vehicle 100 has more faults at this time, and the fault limit flag is set to 2 to limit the output torque of the drive motor to 0%. In addition, the fault type that determines the fault limit flag can also be set to four, five, etc., which is not limited here.

[0083] In actual applications, there may be dozens to hundreds of fault limit signs, and different fault limit signs correspond to different fault limit management modes. In this way, users can adjust the fault limit management mode through preset calibration data to achieve more convenient fault limit management and management mode change.

[0084] Similarly, the safety mode flag and the fault suppression flag can also be set to be determined by multiple fault types and fault status flags, so as to implement safety mode management and fault suppression management in different scenarios according to actual applications.

[0085] In one embodiment, the flag determination module 120 is further configured to generate a fault status table based on multiple fault types; in the fault status table, each fault type corresponds to one fault status flag.

[0086] In this embodiment, the flag determination module 120 can aggregate multiple fault types and corresponding fault status flags to generate a fault status table. In this way, the strategy generation module 130 only needs to communicate with the flag determination module 120 to obtain multiple fault status information, saving the time of communicating with multiple electronic devices and improving the calculation efficiency.

[0087] In one embodiment, the state acquisition module 110, the flag determination module 120 and the strategy generation module 130 can be integrated into the same controller. For example, the state acquisition module 110, the flag determination module 120 and the strategy generation module 130 are integrated into the whole vehicle controller. The state acquisition module 110 can communicate with various electronic devices in the vehicle 100 to obtain the fault type and fault state of each electronic device. The flag determination module 120 then determines the fault state flag corresponding to each fault type, and generates a fault management strategy according to the fault state flag and the corresponding fault type through the strategy generation module 130, so as to realize the fault management of the whole vehicle.

[0088] Alternatively, the state acquisition module 110, the flag determination module 120 and the strategy generation module 130 are integrated into the controller of a certain functional module in the vehicle 100. Taking the motor as an example, the state acquisition module 110, the flag determination module 120 and the strategy generation module 130 can be integrated into the motor controller. The state acquisition module 110 can communicate with electronic devices such as speed sensors and temperature sensors to obtain the fault type and fault state of various electronic devices, and then the flag determination module 120 determines the fault state flag corresponding to each fault type, and the strategy generation module 130 generates a fault management strategy according to the fault state flag and the corresponding fault type, so as to achieve fault management of the motor.

[0089] In one embodiment, the state acquisition module 110, the flag determination module 120 and the strategy generation module 130 can be integrated into different controllers. For example, the state acquisition module 110 can be set in the controller of various electronic devices to obtain the fault state of each electronic device. The flag determination module 120 can be set in the controller of the electronic device to determine the fault state flag corresponding to the fault type of the electronic device. Alternatively, the flag determination module 120 can be set in the vehicle controller to determine the fault state flag corresponding to the fault type of each electronic device. The strategy generation module 130 can be integrated into the vehicle controller to generate a fault management strategy based on the fault state flag and the corresponding fault type, so as to achieve fault management of the vehicle. In addition, the state acquisition module 110, the flag determination module 120 and the strategy generation module 130 can also be set in various domain controllers, such as a powertrain domain controller, a body electronics domain controller, an auxiliary driving domain controller, etc., which are not limited here.

[0090] The present application obtains the fault state corresponding to the fault type through the state acquisition module 110, and determines the fault state flag according to the preset calibration state rule through the flag determination module 120, so that the strategy generation module 130 generates a fault management strategy according to the fault state flag, the fault type and the preset calibration data. In different scenarios, different fault state diagnoses can be achieved by adjusting the preset calibration state rules, and different fault management strategies can be achieved by adjusting the preset calibration data. The modification of the preset calibration state rules and the preset calibration data makes it easier to modify the software logic. In this way, in the face of complex vehicle control systems, the development cycle of the vehicle control system can be reduced and the software development efficiency and quality can be improved by changing the preset calibration state rules and preset calibration data according to actual applications. It is also convenient for developers to adjust the fault management strategy in a timely manner according to different faults, and improve the accuracy of fault diagnosis and the safety performance of the entire vehicle.

[0091] Reference Figure 3 The present application also proposes a fault management method, which is applied to the vehicle 100. The fault management method includes:

[0092] S1: Acquire the fault type of the vehicle 100 and the fault state corresponding to the fault type.

[0093] In this embodiment, the faults of the vehicle 100 may include mechanical faults (e.g., gear shift failure fault, abnormal gear shift fault) and electrical faults (e.g., sensor failure fault, transistor switch fault, etc.). The fault type and the fault state corresponding to the fault type may be determined by communicating with the electronic components in the vehicle 100. For example, the fault code of the oil temperature sensor is 02184B, and the fault state of the oil temperature sensor is determined by reading the voltage value output by the oil temperature sensor. If the voltage value is within the preset voltage range, the fault state of 02184B is determined to be passed; if the voltage value is not within the preset voltage range, the fault state of 02184B is determined to be failed; if the fault state determination is not completed, the fault state of 02184B is not completed.

[0094] S2: Based on the fault state and a preset calibration state rule, determine a fault state flag corresponding to the fault state.

[0095] In this embodiment, the fault status flag can be determined by comparing the fault status of the vehicle 100 according to the preset calibration status rule. The preset calibration status rule can be set according to actual needs to achieve fault diagnosis and fault management in different scenarios.

[0096] Reference Figure 4 In one embodiment, step S2 includes:

[0097] S21: If the fault state is consistent with a preset calibration state, determine that the fault state flag is a first flag value.

[0098] S22: If the fault state is inconsistent with the preset calibration state, determine that the fault state flag is a second flag value.

[0099] For example, the preset calibration status of 02184B is set to Failure. When the fault status of 02184B is Failure, the generated fault status flag is 1; when the fault status of 02184B is Pass or Incomplete, the generated fault status flag is 0. Alternatively, the preset calibration status of 02184B is set to Failure or Incomplete. When the fault status of 02184B is Failure or Incomplete, the generated fault status flag is 1; when the fault status of 02184B is Pass, the generated fault status flag is 0. In this way, users can set calibration status rules according to their needs to achieve fault status diagnosis in different scenarios.

[0100] S3: Generate a fault management strategy based on the fault status flag, the fault type of the vehicle 100 and preset calibration data.

[0101] In this embodiment, the preset calibration data may include the fault type that needs to be faulted or managed and the preset value of the fault status flag corresponding to each fault type. If the fault type of the vehicle 100 actually obtained is in the preset calibration data, and the fault status flag of the fault type is consistent with the preset value of the fault status flag, the corresponding fault management is performed. The preset calibration data can increase / decrease the fault type according to actual needs, or modify the preset value of the fault status flag to achieve fault diagnosis and fault management in different scenarios.

[0102] Reference Figure 5 In one embodiment, step S3 includes:

[0103] S31: If the fault status flag is the first flag value, one or more of restricted function management, safe mode management, and suppressed function management are performed based on the fault type of the vehicle 100 .

[0104] For example, in the preset calibration data, the preset value of the fault status flag of 02184B is 1. If the fault status flag of 02184B is actually obtained to be 1, the restricted function management is executed.

[0105] Reference Figure 6 In one embodiment, step S31 includes:

[0106] S311: If the fault type is a limited function fault, execute the limited function management. If the fault type is a safe mode fault, execute the safe mode management. If the fault type is a suppressed function fault, execute the suppressed function management.

[0107] In this embodiment, the preset calibration data of the limiting function fault may include the fault type that needs to be limited, such as vehicle speed sensor fault (fault code is 02184C), oil temperature sensor fault (fault code is 02184D), battery temperature sensor fault (fault code is 02184E), etc. When the vehicle speed is too high, the fault state flag corresponding to 02184C is obtained as 1, indicating that the vehicle speed in this state may affect the normal operation of the vehicle 100, and the limiting function flag is set to 1 and output to the drive motor of the wheel to limit the output torque of the drive motor, thereby limiting the vehicle speed.

[0108] The preset calibration data of the safety mode fault may include the fault type that requires entering the safety mode, such as the failure of the switch tube in the motor controller (fault code is 02184F), the shift system jamming fault (fault code is 03184A), etc. When the switch tube in the motor controller fails, the fault state flag corresponding to 02184F is obtained as 1, indicating that the fault state may affect the safe operation of the vehicle 100, then the safety mode flag is set to 1 and output to the vehicle controller to control the vehicle 100 to enter the safety mode. After entering the safety mode, the vehicle 100 can drive to the repair shop at a lower speed.

[0109] The preset calibration data for suppressing functional faults may include the types of faults that need to be suppressed, such as vehicle speed sensor faults (fault code 02184C), abnormal battery voltage faults (fault code 03184B), etc. If the battery voltage is too low, it may cause abnormal communication of the entire vehicle, and electrical components such as sensors may not work properly, and faults may also be reported. Therefore, when a low battery voltage fault occurs, it is necessary to suppress the reporting of communication faults and sensor faults. This can avoid the occurrence of secondary faults, guide maintenance personnel to find the real cause of the problem, and facilitate vehicle 100 maintenance. When the battery voltage is too low, the fault status flag corresponding to 03184B is obtained as 1, indicating that the fault state may cause the suppression of communication faults and sensor faults. The fault suppression flag is set to 1 and output to the relevant communication devices and sensors to suppress the reporting of communication faults and sensor faults.

[0110] In actual applications, the preset calibration data in the restricted function management module 131, the safe mode management module 132 and the fault suppression management module 133 can be changed according to actual needs to adjust the fault management mode and realize restricted function management, safe mode management and fault suppression management in different scenarios.

[0111] Reference Figure 7 In one embodiment, step S3 includes:

[0112] S32: If the fault type is a limiting function fault and the fault status flag is a first flag value, execute the first type of limiting function management; if the fault type is a limiting function fault and the fault status flag is a second flag value, execute the second type of limiting function management.

[0113] In this embodiment, the preset calibration data of the limiting function fault may include the fault type that needs to be limited, the preset value of the fault status flag, and the limiting function flag corresponding to different preset values ​​of the fault status flag, as shown in Table 1, for example.

[0114] For example, when the vehicle speed is too high, the fault status flag corresponding to 02184C is obtained as 1, then the limit function flag is set to 1 and output to the wheel drive motor to limit the output torque of the drive motor, thereby limiting the vehicle speed to the first vehicle speed. When the vehicle speed is normal, the fault status flag corresponding to 02184C is obtained as 0, then the limit function flag is set to 2 and output to the wheel drive motor to release the speed limit.

[0115] Reference Figure 8 In one embodiment, step S3 includes:

[0116] S33: If the fault type is a safety mode fault and the fault status flag is a first flag value, execute the first type of safety mode management; if the fault type is a safety mode fault and the fault status flag is a second flag value, execute the second type of safety mode management.

[0117] In this embodiment, the preset calibration data of the safety mode fault may include the fault type that requires entering the safety mode, the preset value of the fault status flag, and the restricted function flags corresponding to different preset values ​​of the fault status flag, as shown in Table 2.

[0118] For example, when the switch tube in the motor controller fails, the fault status flag corresponding to 02184F is obtained as 1, then the safety mode flag is set to 1 and output to the vehicle controller to make the vehicle 100 enter the safety mode. When the switch tube in the motor controller works normally, the fault status flag corresponding to 02184F is obtained as 0, then the limit function flag is set to 2 and output to the vehicle controller to make the vehicle 100 exit the safety mode.

[0119] Reference Fig. 9 In one embodiment, step S3 includes:

[0120] S34: If the fault type is a suppression function fault and the fault status flag is a first flag value, execute the first type of suppression function management; if the fault type is a suppression function fault and the fault status flag is a second flag value, execute the second type of suppression function management.

[0121] In this embodiment, the preset calibration data for suppressing functional faults may include the fault type that needs to be suppressed, the preset value of the fault status flag, and the limiting function flags corresponding to different preset values ​​of the fault status flag, as shown in Table 3.

[0122] For example, when the battery voltage is too low, the fault status flag corresponding to 03184B is obtained as 1, then the fault suppression flag is set to 1 and output to the relevant communication devices and sensors to suppress the communication fault and sensor fault reporting. When the battery voltage is normal, the fault status flag corresponding to 03184B is obtained as 0, then the limit function flag is set to 2 and output to the vehicle controller to release the fault suppression of the relevant communication devices and sensors.

[0123] In one embodiment, in the preset calibration data of the limiting function fault, the fault limiting flag may also be set to be determined by a plurality of fault types and fault status flag preset values, as shown in Table 4, for example.

[0124] When the fault status flag of 02184C is obtained to be 1 and the fault status flag of 03184C is 1, the fault limit flag is set to 1, and the vehicle speed is limited to the first vehicle speed. When the fault status flag of 02184C is obtained to be 1 and the fault status flag of 03184B is 1, the fault limit flag is set to 2, and the vehicle speed is limited to the second vehicle speed. In addition, the fault type for which the fault limit flag is determined to be 1 can also be set to three, four, five, etc., which are not limited here.

[0125] In actual applications, there may be dozens to hundreds of fault limit signs, and different fault limit signs correspond to different fault limit management modes. In this way, users can adjust the fault limit management mode through preset calibration data to achieve more convenient fault limit management and management mode change.

[0126] Similarly, the safety mode flag and the fault suppression flag can also be set to be determined by multiple fault types and fault status flags, so as to implement safety mode management and fault suppression management in different scenarios according to actual applications.

[0127] Reference Fig.10 In one embodiment, the fault management method further includes:

[0128] S4: Generate a fault status table based on multiple fault types; in the fault status table, each fault type corresponds to a fault status flag.

[0129] In this embodiment, a fault status table is generated by aggregating multiple fault types and corresponding fault status flags, and multiple fault status information can be obtained by reading the fault status table, which saves the time of communicating with multiple electronic devices and improves computing efficiency.

[0130] This application obtains the fault state corresponding to the fault type, determines the fault state flag according to the preset calibration state rules, and generates a fault management strategy according to the fault state flag, fault type and preset calibration data. In different scenarios, different fault state diagnoses can be achieved by adjusting the preset calibration state rules, and different fault management strategies can be achieved by adjusting the preset calibration data. The modification of the preset calibration state rules and the preset calibration data makes it easier to modify the software logic. In this way, in the face of complex vehicle control systems, the development cycle of the vehicle control system can be reduced and the software development efficiency and quality can be improved by changing the preset calibration state rules and preset calibration data according to actual applications. It is also convenient for developers to adjust the fault management strategy in a timely manner according to different faults, and improve the accuracy of fault diagnosis and the safety performance of the entire vehicle.

[0131] The present application also proposes an electronic device, which includes a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call the instructions in the memory so that the electronic device executes the above-mentioned fault management method.

[0132] The present application also proposes a storage medium, comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned fault management method.

[0133] The storage medium may be a memory device in an electronic device for storing programs and data. It is understandable that the storage medium here may include both the built-in storage medium in the terminal and the extended storage medium supported by the terminal. The storage medium provides a storage space, which stores the operating system of the terminal. In addition, one or more instructions suitable for being loaded and executed by the processor are also stored in the storage space, and these instructions may be one or more computer programs (including program codes). It should be noted that the storage medium here may be a high-speed RAM memory, or a non-volatile memory, such as at least one disk memory; optionally, it may also be at least one storage medium located away from the aforementioned processor. In one embodiment, the processor may load and execute one or more instructions stored in the storage medium to implement the corresponding steps of the above-mentioned search method.

[0134] In the above, the specific implementation of the present application is described with reference to the accompanying drawings. However, those skilled in the art will appreciate that various changes and substitutions may be made to the specific implementation of the present application without departing from the spirit and scope of the present application. These changes and substitutions are all within the scope defined by the present application.

Claims

1. A fault management method, applied to a vehicle, characterized in that: The fault management method comprises: Acquire a fault type of the vehicle and a fault state corresponding to the fault type; Based on the fault state and a preset calibration state rule, determining a fault state flag corresponding to the fault state; A fault management strategy is generated based on the fault status flag, the fault type of the vehicle and preset calibration data.

2. The fault management method according to claim 1, characterized in that: The determining, based on the fault state and a preset calibration state rule, a fault state flag corresponding to the fault state includes: If the fault state is consistent with the preset calibration state, determining that the fault state flag is a first flag value; If the fault state is inconsistent with the preset calibration state, the fault state flag is determined to be a second flag value.

3. The fault management method according to claim 2, characterized in that: The preset calibration data includes a plurality of fault types and a preset value of a fault status flag corresponding to each fault type, and the generating of a fault management strategy based on the fault status flag, the fault type of the vehicle and the preset calibration data includes: If the fault status flag is consistent with a preset value of the fault status flag corresponding to the fault type of the vehicle, one or more of restricted function management, safe mode management, and suppressed function management are performed based on the fault type of the vehicle.

4. The fault management method according to claim 3, characterized in that: The performing one or more of restricted function management, safe mode management, and inhibited function management based on the fault type of the vehicle includes: If the fault type is a limited function fault, executing the limited function management; If the fault type is a safety mode fault, executing the safety mode management; If the fault type is a suppression function fault, the suppression function management is performed.

5. The fault management method according to claim 2, characterized in that: The fault management method further includes: A fault status table is generated based on the multiple fault types; in the fault status table, each fault type corresponds to a fault status flag.

6. The fault management method according to any one of claims 2 to 5, characterized in that: The preset calibration data includes a plurality of limited function fault types and limited function management strategies corresponding to different fault status flags under each limited function fault type, and the fault management strategy is generated based on the fault status flag, the fault type of the vehicle and the preset calibration data, including: If the fault type is a limiting function fault and the fault status flag is a first flag value, the first type of limiting function management is performed; if the fault type is a limiting function fault and the fault status flag is a second flag value, the second type of limiting function management is performed.

7. The fault management method according to any one of claims 2 to 5, characterized in that: The preset calibration data includes a plurality of safety mode fault types and safety mode management strategies corresponding to different fault status flags under each safety mode fault type, and the fault management strategy is generated based on the fault status flag, the fault type of the vehicle and the preset calibration data, including: If the fault type is a safety mode fault and the fault status flag is a first flag value, the first type of safety mode management is performed; if the fault type is a safety mode fault and the fault status flag is a second flag value, the second type of safety mode management is performed.

8. The fault management method according to any one of claims 2 to 5, characterized in that: The preset calibration data includes a plurality of suppression function fault types and suppression function management strategies corresponding to different fault status flags under each suppression function fault type, and the generating of the fault management strategy based on the fault status flag, the fault type of the vehicle and the preset calibration data includes: If the fault type is a suppression function fault and the fault status flag is a first flag value, the first type of suppression function management is performed; if the fault type is a suppression function fault and the fault status flag is a second flag value, the second type of suppression function management is performed.

9. A vehicle, characterized in that: include: A state acquisition module, used to acquire the fault type of the vehicle and the fault state corresponding to the fault type; A flag determination module, used to determine a fault state flag corresponding to the fault state based on the fault state and a preset calibration state rule; A strategy generation module is used to generate a fault management strategy based on the fault status flag, the fault type of the vehicle and preset calibration data.

10. An electronic device, characterized in that: The electronic device comprises a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the fault management method according to any one of claims 1 to 8.

11. A storage medium, characterized in that: The method comprises computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the fault management method according to any one of claims 1 to 8.

Images