Windshield wiper control method, system, vehicle and storage medium

Abstract

The application provides a wiper control method, system, vehicle and storage medium, and belongs to the technical field of automobiles. The method comprises the following steps: in a state where the wiper is turned on, if a closing request triggered by a fault is received, a safety mode is started; in the safety mode, if a wiper control request is received, the intention of a driver is determined; if the wiper control request is a closing request and the intention of the driver is a wiper closing intention, the safety mode is exited, and the wiper is closed based on the wiper control request. In this way, in the safety mode, whether the wiper is closed is controlled based on the intention of the driver by detecting the intention of the driver, so that the wiper cannot be unexpectedly closed during driving is ensured, and when the intention of the driver is to close the wiper, the wiper cannot be closed due to the safety mode and the like, and the driving experience is optimized.

Description

Technical Field

[0001] This application belongs to the field of automotive technology, and in particular relates to a windshield wiper control method, system, vehicle, and storage medium. Background Technology

[0002] The vehicle wiper control function in the Central Electronic Module (CEM) controls the operation of the wipers by controlling the working state of the wiper motor, thereby ensuring that the driver still has a clear view while driving in the rain and preventing incidents that could affect driving safety.

[0003] In related technologies, when the vehicle body controller detects that the driver has moved the wiper control lever, it issues a start request, which in turn controls the wipers to turn on. However, in the event of a software or hardware malfunction, the wipers may unexpectedly turn off, meaning the driver may not have moved the wiper control lever but triggered a turn-off request. In this case, the vehicle body controller will turn off the wipers under the control of the turn-off request.

[0004] However, if the windshield wipers turn off unexpectedly and fail to clear the windshield in time, it can obstruct the driver's view and increase the risk of losing control of the vehicle. Summary of the Invention

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

[0006] A first aspect of this application provides a windshield wiper control method, the method comprising:

[0007] If a shutdown request triggered by a malfunction is received while the wipers are on, safety mode will be activated.

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

[0009] If the wiper control request is a turn-off request and the driver's intention is to turn off the wipers, exit the safety mode and turn off the wipers based on the wiper control request.

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

[0011] Get the status of the wiper control lever;

[0012] If the wiper control lever is in the ON state, then the driver's intention is determined to be to turn on the wipers.

[0013] If the wiper control lever is in the off state, then the driver's intention is determined to be to turn it off.

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

[0015] Obtain vehicle fault information;

[0016] If the fault information indicates that the vehicle has malfunctioned, the driver's intention is determined to be a shutdown intention.

[0017] In some embodiments, the fault information includes wiper motor status, power status, and battery usage mode; determining that the driver's intention is to turn off the wiper if the fault information indicates a vehicle malfunction includes:

[0018] If the wiper motor status indicates that the motor is stalled, or the power status indicates that the vehicle is powered off, or the battery usage mode indicates that the vehicle is in power-saving mode, then the driver's intention is determined to be an intention to turn off the wiper.

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

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

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

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

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

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

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

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

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

[0028] A third aspect of this application provides a vehicle including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the wiper control method described above.

[0029] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the wiper control method described above.

[0030] The beneficial effects of the embodiments of the present invention compared with the prior art are as follows:

[0031] In this embodiment, when the windshield wipers are on, if a fault-triggered shutdown request is received, a safety mode is activated. In safety mode, both a wiper control request and the driver's intention are received. If the wiper control request is a shutdown request and the driver's intention is also to shut off the wipers, the safety mode is exited, and the wipers are shut off based on the wiper control request. Thus, in safety mode, by detecting the driver's intention and controlling whether to shut off the wipers based on that intention, the wipers are ensured not to shut off unexpectedly during driving, and the wipers are not prevented from being shut off due to safety mode or other reasons when the driver intends to shut them off, thereby optimizing the driving experience. Attached Figure Description

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

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

[0034] Figure 3 A flowchart illustrating a wiper control method provided in an exemplary embodiment is shown.

[0035] Figure 4 A flowchart illustrating a wiper control method provided in an exemplary embodiment is shown.

[0036] Figure 5 This is a schematic diagram of the vehicle controller provided in an embodiment of the present invention. Detailed Implementation

[0037] To make the technical problems, technical solutions, and beneficial effects to be solved by this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this application.

[0038] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0039] With the development of electronic control technology in new energy vehicles, numerous functions designed to enhance the driver experience have been developed. Among the five major vehicle domains, the quality of the body domain and the intelligent cockpit domain has the greatest impact on the driver's experience. The Central Electronic Module (CEM), as the core component of the body domain, is responsible for controlling the vehicle's wipers, interior and exterior lights, windows, door locks, seats, and other devices, as well as the corresponding functions of each device. Therefore, reasonable function judgment strategies and safe and feasible execution are crucial conditions for improving the driver's experience and ensuring driver safety.

[0040] The vehicle wiper control function in the body controller controls the wiper's function by controlling the working state of the wiper motor, thereby ensuring that the driver still has a clear view during rainy weather and preventing incidents that could affect driving safety.

[0041] In some embodiments, when the body controller detects that the driver has moved the wiper control lever, it issues a start request, which in turn controls the wipers to turn on. However, in the event of a software or hardware malfunction, the wipers may turn off unexpectedly, i.e., the driver may not have moved the wiper control lever, but a turn-off request has been triggered. In this case, the body controller will turn off the wipers under the control of the turn-off request.

[0042] However, if the windshield wipers turn off unexpectedly and fail to clear the windshield in time, it can obstruct the driver's view and increase the risk of losing control of the vehicle.

[0043] To reduce the risk of windshield wipers turning off unexpectedly, some embodiments include a monitoring strategy for the transition of windshield wipers from on to off. If the conditions for turning off are not met, the vehicle activates a safety mode once a turn-off request is detected. In safety mode, the vehicle does not respond to new turn-off requests and keeps the windshield wipers on, thereby preventing personal injury caused by unexpected windshield wiper shutdown due to software or hardware malfunction.

[0044] However, testing by developers revealed that when the safety mode is triggered, the vehicle controller does not respond to new shutdown requests, causing the wipers to fail to turn off, potentially damaging the wiper motor. Alternatively, accidental triggering of the safety mode may lead to unexpected wiper activation. These issues not only affect the driver's experience but also potentially compromise driving safety. Therefore, a well-designed monitoring strategy and a proper safety mode recovery strategy are crucial.

[0045] This application provides a windshield wiper control method, system, vehicle, and storage medium. When the windshield wipers are on, if a fault-triggered shutdown request is received, a safety mode is activated. In safety mode, both the wiper control request and the driver's intention are received simultaneously. If the wiper control request is a shutdown request and the driver's intention is also to shut off the wipers, the safety mode is exited, and the wipers are shut off based on the shutdown request. Thus, in safety mode, by detecting the driver's intention and controlling whether to shut off the wipers based on that intention, the wipers are prevented from shutting off unexpectedly during driving. Furthermore, when the driver intends to shut off the wipers, the wipers will not fail to shut off due to safety mode or other reasons, thus optimizing the driving experience.

[0046] Please refer to Figure 1 The diagram illustrates a windshield wiper control system provided in an exemplary embodiment. The system includes a wiper function calculation module 10, a wiper status monitoring module 20, and an arbitration module 30. The wiper status monitoring module 20 is communicatively connected to both the wiper function calculation module 10 and the arbitration module 30.

[0047] See Figure 2 The wiper function calculation module 10 is used to obtain wiper arm status information, vehicle fault information and vehicle mode information, and determine the wiper control request based on the wiper arm status information, vehicle fault information and vehicle mode information; and send the wiper control request to the wiper status 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 based on the wiper arm status information, vehicle fault information, and vehicle mode information.

[0049] Please continue reading Figure 2 The wiper function calculation module 10 and the wiper status monitoring module 20 each receive input signals through independent interfaces. The wiper function calculation module 10 receives wiper lever status information, vehicle fault information, and vehicle mode information. Under normal operating conditions, the wiper function calculation module 10 determines whether a wiper control request has been received based on the wiper lever status information, vehicle fault information, and vehicle mode information. In some embodiments, the vehicle fault information includes wiper motor status, power status, and power usage mode. Accordingly, if the wiper motor status indicates that the motor is not stalled, the power status indicates that the vehicle is not powered off, the battery usage mode indicates that the vehicle is not in power-saving mode, and the vehicle mode indicates that the vehicle is not in transport mode or showroom mode, a wiper control request to turn off the wipers is issued if the wiper control lever is detected to be moved. In some embodiments, when the vehicle detects a fault based on the fault information and needs to turn off the wipers, a wiper control request to turn off the wipers can also be issued. For example, when the wiper motor status indicates that the motor is stalled, or the power status indicates that the vehicle is powered off, or the battery usage mode indicates that the vehicle is in power-saving mode, or the vehicle mode indicates that the vehicle is in transport mode or showroom mode, a wiper control request to turn off the wipers is issued.

[0050] In the event of a software or hardware failure, the wiper function calculation module 10, affected by the failure, automatically generates a wiper control request to turn off the wipers. The wiper function calculation module 10 then sends this wiper control request to the wiper status monitoring module 20.

[0051] It should be noted that the wiper function calculation module 10 also determines whether an activation request has been received based on the state of the wiper control lever. Accordingly, if the wiper control lever is in the 'on' state, the wiper control request is determined to be an activation request. In some embodiments, the wiper function calculation module 10 further determines whether the received wiper activation request is a fault-triggered request. Accordingly, if the wiper control lever is in the 'off' state, or if the vehicle's fault information indicates a malfunction, the wiper activation request is determined to be a fault-triggered activation request; if the wiper control lever is in the 'on' state and the fault information indicates that the vehicle is not malfunctioning, the wiper activation request is determined to be a valid activation request. The process of determining whether the fault information indicates a vehicle malfunction is the same as the process of determining whether the fault information indicates a vehicle malfunction when generating a shutdown request, and will not be repeated here.

[0052] The wiper status monitoring module 20 is used to receive the wiper control request, obtain wiper arm status information and vehicle fault information; determine the status of the safety mode based on the wiper arm status information and vehicle fault information; and send the wiper control request and the status 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 status monitoring module 20 in the form of a wiper request flag. The wiper request flag can be set as needed; in this embodiment, the representation 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; when the wiper control request is a wiper-off request, the wiper request flag is set to 0.

[0054] The wiper status monitoring module 20 is used to receive wiper control requests sent by the wiper function calculation module 10, as well as vehicle fault information and the status of the wiper control lever. The wiper status monitoring module 20 can receive the fault information via an input interface module. This fault information can be obtained from the vehicle's fault information via the Controller Area Network (CAN) bus.

[0055] The wiper status monitoring module 20 determines whether to activate the safety mode based on the received fault information. Specifically, the module determines activation based on the fault information and the status of the wiper control lever. This safety mode can be indicated by a safety flag. When the wiper control lever is in the "on" state and the fault information indicates that the vehicle is not malfunctioning, the safety flag is activated; when the wiper control lever is in the "off" state, or the fault information indicates that the vehicle is malfunctioning, the safety flag is deactivated. The activation or deactivation of the safety flag can be represented by a flag value; for example, a flag value of 1 indicates that the safety flag is activated, and a flag value of 0 indicates that the safety flag is deactivated.

[0056] The fault information includes the wiper motor status, power status, and battery usage mode. Accordingly, the fault information indicates that the vehicle has malfunctioned. The wiper motor status indicates that the motor is stalled, 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 wipers are on, the wiper status monitoring module 20 determines whether to enable the safety mode based on the fault information, the status of the wiper control lever, and whether a shutdown request has been received.

[0058] Accordingly, the wiper status monitoring module 20 is used to determine that the safety mode is enabled if the wiper motor status indicates that the motor is not stalled, the power status indicates that the vehicle is powered on, the battery usage mode indicates that the vehicle is not in power-saving mode, the wiper control lever is in the on state, and the wiper control request is a shutdown request.

[0059] If the wiper control lever is in the on position, it is determined that the driver intends to turn on the wipers. Under the current circumstances, there is no malfunction such as motor stall, vehicle power failure, or vehicle entering power saving mode, meaning there is no need to turn off the wipers. Therefore, if a wiper control request is received that is a turn-off request, it is determined that the wiper control request is an unexpected wiper control request (invalid request). Then, the safety mode is activated to prevent the vehicle from executing the wiper control request, thereby preventing the wiper controller from turning off unexpectedly.

[0060] In some embodiments, when the wipers are on, the wiper status monitoring module 20 determines whether to turn off the safety mode based on the fault information, the status of the wiper control lever, and whether a turn-off request has been received.

[0061] Accordingly, the wiper status monitoring module 20 is used to determine that the safety mode is off if the wiper motor status indicates that the motor is stalled, 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, or the wiper control lever status is off.

[0062] If the wiper control lever is in the on position, it is determined that the driver intends to turn off the wipers. Alternatively, if a fault such as motor stall, vehicle power failure, or vehicle entering power-saving mode occurs, requiring the wipers to be turned off, then if a wiper control request is received that is a turn-off request, it is determined that the wiper control request is the expected wiper control request (valid request). The safety mode is then deactivated to allow the vehicle to execute the wiper control request. This ensures that the wipers will not turn off unexpectedly during driving, and that the wipers will not be unable to be turned off due to safety mode or other reasons when the driver intends to turn them off, thus optimizing the driving experience.

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

[0064] The wiper status 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 valid based on the safety flag. If the safety flag is active, it does not respond to the turn-off request and keeps the wipers on; or, if the safety flag is inactive, it responds to the turn-off request and controls the wipers to turn off. Specifically, when the arbitration module 30 determines whether to respond to the turn-off request based on the safety flag, it determines the output wiper request flag based on the status of the safety flag. When the safety flag is active, the arbitration module 30 sets the output wiper request flag to the flag value corresponding to the turn-on request; when the safety flag is inactive, the arbitration module 30 sets the output wiper request flag to the flag value corresponding to the turn-off request. The arbitration module 30 outputs the wiper request flag via CAN to fulfill the requirement of controlling the wiper arm.

[0065] In this implementation, the process of determining the safety flag bit is decoupled from the process of determining the wiper request flag bit. This ensures that the wipers will not turn off unexpectedly during driving, while reducing the probability of the wiper status monitoring module 20 falsely triggering the safety mode. When the driver intends to turn off the wipers, the wipers will not fail to turn off due to the safety mode, thus improving software usability.

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

[0067] In this embodiment, when the windshield wipers are on, if a fault-triggered shutdown request is received, a safety mode is activated. In safety mode, both a wiper control request and the driver's intention are received. If the wiper control request is a shutdown request and the driver's intention is also to shut off the wipers, the safety mode is exited, and the wipers are shut off based on the shutdown request. Thus, in safety mode, by detecting the driver's intention and controlling whether to shut off the wipers based on that intention, the wipers are ensured not to shut off unexpectedly during driving, and the wipers are not prevented from being shut off due to safety mode or other reasons when the driver intends to shut them off, thus optimizing the driving experience.

[0068] The present solution will be described below with reference to specific method embodiments. See also Figure 3 The diagram illustrates a flowchart of a windshield wiper control method provided by an exemplary embodiment. By way of example and not limitation, the method is applied to a vehicle configured with the aforementioned windshield wiper control system.

[0069] S301: If a fault-triggered shutdown request is received while the windshield wipers are on, the vehicle will activate a safety mode.

[0070] When the windshield wipers are on, if a wiper control request to turn off the wipers is received, the vehicle determines whether the request is triggered by a fault.

[0071] In practical applications, when the windshield wipers are on, if a closing request is detected, the vehicle checks whether the request is an unexpected one. If the request is expected, it is executed, and the wiper controller is turned off. If the request is unexpected, the vehicle activates a safety mode.

[0072] This safety mode refers to the mode in which safety control requests are turned off, and in this safety mode, the vehicle does not respond to wiper control requests.

[0073] Whether a vehicle has entered safe mode can be indicated by a safety flag. This safety flag can be set as needed, and in this embodiment, the setting method is not specifically limited. For example, when the safety flag is active, its value is set to 1; when the safety flag is inactive, its value is set to 0.

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

[0075] The driver's intention can be determined by the windshield wiper control lever, vehicle malfunction information, or the driver's voice signal. This embodiment does not impose specific limitations on these methods.

[0076] In some embodiments, the vehicle acquires the state of the wiper control lever; if the state of the wiper control lever is on, the driver's intention is determined to be to turn on the wipers; if the state of the wiper control lever is off, the driver's intention is determined to turn off the wipers.

[0077] In this implementation, the driver's intention is determined based on the state of the wiper control lever. When the driver intends to turn off the wipers, the system responds to the driver's intention and turns off the wipers in a timely manner. This ensures that the wipers do not turn off unexpectedly during driving, and also prevents the wipers from failing to turn off due to safety modes or other reasons when the driver intends to turn them off, thus optimizing the driving experience.

[0078] In some embodiments, the vehicle acquires vehicle fault information; if the fault information indicates that the vehicle has malfunctioned, the driver's intention is determined to be a shutdown intention.

[0079] The fault information includes the wiper motor status, power status, and battery usage mode. The process by which the vehicle determines the driver's intention to turn off the wiper based on the fault information includes: if the wiper motor status indicates that the motor is stalled, or the power status indicates that the vehicle is powered off, or the battery usage mode indicates that the vehicle is in power-saving mode, then the driver's intention is determined to be to turn off the wiper.

[0080] In this implementation, the driver's intention is determined through fault information so that the windshield wipers can be turned off in time when the vehicle malfunctions. This ensures that the wipers do not turn off unexpectedly during driving, while also preventing the wipers from turning on when the vehicle is malfunctioning, which could lead to problems such as escalating the malfunction.

[0081] In some embodiments, the vehicle acquires the driver's voice signal, parses the voice signal, and obtains a parsing result. If the parsing result indicates that the driver intends to turn off the windshield wipers, then the driver's intention is determined to be an intention to turn them off.

[0082] In this implementation, the driver's intention is determined based on the driver's voice signal. When the driver intends to turn off the windshield wipers, the system can respond to the driver's intention and turn off the windshield wipers in a timely manner. This ensures that the windshield wipers will not turn off unexpectedly during driving, and also prevents the windshield wipers from failing to turn off due to reasons such as safety mode when the driver intends to turn them off, thus optimizing the driving experience.

[0083] S303, if the wiper control request is a turn-off request and the driver's intention is to turn off the wipers, the vehicle exits the safety mode and turns off the wipers based on the wiper control request.

[0084] The vehicle determines whether the wiper request flag responds to the wiper control request (off request) used to control the wipers to turn off based on the safety flag. If the safety flag is active, the vehicle does not respond to the off request and keeps the wipers on; or, if the safety flag is off, the vehicle controls the wipers to turn off in response to the off request.

[0085] Specifically, when the vehicle determines whether to respond to the turn-off request based on the safety flag, it determines the output wiper request flag based on the state of the safety flag. When the safety flag is active, the output wiper request flag is set to the flag value corresponding to the turn-on request; when the safety flag is inactive, the output wiper request flag is set to the flag value corresponding to the turn-off request. Then, the wiper request flag is output to the wiper motor controller so that the wiper motor controller can control the operation of the wiper motor based on the wiper request flag.

[0086] In this implementation, the process of determining the safety flag bit is decoupled from the process of determining the wiper request flag bit. This ensures that the wipers will not turn off unexpectedly during driving, while reducing the probability of the wiper status monitoring module erroneously triggering the safety mode. When the driver intends to turn off the wipers, the wipers will not fail to turn off due to the safety mode, thus improving software usability.

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

[0088] It should be noted that in this implementation, the shutdown request and the status flag are judged simultaneously. This way, the historical status flag judgment results will no longer affect the current judgment result. Therefore, even if there is a situation in the past where the safety flag is activated, the windshield wipers will not be unable to be turned off due to the safety mode when the driver intends to turn them off, thus improving the driver's driving experience.

[0089] In this embodiment, when the windshield wipers are on, if a fault-triggered shutdown request is received, a safety mode is activated. In safety mode, both a wiper control request and the driver's intention are received. If the wiper control request is a shutdown request and the driver's intention is also to turn off the wipers, the safety mode is exited, and the wipers are turned off based on the wiper control request. Thus, in safety mode, by detecting the driver's intention and controlling whether to turn off the wipers based on that intention, the wipers are ensured not to shut off unexpectedly during driving, and the wipers are not prevented from being turned off due to safety mode or other reasons when the driver intends to do so, thus optimizing the driving experience.

[0090] Regarding whether a received shut-off request is a fault-triggered shut-off request, in some embodiments, the vehicle can automatically detect whether a fault has occurred in the software or hardware system of the wiper control system. If a fault occurs, a fault report is generated. When the vehicle receives a fault report, if a shut-off request is received, it is determined that the shut-off request is a fault-triggered shut-off request. In some embodiments, the vehicle can also combine information such as vehicle fault information and the status of the wiper control lever to determine whether the received shut-off request is a fault-triggered shut-off request. See also Figure 4 The diagram illustrates a flowchart of a windshield wiper control method provided by an exemplary embodiment. By way of example and not limitation, the method is applied to a vehicle configured with the aforementioned windshield wiper control system.

[0091] S401: When the windshield wipers are on, if a request to turn them off is received, the status of the wiper control lever and vehicle fault information are obtained.

[0092] The wiper control lever has several states, including off and on. This state can be triggered manually by the driver, or via voice command, touchscreen, etc. This embodiment does not specifically limit the triggering method. The fault information includes wiper motor status, power status, and battery usage mode.

[0093] S402, if the wiper control lever is in a non-off state and the fault information indicates that the vehicle has not malfunctioned, the vehicle determines that the closing request is a fault-triggered closing request.

[0094] The vehicle can determine whether the shutdown request is a fault-triggered shutdown request based on the wiper control lever, or based on whether the vehicle is malfunctioning. If the shutdown request is triggered by the wiper control lever, or if the shutdown request is triggered due to a vehicle malfunction, the shutdown request is considered an expected shutdown request; otherwise, the shutdown request is a fault-triggered shutdown request.

[0095] When the wiper control lever is in the off state, the vehicle can determine that the closing request was not initiated by the driver. The vehicle then proceeds to determine whether the closing request was triggered by a vehicle malfunction. In some embodiments, the malfunction information includes wiper motor status, power status, and battery usage mode. This step includes: if the wiper control lever is in the off state, the wiper motor status indicates that the motor is not stalled, the power status indicates that the vehicle is not powered off, and the battery usage mode indicates that the vehicle is not in power-saving mode, then the closing request is determined to be an invalid closing request.

[0096] S403, if the wiper control lever is in the off state, or the fault information indicates that the vehicle has malfunctioned, the vehicle determines that the closing request is the expected closing request.

[0097] When the wiper control lever is in the off state, the vehicle can determine that the closing request was initiated by the driver, or that the closing request was triggered by a vehicle malfunction, and thus determine that the closing request is a valid closing request. In some embodiments, the malfunction information includes wiper motor status, power status, and battery usage mode; this step includes: if the wiper control lever is in the off state, or the wiper motor status indicates that the motor is stalled, or the power status indicates that the vehicle is powered down, or the battery usage mode indicates that the vehicle is in power-saving mode, then determine that the closing request is a valid closing request.

[0098] In this embodiment, the order in which the vehicle determines the state of the windshield wiper arm and whether the vehicle is malfunctioning is not specifically limited. The vehicle may first determine the state of the windshield wiper arm and then determine whether the vehicle is malfunctioning; the vehicle may also first determine whether the vehicle is malfunctioning and then determine the state of the windshield wiper arm; or the vehicle may simultaneously determine both the state of the windshield wiper arm and whether the vehicle is malfunctioning.

[0099] In this implementation, the validity of the request to turn off the wipers is determined by combining the status of the wiper arm and the vehicle's fault information. At the same time, the driver's intention and the vehicle's fault information are monitored to ensure that if the monitoring conditions or the driver's intention no longer meet the requirements for turning on the wipers when the fault disappears, the wipers can be turned off.

[0100] S404, Vehicle Startup Safety Mode.

[0101] This step is based on the same principle as step S301, and will not be repeated here.

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

[0103] This step is based on the same principle as step S302, and will not be repeated here.

[0104] S406, if the wiper control request is a turn-off request and the driver's intention is to turn off the wipers, the vehicle exits the safety mode and turns off the wipers based on the wiper control request.

[0105] This step is based on the same principle as step S303, and will not be repeated here.

[0106] In this embodiment, when the windshield wipers are on, if a fault-triggered shutdown request is received, a safety mode is activated. In safety mode, both a wiper control request and the driver's intention are received. If the wiper control request is a shutdown request and the driver's intention is also to turn off the wipers, the safety mode is exited, and the wipers are turned off based on the wiper control request. Thus, in safety mode, by detecting the driver's intention and controlling whether to turn off the wipers based on that intention, the wipers are ensured not to shut off unexpectedly during driving, and the wipers are not prevented from being turned off due to safety mode or other reasons when the driver intends to do so, thus optimizing the driving experience.

[0107] It should be understood that the sequence number of each step in the above embodiments does not imply 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 this application.

[0108] Figure 5 This is a schematic diagram of a vehicle provided in an exemplary embodiment of this application. (As shown...) Figure 5As shown, the vehicle 5 in 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 windshield wiper control program. When the processor 50 executes the computer program 52, it implements the steps in the various windshield wiper control method embodiments described above, for example... Figure 3 The steps S301 to S303 are shown. Alternatively, when the processor 50 executes the computer program 52, it implements the functions of each unit in the above-described device embodiments, for example... Figure 1 The functions of units 10 to 30 are shown.

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

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

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

[0112] The arbitration module 30 is used to generate and output a wiper control command based on the wiper control request and the state of the safety mode. The vehicle 5 can be any vehicle with control functions. The vehicle 5 may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art will understand that... Figure 5 This is merely an example of vehicle 5 and does not constitute a limitation on vehicle 5. It may include more or fewer components than shown, or combine certain components, or different components. For example, vehicle 5 may also include input / 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 (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), 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.

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

[0115] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to 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 embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0116] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0117] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0118] In the embodiments provided in this 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 merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0120] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0121] If the integrated module / unit is implemented as 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, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed 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 electrical carrier signals and telecommunication signals.

[0122] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the above method embodiments.

[0123] This application also provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the various method embodiments above.

[0124] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A windshield wiper control method, characterized in that, The method includes: If a shutdown request is received due to a software or hardware malfunction in the wiper control system while the wipers are on, a safety mode will be activated. In safe mode, if a wiper control request is received, the status of the wiper control lever and vehicle fault information are obtained to determine the driver's intention. The determination of the driver's intent includes: If the wiper control lever is in the off state, or the fault information indicates that the vehicle has malfunctioned, then the driver's intention is determined to be to turn off the wipers. If the wiper control lever is in the on state and the fault information indicates that the vehicle has not malfunctioned, then the driver's intention is determined to be to turn on the wipers. If the wiper control request is a turn-off request and the driver's intention is to turn off the wipers, exit the safety mode and turn off the wipers based on the wiper control request to prevent the wipers from turning off unexpectedly during driving.

2. The method as described in claim 1, characterized in that, The fault information includes wiper motor status, power status, and battery usage mode; if the fault information indicates that the vehicle has malfunctioned, determining that the driver's intention is to turn off the wiper includes: If the wiper motor status indicates that the motor is stalled, or the power status indicates that the vehicle is powered off, or the battery usage mode indicates that the vehicle is in power-saving mode, then the driver's intention is determined to be an intention to turn off the wiper.

3. A windshield wiper control system for preventing windshield wipers from unexpectedly shutting off during driving, characterized in that, The system includes: a wiper function calculation module, a wiper status monitoring module, and an arbitration module; The wiper function calculation module is used to obtain wiper control lever status information, vehicle fault information, and vehicle mode information; based on the wiper control lever status information, vehicle fault information, and vehicle mode information, determine the wiper control request; and send the wiper control request to the wiper status monitoring module. The wiper status monitoring module is used to receive the wiper control request, obtain wiper control lever status information and vehicle fault information; determine the driver's intention based on the wiper control lever status information and vehicle fault information; determine the status of the safety mode based on the driver's intention and the wiper control request; and send the wiper control request and the status of the safety mode to the arbitration module. The safety mode is activated when the wipers are on, if a shutdown request triggered by a software or hardware fault in the wiper control system is received. The arbitration module is used to generate wiper control commands based on the wiper control request and the status of the safety mode, and output the wiper control commands. The determination of the driver's intention includes: if the wiper control lever status information is in the off state, or the fault information indicates that the vehicle has malfunctioned, then the driver's intention is to turn off the wipers; if the wiper control lever status information is in the on state and the fault information indicates that the vehicle has not malfunctioned, then the driver's intention is to turn on the wipers. The determination of the safety mode state includes: if the wiper control request is a turn-off request and the driver's intention is to turn off the wipers, then the safety mode is determined to be off, so as to allow the wipers to be turned off based on the wiper control request.

4. The system as described in claim 3, characterized in that, The fault information includes wiper motor status, power status, and battery usage mode. The wiper status monitoring module is used to determine that the safety mode is off if the wiper motor status indicates that the motor is stalled, the power status indicates that the vehicle is powered off, the battery usage mode indicates that the vehicle is in power-saving mode, or the wiper control lever status is off.

5. The system as described in claim 3 or 4, characterized in that, The arbitration module is used to output a wiper off command when the safety mode is off and the wiper control request is an off request.

6. The system as described in claim 3, characterized in that, The fault information includes wiper motor status, power status, and battery usage mode. The wiper status monitoring module is used to determine that the safety mode is enabled if the wiper motor status indicates that the motor is not stalled, the power status indicates that the vehicle is powered on, the battery usage mode indicates that the vehicle is not in power-saving mode, the wiper control lever is in the on state, and the wiper control request is a shutdown request.

7. A vehicle, characterized in that, The vehicle includes a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the wiper control method as described in claim 1 or 2.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the wiper control method as described in claim 1 or 2.

Images