Windscreen wiper fault detection method, device and system and vehicle
By detecting whether the wiper can rotate and set angle when the vehicle is started, determining its fault status and automatically restarting, the problem of insufficient usability caused by the system module failure of the wiper is solved, ensuring the reliability and user safety of the wiper.
Patent Information
- Application Number
- CN202411404061.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-09
- Publication Date
- 2024-12-06
AI Technical Summary
In the prior art, the wiper has insufficient availability due to system module failure, making it difficult for users to know the fault condition, which may be unavailable during use.
When the vehicle is started, by sending instructions to the electronic wiper module, check whether the wiper can rotate and set angle, determine whether the wiper has a fault based on the execution results, and automatically restart the wiper in the event of a fault to ensure its availability.
It realizes automatic detection of wiper failures when the vehicle starts, promptly reminds users and troubleshoots, ensuring the availability of wipers and overall system reliability, and avoiding users' ignorant failure use.
Smart Images

Figure CN119078704A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle technology, and in particular to a wiper fault detection method, device, system and vehicle. Background Art
[0002] In a vehicle equipped with a vehicle control system, the wipers usually send operating instructions from the control elements on the steering wheel of the vehicle to the controller in the vehicle, and the controller then sends corresponding action signals to the electronic wiper module. The electronic wiper module controls the state of the wipers according to the action signals.
[0003] According to the related technology, whether the wiper performs the wiping action is only controlled by the electronic wiper module. When any module between the electronic wiper module and the vehicle controller is abnormal, the operation of the wiper cannot be controlled by the control elements on the steering wheel, which leads to wiper failure. Users usually cannot know whether there is a wiper failure when driving the vehicle, which leads to insufficient wiper availability when users enable the wipers. Summary of the invention
[0004] The present application provides a wiper fault detection method, device, system and vehicle, which are used to solve the problem in the prior art that the wiper is easily prone to insufficient availability due to system module failure.
[0005] In a first aspect, the present application provides a wiper fault detection method, which is applied to a vehicle-mounted controller, the vehicle-mounted controller is connected to an electronic wiper module in the vehicle, the electronic wiper module is used to control the working state of the wiper in the vehicle, and the wiper fault detection method includes:
[0006] In response to the vehicle entering a power-on state, sending a first instruction to the electronic wiper module, wherein the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle, the electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return a first execution result of the first rotation signal to the vehicle controller, and the first signal is used to rotate the wiper to the set angle;
[0007] In response to a first execution result returned by the electronic wiper module, a first fault detection result of the wiper is determined, wherein the first fault detection result includes that the wiper is in a normal state, or that the wiper is in a fault state.
[0008] In a second aspect, the present application provides a wiper fault detection device, which is applied to a vehicle-mounted controller, the vehicle-mounted controller is connected to an electronic wiper module in the vehicle, and the electronic wiper module is used to control the working state of the wiper in the vehicle, including:
[0009] a control module, configured to send a first instruction to the electronic wiper module in response to the vehicle entering a power-on state, wherein the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle, the electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return a first execution result of the first rotation signal to the vehicle controller, wherein the first signal is used to rotate the wiper to the set angle;
[0010] The analysis module is used to determine a first fault detection result of the wiper in response to a first execution result returned by the electronic wiper module, wherein the first fault detection result includes that the wiper is in a normal state, or that the wiper is in a fault state.
[0011] In a third aspect, an embodiment of the present application provides a wiper control system, the wiper control system comprising: a controller, an electronic wiper module, and a wiper;
[0012] The controller is connected to the electronic wiper module and executes the wiper fault detection method of the first aspect and various possible designs of the first aspect;
[0013] The electronic wiper module is connected to the wiper and is used to control the working state of the wiper.
[0014] In a fourth aspect, an embodiment of the present application provides a vehicle, which includes the wiper control system provided in the third aspect of the present disclosure.
[0015] The wiper fault detection method, device, system and vehicle provided by the present application send a first instruction to the electronic wiper module when the vehicle enters the power-on state, and then determine the first fault detection result of the wiper according to the first execution result returned by the electronic wiper module. Thus, the wiper fault detection during the vehicle startup and power-on process is realized, and the detection process does not require user participation and is usually imperceptible to the user. It can not only pre-determine whether the wiper has a fault during the operation of the vehicle, so as to promptly remind the user of the possible fault of the wiper and perform fault processing, but also promptly determine the fault of the wiper so as to restart the wiper in time, thereby ensuring the availability of the wiper and the overall reliability of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0017] Figure 1 An application scenario diagram of the wiper fault detection method provided in an embodiment of the present application;
[0018] Figure 2 A flow chart of a wiper fault detection method provided in an embodiment of the present application;
[0019] Figure 3 A flow chart of a wiper fault detection method provided by yet another embodiment of the present application;
[0020] Figure 4a A flow chart of a wiper fault detection method provided by yet another embodiment of the present application;
[0021] Figure 4b for Figure 4a A flow chart of a method for determining a third fault detection result provided in the illustrated embodiment;
[0022] Figure 5a A flow chart of a wiper fault detection method provided by yet another embodiment of the present application;
[0023] Figure 5b for Figure 5a A flow chart of a method for determining a fault cause provided in the illustrated embodiment;
[0024] Figure 6 A schematic diagram of the structure of a wiper fault detection device provided in an embodiment of the present application;
[0025] Figure 7 A schematic diagram of the structure of a wiper control system provided in an embodiment of the present application.
[0026] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0027] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0028] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will be described below in conjunction with the accompanying drawings.
[0029] In the automotive-related field, in a vehicle equipped with a vehicle control system, the wipers usually send operating instructions from the control elements on the steering wheel of the vehicle to the controller in the vehicle, or based on the operating instructions generated by the vehicle controller according to the algorithm, the controller then sends the corresponding action signal to the electronic wiper module, and the electronic wiper module controls the state of the wipers according to the action signal.
[0030] According to the related technology, whether the wiper performs the wiping action is only controlled by the electronic wiper module. When any module between the electronic wiper module and the vehicle controller is abnormal, the operation of the wiper cannot be controlled by the control elements on the steering wheel, which leads to wiper failure. When the user is driving the vehicle, he usually cannot know whether the wiper has a fault, resulting in the wiper being unusable and insufficient in availability when the user enables the wiper.
[0031] In order to solve the above problems, the embodiments of the present invention provide a wiper fault detection method, device, car key and vehicle, which perform a wiper fault self-check when the vehicle is powered on, and determine whether the wiper has a fault based on the self-check result, so that the user can promptly understand the possible faults of the wiper and ensure the availability of the wiper and the system reliability.
[0032] The application scenarios of the embodiments of the present disclosure are explained below:
[0033] Figure 1 This is an application scenario diagram of the wiper fault detection method provided by the embodiment of the present disclosure. Figure 1 As shown, during the startup and operation of the vehicle 100 , the onboard controller 110 will detect the status of the wiper 130 through the electronic wiper module 120 so as to timely determine the availability of the wiper 130 and ensure the driving safety of the vehicle 100 .
[0034] It should be noted that Figure 1 In the scenario shown, only one vehicle, on-board controller, electronic wiper module and wiper are used as an example for illustration, but the present disclosure is not limited to this, that is, the number of vehicles, on-board controllers, electronic wiper modules and wipers can be arbitrary.
[0035] The wiper fault detection method provided by the present disclosure is described in detail below through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.
[0036] Figure 2 Flow chart of a wiper fault detection method provided by an embodiment of the present application. Figure 2As shown, it is applied to a vehicle controller, the vehicle controller is connected to an electronic wiper module in the vehicle, and the electronic wiper module is used to control the working state of the wiper in the vehicle, including but not limited to the following steps:
[0037] Step S201: In response to the vehicle entering a power-on state, sending a first instruction to an electronic wiper module.
[0038] Among them, the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle. The electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return the first execution result of the first rotation signal to the vehicle controller. The first signal is used to rotate the wiper to a set angle.
[0039] Specifically, when the vehicle is powered on, it will automatically trigger the detection of whether the wiper has a fault, and promptly determine whether the wiper has a fault, such as the wiper motor cannot work. This process is also the startup self-check process of the wiper.
[0040] The specific implementation method of starting the self-test is that the vehicle-mounted controller generates a pre-configured first instruction and sends the first instruction to the electronic wiper module, and the electronic wiper module controls the wiper motor to drive the wiper to rotate. The electronic wiper module can determine the first execution result corresponding to the first instruction according to whether the wiper is rotated, so that the vehicle-mounted controller can determine whether the wiper is normal according to the first execution result.
[0041] In some embodiments, the first execution result only needs to include whether the wiper has rotated, but does not need to include whether the wiper has rotated a set angle corresponding to the first instruction. Because in actual operation, the wiper itself will not rotate only a specific angle, but will swing back and forth within a fixed range. Therefore, it is less practical to detect whether it can rotate a certain set angle, and it is only necessary to ensure that it can rotate according to the first instruction.
[0042] Step S202: In response to a first execution result returned by the electronic wiper module, determining a first fault detection result of the wiper.
[0043] The first fault detection result includes that the wiper is in a normal state, or that the wiper is in a fault state.
[0044] Specifically, the electronic wiper module will generate a corresponding first execution result according to whether the wiper is rotating, and the vehicle controller will determine whether the wiper is faulty according to the first execution result. This determination result is the first fault detection result.
[0045] In some embodiments, if the first fault detection result is that the wiper is normal, the vehicle-mounted controller will only record the detection result and will not notify the driver in the vehicle. The entire detection result is completed without the driver's perception and the availability of the wiper is ensured.
[0046] In some embodiments, if the first fault detection result is that the wiper is abnormal, the on-board controller can directly control the wiper (motor) to restart through the electronic wiper module to achieve direct and rapid processing of the wiper fault. If the wiper is normal after restarting (the self-test process can be started again), the on-board controller only needs to record the detection result without notifying the driver on the vehicle; if the wiper is still abnormal after restarting, the on-board controller can report to the cloud server and the driver to remind the driver to repair the wiper in time to ensure its availability.
[0047] The wiper fault detection method provided in this embodiment sends a first instruction to the electronic wiper module when the vehicle enters the power-on state, and then determines the first fault detection result of the wiper according to the first execution result returned by the electronic wiper module. Thus, the wiper fault detection during the vehicle startup and power-on process is realized, and the detection process does not require user participation and is usually imperceptible to the user. It can not only pre-determine whether the wiper has a fault during the operation of the vehicle, so as to promptly remind the user of the possible fault of the wiper and perform fault processing, but also promptly determine the fault of the wiper so as to restart the wiper in time, thereby ensuring the availability of the wiper and the overall reliability of the system.
[0048] Figure 3 The process of the wiper fault detection method provided in the embodiment of the present application Figure 2 .like Figure 3 As shown, the wiper fault detection method comprises the following steps:
[0049] Step S301: in response to the vehicle entering a power-on state, sending a first instruction to an electronic wiper module.
[0050] Among them, the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle. The electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return the first execution result of the first rotation signal to the vehicle controller. The first signal is used to rotate the wiper to a set angle.
[0051] Specifically, this embodiment further explains in detail the wiper self-check process during vehicle startup and power-on in the wiper fault detection method.
[0052] In some embodiments, the angle is set to an angle value less than 2 degrees.
[0053] Specifically, in order to make the wiper self-check action during the vehicle startup and power-on process imperceptible to the driver, and the self-check process requires the wiper to perform a rotation action, the set angle contained in the first instruction is usually as small as possible, preferably not exceeding 2 degrees. For example, any angle from 0.5 degrees to 1 degree can be selected.
[0054] Step S302: If the first execution result is that the wiper has executed a rotation action, determine that the first fault detection result of the wiper is a normal state.
[0055] Specifically, as long as the wiper rotates, it can be determined that the wiper is in a normal state.
[0056] In some embodiments, the electronic wiper module itself is configured with a function of detecting whether the wiper is rotating, which can be determined by detecting whether the current signal remains fixed during the process of inputting the current signal to the motor of the wiper. If the current signal remains fixed, it means that the motor has normally performed the rotation action after receiving the current signal and has driven the wiper to rotate.
[0057] In some embodiments, depending on the different configuration functions of the vehicle, a sensor for monitoring the rotation of the wiper, such as an angle sensor, may also be configured in the electronic wiper module to determine whether the wiper is rotating, which is not limited here.
[0058] Step S303: If the first execution result is that the wiper does not perform the rotation action, determine that the first fault detection result of the wiper is a fault state.
[0059] Specifically, if after sending the first instruction, the first execution result fed back by the on-board controller is that the wiper does not perform the rotation action, it can be determined that the result corresponding to this self-test (ie, the first fault detection result) is a fault state.
[0060] In some embodiments, if the vehicle controller does not receive the first execution result after sending the first instruction, it can confirm that the self-test result is that the electronic wiper module is in a faulty state, and issue a restart instruction to the electronic wiper module to try to restore the state of the electronic wiper module. If the electronic wiper module cannot be restored to normal, it is necessary to record the fault information of the electronic wiper module and send the fault information to the driver (such as displaying the fault information on the central control screen).
[0061] Step S304: Send a second instruction to the electronic wiper module.
[0062] The second instruction is used to instruct the electronic wiper module to control the wiper to restart.
[0063] Specifically, when the first fault detection result is that the wiper is in a faulty state, the on-board sensor can directly send a second instruction to the electronic wiper module to try to restart the wiper.
[0064] In some embodiments, the wiper may be restarted by disconnecting and reconnecting the wiper motor, or by other methods, which are not limited here.
[0065] Step S305: Send a third instruction to the electronic wiper module.
[0066] The third instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle after restarting.
[0067] Specifically, if the wiper is restarted successfully, a third instruction may be sent to the electronic wiper module (therefore, the third instruction is usually sent after a set time interval, such as 1 second or 2 seconds, after the second instruction) to perform self-check again.
[0068] The content of the third instruction may be the same as or different from that of the first instruction. For example, the set rotation angle may be another angle value different from that of the first instruction. There is no limitation here.
[0069] Step S306: If the second execution result corresponding to the third instruction is that the wiper has performed a rotation action, determine that the second fault detection result of the wiper is a normal state.
[0070] Specifically, if the detection result based on the third instruction is that the wiper is normal, then the wiper self-test result of the vehicle power-on startup process (that is, the first fault detection result) can also be considered that the wiper is in a normal state, and the results of the two tests are recorded in the log file to distinguish them from the detection results in step S302, so as to facilitate subsequent maintenance of the wiper according to the log file.
[0071] Step S307: if the second execution result corresponding to the third instruction is that the wiper does not perform the rotation action, determine that the second fault detection result of the wiper is a fault state.
[0072] Specifically, if the detection result based on the third instruction is still a wiper fault, the wiper may be in a faulty state and the fault cannot be resolved by restarting itself.
[0073] Step S308: Generate alarm information based on the fault status, and send the alarm information to the user interaction interface in the vehicle.
[0074] Specifically, when the second fault detection result is that the wiper is in a faulty state, the on-board controller needs to send the information corresponding to the fault state in the form of an alarm message to the user (that is, displayed on the vehicle user interaction interface) and the cloud server (which can then be sent by the cloud server to the user's smart terminal application so that the user can understand the fault information).
[0075] The wiper fault detection method provided in this embodiment, during the vehicle power-on startup process, uses the first instruction to make the electronic wiper module drive the wiper to rotate, so as to perform self-checking, and automatically restarts when the wiper fails, and performs fault detection again, and then notifies the driver of the corresponding alarm information of the fault. In this way, the wiper status can be quickly and effectively confirmed when the vehicle is started, and its availability can be guaranteed by automatic restarting, and the fault information can be promptly notified to the driver, so that maintenance and other methods can be taken in time to ensure the availability of the wiper, thereby ensuring the driving safety and reliability of the vehicle.
[0076] Figure 4a The process of the wiper fault detection method provided in the embodiment of the present application Figure 2 .like Figure 4a As shown, the wiper fault detection method comprises the following steps:
[0077] Step S401: In response to the vehicle entering a power-on state, sending a first instruction to an electronic wiper module.
[0078] Step S402: determining a first fault detection result of the wiper in response to a first execution result returned by the electronic wiper module.
[0079] Specifically, this embodiment further explains in detail the wiper fault detection process during the driving process after the vehicle is started and powered on in the wiper fault detection method.
[0080] Step S401 to step S402 and Figure 2 The corresponding steps in the illustrated embodiment are the same in content and will not be described again here.
[0081] Step S403: Send a fourth instruction to the electronic wiper module.
[0082] Among them, the fourth instruction is used to instruct the electronic wiper module to control the wiper to switch to the wiping state. The wiping state is used to indicate the state in which the wiper completes a single wiping action or continuously completes the wiping action. The electronic wiper module is used to feedback the third execution result corresponding to the fourth instruction and the status information of the wiper corresponding to the fourth instruction to the vehicle controller.
[0083] Specifically, when the first fault detection result is that the wiper is in a normal state, when the user controls the wiper to work or the vehicle-mounted controller determines that the wiper needs to be controlled to work (such as automatically adjusting the working state of the wiper when it is detected that it is raining outside), the vehicle-mounted controller will also detect and determine whether there is a fault with the wiper.
[0084] Therefore, before detection and judgment, it is necessary to send a command to control the wiper to work, that is, the vehicle controller receives the fourth command for adjusting the wiper state triggered by the user through the control on the steering wheel (such as a button or a paddle or an adjustment lever), or the vehicle controller automatically sends the fourth command to the electronic wiper module when judging that the external environment requires the wiper to start working. At this time, the detection of whether the wiper is faulty will be triggered.
[0085] Step S404: determine the state information and the vehicle state, and determine the enabling state of the electronic wiper module.
[0086] The enabling state includes an action-supporting state and an action-unsupporting state. The action-supporting state is used to indicate that the wiper has the ability to complete the wiping action, and the action-unsupporting state is used to indicate that the wiper does not have the ability to complete the wiping action.
[0087] Specifically, before performing wiper status detection, it is also necessary to determine the enabling state of the electronic wiper module, that is, to determine whether the electronic wiper module can rotate the wiper (that is, whether the wiper is in a state capable of completing the wiping action).
[0088] If the electronic wiper module is in a state that does not support action, the electronic wiper module cannot control the wiper action, cannot determine whether the wiper is faulty, and fault detection is actually impossible. Therefore, it is necessary to first determine whether the electronic wiper module is in a state that supports action.
[0089] Furthermore, the specific method for determining the enabling state is as follows:
[0090] If the input current is non-zero and the vehicle is in a powered-on state, the enable state of the electronic wiper module is determined to be a supported action state; or, if the input current is zero and / or the vehicle is in a powered-off state, the enable state of the electronic wiper module is determined to be a non-supported action state.
[0091] Specifically, the enabling state of the electronic wiper module can be determined by combining the input current of the electronic wiper module to the wiper motor and the current power-on state of the vehicle.
[0092] Step S405: Determine the blocked state of the wiper based on the state information.
[0093] The blocked state includes a normal state and an abnormal state. The abnormal state is used to indicate that the wiper is unable to rotate, and the normal state is used to indicate that the wiper is rotating normally.
[0094] Specifically, in addition to the enabling state of the electronic wiper module, it is also necessary to determine the blocked state of the wiper, such as whether there is an object on the window glass blocking the wiper rotation. If there is an object blocking the wiper, it is an abnormal state, otherwise it is a normal state.
[0095] If the wiper is in an abnormal state, even if the fourth instruction is sent to the electronic wiper module, it is impossible to determine whether there is a fault based on the rotation of the wiper. Therefore, it is necessary to first ensure that the blocked state of the wiper is normal.
[0096] Furthermore, the method for determining the wiper blocking state is as follows:
[0097] If the input current continues to increase within a set time period, it is determined that the wiper is in an abnormal state; or, if the output current remains unchanged within a set time period, it is determined that the wiper is in a normal state.
[0098] Specifically, when the wiper is blocked and cannot rotate (i.e., it is in an abnormal state), the electronic wiper module will automatically input a larger current to the wiper's rotating motor to enable the wiper to complete the rotation action normally. Therefore, if the input current continues to increase, it means that the wiper is in an abnormal state. Conversely, if the input current remains unchanged, it means that the wiper is in a normal rotation state (i.e., normal state).
[0099] Step S406: Determine a third fault detection result of the wiper based on the enabled state, the locked-rotor state and the third execution result.
[0100] The third fault detection result includes that the wiper is in a normal state, or that the wiper is in a fault state.
[0101] Specifically, after determining the corresponding states of the electronic wiper module and the wiper, fault detection of the wiper can be performed in combination with the third execution result corresponding to the fourth instruction.
[0102] Furthermore, if Figure 4b As shown, it is a flow chart of a method for determining a third fault detection result, which includes the following steps:
[0103] Step S4061: Determine that the enabling state is the supporting action state and the stalling state is the normal state.
[0104] Specifically, as analyzed above, before performing fault detection, it is necessary to first ensure that the enabling state of the electronic wiper module is in the supporting action state and the blocked state of the wiper is in the normal state. Only then will the fault detection result be reliable.
[0105] Step S4062: If the third execution result is that the wiper has executed a rotation action, determine that the third fault detection result of the wiper is a normal state.
[0106] Specifically, when the above conditions are met, the judgment on whether the wiper has a fault is the same as the fault judgment principle during the wiper self-test during the vehicle power-on process. As long as the wiper can perform the rotation action normally, it can be determined that the wiper is in a normal state.
[0107] Step S4063: If the third execution result is that the wiper does not perform the rotation action, determine that the third fault detection result of the wiper is a fault state.
[0108] Specifically, similarly, if the wiper cannot rotate normally when the aforementioned conditions are met, it can be determined that the wiper is in a faulty state.
[0109] Step S407: Send a second instruction to the electronic wiper module.
[0110] The second instruction is used to instruct the electronic wiper module to control the wiper to restart.
[0111] Specifically, if the third fault detection result is that the wiper is in a faulty state, you can also try to restart the wiper (i.e. send the second instruction). If the restart fails, the alarm information corresponding to the fault signal is sent to the user and the cloud server. If the restart is successful, the fault detection result is recorded. The corresponding process is the same as the corresponding steps in the previous embodiment, and will not be repeated here.
[0112] The wiper fault detection method provided in this embodiment can also detect the wiper fault after the wiper self-check is completed during the vehicle power-on startup process, and when the wiper is started during vehicle operation. Therefore, when the wiper has a fault, it can automatically restart to try to solve the fault, improve the wiper availability, ensure vehicle safety and reliability, and can transmit fault information to the user and cloud server in a timely manner, so as to facilitate the inspection and maintenance of the wiper.
[0113] Figure 5a The process of the wiper fault detection method provided in the embodiment of the present application Figure 2 .like Figure 5a As shown, the wiper fault detection method comprises the following steps:
[0114] Step S501: in response to the vehicle entering a power-on state, sending a first instruction to an electronic wiper module.
[0115] Step S502: In response to a first execution result returned by the electronic wiper module, determining a first fault detection result of the wiper.
[0116] Specifically, this embodiment further illustrates the fault cause analysis process based on wiper fault detection based on the previous embodiment.
[0117] Step S501 to step S502 and Figure 2 The corresponding steps in the illustrated embodiment are the same in content and will not be described again here.
[0118] Step S503: Record the command information sent by the vehicle controller to the electronic wiper module and the execution result information fed back by the electronic wiper module in a log file.
[0119] The instruction information includes a first instruction, and the execution result information includes a first execution result.
[0120] Specifically, the command information sent by the vehicle-mounted controller to the electronic wiper during the wiper detection process (including the first to fourth instructions in the aforementioned embodiment), and the execution result information of the electronic wiper module based on the wiper status feedback (including the first to third execution results in the aforementioned embodiment) will be recorded in real time in the log file by the vehicle-mounted controller, so that the fault condition and cause of the wiper can be judged according to the log file, which is convenient for inspection and maintenance.
[0121] Step S504: If the wiper is in a fault state, determine the fault cause corresponding to the fault state based on the instruction information and execution result information in the log file.
[0122] Specifically, when the wiper is in a faulty state, the cause of the fault can be automatically determined based on the log file.
[0123] Furthermore, if Figure 5b As shown, it is a flow chart of a method for determining the cause of a fault, which includes the following steps:
[0124] Step S5041: Determine whether the wiper is in a faulty state.
[0125] Specifically, the automatic fault cause determination process here is a process that is automatically performed when the wiper is in a faulty state. Its purpose is to facilitate maintenance personnel and users to understand the specific situation of the wiper in a timely manner, and to facilitate subsequent inspections and repairs.
[0126] Step S5042: If the log file includes instruction information but does not include execution result information, it is determined that the cause of the fault is a fault in the electronic wiper module.
[0127] Specifically, when there is a fault in the wiper, and the on-board controller has sent corresponding command information to the electronic wiper module, but the on-board controller has not received corresponding feedback from the electronic wiper module (the corresponding relationship can be judged by the timestamp of the corresponding information in the log file), it can be automatically judged that there is a fault in the electronic wiper module.
[0128] Step S5043: If the log file does not include instruction information, it is determined that the cause of the fault is a fault in the vehicle controller.
[0129] Specifically, in another case, if the driver sends a wiper control instruction to the vehicle controller, but the log file does not record the instruction information sent by the vehicle controller (the log file will record the instruction information issued by the driver), it can be determined that the corresponding module in the vehicle controller is faulty.
[0130] In some embodiments, if the log file contains instruction information and execution result information, it can be determined that the wiper itself (including its corresponding motor) has a fault.
[0131] The wiper fault detection method provided in this embodiment records the command information and execution result information in the wiper fault detection process through a log file, so as to automatically determine the cause of the fault when the wiper is in a fault state. Thus, when the wiper is in a fault state, the fault information can be automatically determined so as to transmit the fault information to the cloud server and the driver, which is convenient for timely and rapid inspection and maintenance of the wiper.
[0132] Figure 6 This is a schematic diagram of the structure of the wiper fault detection device provided in the embodiment of the present application. Figure 6 As shown, the wiper fault detection device 600 is applied to a vehicle-mounted controller, which is connected to an electronic wiper module in the vehicle. The electronic wiper module is used to control the working state of the wiper in the vehicle, and includes: a control module 610 and an analysis module 620;
[0133] The control module 610 is used to send a first instruction to the electronic wiper module in response to the vehicle entering a power-on state, wherein the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle, and the electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return a first execution result of the first rotation signal to the vehicle controller, and the first signal is used to rotate the wiper to the set angle;
[0134] The analysis module 620 is used to determine a first fault detection result of the wiper in response to a first execution result returned by the electronic wiper module, wherein the first fault detection result includes that the wiper is in a normal state, or that the wiper is in a fault state.
[0135] In some embodiments, the control module 610 specifically includes setting the angle to an angle value less than 2 degrees.
[0136] In some embodiments, the analysis module 620 is specifically used to determine that the first fault detection result of the wiper is a normal state if the first execution result is that the wiper has performed a rotation action; if the first execution result is that the wiper has not performed a rotation action, determine that the first fault detection result of the wiper is a fault state.
[0137] In some embodiments, the analysis module 620 is also used to, if the first execution result is that the wiper does not perform a rotation action, after determining that the first fault detection result of the wiper is a fault state, send a second instruction to the electronic wiper module, the second instruction is used to instruct the electronic wiper module to control the wiper to restart; send a third instruction to the electronic wiper module, wherein the third instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle after the restart; if the second execution result corresponding to the third instruction is that the wiper performs a rotation action, determine that the second fault detection result of the wiper is a normal state; if the second execution result corresponding to the third instruction is that the wiper does not perform a rotation action, determine that the second fault detection result of the wiper is a fault state; based on the fault state, generate an alarm message, and send the alarm message to the user interaction interface in the vehicle.
[0138] In some embodiments, the analysis module 620 is further used to, in response to the execution result returned by the electronic wiper module, after determining the fault detection result of the wiper, send a fourth instruction to the electronic wiper module, wherein the fourth instruction is used to instruct the electronic wiper module to control the wiper to switch to the wiping state, and the wiping state is used to indicate the state in which the wiper completes a single wiping action or the state in which the wiper continuously completes the wiping action, and the electronic wiper module is used to feed back to the vehicle controller the third execution result corresponding to the fourth instruction and the state information of the wiper corresponding to the fourth instruction; determine the state information and the vehicle state, and determine the enabling state of the electronic wiper module, wherein the enabling state includes supporting the dynamic The supported action state is used to indicate that the wiper has the ability to complete the wiping action, and the unsupported action state is used to indicate that the wiper does not have the ability to complete the wiping action; based on the state information, the blocked state of the wiper is determined, wherein the blocked state includes a normal state and an abnormal state, wherein the abnormal state is used to indicate that the wiper is in a state where it cannot rotate, and the normal state is used to indicate that the wiper is in a state where it rotates normally; based on the enabled state, the blocked state and the third execution result, a third fault detection result of the wiper is determined, wherein the third fault detection result includes that the wiper is in a normal state, or that the wiper is in a faulty state.
[0139] In some embodiments, the analysis module 620 is specifically used to, if the execution status information includes the input current of the motor corresponding to the wiper, if the input current is non-zero, and the vehicle is in a powered-on state, determine that the enable state of the electronic wiper module is a supported action state; or, if the input current is zero, and / or the vehicle is in a powered-off state, determine that the enable state of the electronic wiper module is a non-supported action state.
[0140] In some embodiments, the analysis module 620 is specifically used to determine that the wiper is in an abnormal state if the input current continues to increase within a set time period; or, if the output current remains unchanged within a set time period, determine that the wiper is in a normal state.
[0141] In some embodiments, the analysis module 620 is specifically used to determine that the enabled state is a supporting action state and the blocked state is a normal state; if the third execution result is that the wiper has performed a rotation action, determine that the second fault detection result of the wiper is a normal state; if the third execution result is that the wiper has not performed a rotation action, determine that the second fault detection result of the wiper is a fault state.
[0142] In some embodiments, the analysis module 620 is further configured to send a second instruction to the electronic wiper module after determining that the second fault detection result of the wiper is a fault state if the third execution result is that the wiper does not perform the rotation action.
[0143] In some embodiments, the analysis module 620 is also used to record the command information sent by the vehicle-mounted controller to the electronic wiper module and the execution result information fed back by the electronic wiper module in a log file, wherein the command information includes a first command, and the execution result information includes a first execution result; if the wiper is in a fault state, determine the fault cause corresponding to the fault state based on the command information and execution result information in the log file.
[0144] In some embodiments, the analysis module 620 is specifically used to determine whether the wiper is in a faulty state; if the log file includes instruction information but does not contain execution result information, the cause of the fault is determined to be a fault in the electronic wiper module; if the log file does not include instruction information, the cause of the fault is determined to be a fault in the vehicle controller.
[0145] The wiper fault detection device provided in the embodiment of the present application can be used to implement the technical solution of the wiper fault detection method in the above embodiment. Its implementation principle and technical effect are similar and will not be repeated here.
[0146] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, the control module 610 can be a separately established processing element, or it can be integrated in a chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The function of the above control module 610. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.
[0147] Figure 7 A schematic diagram of a wiper control system provided in an embodiment of the present application is shown in FIG. Figure 7 As shown, the wiper control system 700 includes: a controller 710 , an electronic wiper module 720 , and a wiper 730 .
[0148] The controller 710 is connected to the electronic wiper module 720 and executes the wiper fault detection method shown in the above embodiment;
[0149] The electronic wiper module 720 is connected to the wiper 730 and is used to control the working state of the wiper 730 .
[0150] The relevant instructions can be understood by referring to the relevant descriptions and effects corresponding to the method embodiments, which will not be repeated here.
[0151] An embodiment of the present application provides a vehicle, which includes the wiper control system provided in the above embodiment.
[0152] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.
[0153] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0154] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.
[0155] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.
[0156] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. If not specifically stated, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. If not specifically stated, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.
[0157] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.
[0158] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0159] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.
[0160] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
Claims
1. A wiper fault detection method, characterized in that: Applied to a vehicle-mounted controller, the vehicle-mounted controller is connected to an electronic wiper module in the vehicle, and the electronic wiper module is used to control the working state of the wiper in the vehicle, including: In response to the vehicle entering a power-on state, sending a first instruction to the electronic wiper module, wherein the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle, the electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return a first execution result of the first rotation signal to the on-board controller, wherein the first signal is used to make the wiper rotate to the set angle; In response to a first execution result returned by the electronic wiper module, a first fault detection result of the wiper is determined, wherein the first fault detection result includes that the wiper is in a normal state, or that the wiper is in a fault state.
2. The method according to claim 1, characterized in that: The set angle is an angle value less than 2 degrees.
3. The method according to claim 1, characterized in that: The step of determining a fault detection result of the wiper in response to a first execution result returned by the electronic wiper module comprises: If the first execution result is that the wiper has performed a rotation action, determining that the first fault detection result of the wiper is a normal state; If the first execution result is that the wiper does not perform the rotation action, it is determined that the first fault detection result of the wiper is a fault state.
4. The method according to claim 3, characterized in that If the first execution result is that the wiper does not perform the rotation action, after determining that the first fault detection result of the wiper is a fault state, the method further includes: Sending a second instruction to the electronic wiper module, wherein the second instruction is used to instruct the electronic wiper module to control the wiper to restart; Sending a third instruction to the electronic wiper module, wherein the third instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle after the restart is completed; If the second execution result corresponding to the third instruction is that the wiper has performed a rotation action, determining that the second fault detection result of the wiper is a normal state; If the second execution result corresponding to the third instruction is that the wiper does not perform the rotation action, determining that the second fault detection result of the wiper is a fault state; Based on the fault status, an alarm message is generated and sent to a user interaction interface in the vehicle.
5. The method according to any one of claims 1 to 4, characterized in that After determining the fault detection result of the wiper in response to the execution result returned by the electronic wiper module, the method further includes: Sending a fourth instruction to the electronic wiper module, wherein the fourth instruction is used to instruct the electronic wiper module to control the wiper to switch to a wiping state, wherein the wiping state is used to indicate a state in which the wiper completes a single wiping action or a state in which the wiper continuously completes the wiping action, and the electronic wiper module is used to feed back to the vehicle controller a third execution result corresponding to the fourth instruction and state information of the wiper corresponding to the fourth instruction; Determine the state information and the vehicle state, and determine the enabling state of the electronic wiper module, wherein the enabling state includes a supporting action state and a non-supporting action state, the supporting action state is used to indicate that the wiper has the ability to complete the wiping action, and the non-supporting action state is used to indicate that the wiper does not have the ability to complete the wiping action; Based on the state information, determining a blocked state of the wiper, wherein the blocked state includes a normal state and an abnormal state, wherein the abnormal state is used to indicate that the wiper is in a state where it cannot rotate, and the normal state is used to indicate that the wiper is in a state where it rotates normally; Based on the enabled state, the locked state and the third execution result, a third fault detection result of the wiper is determined, wherein the third fault detection result includes that the wiper is in a normal state, or that the wiper is in a faulty state.
6. The method according to claim 5, characterized in that The execution status information includes the input current of the motor corresponding to the wiper; The determining the execution state information and the vehicle state, and determining the enabling state of the electronic wiper module, includes: If the input current is non-zero and the vehicle is in a powered-on state, determining that the enabling state of the electronic wiper module is a supporting action state; or, If the input current is zero and / or the vehicle is in a power-off state, it is determined that the enabling state of the electronic wiper module is a non-supporting action state.
7. The method according to claim 6, characterized in that The determining the blocked state of the wiper based on the state information includes: If the input current continues to increase within a set time period, it is determined that the wiper is in an abnormal state; or, If the output current remains unchanged within the set time period, it is determined that the wiper is in a normal state.
8. The method according to claim 7, characterized in that The determining, based on the enabled state, the locked-rotor state and the third execution result, a second fault detection result of the wiper includes: Determining that the enabling state is a supporting action state and the stalling state is a normal state; If the third execution result is that the wiper has performed a rotation action, determining that the second fault detection result of the wiper is a normal state; If the third execution result is that the wiper does not perform the rotation action, it is determined that the second fault detection result of the wiper is a fault state.
9. The method according to claim 8, characterized in that If the third execution result is that the wiper does not perform the rotation action, after determining that the second fault detection result of the wiper is a fault state, the method further includes: A second instruction is sent to the electronic wiper module, where the second instruction is used to instruct the electronic wiper module to control the wiper to restart.
10. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Recording the instruction information sent by the vehicle-mounted controller to the electronic wiper module and the execution result information fed back by the electronic wiper module in a log file, wherein the instruction information includes the first instruction, and the execution result information includes the first execution result; If the wiper is in a fault state, the fault state is determined to correspond to a fault cause based on the instruction information and the execution result information in the log file.
11. The method according to claim 10, characterized in that If the wiper is in a fault state, determining the fault cause corresponding to the fault state based on the instruction information and the execution result information in the log file includes: determining that the wiper is in a fault state; If the log file includes instruction information but does not include execution result information, it is determined that the cause of the fault is that the electronic wiper module is faulty; If the log file does not include instruction information, it is determined that the cause of the fault is a fault in the vehicle controller.
12. A wiper fault detection device, characterized in that: Applied to a vehicle-mounted controller, the vehicle-mounted controller is connected to an electronic wiper module in the vehicle, and the electronic wiper module is used to control the working state of the wiper in the vehicle, including: a control module, configured to send a first instruction to an electronic wiper module in response to the vehicle entering a power-on state, wherein the first instruction is used to instruct the electronic wiper module to control the wiper to rotate to a set angle, the electronic wiper module is used to send a first signal to the wiper based on the first rotation instruction, and return a first execution result of the first rotation signal to the on-board controller, wherein the first signal is used to make the wiper rotate to the set angle; An analysis module is used to determine a first fault detection result of the wiper in response to a first execution result returned by the electronic wiper module, wherein the first fault detection result includes that the wiper is in a normal state, or that the wiper is in a faulty state.
13. A wiper control system, characterized in that: include: Controller, electronic wiper module, wiper; The controller is connected to the electronic wiper module and performs the method according to any one of claims 1 to 11; The electronic wiper module is connected to the wiper and is used to control the working state of the wiper.
14. A vehicle, characterized in that: The vehicle comprises the wiper control system as claimed in claim 13.
