Windshield wiper control method and system, vehicle and storage medium

Abstract

The invention provides a windshield wiper control method and system, a vehicle and a storage medium, and belongs to the technical field of automobiles. The method comprises the steps that when a windshield wiper is in an open state, if a closing request triggered by a fault is received, a safety mode is started; in the safety mode, if a windshield wiper control request is received, the intention of a driver is determined; if the windshield wiper control request is a closing request, the intention of the driver is the intention of closing the windshield wiper, the safety mode is quitted, and the windshield wiper is closed based on the windshield wiper control request. In this way, in the safe mode, whether the windshield wiper is turned off or not is controlled based on the intention of the driver by detecting the intention of the driver, it is guaranteed that the windshield wiper cannot be turned off unexpectedly in the driving process, meanwhile, when the driver intends to turn off the windshield wiper, the situation that the windshield wiper cannot be turned off due to the safe mode and other reasons is avoided, and the driving experience is optimized.

Description

Technical Field

[0001] The present application belongs to the field of automobile technology, and in particular, relates to a wiper control method, system, vehicle and storage medium. Background Art

[0002] The vehicle wiper control function in the body controller (Central Electronic Module, CEM) controls the working state of the wiper by controlling the working state of the wiper motor, thereby ensuring that the driver still has a clear field of vision during driving in rainy days, thereby preventing incidents that affect driving safety.

[0003] In the related art, when the body controller detects that the driver has turned on the wiper lever, it issues a start request, and controls the wipers to turn on through the start request. However, when the software system or hardware fails, the wipers are prone to unexpected shutdown, that is, the driver has not turned on the wiper lever, but has triggered a shutdown request. At this time, the body controller turns off the wipers under the control of the shutdown request.

[0004] However, if the wipers are turned off unexpectedly and fail to clean the windshield in time, the driver's vision may be obstructed, leading to the risk of vehicle loss of control. Summary of the invention

[0005] The purpose of the present application is to provide a wiper control method, system, vehicle and storage medium, aiming to solve the problem of vehicle loss of control caused by traditional wipers being turned off.

[0006] A first aspect of an embodiment of the present application provides a wiper control method, the method comprising:

[0007] When the wipers are turned on, if a shutdown request triggered by a fault is received, the safety mode is activated;

[0008] In safety mode, if a wiper control request is received, the driver's intention is determined;

[0009] If the wiper control request is a closing request, and the driver intends to close the wipers, the safety mode is exited, and the wipers are closed based on the wiper control request.

[0010] In some embodiments, determining the driver's intention includes:

[0011] Get the status of the wiper lever;

[0012] If the state of the wiper control lever is the on state, determining that the driver's intention is to turn on the wipers;

[0013] If the state of the wiper control lever is the off state, it is determined that the driver's intention is a turning-off intention.

[0014] In some embodiments, determining the driver's intention includes:

[0015] Obtain vehicle fault information;

[0016] If the fault information indicates that a fault occurs in the vehicle, it is determined that the driver's intention is a shutdown intention.

[0017] In some embodiments, the fault information includes a wiper motor state, a power supply state, and a battery usage mode; if the fault information indicates that the vehicle has a fault, determining that the driver's intention is a shutdown intention includes:

[0018] If the wiper motor state indicates that the motor is blocked, or the power state indicates that the vehicle is in a power-off state, or the battery usage mode indicates that the vehicle is in a power-saving mode, it is determined that the driver's intention is a shutdown intention.

[0019] A second aspect of an embodiment of the present application provides a wiper control system, the system comprising: a wiper function calculation module, a wiper state monitoring module and an arbitration module;

[0020] The wiper function calculation module is used to obtain wiper lever state information, vehicle fault information and vehicle mode information, determine a wiper control request based on the wiper lever state information, vehicle fault information and vehicle mode information; and send the wiper control request to the wiper state monitoring module;

[0021] The wiper state monitoring module is used to receive the wiper control request, obtain wiper lever state information and vehicle fault information; determine the state of the safety mode based on the wiper lever state information and vehicle fault information; and send the wiper control request and the state of the safety mode to the arbitration module;

[0022] The arbitration module is used to generate a wiper control instruction based on the wiper control request and the state of the safety mode, and output the wiper control instruction.

[0023] In some embodiments, the fault information includes wiper motor status, power supply status, and battery usage mode;

[0024] The wiper status monitoring module is used to determine that the safety mode is in the off state if the wiper motor status indicates that the motor is stuck, or the power status indicates that the vehicle is powered on, or the battery usage mode indicates that the vehicle is in the power saving mode, or the wiper control lever is in the off state.

[0025] In some embodiments, the arbitration module is configured to output a wiper closing instruction if the wiper control request is a closing request when the safety mode is in an off state.

[0026] In some embodiments, the fault information includes wiper motor status, power supply status, and battery usage mode;

[0027] The wiper status monitoring module is used to determine that the safety mode is on if the wiper motor status indicates that the motor is not stuck, and the power status indicates that the vehicle is in a power-off state, and the battery usage mode indicates that the vehicle is not in a power-saving mode, and the state of the wiper control lever is on, and the wiper control request is a closing request.

[0028] A third aspect of an embodiment of the present application provides a vehicle, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the wiper control method as described above when executing the computer program.

[0029] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the wiper control method as described above is implemented.

[0030] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0031] In the embodiment of the present application, when the wiper is turned on, if a shutdown request triggered by a fault is received, the safety mode is started. In the safety mode, the wiper control request and the driver's intention are received at the same time. If the wiper control request is a shutdown request and the driver's intention is also to shut down the wiper, the safety mode is exited and the wiper is shut down based on the wiper control request. In this way, in the safety mode, by detecting the driver's intention, whether to shut down the wiper is controlled based on the driver's intention. While ensuring that the wiper will not be unexpectedly shut down during driving, when the driver intends to shut down the wiper, the wiper will not be unable to be shut down due to reasons such as the safety mode, thereby optimizing the driving experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of a wiper control system provided by an exemplary embodiment is shown;

[0033] Figure 2 A schematic diagram of a wiper control system provided by an exemplary embodiment is shown;

[0034] Figure 3 A schematic flow chart of a wiper control method provided by an exemplary embodiment is shown;

[0035] Figure 4 A schematic flow chart of a wiper control method provided by an exemplary embodiment is shown;

[0036] Figure 5 It is a schematic diagram of the structure of a vehicle controller provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0037] In order to make the technical problems, technical solutions and beneficial effects to be solved by the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. 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.

[0038] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0039] With the development of electronic control technology for new energy vehicles, a large number of functions that enhance driver experience have been developed. Among the five domains of the vehicle, the quality of the functions in the body domain and the intelligent cockpit domain can most affect the driver's driving experience. Among them, the body controller (Central Electronic Module, CEM) as the core component of the body domain is responsible for controlling the vehicle wipers, vehicle interior and exterior lights, windows, door locks, seats and other components and the corresponding functions of each component. Therefore, a reasonable function judgment strategy and safe and feasible execution are important conditions for improving driver experience and ensuring driver safety.

[0040] The vehicle wiper control function in the body controller controls the functional state of the wiper by controlling the working state of the wiper motor, thereby ensuring that the driver still has a clear field of vision during driving in rainy days, thereby preventing incidents that affect driving safety.

[0041] In some embodiments, when the body controller detects that the driver has moved the wiper lever, a start request is issued, and the wipers are controlled to turn on through the start request. However, when the software system or hardware fails, the wipers are prone to unexpected shutdown, that is, the driver does not move the wiper lever, but triggers a shutdown request. At this time, the body controller turns off the wipers under the control of the shutdown request.

[0042] However, if the wipers are turned off unexpectedly and fail to clean the windshield in time, the driver's vision may be obstructed, leading to the risk of vehicle loss of control.

[0043] In order to reduce the unexpected shutdown of the wipers, in some embodiments, a corresponding monitoring strategy is set for the transition of the wipers from the on state to the off state. When the shutdown conditions are not met, once the shutdown request sent by the vehicle wiper function is detected, the vehicle activates the safety mode. In the safety mode, it does not respond to new shutdown requests and keeps the wipers in the on state, thereby preventing personal injury caused by unexpected shutdown of the wipers due to software or hardware failure.

[0044] However, the developers have tested and found that when the safety mode is triggered, the body controller does not respond to the new shutdown request, resulting in the wiper being unable to be turned off, which may cause damage to the wiper motor, or when the safety mode is triggered by mistake, it may cause the wiper to turn on unexpectedly. These situations will not only affect the driver's driving experience, but may also affect driving safety. Therefore, it is particularly important to design a reasonable monitoring strategy and a recovery strategy for the safety mode.

[0045] The present application provides a wiper control method, system, vehicle and storage medium. When the wiper is turned on, if a shutdown request triggered by a fault is received, the safety mode is started. In the safety mode, the wiper control request and the driver's intention are received at the same time. If the wiper control request is a shutdown request and the driver's intention is also to shut down the wiper, the safety mode is exited and the wiper is shut down based on the shutdown request. In this way, in the safety mode, by detecting the driver's intention, whether to shut down the wiper is controlled based on the driver's intention. While ensuring that the wiper will not be unexpectedly shut down during driving, when the driver intends to shut down the wiper, the wiper will not be unable to be shut down due to reasons such as the safety mode, thereby optimizing the driving experience.

[0046] Please refer to Figure 1 , which shows a schematic diagram of a wiper control system provided by an exemplary embodiment. The system includes: a wiper function calculation module 10, a wiper state monitoring module 20 and an arbitration module 30. The wiper state monitoring module 20 is communicated with the wiper function calculation module 10 and the arbitration module 30 respectively.

[0047] See also Figure 2 The wiper function calculation module 10 is used to obtain wiper rod state information, vehicle fault information and vehicle mode information, determine a wiper control request based on the wiper rod state information, vehicle fault information and vehicle mode information; and send the wiper control request to the wiper state monitoring module 20.

[0048] The wiper control request includes a wiper on request and a wiper off request. The wiper function calculation module 10 can determine whether the wiper control request is a wiper on request or a wiper off request according to wiper lever state information, vehicle fault information and vehicle mode information.

[0049] Please continue to see Figure 2 , the wiper function calculation module 10 and the wiper state monitoring module 20 receive input signals through independent interfaces respectively. Among them, the wiper function calculation module 10 receives wiper lever state information, vehicle fault information and vehicle mode information. Under normal operation, the wiper function calculation module 10 determines whether a wiper control request is received according to the wiper lever state information, vehicle fault information and vehicle mode information. In some embodiments, the vehicle fault information includes information such as wiper motor state, power state and power use mode. Accordingly, when the wiper motor state indicates that the motor is not blocked, and the power state indicates that the vehicle is not in a power-off state, and the battery use mode indicates that the vehicle is not in a power-saving mode, and the vehicle mode indicates that the vehicle is not in a transport mode or a showroom mode, if it is detected that the wiper control lever is moved, a wiper control request for turning off the wiper is issued. In some embodiments, when the vehicle detects that the vehicle has a fault according to the fault information and needs to turn off the wiper, a wiper control request for turning off the wiper can also be issued. For example, when the wiper motor status indicates that the motor is stuck, or the power status indicates that the vehicle is in a power-off state, or the battery usage mode indicates that the vehicle is in a power saving mode, or the vehicle mode indicates that the vehicle is in a transport mode or a showroom mode, a wiper control request for turning off the wipers is issued.

[0050] When a software or hardware failure occurs, the wiper function calculation module 10 is affected by the software or hardware failure and automatically generates a wiper control request for closing the wiper. The wiper function calculation module 10 sends the wiper control request to the wiper state monitoring module 20 .

[0051] It should be noted that the wiper function calculation module 10 also determines whether an opening request is received according to the state of the wiper control lever. Accordingly, when the state of the wiper control lever is the opening state, the wiper control request is determined to be an opening request. In some embodiments, the wiper function calculation module 10 also determines whether the received wiper opening request is a fault-triggered request. Accordingly, when the state of the wiper control lever is the non-opening state, or the fault information of the vehicle indicates that the vehicle has a fault, the wiper opening request is determined to be a fault-triggered opening request; when the state of the wiper control lever is the opening state, and the fault information indicates that the vehicle has not a fault, the wiper opening request is determined to be a valid opening request. Among them, the process of determining whether the fault information indicates that the vehicle has a fault is the same as the principle of the process of determining whether the fault information indicates that the vehicle has a fault when generating the closing request, and will not be repeated here.

[0052] The wiper status monitoring module 20 is used to receive the wiper control request, obtain wiper lever status information and vehicle fault information; determine the state of the safety mode based on the wiper lever status information and the vehicle fault information; and send the wiper control request and the state of the safety mode to the arbitration module.

[0053] In some embodiments, the wiper function calculation module 10 sends the wiper control request to the wiper state monitoring module 20 in the form of a wiper request flag. The wiper request flag can be set as needed. In the embodiment of the present application, the representation method of the wiper request flag is not specifically limited. For example, when the wiper control request is a wiper on request, the wiper request flag is set to 1, and when the wiper control request is a wiper off request, the wiper request flag is set to 0.

[0054] The wiper state monitoring module 20 is used to receive the wiper control request sent by the wiper function calculation module 10, and receive the fault information of the vehicle and the state of the wiper control lever. The wiper state monitoring module 20 can receive the fault information through the input interface module. The fault information can obtain the fault information of the vehicle through the controller area network bus (Controller Area Network, CAN).

[0055] The wiper state monitoring module 20 determines whether to turn on the safety mode based on the received fault information. The wiper state monitoring module 20 determines whether to turn on the safety mode based on the fault information and the state of the wiper control lever. The safety mode can be represented by a safety flag. When the state of the wiper control lever is in the on state and the fault information indicates that the vehicle has not failed, the safety flag is activated. When the state of the wiper control lever is in the off state or the fault information indicates that the vehicle has failed, the safety flag is turned off. The activation state or the off state of the safety flag can be represented by a mark value. For example, when the mark value is 1, it indicates that the safety flag is in the activated state, and when the mark value is 0, it indicates that the safety flag is in the off state.

[0056] Among them, the fault information includes the wiper motor status, power status, and battery usage mode. Accordingly, the fault information indicates that a vehicle fault occurs, which means that the wiper motor status indicates that the motor is stuck, or the power status indicates that the vehicle is powered on, or the battery usage mode indicates that the vehicle is in power saving mode.

[0057] In some embodiments, when the wiper is turned on, the wiper state monitoring module 20 determines whether to turn on the safety mode according to the fault information, the state of the wiper control lever and whether a shutdown request is received.

[0058] Correspondingly, the wiper status monitoring module 20 is used to determine that the safety mode is on if the wiper motor status indicates that the motor is not stuck, and the power status indicates that the vehicle is powered on, and the battery usage mode indicates that the vehicle is not in power saving mode, and the wiper control lever status is on, and the wiper control request is a closing request.

[0059] If the wiper control lever is in the open state, it is determined that the driver intends to turn on the wipers, and in the current situation, there is no fault such as motor jam, vehicle power failure or vehicle entering power saving mode, that is, there is no need to turn off the wipers. Therefore, if the received wiper control request is a shutdown request, it is determined that the wiper control request is an unexpected wiper control request (invalid request), and the safety mode is turned on to prevent the vehicle from executing the wiper control request, thereby preventing the wiper controller from being unexpectedly shut down.

[0060] In some embodiments, when the wiper is turned on, the wiper state monitoring module 20 determines whether to turn off the safety mode according to the fault information, the state of the wiper control lever and whether a turn-off request is received.

[0061] Correspondingly, the wiper status monitoring module 20 is used to determine that the safety mode is in the off state if the wiper motor status indicates that the motor is stuck, or the power status indicates that the vehicle is powered on, or the battery usage mode indicates that the vehicle is in the power saving mode, or the wiper control lever is in the off state.

[0062] If the wiper control lever is in the open state, it is determined that the driver intends to turn off the wipers, or in the current situation, a fault such as motor jam, vehicle power failure or vehicle entering power saving mode has occurred, and the wipers need to be turned off. Therefore, if the wiper control request received is a shutdown request, it is determined that the wiper control request is the expected wiper control request (valid request), and the safety mode is turned off to enable the vehicle to execute the wiper control request. This ensures that the wipers will not be turned off unexpectedly during driving. When the driver intends to turn off the wipers, the wipers will not be unable to be turned off due to reasons such as the safety mode, thereby optimizing the driving experience.

[0063] The arbitration module 30 is used to generate a wiper control instruction based on the wiper control request and the state of the safety mode, and output the wiper control instruction.

[0064] The wiper state monitoring module 20 sends the safety flag and the wiper request flag to the arbitration module 30. The arbitration module 30 determines whether the wiper request flag is a valid wiper request flag according to the safety flag. If the safety flag is in an activated state, the wiper is kept in an on state without responding to the shutdown request, or, if the safety flag is in an inactive state, the wiper is controlled to be turned off in response to the shutdown request. When the arbitration module 30 determines whether to respond to the shutdown request according to the safety flag, the output wiper request flag is determined according to the state of the safety flag. When the state of the safety flag is in an activated state, the arbitration module 30 sets the output wiper request flag to the mark value corresponding to the on request; when the safety flag is in an inactive state, the arbitration module 30 sets the output wiper request flag to the mark value corresponding to the off request. The arbitration module 30 outputs the wiper request flag through CAN to achieve the demand of controlling the wiper rod.

[0065] In the present implementation, the process of determining the safety flag is decoupled from the process of determining the wiper request flag, thereby ensuring that the wipers will not be unexpectedly turned off during driving, while reducing the probability of false triggering of the safety mode of the wiper status monitoring module 20. When the driver intends to turn off the wipers, the wipers will not be unable to be turned off due to the safety mode, thereby improving software availability.

[0066] It should be noted that when the wiper control request is an on request, the arbitration module 30 also determines whether to output the on request based on the fault flag. When the fault flag is in an inactive state, the on request is output; when the fault flag is in an active state, the off request is output.

[0067] In the embodiment of the present application, when the wiper is turned on, if a shutdown request triggered by a fault is received, the safety mode is started. In the safety mode, the wiper control request and the driver's intention are received at the same time. If the wiper control request is a shutdown request and the driver's intention is also to shut down the wiper, the safety mode is exited and the wiper is shut down based on the shutdown request. In this way, in the safety mode, by detecting the driver's intention, whether to shut down the wiper is controlled based on the driver's intention. While ensuring that the wiper will not be unexpectedly shut down during driving, when the driver intends to shut down the wiper, the wiper will not be unable to be shut down due to reasons such as the safety mode, thereby optimizing the driving experience.

[0068] The present solution is described below in conjunction with a specific method embodiment. Figure 3 , which shows a flow chart of a wiper control method provided by an exemplary embodiment. As an example but not a limitation, the method is applied to a vehicle, and the vehicle is configured as the above-mentioned wiper control system.

[0069] S301, when the wipers are turned on, if a shutdown request triggered by a fault is received, the vehicle starts a safety mode.

[0070] When the wipers are in the on state, if a wiper control request for turning off the wipers is received, the vehicle determines whether the turning-off request is a turning-off request triggered by a fault.

[0071] In actual application, when the wiper is in the on state, if a shutdown request is detected, the vehicle detects whether the shutdown request is an unexpected shutdown request. When the shutdown request is an expected shutdown request, the shutdown request is executed to shut down the wiper controller. When the shutdown request is an unexpected shutdown request, the vehicle starts the safety mode.

[0072] The safety mode refers to a mode of a safety control off request, in which the vehicle does not respond to a wiper control request.

[0073] Whether the vehicle enters the safety mode can be indicated by a safety flag. The safety flag can be set as needed. In the embodiment of the present application, the setting method of the safety flag is not specifically limited. For example, when the safety flag is in an activated state, the flag value of the safety flag is set to 1, and when the safety flag is in an inactivated state, the flag value of the safety flag is set to 0.

[0074] S302, in safety mode, if a wiper control request is received, the vehicle determines the driver's intention.

[0075] The driver's intention may be determined by a wiper control lever controlled by the driver, or the driver's intention may be determined by fault information of the vehicle, or the driver's intention may be determined by information such as the driver's voice signal, etc. In the embodiments of the present application, no specific limitation is made to this.

[0076] In some embodiments, the vehicle obtains the state of the wiper control lever; if the state of the wiper control lever is on, it is determined that the driver intends to turn on the wipers; if the state of the wiper control lever is off, it is determined that the driver intends to turn off.

[0077] In this implementation, the driver's intention is determined based on the state of the wiper control lever, so that when the driver intends to turn off the wipers, the system can respond to the driver's intention and turn off the wipers in time. While ensuring that the wipers will not be turned off unexpectedly during driving, when the driver intends to turn off the wipers, the wipers will not be unable to be turned off due to safety mode or other reasons, thereby optimizing the driving experience.

[0078] In some embodiments, the vehicle obtains fault information of the vehicle; if the fault information indicates that the vehicle has a fault, it is determined that the driver's intention is a shutdown intention.

[0079] Among them, the fault information includes the wiper motor status, power status, and battery usage mode; the process by which the vehicle determines that the driver's intention is to shut down based on the fault information includes: if the wiper motor status indicates that the motor is stuck, or the power status indicates that the vehicle is in a power-off state, or the battery usage mode indicates that the vehicle is in a power saving mode, it is determined that the driver's intention is to shut down.

[0080] In this implementation, the driver's intention is determined through fault information so that the wipers can be turned off in time when a vehicle failure occurs. This ensures that the wipers will not be turned off unexpectedly during driving, while preventing the wipers from turning on in the event of a vehicle failure, causing problems such as fault escalation.

[0081] In some embodiments, the vehicle acquires a voice signal from the driver, analyzes the voice signal, and obtains an analysis result. If the analysis result indicates that the driver intends to turn off the wipers, it is determined that the driver intends to turn off the wipers.

[0082] In this implementation, the driver's intention is determined based on the driver's voice signal, so that when the driver intends to turn off the wipers, the system can respond to the driver's intention and turn off the wipers in time. While ensuring that the wipers will not be turned off unexpectedly during driving, when the driver intends to turn off the wipers, the wipers will not be unable to be turned off due to safety mode or other reasons, thereby optimizing the driving experience.

[0083] S303: If the wiper control request is a closing request and the driver intends to close the wipers, the vehicle exits the safety mode and closes the wipers based on the wiper control request.

[0084] The vehicle determines whether the wiper request flag responds to the wiper control request (close request) for controlling the wiper to close according to the safety flag. If the safety flag is in an activated state, the close request is not responded to and the wiper is kept in an on state, or, if the safety flag is in an off state, the wiper is controlled to close in response to the close request.

[0085] Among them, when the vehicle determines whether to respond to the shutdown request based on the safety flag, the output wiper request flag is determined according to the state of the safety flag. When the state of the safety flag is activated, the output wiper request flag is set to the mark value corresponding to the turn-on request; when the safety flag is in an inactive state, the output wiper request flag is set to the mark value corresponding to the shutdown request, and then the wiper request flag is output to the motor controller of the wiper, so that the motor controller of the wiper controls the operation of the wiper motor according to the wiper request flag.

[0086] In this implementation, the process of determining the safety flag is decoupled from the process of determining the wiper request flag, which ensures that the wipers will not be turned off unexpectedly during driving, while reducing the probability of false triggering of the safety mode of the wiper status monitoring module. When the driver intends to turn off the wipers, the wipers will not be unable to be turned off due to the safety mode, thereby improving software availability.

[0087] In this step, the vehicle switches the safety flag from an activated state to an off state, thereby exiting the safety state, so that the vehicle can respond normally to the shutdown request.

[0088] One point that needs to be explained is that, in the present implementation, the shutdown request and the status flag are judged at the same time, so that the historical status flag judgment result no longer affects the current judgment result. Therefore, even if there is a situation in the historical process where the safety flag is activated, when the driver intends to turn off the wipers, the wipers will not be unable to be turned off due to the safety mode, thereby improving the driver's driving experience.

[0089] In the embodiment of the present application, when the wiper is turned on, if a shutdown request triggered by a fault is received, the safety mode is started. In the safety mode, the wiper control request and the driver's intention are received at the same time. If the wiper control request is a shutdown request and the driver's intention is also to shut down the wiper, the safety mode is exited and the wiper is shut down based on the wiper control request. In this way, in the safety mode, by detecting the driver's intention, whether to shut down the wiper is controlled based on the driver's intention. While ensuring that the wiper will not be unexpectedly shut down during driving, when the driver intends to shut down the wiper, the wiper will not be unable to be shut down due to reasons such as the safety mode, thereby optimizing the driving experience.

[0090] Whether the shutdown request received by the vehicle is a shutdown request triggered by a fault. In some embodiments, the vehicle can automatically detect whether the software or hardware system of the wiper control system has a fault. If a fault occurs, a fault report is generated. When the vehicle receives the fault report, if a shutdown request is received, the shutdown request is determined to be a shutdown request triggered by a fault. In some embodiments, the vehicle can also determine whether the received shutdown request is a shutdown request triggered by a fault by combining information such as the vehicle's fault information and the status of the wiper control lever. Figure 4 , which shows a flow chart of a wiper control method provided by an exemplary embodiment. As an example but not a limitation, the method is applied to a vehicle, and the vehicle is configured as the above-mentioned wiper control system.

[0091] S401, when the wiper is in the on state, if a closing request is received, the state of the wiper control lever and the fault information of the vehicle are obtained.

[0092] The state of the wiper control lever includes a closed state, an open state, etc. The state of the wiper control lever can be manually triggered by the driver, or can be triggered by the driver through voice commands, touch screen, etc., which is not specifically limited in the embodiment of the present application. The fault information includes the wiper motor state, power supply state, and battery usage mode.

[0093] S402: If the state of the wiper control lever is not in the closed state, and the fault information indicates that the vehicle has not failed, the vehicle determines that the closing request is a closing request triggered by a fault.

[0094] The vehicle can determine whether the closing request is a closing request triggered by a fault according to the wiper control lever or according to whether the vehicle is faulty. When the closing request is a request triggered by the wiper control lever or the closing request is triggered by a vehicle fault, the closing request is an expected closing request, otherwise, the closing request is a closing request triggered by a fault.

[0095] When the state of the wiper lever is not closed, the vehicle can determine that the closing request is not determined by the driver's intention, and the vehicle continues to determine whether the closing request is a closing request triggered by a vehicle fault. In some embodiments, the fault information includes the wiper motor state, the power state, and the battery usage mode; this step includes: if the state of the wiper lever is not closed, and the wiper motor state indicates that the motor is not blocked, and the power state indicates that the vehicle is not in a power-off state, and the battery usage mode indicates that the vehicle is not in a power-saving mode, determine that the closing request is an invalid closing request.

[0096] S403: If the state of the wiper control lever is the closed state, or the fault information indicates that the vehicle has a fault, the vehicle determines that the closing request is an expected closing request.

[0097] When the state of the wiper control lever is the closed state, the vehicle can determine that the closing request is determined by the driver's intention, or when the vehicle determines that the closing request is a closing request triggered by a vehicle fault, the closing request is determined to be a valid closing request. In some embodiments, the fault information includes the wiper motor state, the power state, and the battery usage mode; this step includes: if the state of the wiper control lever is the closed state, or the wiper motor state indicates that the motor is blocked, or the power state indicates that the vehicle is in a power-off state, or the battery usage mode indicates that the vehicle is in a power-saving mode, the closing request is determined to be a valid closing request.

[0098] In the embodiment of the present application, the order in which the vehicle determines the state of the wiper lever and whether the vehicle is faulty is not specifically limited. The vehicle may first determine the state of the wiper lever and then determine whether the vehicle is faulty; the vehicle may first determine whether the vehicle is faulty and then determine the state of the wiper lever; the vehicle may also simultaneously determine the state of the wiper lever and whether the vehicle is faulty.

[0099] In this implementation, the validity test result of the shutdown request is determined in combination with the status of the wiper lever and the vehicle's fault information, and the driver's intention and the vehicle's fault information are monitored at the same time to ensure that when the fault disappears, once the monitoring conditions or the driver's intention no longer meet the requirements for turning on the wipers, the wipers are allowed to be turned off.

[0100] S404, the vehicle starts a safety mode.

[0101] The principle of this step is the same as that of step S301 and will not be repeated here.

[0102] S405, in safety mode, if a wiper control request is received, the vehicle determines the driver's intention.

[0103] The principle of this step is the same as that of step S302 and will not be repeated here.

[0104] S406: If the wiper control request is a closing request and the driver intends to close the wipers, the vehicle exits the safety mode and closes the wipers based on the wiper control request.

[0105] The principle of this step is the same as that of step S303 and will not be repeated here.

[0106] In the embodiment of the present application, when the wiper is turned on, if a shutdown request triggered by a fault is received, the safety mode is started. In the safety mode, the wiper control request and the driver's intention are received at the same time. If the wiper control request is a shutdown request and the driver's intention is also to shut down the wiper, the safety mode is exited and the wiper is shut down based on the wiper control request. In this way, in the safety mode, by detecting the driver's intention, whether to shut down the wiper is controlled based on the driver's intention. While ensuring that the wiper will not be unexpectedly shut down during driving, when the driver intends to shut down the wiper, the wiper will not be unable to be shut down due to reasons such as the safety mode, thereby optimizing the driving experience.

[0107] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0108] Figure 5 FIG. 1 is a schematic diagram of a vehicle provided by an exemplary embodiment of the present application. Figure 5As shown, the vehicle 5 of this embodiment includes: a processor 50, a memory 51, and a computer program 52 stored in the memory 51 and executable on the processor 50, such as a wiper control program. When the processor 50 executes the computer program 52, the steps in the above-mentioned various wiper control method embodiments are implemented, such as Figure 3 Alternatively, when the processor 50 executes the computer program 52, the functions of each unit in the above-mentioned device embodiments are realized, for example Figure 1 The functions of units 10 to 30 are shown.

[0109] Exemplarily, the computer program 52 may be divided into one or more units, which are stored in the memory 51 and executed by the processor 50 to complete the present application. The one or more units may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program 52 in the vehicle 5. For example, the computer program 52 may be divided into a wiper function calculation module, a wiper state monitoring module, and an arbitration module, and the specific functions of each module are as follows:

[0110] The wiper function calculation module 10 is used to obtain wiper lever state information, vehicle fault information and vehicle mode information, determine a wiper control request based on the wiper lever state information, vehicle fault information and vehicle mode information; and send the wiper control request to the wiper state monitoring module 20;

[0111] The wiper state monitoring module 20 is used to receive the wiper control request, obtain wiper lever state information and vehicle fault information; determine the state of the safety mode based on the wiper lever state information and the vehicle fault information; and send the wiper control request and the state of the safety mode to the arbitration module 30;

[0112] The arbitration module 30 is used to generate a wiper control instruction based on the wiper control request and the state of the safety mode, and output the wiper control instruction. The vehicle 5 can be any vehicle with a control function. The vehicle 5 can include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art can understand that Figure 5 It is only an example of the vehicle 5 and does not constitute a limitation of the vehicle 5. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the vehicle 5 may also include input and output devices, network access devices, buses, etc.

[0113] The processor 50 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0114] The memory 51 may be an internal storage unit of the vehicle 5, such as a hard disk or memory of the vehicle 5. The memory 51 may also be an external storage device of the vehicle 5, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the vehicle 5. Further, the memory 51 may also include both an internal storage unit of the vehicle 5 and an external storage device. The memory 51 is used to store the computer program and other programs and data required by the terminal device. The memory 51 may also be used to temporarily store data that has been output or is to be output.

[0115] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0116] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0117] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0118] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0119] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0120] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0121] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0122] The embodiments of the present application further provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0123] The embodiment of the present application also provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0124] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A wiper control method, characterized in that: The method comprises: When the wipers are turned on, if a shutdown request triggered by a fault is received, the safety mode is activated; In safety mode, if a wiper control request is received, the driver's intention is determined; If the wiper control request is a closing request, and the driver intends to close the wipers, the safety mode is exited, and the wipers are closed based on the wiper control request.

2. The method according to claim 1, characterized in that Determining the driver's intention includes: Get the status of the wiper lever; If the state of the wiper control lever is the on state, determining that the driver's intention is to turn on the wipers; If the state of the wiper control lever is the off state, it is determined that the driver's intention is a turning-off intention.

3. The method according to claim 1 or 2, characterized in that Determining the driver's intention includes: Obtain vehicle fault information; If the fault information indicates that a fault occurs in the vehicle, it is determined that the driver's intention is a shutdown intention.

4. The method according to claim 3, characterized in that The fault information includes a wiper motor state, a power supply state, and a battery usage mode; if the fault information indicates that the vehicle has a fault, determining that the driver's intention is a shutdown intention includes: If the wiper motor state indicates that the motor is blocked, or the power state indicates that the vehicle is in a power-off state, or the battery usage mode indicates that the vehicle is in a power-saving mode, it is determined that the driver's intention is a shutdown intention.

5. A wiper control system, characterized in that: The system comprises: a wiper function calculation module, a wiper state monitoring module and an arbitration module; The wiper function calculation module is used to obtain wiper lever state information, vehicle fault information and vehicle mode information, determine a wiper control request based on the wiper lever state information, vehicle fault information and vehicle mode information; and send the wiper control request to the wiper state monitoring module; The wiper state monitoring module is used to receive the wiper control request, obtain wiper lever state information and vehicle fault information; determine the state of the safety mode based on the wiper lever state information and vehicle fault information; and send the wiper control request and the state of the safety mode to the arbitration module; The arbitration module is used to generate a wiper control instruction based on the wiper control request and the state of the safety mode, and output the wiper control instruction.

6. The system according to claim 5, characterized in that The fault information includes the wiper motor status, power supply status, and battery usage mode; The wiper status monitoring module is used to determine that the safety mode is in the off state if the wiper motor status indicates that the motor is stuck, or the power status indicates that the vehicle is in a power-off state, or the battery usage mode indicates that the vehicle is in a power saving mode, or the wiper control lever is in the off state.

7. The system according to claim 5 or 6, characterized in that The arbitration module is configured to output a wiper closing instruction when the safety mode is in an off state and if the wiper control request is a closing request.

8. The system according to claim 5, characterized in that The fault information includes the wiper motor status, power supply status, and battery usage mode; The wiper status monitoring module is used to determine that the safety mode is on if the wiper motor status indicates that the motor is not blocked, and the power status indicates that the vehicle is powered on, and the battery usage mode indicates that the vehicle is not in power saving mode, and the wiper control lever status is on, and the wiper control request is a closing request.

9. A vehicle, characterized in that: The vehicle comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the wiper control method according to any one of claims 1 to 4.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the wiper control method according to any one of claims 1 to 4 is implemented.

Images