Fault indicator light control method and apparatus, electronic device, and readable storage medium

Abstract

The application discloses a kind of fault indicator light control method, device, electronic equipment and readable storage medium, involve automobile fault diagnosis technical field.The fault indicator light control method includes the following steps: obtaining the engine fault level of automobile, low-voltage power-on state, engine state, fault state, fault duration and the high-voltage power-on state of power battery;According to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration and the high-voltage power-on state, determine target display state parameter;According to the target display state parameter control fault indicator light display state, the present application reduces the misjudgment rate of engine fault state to user.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of malfunction indicator lamp control, and in particular to a malfunction indicator lamp control method and device, an electronic device and a readable storage medium. BACKGROUND

[0002] The malfunction indicator (MI) lamp in the on-board diagnostic system is used to indicate the engine fault state. At present, the engine controller on the automobile activates different MI modes according to preset display state parameters in different fault states, power-on states, engine start or stop states, and sends corresponding MI lamp state messages to the instrument to control the display state of the malfunction indicator lamp through the instrument.

[0003] However, the above method only considers the case where only a fuel engine is used as the driving power. When a user uses a hybrid vehicle for pure electric driving, the engine will not start or the vehicle will be powered by the power battery for a long time in the camping mode and the like, i.e., the automobile is in a high-voltage power-on state and the engine is in a stop state. Even if the engine has no fault or only a C-class fault that does not affect the main performance, the MI lamp will still flash 1 or 2 times every 5 seconds after self-checking, which will cause some users to misjudge the engine fault state when the automobile is in a pure electric driving or pure electric power supply scene, and reduce the driving and vehicle experience of the user. SUMMARY

[0004] The main purpose of the present application is to provide a malfunction indicator lamp control method, which aims to solve the technical problem of misjudgment of the engine fault state by the user caused by the existing display state parameters.

[0005] To achieve the above purpose, in a first aspect, the present application provides a malfunction indicator lamp control method, which comprises:

[0006] obtaining the engine fault level, low-voltage power-on state, engine state, fault state, fault duration of the automobile, and high-voltage power-on state of the power battery;

[0007] determining a target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state;

[0008] controlling the display state of the malfunction indicator lamp according to the target display state parameter.

[0009] According to the first aspect, the step of determining a target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state comprises:

[0010] If the engine fault level of the automobile is no fault or the first fault level, the low-voltage power-on state is the power-on state, the engine state is the stop state, the fault state is in fault, and the high-voltage power-on state is in the high-voltage power-on state, the target display state parameter is off.

[0011] According to the first aspect, the automobile comprises an engine controller and a vehicle controller, the steps of acquiring the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration of the automobile, and the high-voltage power-on state of the power battery comprise:

[0012] acquiring the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration by the engine controller;

[0013] acquiring the high-voltage power-on state by the vehicle controller.

[0014] According to the first aspect, or any one of the implementation manners of the first aspect, the step of determining the target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state comprises:

[0015] sending the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration to the vehicle controller by the engine controller;

[0016] querying in a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state by the vehicle controller to obtain the target display state parameter.

[0017] According to the first aspect, or any one of the implementation manners of the first aspect, the step of determining the display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state comprises:

[0018] querying in a second preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration by the engine controller to obtain a second display state parameter;

[0019] sending the engine fault level, the low-voltage power-on state, the fault state, and the fault duration to the vehicle controller by the engine controller;

[0020] determining, by the vehicle controller, whether the vehicle is in a high-voltage power-on state and whether the engine has been started in the current driving cycle;

[0021] If the vehicle is not in the high-voltage power-on state or the engine has been started in the current driving cycle, the second display state parameter is set as the target display state parameter.

[0022] According to the first aspect, or any one of the implementation forms of the first aspect, after the step of determining, by the vehicle controller, whether the vehicle is in a high-voltage power-on state and whether the engine has been started in the current driving cycle, the method further comprises:

[0023] If the vehicle is in the high-voltage power-on state and the engine has not been started in the current driving cycle, the target display state parameter is obtained by the vehicle controller according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state in a first preset mapping table.

[0024] According to the first aspect, or any one of the implementation forms of the first aspect, the step of determining the display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state comprises:

[0025] The high-voltage power-on state is transmitted to the engine controller by the vehicle controller.

[0026] The target display state parameter is obtained by the engine controller according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state in a first preset mapping table.

[0027] Secondly, the present application provides a fault indicator light control device, which comprises:

[0028] A parameter acquisition module is configured to acquire an engine fault level, a low-voltage power-on state, an engine state, a fault state, a fault duration, and a high-voltage power-on state of a power battery of a vehicle.

[0029] A strategy determination module is configured to determine a target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state.

[0030] A display control module is configured to control a display state of a fault indicator light according to the target display state parameter.

[0031] According to a second aspect, the strategy determining module is further configured to:

[0032] If the engine failure level of the automobile is no failure or a first failure level, the low-voltage power-on state is the power-on state, the engine state is the stop state, the failure state is in failure, and the automobile is in a high-voltage power-on state, the target display state parameter is off.

[0033] According to the second aspect, the automobile comprises an engine controller and a vehicle controller, and the parameter obtaining module is further configured to:

[0034] obtain the engine failure level, the low-voltage power-on state, the engine state, the failure state, and the failure duration through the engine controller;

[0035] obtain the high-voltage power-on state through the vehicle controller.

[0036] According to the second aspect, or any one of the implementation forms of the second aspect, the strategy determining module is further configured to:

[0037] send the engine failure level, the low-voltage power-on state, the engine state, the failure state, and the failure duration to the vehicle controller through the engine controller;

[0038] obtain the target display state parameter through the vehicle controller according to the engine failure level, the low-voltage power-on state, the engine state, the failure state, the failure duration, and the high-voltage power-on state in a first preset mapping table.

[0039] According to the second aspect, or any one of the implementation forms of the second aspect, the strategy determining module is further configured to:

[0040] obtain a second display state parameter through the engine controller according to the engine failure level, the low-voltage power-on state, the engine state, the failure state, and the failure duration in a second preset mapping table;

[0041] send the engine failure level, the low-voltage power-on state, the failure state, and the failure duration to the vehicle controller through the engine controller;

[0042] determine whether the automobile is in a high-voltage power-on state and whether the engine has been started in the current driving cycle through the vehicle controller;

[0043] if the automobile is not in a high-voltage power-on state or the engine has been started in the current driving cycle, set the second display state parameter as the target display state parameter.

[0044] According to a second aspect, or any possible implementation mode of the second aspect, the strategy determining module is further configured to:

[0045] If the automobile is in the high-voltage power-on state and the engine has not been started in the current driving cycle, the target display state parameter is obtained by the vehicle controller querying a first preset mapping table according to the engine fault level, the low-voltage power-on state, the fault state, the fault duration, and the high-voltage power-on state.

[0046] According to a second aspect, or any possible implementation mode of the second aspect, the strategy determining module is further configured to:

[0047] The high-voltage power-on state is transmitted to the engine controller by the vehicle controller.

[0048] The target display state parameter is obtained by the engine controller querying a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state.

[0049] In a third aspect, the present application provides a fault indicator lamp control device, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the computer program is configured to implement the steps of the fault indicator lamp control method.

[0050] The third aspect and any possible implementation mode of the third aspect correspond to the first aspect and any possible implementation mode of the first aspect respectively. The technical effects of the third aspect and any possible implementation mode of the third aspect correspond to the technical effects of the first aspect and any possible implementation mode of the first aspect, which will not be described here.

[0051] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the processor executes the fault indicator lamp control method according to the first aspect or any possible implementation mode of the first aspect.

[0052] The fourth aspect and any possible implementation mode of the fourth aspect correspond to the first aspect and any possible implementation mode of the first aspect respectively. The technical effects of the fourth aspect and any possible implementation mode of the fourth aspect correspond to the technical effects of the first aspect and any possible implementation mode of the first aspect, which will not be described here.

[0053] In a fifth aspect, an embodiment of the present application provides a computer program, which comprises instructions for executing the fault indicator light control method in the first aspect and any possible implementation manner of the first aspect.

[0054] The fifth aspect and any possible implementation manner of the fifth aspect correspond to the first aspect and any possible implementation manner of the first aspect respectively. For details, refer to the technical effects of the first aspect and any possible implementation manner of the first aspect, which will not be repeated here.

[0055] The present application provides a fault indicator light control method, device, equipment and readable storage medium, by acquiring the engine fault level, low voltage power-on state, engine state, fault state, fault duration of the automobile and high voltage power-on state of the power battery, then determining the target display state parameter according to the engine fault level, low voltage power-on state, engine state, fault state, fault duration and high voltage power-on state, and then controlling the display state of the fault indicator light according to the target display state parameter. Compared with the prior art, the technical scheme of the present application overcomes the technical defects that the prior art only considers the fuel engine as the driving power and does not consider the high voltage power-on state, adds the high voltage power-on state of the power battery as a parameter for determining the target display state parameter, can distinguish between the use scenarios of engine shutdown and high voltage power-on state and the use scenarios of engine shutdown and high voltage non-power-on state in the use process of the hybrid vehicle, avoids the same MI light flashing state of the user in the high voltage power-on state of pure electric driving or pure electric power supply as the use scenarios of engine shutdown and high voltage non-power-on state, thereby causing the user to misjudge that the engine has a higher fault level, reduces the misjudgment rate of the user to the engine fault state, and improves the driving and vehicle experience of the user. BRIEF DESCRIPTION OF DRAWINGS

[0056] Figure 1 It is a flowchart of the first embodiment of the fault indicator light control method of the present application;

[0057] Figure 2 It is a connection diagram of the components of the automobile involved in the embodiment of the present application;

[0058] Figure 3 It is a flowchart of step S200, steps S211 to S212, steps S221 to S225 and steps S231 to S232 in the embodiment of the present application;

[0059] Figure 4 It is a structural diagram of the fault indicator light control device of the present application;

[0060] Figure 5 Figure 1 is a schematic diagram of a device structure of a hardware operating environment involved in an embodiment of the present application.

[0061] The implementation, functional features and advantages of the present application will be further described with reference to the embodiments in conjunction with the accompanying drawings. DETAILED DESCRIPTION

[0062] The technical solutions in the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.

[0063] The term "and / or" in the present application is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone.

[0064] The terms "first" and "second" and the like in the specification and claims of the embodiments of the present application are used to distinguish different objects, and are not used to describe the specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, and are not used to describe the specific order of the target objects.

[0065] In the embodiments of the present application, the words such as "exemplary" or "for example" are used to mean an example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words such as "exemplary" or "for example" are intended to present the relevant concept in a specific manner.

[0066] It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0067] The fault indicator control method of the present application will be described below in conjunction with some prior art:

[0068] The fault indicator MI in the vehicle-mounted diagnosis system currently provided in the vehicle is usually used to indicate the engine fault state. The engine controller (EMS, Engine Management System) on the current market vehicle will activate different MI modes according to the preset display state parameters in different fault states, power-on states, engine start or stop states, and send the corresponding MI lamp state message to the instrument to control the display state of the fault indicator lamp through the instrument.

[0069] However, the display state parameter of the prior art only considers the case where the engine is the only driving force, specifically including the use scenario of the engine stop state when the low-voltage is powered on (the key is powered on) and the use scenario of the engine running state when the low-voltage is powered on, and when the user uses the hybrid vehicle for pure electric driving and the engine is not started or in the camping mode and the like, the vehicle is powered by the power battery for a long time, that is, in the high-voltage powered-on state and the engine is in the stop state, even if the engine has no fault or only a C-class fault that does not affect the main performance, the MI lamp will still flash 1 time or 2 times every 5 seconds according to the display state parameter of the scenario of the engine stop state when the low-voltage is powered on (the key is powered on) after self-checking, but in this case the engine is not started and will not affect this trip, but the flashing MI lamp will attract the user's attention, and even affect the driving safety. In the prior art, the MI lamp will not flash if the engine has no fault or only a C-class fault that does not affect the main performance after self-checking when the engine is running, and will only flash if a more serious engine fault occurs, so the flashing of the MI lamp in the pure electric driving state will cause some users to associate the engine with a more serious fault when they are in the driving state, resulting in a user misjudgment of the engine fault state, unnecessary panic during driving, and a reduction in the user's driving experience.

[0070] The application solves the problem that some users will panic due to misjudgment of the engine fault state under the display state parameter of the prior art when the hybrid vehicle is in the pure electric driving, camping mode and the like, and the engine is not started for a long time in the high-voltage state.

[0071] In an embodiment of the application, the engine fault level, low-voltage powered-on state, engine state, fault state, fault duration and high-voltage powered-on state of the power battery of the vehicle are obtained, and then the target display state parameter is determined according to the engine fault level, low-voltage powered-on state, engine state, fault state, fault duration and high-voltage powered-on state, and the display state of the fault indicator lamp is controlled according to the target display state parameter. Compared with the prior art, the technical solution of the embodiment of the application overcomes the technical defects of the prior art that only considers the engine as the driving force and does not consider the high-voltage powered-on state, adds the high-voltage powered-on state as a parameter for determining the target display state parameter, can distinguish between the use scenario of the engine stop and high-voltage powered-on state and the use scenario of the engine stop and high-voltage unpowered state during the use of the hybrid vehicle, avoids the same MI lamp flashing state of the use scenario of the engine stop and high-voltage unpowered state in the pure electric driving mode of the high-voltage powered-on state, which leads to the user misjudging that the engine has a fault of a higher level, reduces the misjudgment rate of the user for the engine fault state, and improves the user's driving experience of the hybrid vehicle.

[0072] Referring to Figure 1 , Figure 1 is a flowchart of a first embodiment of the fault indicator light control method of the present application. It should be noted that although a logical order is shown in the flowchart, in some cases, the steps shown or described can be performed in an order different from that shown here.

[0073] The first embodiment of the present application provides a fault indicator light control method, which comprises the following steps:

[0074] Step S100, obtaining the engine fault level, low-voltage power-on state, engine state, fault state, fault duration of the automobile, and high-voltage power-on state of the power battery;

[0075] In this embodiment, it should be noted that the engine fault level includes no fault, class C fault, class B fault, or class A fault; the low-voltage power-on state includes low-voltage power-on state or low-voltage power-off state, wherein when the low-voltage power-on state is power-off (i.e. the automobile is not started by the key), the vehicle's on-board diagnostic system does not work, and the MI light is not lit or flashed; the engine state includes running state or stop state; the fault state includes fault or normal, specifically, if the current engine fault level is class C fault or above, the fault state is fault, if the current engine fault level is no fault, and the effective OBD (On-Board Diagnostics) driving cycle number of the automobile after the last fault has reached the preset cycle number, for example, 10 times, it can be determined that the fault state is normal, wherein the preset cycle number can be set according to specific needs, which is not limited here; similarly, if the current engine fault level is no fault, and the effective OBD driving cycle number of the automobile after the last fault has not reached the preset cycle number, the fault state is still fault, and the display of the MI light is still controlled according to the display state parameter corresponding to the fault level when the last fault occurred, which can exclude the misjudgment that the fault state is normal due to the intermittent fault of the automobile engine; the fault duration is the duration corresponding to the detected engine fault level; the high-voltage power-on state includes high-voltage power-on state or high-voltage power-off state.

[0076] As an example, after the target vehicle is started by the key, whether the engine is started or not, the engine is self-checked by the on-board diagnostic system, and the engine fault level, low-voltage power-on state, engine state, fault state, fault duration, and high-voltage power-on state of the power battery of the automobile are obtained through the engine controller in the automobile.

[0077] As an example, the B-class faults include B1-class faults and B2-class faults, and the engine fault levels can be classified as follows:

[0078] A-class faults: if the fault causes emissions to exceed the preset OBD limit value, the fault is classified as an A-class fault;

[0079] B1-class faults: if the fault causes emissions to possibly exceed the OBD limit value, but the impact on emissions is uncertain, so the actual emissions can be higher or lower than the OBD limit value;

[0080] B2-class faults: faults that can affect emissions but will not exceed the OBD limit value;

[0081] C-class faults: faults that can affect emissions but will not exceed the standard limit value.

[0082] In the step S100, the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state of the power battery are obtained, including:

[0083] In the step S110, the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration are obtained by the engine controller;

[0084] In the step S120, the high-voltage power-on state is obtained by the vehicle controller.

[0085] In the embodiments, it should be noted that, referring to Figure 2 , the automobile at least includes an engine controller 1 and a vehicle controller 2 (VCU, Vehicle control unit), an instrument 3, and a fault indicator 4 controlled by the instrument, the engine controller 1 can be used to obtain the self-checking result of the engine diagnosed by the on-board diagnostic system, which specifically includes engine fault level, low-voltage power-on state, engine state, fault state, and fault duration, etc. The high-voltage power-on state is related to the power supply state of the power battery 5 of the automobile, which needs to be detected and obtained in combination with the vehicle controller 2, to determine whether the automobile is in a high-voltage power state in a pure electric driving mode or a camping mode through the high-voltage power-on state, to distinguish between a high-voltage non-power-on parking scene in a low-voltage power-on state and an engine stop state or a high-voltage power-on driving scene or camping power scene in a low-voltage power-on state and an engine stop state, and to develop different display state parameters and control the display state of the fault indicator 4 through the instrument 3 according to the display state parameters to avoid user confusion and misjudgment of the engine fault level.

[0086] Step S200, determining a target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state;

[0087] In the embodiment, it can be understood that in the process of determining the target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state, a preset mapping table containing the correspondence between each parameter and the MI display state parameter can be used. In the preset mapping table, three use scenarios can be set: a use scenario of low-voltage power-on, engine stop state, and high-voltage not powered on, a use scenario of low-voltage power-on, engine running state, and high-voltage not powered on, and a use scenario of low-voltage power-on and high-voltage power-on. The use scenario of low-voltage power-on and high-voltage power-on includes the case of low-voltage power-on, engine stop state, and high-voltage power-on, and the use scenario of low-voltage power-on, engine running state, and high-voltage power-on. Both of the two use scenarios include the high-voltage power-on state, so they can be combined into one use scenario. However, the prior art only includes two use scenarios: a use scenario of low-voltage power-on and engine stop state, and a use scenario of low-voltage power-on and engine running state. It can be understood that the use scenario of low-voltage power-on, engine stop state, and high-voltage not powered on and the use scenario of low-voltage power-on, engine stop state, and high-voltage power-on are both classified as the first use scenario in the prior art, and the same display state parameter is used. However, in fact, in the hybrid vehicle driving situation, the car may be in a parked state and a running state in the two use scenarios, respectively. The use scenario of low-voltage power-on, engine stop state, and high-voltage power-on may be a pure electric driving mode. In this case, the prior art performs MI lamp flashing when the engine self-checking is completed and a C-class fault that does not affect driving is obtained. However, the engine is not started in the pure electric driving mode, and it will not affect the current driving state, but it will still cause the user to see the MI lamp flashing when driving in the pure electric driving mode, which may lead to the user misjudging the engine fault state, affecting the user's mood and driving experience. In the embodiment, the use scenario of low-voltage power-on, engine stop state, and high-voltage not powered on is distinguished from the use scenario of low-voltage power-on and high-voltage power-on by the three preset use scenarios, and different display state parameters are formulated, so as to avoid the user misjudging the engine fault state when driving in the pure electric driving mode.

[0088] For example, when the vehicle is in a low-voltage power-on, engine-off, and high-voltage-off usage scenario, if the engine fault level is detected as no fault or a Class C fault during engine self-check, the target fault indicator light will flash once or twice every 5 seconds. However, when the vehicle is in a low-voltage power-on, engine-off, and high-voltage-on usage scenario, if the engine fault level is detected as no fault or a Class C fault during engine self-check, the target fault indicator light will be off, i.e., it will not flash, so as not to cause unnecessary impact on users who are driving in pure electric mode.

[0089] The step S200, which involves determining the target display status parameters based on the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state, includes:

[0090] If the engine fault level of the car is no fault or first fault level, the low voltage power-on state is power-on state, the engine status is stopped state, and the fault status is faulty and under high voltage power-on state, then the target display status parameter is off.

[0091] In this embodiment, it should be noted that the above embodiment provides a method for determining the target display status parameters when the vehicle's engine fault level is no fault or first fault level, the low-voltage power-on state is powered on, the engine state is stopped, and the fault state is faulty and under high-voltage power-on state. Compared with the prior art, which does not distinguish whether it is under high-voltage power-on state, when the vehicle's engine fault level is no fault or Class C fault, the low-voltage power-on state is powered on, the engine state is stopped, and the fault state is faulty, the MI light displays the status parameters by flashing once or twice every 5 seconds, which can cause psychological pressure on the user. Here, the first fault level is Class C fault. This embodiment, by specifically subdividing the high-voltage power-on state, ensures that when the user encounters an engine fault level of no fault or first fault level in the self-check result during pure electric driving, which does not affect the main performance and does not affect the driving safety, the user will not see the MI light flashing, thus avoiding unnecessary panic.

[0092] Among them, reference Figure 3 The step S200, which involves determining the target display status parameters based on the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state, includes:

[0093] Step S211, sending the engine fault level, the low-voltage power-on state, the engine state, the fault state and the fault duration to the vehicle controller through the engine controller;

[0094] Step S212, obtaining a target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration and the high-voltage power-on state in a first preset mapping table through the vehicle controller.

[0095] In the embodiment, it should be noted that the embodiment provides a control method for realizing the MI display strategy corresponding to the first preset mapping table. The engine controller and the vehicle controller applied in the embodiment are obtained by modifying the vehicle hardware based on the fault indicator light control method in the prior art. The vehicle hardware includes the engine controller, the vehicle controller and the instrument, and is not limited herein. It should also be noted that in the prior art, the engine controller is mainly used to obtain the engine fault level, the low-voltage power-on state, the engine state, the fault state and the fault duration, and to activate the corresponding MI mode according to the above parameters and the built-in second preset mapping table, to determine the display state parameter corresponding to the MI mode, to send the engine fault level, the low-voltage power-on state, the engine state, the fault state and the fault duration and the MI lamp state message corresponding to the display state parameter to the vehicle controller, and to transmit the MI lamp state message to the instrument through the vehicle controller, so as to control the display state of the MI lamp through the instrument. The embodiment mainly modifies the vehicle controller in the prior art, so that the vehicle controller can activate the corresponding MI mode in the built-in first preset mapping table according to the parameters sent by the engine controller and the high-voltage power-on state obtained by itself, and determine the target display state parameter corresponding to the MI mode, and then send the MI lamp state message corresponding to the target display state parameter to the instrument, so that the instrument controls the display state of the MI lamp according to the MI lamp state message. In the implementation process of the embodiment, the engine controller is not modified, so it still determines the corresponding display state parameter according to the built-in second preset mapping table and sends the corresponding MI lamp state message to the vehicle controller, but it does not need to process the MI lamp state message or control the display state of the MI lamp according to the MI lamp state message.

[0096] As an example, four MI modes are included in the first preset mapping table, and correspond to four activated MI conditions, respectively corresponding to the engine fault level being no fault, class C fault, class B fault and class B fault count <200h, class A fault or class B fault count ≥200h, wherein the fault count is the fault duration, and different vehicle states correspond to different display state parameters in the four MI modes. The various vehicle states include: key power-on (i.e. low voltage power-on) and engine stop state and high voltage not powered on, key power-on and high voltage not powered on and engine running state, key power-on and high voltage powered on, etc. Among them, the latter two vehicle states correspond to the same display state parameter in the same MI mode. In addition, it should be noted that if the current engine fault level is no fault, and the number of valid OBD driving cycles since the last fault does not reach the preset cycle number, the fault state is still in fault, and the display of the MI lamp still needs to be controlled according to the display state parameter corresponding to the fault level corresponding to the last fault. In addition, it should be noted that when multiple MI modes are triggered simultaneously, mode 4 > mode 3 > mode 2 > mode 1, and only one MI activation mode exists at the same time. As an example, the first preset mapping table can refer to Table 1 below:

[0097] Table 1 First preset mapping table

[0098]

[0099] As an example, the various possible situations involved in the MI display strategy corresponding to the first preset mapping table and the corresponding display state parameters are as follows:

[0100] 1) If there is no fault, MI activation mode 1, at this time, if the low voltage is powered on, the engine is stopped, and the high voltage is not powered on, the MI lamp flashes once every 5s after self-checking;

[0101] 2) If there is no fault, MI activation mode 1, at this time, if the low voltage is powered on, the engine is running, and the high voltage is not powered on, the MI lamp is extinguished;

[0102] 3) If there is no fault, MI activation mode 1, at this time, if the low voltage is powered on, and the high voltage is powered on, the MI lamp is extinguished;

[0103] 4) If the engine fault level is class C fault, MI activation mode 2, at this time, if the low voltage is powered on, the engine is stopped, and the high voltage is not powered on, the MI lamp flashes twice every 5s after self-checking.

[0104] 5) If the engine fault level is class C fault, MI activation mode 2, at this time, if the low voltage is powered on, the engine is running, and the high voltage is not powered on, the MI lamp is extinguished.

[0105] 6) If the engine fault level is Class C, MI activation mode 2 will be activated. At this time, if both low voltage and high voltage are powered on, the MI light will turn off.

[0106] 7) If the engine fault level is B-class fault and the B1-class fault count is ≤200h, MI activation mode 3 is activated. At this time, if the low voltage is powered on, the engine is stopped and the high voltage is not powered on, the MI light will flash 3 times every 5 seconds after self-test.

[0107] 8) If the engine fault level is B-class fault and the B1-class fault count is ≤200h, MI activation mode 3 is activated. At this time, if the low voltage is powered on, the engine is running, and the high voltage is not powered on, the MI light will stay on for 15 seconds after the engine is started or the high voltage is powered on, and then turn off.

[0108] 9) If the engine fault level is B-class fault and the B1-class fault count is ≤200h, MI activation mode 3 is activated. At this time, if both low voltage and high voltage are powered on, the MI light will remain on for 15 seconds after high voltage is powered on or the engine is started, and then turn off.

[0109] 10) If the engine fault level is Class A or the B1 fault count is >200h, MI activation mode 4 is activated. At this time, if the low voltage is powered on, the engine is stopped and the high voltage is not powered on, the MI light will stay on after self-test.

[0110] 11) If the engine fault level is Class A or the B1 fault count is >200h, MI activation mode 4 is activated. At this time, if the low voltage is powered on, the engine is running and the high voltage is not powered on, the MI light will remain on after the engine is started or the high voltage is powered on.

[0111] 12) If the engine fault level is Class A or the B1 fault count is >200h, MI activation mode 4 is activated. At this time, if both low voltage and high voltage are powered on, the MI light will remain on after high voltage is powered on or the engine is started.

[0112] Among them, reference Figure 3 The step S200, which involves determining the target display status parameters based on the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state, may further include:

[0113] Step S221: The engine controller queries a second preset mapping table based on the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration to obtain the second display status parameter.

[0114] Step S221: The engine fault level, the low voltage power-on state, the engine state, the fault state, and the fault duration are sent to the vehicle controller through the engine controller.

[0115] Step S223, determining whether the vehicle is in high-voltage power-on state and the engine is started in the current driving cycle by the vehicle controller.

[0116] Step S224, if the vehicle is not in high-voltage power-on state or the engine is started in the current driving cycle, setting the second display state parameter as the target display state parameter.

[0117] In the embodiment, it should be noted that the embodiment provides a control method for realizing the MI display strategy corresponding to the first preset mapping table. Although the second preset mapping table is applied in the above process, the MI display strategy in the prior art is included in the second preset mapping table. In the process of realizing the MI display strategy corresponding to the first preset mapping table, if the display state parameter is consistent with the second preset mapping table under certain conditions, the MI lamp display control method in the prior art can be used to reduce the difficulty of modification of the hardware device.

[0118] In addition, it should be noted that steps S221 to S224 and steps S211 to S212 are in parallel relationship, and are both an embodiment of step S200, that is, step S200 can adopt the embodiment of steps S221 to S224, or can adopt the embodiment of steps S211 to S212. The engine controller and the vehicle controller applied in the embodiment are obtained based on the modification of the vehicle hardware applied in the fault indicator lamp control method in the prior art. The embodiment mainly modifies the vehicle controller in the prior art. After the engine controller in the prior art determines the second display state parameter based on the second preset mapping table in the fault indicator lamp control method in the prior art and sends the engine fault level, the low-voltage power-on state, the engine state, the fault state and the fault duration to the vehicle controller, the vehicle controller determines whether the vehicle is in high-voltage power-on state and the engine is started in the current driving cycle. If the vehicle is not in high-voltage power-on state or the engine is started in the current driving cycle, the pure electric driving mode does not need to be considered, and the MI lamp can be controlled according to the determined second display state parameter. Compared with the previous embodiment, a pre-judgment process is added to avoid the calculation and determination of the target display state parameter by the vehicle controller every time, thereby saving the calculation amount of the vehicle controller.

[0119] Exemplarily, it is judged by the vehicle controller whether the automobile is in a high-voltage power-on state and whether the engine has started in the current driving cycle. If the automobile is not in a high-voltage power-on state, the automobile is not powered by the battery, or the engine is in a stop state, the automobile is in a parking state, or the engine is in a start state, the automobile is in a driving state powered by the engine, and the use scenarios of the engine stop and the high-voltage power-on state and the use scenarios of the engine stop and the high-voltage power-on state cannot be distinguished, and the above scenarios are confused to determine the same display state parameter. In order to save the computing power of the vehicle controller, the display state of the MI lamp can be controlled according to the display state parameter determined by the engine controller and the second preset mapping table in the prior art.

[0120] Exemplarily, the second preset mapping table includes four MI modes and corresponds to four activated MI conditions, respectively corresponding to the engine fault level being no fault, class C fault, class B fault and class B fault count <200h, class A fault or class B fault count ≥200h. The fault count is the fault duration. In the four MI modes, different automobile states correspond to different display state parameters. Various automobile states include: key power-on (i.e. low-voltage power-on) and engine stop state and key power-on and engine start state. Exemplarily, the second preset mapping table can refer to Table 2 below:

[0121] Table 2 Second preset mapping table

[0122]

[0123] Referring to Figure 3 After the step of judging by the vehicle controller whether the automobile is in a high-voltage power-on state and whether the engine has started in the current driving cycle in step S223, the method further comprises:

[0124] In step S225, if the automobile is in a high-voltage power-on state and the engine has not started in the current driving cycle, the vehicle controller queries the first preset mapping table according to the engine fault level, the low-voltage power-on state, the fault state, the fault duration and the high-voltage power-on state to obtain a target display state parameter.

[0125] It should be noted that the embodiment provides a display state parameter determination method in the case that the vehicle is in a high-voltage power-on state and the engine has not started in the current driving cycle after the step of determining whether the vehicle is in a high-voltage power-on state and whether the engine has started in the current driving cycle by the vehicle controller. After the engine controller determines the second display state parameter according to the parameters obtained by it, it is determined by the vehicle controller that the vehicle is in a high-voltage power-on state and the engine has not started in the current driving cycle, which indicates that the vehicle is in an electricity consumption state in the pure electric driving mode or the camping mode. In the current situation, the fault state of the engine will not affect the driving safety or the electricity consumption safety, and it is necessary to avoid the situation that the MI lamp flashes to cause the user or the user to misjudge the engine fault level when the engine fault level is no fault or C-class fault in the MI display strategy in the prior art. In the embodiment, the corresponding target display state parameter is queried by the first preset mapping table.

[0126] Exemplarily, in the case that the vehicle is in a high-voltage power-on state and the engine has not started in the current driving cycle, if the engine fault level is no fault or C-class fault, the low-voltage power-on state is power-on, and the fault state is fault, the target display state parameter queried in the first preset mapping table is extinguished, that is, in this case, the MI lamp does not need to be lit or flashed.

[0127] Referring to Figure 3 , the step S200 of determining the target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration and the high-voltage power-on state can further include:

[0128] Step S231, transmitting the high-voltage power-on state to the engine controller by the vehicle controller;

[0129] Step S232, querying by the engine controller in a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration and the high-voltage power-on state to obtain a target display state parameter.

[0130] It should be noted that the embodiment provides a control method for realizing the MI display strategy corresponding to the first preset mapping table, and steps S231 to S232 are in parallel relationship with steps S221 to S224 and steps S211 to S212, which are all an embodiment of step S200, that is, step S200 can adopt the embodiment of steps S231 to S232, or the embodiment of steps S221 to S224, or the embodiment of steps S211 to S212. Different from the previous two embodiments, the embodiment mainly adds a high-voltage power-on state self-defined CAN (bus) message between the vehicle controller and the engine controller in the prior art to send the high-voltage power-on state to the engine controller, and adds a built-in first preset mapping table in the engine controller. The above three embodiments have their own advantages, and the host factory or product line can choose the embodiment that meets its own needs according to the degree of controller software and hardware development, wherein the embodiment of steps S211 to S212 only involves vehicle controller software changes, and is conducive to directly managing engine system faults from the vehicle level; the embodiment of steps S221 to S224 also only involves vehicle controller software changes, and it saves the vehicle controller's computing power to a certain extent compared with the embodiment of steps S211 to S212; the embodiment of steps S231 to S232 involves vehicle controller and engine controller software modification, and requires adding a self-defined CAN message, but the software changes of the two controllers are very small, the development cycle is the shortest, and the cost is also the lowest. The embodiment provides the above three control methods for realizing the MI display strategy corresponding to the first preset mapping table, which only needs to partially modify the existing engine controller and vehicle controller on the vehicle, reduces the cost, and is more conducive to platform application.

[0131] Exemplarily, when the vehicle controller detects that the vehicle is in a high-voltage power-on state, the vehicle controller sends a CAN message including the high-voltage power-on state to the engine controller; the engine controller obtains that the current engine fault level of the engine is a C-class fault, the low-voltage power-on state is power-on, the engine state is a starting state, the fault state is in a fault, and the fault duration is 1h; and the engine controller queries the target display state parameter as off in the first preset mapping table according to the above parameters; and then the engine controller sends an MI lamp state message including the target display state parameter to the vehicle controller, and the vehicle controller transmits the MI lamp state message to the report for the report to control the display state of the MI lamp as off according to the MI lamp state message.

[0132] Step S300, controlling the display state of the fault indicator according to the target display state parameter.

[0133] In this embodiment, it can be understood that the malfunction indicator light (MI light) is installed on the instrument, that is, the display state of the malfunction indicator light is controlled by the instrument, the instrument can receive the MI light state message including the target display state parameter sent by the engine controller or the vehicle controller, and control the display state of the MI light according to the MI light state message.

[0134] As an example, the target display state parameter can include: off, flashing once every 5s, flashing twice every 5s, flashing three times every 5s, constant 15s, and constant.

[0135] In the first embodiment of the application, the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state of the power battery of the automobile are obtained, and then the target display state parameter is determined according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state, and the display state of the malfunction indicator light is controlled according to the target display state parameter. Compared with the prior art, the technical scheme of the application overcomes the technical defects of the prior art that only considers the engine as the driving power and does not consider the high-voltage power-on state, adds the high-voltage power-on state as a parameter for determining the target display state parameter, can distinguish between the use scenarios of the engine shutdown and the high-voltage power-on state and the use scenarios of the engine shutdown and the high-voltage power-off during the use of the hybrid vehicle, avoids the same MI light flashing state of the user in the pure electric driving mode of the high-voltage power-on state and the use scenarios of the engine shutdown and the high-voltage power-off, thereby causing the user to misjudge that the engine has a higher fault level, reduces the misjudgment rate of the user to the engine fault state, and improves the driving experience of the user to the hybrid vehicle.

[0136] Reference Figure 4 , Figure 4 The figure is a structural schematic diagram of the malfunction indicator light control device of the application.

[0137] The application also provides a malfunction indicator light control device, which comprises:

[0138] The parameter acquisition module 10 is configured to acquire the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state of the power battery of the automobile.

[0139] The strategy determination module 20 is configured to determine the target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state.

[0140] The display control module 30 is configured to control the display state of the fault indicator according to the target display state parameter.

[0141] Optionally, the policy determination module 20 is further configured to:

[0142] If the engine fault level of the automobile is no fault or a first fault level, the low-voltage power-on state is the power-on state, the engine state is the stop state, the fault state is in fault, and the automobile is in the high-voltage power-on state, the target display state parameter is off.

[0143] Optionally, the automobile comprises an engine controller and a vehicle controller, and the parameter acquisition module 10 is further configured to:

[0144] acquire the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration through the engine controller;

[0145] acquire the high-voltage power-on state through the vehicle controller.

[0146] Optionally, the policy determination module 30 is further configured to:

[0147] send the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration to the vehicle controller through the engine controller;

[0148] query, through the vehicle controller, the target display state parameter in a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state.

[0149] Optionally, the policy determination module 30 is further configured to:

[0150] query, through the engine controller, a second display state parameter in a second preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, and the fault duration;

[0151] send the engine fault level, the low-voltage power-on state, the fault state, and the fault duration to the vehicle controller through the engine controller;

[0152] determine, through the vehicle controller, whether the automobile is in the high-voltage power-on state and whether the engine has been started in the current driving cycle;

[0153] if the automobile is not in the high-voltage power-on state or the engine has been started in the current driving cycle, set the second display state parameter as the target display state parameter.

[0154] Optionally, the policy determination module 30 is further configured to:

[0155] If the automobile is in the high-voltage power-on state and the engine has not been started in the current driving cycle, the target display state parameter is obtained by the vehicle controller querying a first preset mapping table according to the engine fault level, the low-voltage power-on state, the fault state, the fault duration and the high-voltage power-on state.

[0156] Optionally, the policy determination module 30 is further configured to:

[0157] The high-voltage power-on state is transmitted to the engine controller by the vehicle controller.

[0158] The target display state parameter is obtained by the engine controller querying a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration and the high-voltage power-on state.

[0159] As shown in Figure 5 FIG. 1 is a device structure schematic diagram of a hardware running environment involved in an embodiment of the present application. Figure 5

[0160] Specifically, the fault indicator light control device can be a VCU (Vehicle Control Unit, vehicle controller), a PC (Personal Computer, personal computer), a tablet computer, a portable computer or a server, etc.

[0161] As shown in Figure 5 ​As shown, the fault indicator light control device can include a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to realize the connection communication between these components. The user interface 1003 can include a display, an input unit such as a keyboard, and can also include a standard wired interface, a wireless interface. The network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 can be a high-speed random access memory (RAM) memory, or a stable non-volatile memory (NVM) such as a disk memory. The memory 1005 can also be a storage device independent of the aforementioned processor 1001.

[0162] Those skilled in the art can understand that Figure 5 The device structure shown in the foregoing embodiments does not constitute a limitation on the fault indicator light control device, and can include more or fewer components than shown, or combine certain components, or different component arrangements.

[0163] As Figure 5 As shown, the memory 1005, as a computer storage medium, can include an operating system, a network communication module, a user interface module, and a fault indicator light control application.

[0164] In Figure 5 In the device shown, the network interface 1004 is mainly used to connect to a background server and communicate data with the background server; the user interface 1003 is mainly used to connect to a client and communicate data with the client; and the processor 1001 can be used to call the fault indicator light control program stored in the memory 1005 to realize the operations in the fault indicator light control method provided in the foregoing embodiments.

[0165] In addition, the embodiment of the present application also proposes a vehicle, which includes the fault indicator light control device described above. Of course, it can be understood that the vehicle also includes an energy storage device, a driving device, and other devices that ensure the normal operation of the vehicle.

[0166] In addition, the embodiment of the present application also proposes a computer storage medium, which stores a computer program. When the processor executes the computer program, the operations in the fault indicator light control method provided in the foregoing embodiments are realized, and the specific steps will not be described here.

[0167] It should be noted that, in the present document, the terms such as first and second, etc. are used only to distinguish one entity / operation / element from another entity / operation / element, and do not necessarily require or imply any such actual relationship or order between such entities / operations / elements; the terms "comprising", "containing" or any other variant thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or system including a list of elements does not necessarily include only those elements recited, but can include other elements not expressly listed or inherent to such process, method, article or system. Without more limitations, an element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or system including the element.

[0168] For the device embodiments, since they are basically similar to the method embodiments, they are described more simply, and the relevant parts are referred to the part of the description of the method embodiments. The above-described device embodiments are only illustrative, and the units described as separate components can or can not be physically separated. Part or all of the modules can be selected according to actual needs to achieve the purpose of the present application. Those skilled in the art can understand and implement it without creative labor.

[0169] The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0170] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of software and the necessary general hardware platform, of course, they can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk) as described above, and includes a number of instructions for making a terminal device (which can be a mobile phone, a computer, a server, a vehicle, or a network device, etc.) execute the methods described in various embodiments of the present application.

[0171] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent flow transformation made by using the content of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method of controlling a malfunction indicator light, characterized by, The fault indicator control method comprises: obtaining the engine fault level, low-voltage power-on state, engine state, fault state, fault duration of the automobile and high-voltage power-on state of the power battery; determining the target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state; controlling the display state of the fault indicator according to the target display state parameter; wherein the step of determining the target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state comprises: if the engine fault level of the automobile is no fault or first fault level, the low-voltage power-on state is power-on state, the engine state is shutdown state, the fault state is in fault and the automobile is in high-voltage power-on state, the target display state parameter is off.

2. The method of claim 1, wherein the fault indicator light is turned on when the engine is in the off state and the engine is not in the off state. The automobile comprises an engine controller and a vehicle controller, and the step of obtaining the engine fault level, low-voltage power-on state, engine state, fault state, fault duration of the automobile and high-voltage power-on state of the power battery comprises: obtaining the engine fault level, low-voltage power-on state, engine state, fault state and fault duration through the engine controller; obtaining the high-voltage power-on state through the vehicle controller.

3. The method of claim 2, wherein the fault indicator light is turned on when the fault indicator light is turned off. The step of determining the target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state comprises: sending the engine fault level, low-voltage power-on state, engine state, fault state and fault duration to the vehicle controller through the engine controller; obtaining the target display state parameter by querying in a first preset mapping table according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state through the vehicle controller.

4. The method of claim 2, wherein the fault indicator light is turned on when the fault indicator light is turned off. The step of determining the target display state parameter according to the engine fault level, low-voltage power-on state, engine state, fault state, fault duration and high-voltage power-on state comprises: obtaining a second display state parameter by querying in a second preset mapping table according to the engine fault level, low-voltage power-on state, engine state, fault state and fault duration through the engine controller; sending the engine fault level, low-voltage power-on state, fault state and fault duration to the vehicle controller through the engine controller; determining whether the automobile is in high-voltage power-on state and whether the engine has been started in the current driving cycle through the vehicle controller; if the automobile is not in high-voltage power-on state or the engine has been started in the current driving cycle, setting the second display state parameter as the target display state parameter.

5. The method of claim 4, wherein the fault indicator light is turned on when the fault indicator light is turned off. After the step of determining whether the automobile is in a high-voltage power-on state and whether the engine has started in the current driving cycle by the vehicle controller, the method further comprises: If the automobile is in a high-voltage power-on state and the engine has not started in the current driving cycle, the target display state parameter is obtained by querying a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state by the vehicle controller.

6. The fault indicator light control method as described in claim 2, characterized in that, The step of determining the display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state comprises: The high-voltage power-on state is transmitted to the engine controller by the vehicle controller; The target display state parameter is obtained by querying a first preset mapping table according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state by the engine controller.

7. A malfunction indicator light control device characterized by comprising: The fault indicator light control device comprises: A parameter acquisition module is configured to acquire an engine fault level, a low-voltage power-on state, an engine state, a fault state, a fault duration, and a high-voltage power-on state of a power battery of an automobile. A strategy determination module is configured to determine a target display state parameter according to the engine fault level, the low-voltage power-on state, the engine state, the fault state, the fault duration, and the high-voltage power-on state. A display control module is configured to control a display state of a fault indicator light according to the target display state parameter. The strategy determination module is further configured to set the target display state parameter as off if the engine fault level of the automobile is no fault or a first fault level, the low-voltage power-on state is a power-on state, the engine state is a shutdown state, the fault state is in a fault, and the automobile is in a high-voltage power-on state.

8. An electronic device, comprising: The electronic device comprises: At least one processor; A memory connected to the at least one processor in communication; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the steps of the fault indicator light control method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program for implementing a fault indicator light control method, and the program is executed by a processor to implement the steps of the fault indicator light control method according to any one of claims 1 to 6.

Images