Brake clearance compensation method and apparatus for electromechanical brake system, and device
By acquiring vehicle driving status data after braking through software control algorithms, determining braking demand, and releasing the braking actuator, the problem of mismatched braking force caused by sensor errors is solved, thereby improving braking performance and saving costs.
Patent Information
- Application Number
- PCT/CN2025/099491
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2025-06-06
- Publication Date
- 2026-11-12
AI Technical Summary
In electromechanical braking systems, the detected braking force may not match the actual braking force due to sensor accuracy and error, thus affecting the braking effect.
The system uses software control algorithms to acquire vehicle driving status data after braking, determine whether there is a braking demand, and control the motor drive transmission mechanism to release the braking actuator when the estimated braking parameters are less than the threshold, thereby achieving braking gap compensation.
It improves braking performance, avoids the effects of sensor errors, and saves the cost of additional sensor mechanisms.
Smart Images

Figure CN2025099491_12112026_PF_FP_ABST
Abstract
Description
Brake gap compensation method, device and equipment for electronic mechanical brake system
[0001] The present application claims priority to the Chinese patent application No. 202510593049.0, filed on May 9, 2025, to the Chinese Patent Office, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD
[0002] The present application belongs to the field of automotive technology, for example, relates to a brake gap compensation method, device and equipment for an electronic mechanical brake system. BACKGROUND
[0003] Electronic mechanical brake (EMB) is one of the hotspots in the field of chassis-by-wire, which uses an electronic controller and a mechanical actuator to directly apply brake force to the wheel end, significantly reducing system components, while providing faster response speed and higher flexibility in wheel end execution, and is a high-integration solution for brake systems.
[0004] Currently, the electronic mechanical brake system uses a force sensor to detect the size of the brake force of the current wheel end actuator.
[0005] However, due to the influence of sensor accuracy and error, the detected brake force and the estimated brake parameter do not match, which further leads to poor brake effect. SUMMARY
[0006] The present application provides a brake gap compensation method, device and equipment for an electronic mechanical brake system, which can solve the influence of sensor accuracy and error by compensating for brake gap, and improve the brake performance of the vehicle.
[0007] In a first aspect, the present application provides a brake gap compensation method for an electronic mechanical brake system, the electronic mechanical brake system comprising a motor, a transmission mechanism, a piston and a brake actuator, the motor being configured to drive the transmission mechanism to move the piston, the piston being configured to drive the brake actuator to clamp or release a brake disc of a vehicle wheel, the method comprising:
[0008] obtaining driving state data of the vehicle wheel after braking of the vehicle;
[0009] determining whether the driving state data returns to a target value, the target value being associated with the driving state data of the vehicle wheel before braking;
[0010] determining whether there is a pressure building demand for the brake disc of the vehicle according to a control instruction of the vehicle;
[0011] acquiring an estimated braking parameter of the wheel, when the driving state data is not restored to the target value and the brake disc does not have the pressure building demand;
[0012] controlling the motor to drive the transmission mechanism to drive the piston, so that the piston drives the brake actuating mechanism to release the brake disc, when the estimated braking parameter is less than a second threshold value.
[0013] In an implementable embodiment, the determining whether the brake disc of the vehicle has the pressure building demand according to the control instruction of the vehicle comprises:
[0014] acquiring a target braking force and / or a target torque of the motor according to the control instruction of the vehicle;
[0015] determining that the brake disc does not have the pressure building demand when the target braking force is less than a first threshold value, and / or determining that the brake disc does not have the pressure building demand when the target torque is less than a torque threshold value.
[0016] In an implementable embodiment, the estimated braking parameter is a braking force collected by a sensor of the wheel, and the controlling the motor to drive the transmission mechanism to drive the piston, so that the piston drives the brake actuating mechanism to release the brake disc comprises:
[0017] determining whether the position of the piston is greater than a third threshold value when the estimated braking parameter is less than a second threshold value.
[0018] controlling the motor to drive the transmission mechanism to drive the piston to retreat to a target position point at a target speed, so that the piston drives the brake actuating mechanism to release the brake disc, when the position of the piston is greater than a third position.
[0019] In an implementable embodiment, the method further comprises:
[0020] acquiring a contact point between the brake actuating mechanism and the brake disc;
[0021] determining whether the position of the piston is greater than the third threshold value according to the position of the contact point and the position of the piston.
[0022] In an implementable embodiment, the method further comprises:
[0023] In the case that any preset condition is met, the brake actuator is kept clamping the brake disc, and the preset condition includes that the driving state data returns to the target value, the pressure building demand exists, the estimated brake parameter is greater than or equal to the third threshold value, and the position of the piston is less than or equal to the third position.
[0024] In an implementable embodiment, the transmission mechanism includes a speed reduction and torque increasing mechanism, a ball screw and a screw nut, the motor drives the speed reduction and torque increasing mechanism, the speed reduction and torque increasing mechanism drives the ball screw, and the ball screw drives the piston, and the method further includes:
[0025] obtaining a mechanical angle of rotation of the motor, a transmission ratio of the speed reduction and torque increasing mechanism, a thread pitch of the screw nut and a pitch circle radius;
[0026] determining the position of the piston according to the mechanical angle, the transmission ratio, the thread pitch and the pitch circle radius.
[0027] In an implementable embodiment, the driving state data includes wheel speed and / or slip ratio, and the obtaining of the driving state data of the wheel after the vehicle is braked includes:
[0028] obtaining an angular velocity of the wheel, a wheel radius and a vehicle speed of the vehicle after the vehicle is braked;
[0029] determining the slip ratio according to the angular velocity, the wheel radius and the vehicle speed.
[0030] In an implementable embodiment, after the motor is controlled to drive the transmission mechanism to drive the piston to make the piston drive the brake actuator to release the brake disc, the method further includes:
[0031] in the case that the driving state data returns to the target value, determining whether the brake disc of the vehicle has a pressure building demand;
[0032] in the case that the pressure building demand exists, continuing to control the motor to drive the transmission mechanism to drive the piston to make the piston drive the brake actuator to clamp the brake disc.
[0033] In a second aspect, the embodiments of the present application provide a brake gap compensation device of an electromechanical brake system, which includes:
[0034] an obtaining module configured to obtain driving state data of a wheel after a vehicle is braked;
[0035] a data determining module configured to determine whether the driving state data returns to a target value, the target value being associated with driving state data of the wheel before braking.
[0036] The demand determination module is configured to determine whether the brake discs of the vehicle have a pressure build-up requirement based on the control commands of the vehicle.
[0037] The parameter acquisition module is configured to acquire the estimated braking parameters of the wheel when the driving status data has not recovered to the target value and the brake disc does not have the pressure build-up requirement.
[0038] The control module is configured to control the motor to drive the transmission mechanism to drive the piston when the estimated braking parameter is less than a second threshold, so that the piston drives the braking actuator to release the brake disc.
[0039] Thirdly, embodiments of this application provide an electronic device, including: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the method described above.
[0040] The braking clearance compensation method, apparatus, and device for the electromechanical braking system provided in this application can automatically release the residual braking force at the wheel end through software when the estimated braking parameters of the wheel are less than a second threshold due to sensor errors, but the wheel still has braking force, thereby improving braking performance. At the same time, this solution does not require additional redundant sensor mechanisms, thus saving costs. Attached Figure Description
[0041] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0042] Figure 1 is a schematic diagram of the electromechanical braking system provided in an embodiment of this application;
[0043] Figure 2 is a schematic diagram of the braking process according to an embodiment of this application;
[0044] Figure 3 is a schematic flowchart of the braking clearance compensation method provided in an embodiment of this application;
[0045] Figure 4 is a schematic flowchart of another braking clearance compensation method provided in an embodiment of this application;
[0046] Figure 5 is a schematic diagram of the brake clearance compensation device provided in an embodiment of this application;
[0047] Figure 6 is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. Detailed Implementation
[0048] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.
[0049] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.
[0050] Electro-mechanical braking (EMB) is currently a hot research topic in the field of drive-by-wire chassis. It uses electronic controllers and mechanical actuators to directly apply braking force to the wheel ends, significantly reducing system components while offering faster response and greater wheel-end actuation flexibility, representing a highly integrated braking system solution. In EMB systems, constant monitoring of tire braking performance is crucial. Compared to electro-hydraulic braking systems, which control the master cylinder hydraulic pressure and adjust wheel cylinder hydraulic pressure based on the current actual hydraulic pressure reading from the master cylinder hydraulic pressure sensor for optimal wheel braking performance, EMB systems adjust the pressure between the brake pads and the friction disc. Force sensors display the current braking force of the wheel-end actuators. However, due to sensor accuracy and error, when the force sensor shows no braking force at the wheel end, the wheel may actually be braking, leading to problems with the overall vehicle braking performance.
[0051] To address the aforementioned issues, this application provides a brake clearance compensation scheme based on an EMB system. By using a software control algorithm, the electromechanical braking system can achieve wheel dynamic recognition and wheel braking recovery. When the force sensor value is zero, the software automatically releases the residual braking force at the wheel end, thereby compensating for the brake clearance and preventing the wheel from actually being in a braking state, thus improving braking performance.
[0052] For example, Figure 1 is a schematic diagram of the structure of the electromechanical braking system provided in the embodiment of this application. As shown in Figure 1, the motor is equipped with a speed reduction and torque amplification mechanism, which is equipped with a motion conversion mechanism (e.g., a ball screw). The rotation output by the speed reduction and torque amplification mechanism is converted into translation by the screw nut, and the piston 11 pushes the friction lining 14 to press the brake disc 13.
[0053] The motor integrates an angle sensor to sense the current motor angle. It also integrates a current sensor to sense the current motor current. The motion conversion mechanism integrates a force sensor 12 to sense the clamping force exerted by the friction pads 14 on the brake disc 13.
[0054] In this embodiment, when the motor controller receives a clamping command from the upper-level controller, it drives the motor to rotate forward to complete the clamping; when it receives a release command, it drives the motor to rotate in reverse to complete the release. Specifically, during the operation of the electromechanical braking system, the upper-level control system can send clamping / release commands to the execution control system according to the braking intention of the driver or the intelligent driving system. The calculation module calculates the current piston position based on the motor angle and the actuator parameters. At the same time, the contact point identification module can enable / disable the contact point identification function according to the clamping / release command from the upper-level control system. When the function is enabled, the contact point is refreshed based on the clamping force, current, and piston position of the actuator.
[0055] Specifically, when the upper-level control system issues a clamping command, the drive motor rotates forward based on the piston position and the clamping force of the actuator to complete the clamping. When the upper-level control system issues a release command, the drive motor rotates in reverse based on the piston position and the contact point, reversing the piston to a position that maintains a fixed distance from the contact point. Furthermore, through the clamping / release arbitration function module, the motor torque for executing clamping or release control can be determined based on the clamping / release commands from the upper-level control system.
[0056] For example, Figure 2 is a schematic diagram of the braking process according to an embodiment of this application. As shown in Figure 2, it includes the following steps: Step S210: Upper-level braking intention. Step S220: Target braking force distribution to the four wheels of the vehicle. Step S230: Clamping / release control. Step S240: Control arbitration based on release torque or clamping torque. Step S250: Actuator performs braking. Step S260: Wheel dynamic recovery.
[0057] The technical solution of this application will now be described in detail 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 described again in some embodiments.
[0058] Figure 3 is a schematic flowchart of the brake clearance compensation method provided in an embodiment of this application. This method can be applied to vehicles equipped with an electromechanical braking system, wherein the electromechanical braking system includes a motor, a transmission mechanism, a piston, and a brake actuator. The motor is configured to drive the transmission mechanism to move the piston, and the piston is configured to drive the brake actuator to clamp the brake disc of the wheel or release the brake disc. Taking an electronic device in the vehicle as the main body for executing this method as an example, as shown in Figure 3, the method specifically includes the following steps:
[0059] Step S310: Obtain the driving status data of the wheels after the vehicle brakes.
[0060] In this embodiment, the driver or intelligent driving system can trigger the vehicle's braking. The vehicle's upper control system sends a clamping / releasing command to the execution control system according to the driver's or intelligent driving system's braking intention, thereby controlling the friction pads to clamp the brake disc to achieve braking.
[0061] Additionally, in certain special scenarios, if a vehicle is equipped with features such as Anti-lock Braking System (ABS), Vehicle Dynamic Control (VDC), and Traction Control System (TCS), then braking can be achieved through one of these features.
[0062] Taking the anti-lock braking system (ABS) as an example, the ABS system continuously monitors the wheel speed and slippage. During the entire braking process, multiple clamping and releasing actions occur, meaning the brake actuator repeatedly clamps and releases the brake disc. This requires precise control of the brake actuator's reciprocating motion, timely retraction to release the brake disc when braking is not needed, and timely forward movement to clamp the brake disc when braking is required.
[0063] Step S320: Determine whether the driving status data has been restored to the target value.
[0064] The target value is associated with the wheel's driving status data before braking.
[0065] In this embodiment, the target value can refer to the driving state data of the vehicle when the wheels are moving normally before braking. For example, the driving state data may include the wheel slip ratio and wheel speed.
[0066] It should be noted that a vehicle has multiple wheels (for example, a car has four wheels), and the wheel mentioned in this embodiment refers to the same wheel. For example, if a vehicle includes wheel A and wheel B, then the wheel mentioned in this embodiment can refer to wheel A.
[0067] In this embodiment, driving status data can be collected by sensors, such as wheel speed, which can be collected by wheel speed sensors.
[0068] Step S330: Based on the vehicle's control commands, determine whether there is a pressure build-up requirement for the vehicle's brake discs.
[0069] In this embodiment, pressure build-up demand can be used to characterize whether braking of the wheel is required. If there is pressure build-up demand, it means that the driver or intelligent driving system wants to brake the wheel, that is, the braking actuator needs to move forward and clamp the brake disc.
[0070] For example, in some embodiments, control commands from the upper-level control system can be obtained. These commands may include a target braking force. If the target braking force is less than a first threshold, it is determined that there is no pressure build-up requirement on the brake disc. For example, the first threshold may be 0.
[0071] Furthermore, in some other embodiments, the target torque of the motor can also be obtained, and if the target torque is less than the torque threshold, it can be determined that there is no pressure build-up requirement for the brake disc.
[0072] By determining whether the vehicle requires pressure build-up, the system can determine whether re-braking is needed after initial braking, allowing for more precise control of piston movement. For example, if re-braking is required, the piston's retraction distance doesn't need to be excessive, ensuring that the piston can quickly engage the brake actuator to clamp the brake disc upon re-braking. During piston retraction, the brake actuator releases the brake disc, creating a gap between them; the greater the piston's retraction distance, the larger the gap. Conversely, during piston forward movement, the brake actuator clamps the brake disc; the greater the forward distance, the greater the clamping force on the brake disc, resulting in stronger braking force.
[0073] Step S340: If the driving status data has not recovered to the target value and there is no pressure build-up requirement for the brake disc, obtain the estimated braking parameters of the wheel.
[0074] For example, the estimated braking parameters can refer to braking force or braking torque. The braking force can be obtained from sensors on the wheels or calculated using a wheel-end braking force estimation scheme.
[0075] In this embodiment, the force sensor on the wheel is affected by accuracy and error, leading to the following situation: the force sensor collects an estimated braking parameter of zero, but the braking actuator still clamps the brake disc, meaning the wheel still has braking force. This can cause the electromechanical braking system to misjudge, because when the force sensor collects an estimated braking parameter of zero, the electromechanical braking system may no longer control the piston to retract, resulting in the wheel still having braking force, and the wheel's driving state data cannot be restored to the target value.
[0076] Step S350: If the estimated braking parameters are less than the second threshold, control the motor to drive the transmission mechanism to drive the piston, so that the piston drives the braking actuator to release the brake disc.
[0077] In this embodiment, the piston can move forward or backward. When the piston moves forward, it drives the brake actuator to clamp the brake disc, and the braking force gradually increases. When the piston moves backward, it drives the brake actuator to release the brake disc, and the braking force gradually decreases. The second threshold can be preset.
[0078] In this embodiment, when the estimated braking parameters are less than the second threshold and the wheel's driving status data has not recovered to the target value, it indicates that there is still braking force on the wheel, that is, the braking actuator is still clamping the brake disc and there is no gap between them. When the piston drives the braking actuator to release the brake disc, a gap will slowly appear between the braking actuator and the brake disc, and the braking force will gradually decrease, thereby achieving brake gap compensation.
[0079] In this embodiment, if the sensor has an error, causing the estimated braking parameters of the wheel to be less than the second threshold, but the wheel still has braking force, the residual braking force at the wheel end can be automatically released by software to improve braking performance. At the same time, this solution does not require additional redundant sensor mechanisms, which can save costs.
[0080] Figure 4 is a schematic flowchart of another braking clearance compensation method provided in an embodiment of this application. As shown in Figure 4, it includes the following steps:
[0081] Step S410: Upper-level target braking force control. Step S420: Vehicle wheel dynamic recognition. Step S430: Wheel speed / slip ratio of a certain wheel cannot be recovered. Step S440: Target force is less than threshold A. Step S450: Braking force of the wheel collected by the sensor is less than threshold B. Step S460: Is the piston position greater than threshold C? Step S470: Output the piston retraction speed D. Step S480: The actuator performs a clamping or releasing action. Step S490: Is the wheel speed / slip ratio of the wheel recovered?
[0082] In this embodiment, driving status data may refer to wheel speed and / or slip ratio. Estimated braking parameters may refer to the braking force of the wheel collected by the sensor.
[0083] In this embodiment, if the estimated braking parameters are less than the second threshold, it is necessary to determine whether the position of the piston is greater than the third threshold (i.e., threshold C mentioned in this embodiment). Specifically, if the piston's position is greater than the third position, the control motor drives the transmission mechanism to move the piston back to the target position at the target speed, so that the piston drives the braking actuator to release the brake disc.
[0084] The target position can be a pre-set position. When the piston is at the target position, the brake actuator will stop clamping the brake disc. If the piston continues to move forward, the brake actuator will clamp the brake disc again.
[0085] In this embodiment, the target speed can be preset. The higher the target speed, the faster the braking actuator releases the brake disc, and the faster the braking force decreases. This allows the wheel's driving status data to return to the target value as quickly as possible. In anti-lock braking scenarios, this increases the friction between the wheel and the ground, improving the vehicle's braking performance and driving safety.
[0086] In other embodiments, a reference point can be set to determine whether the piston's position is greater than a third threshold. Specifically, the contact point between the brake actuator and the brake disc can be obtained. For example, the piston can move forward or backward. When the piston moves forward to the front of the contact point, its position is greater than the third threshold; when the piston moves backward to the rear of the contact point, its position is less than the third threshold.
[0087] In this embodiment, the contact point can refer to the actual contact or proximity position between the braking actuator (such as brake caliper, friction pad, etc.) and the object being braked (such as brake disc).
[0088] The contact point is a position determined and updated by the system based on parameters such as sensors, clamping force of the braking actuator, current, and piston position. During clamping, when the upper control system issues a clamping command, it drives the motor to rotate forward based on the piston position and clamping force of the braking actuator, causing the braking actuator to move towards the object being braked and gradually clamp it. At this point, the contact point is the position where the braking actuator begins to contact the object being braked and perform the clamping operation. During release, when the upper control system issues a release command, it drives the motor to rotate in reverse based on the piston position and contact point, causing the braking actuator to move away from the object being braked to a safe or preset position. Here, the contact point serves as a reference point, ensuring that the piston rotates to a position that maintains a certain fixed distance from the contact point, avoiding excessive separation between the braking actuator and the object being braked or unnecessary impact.
[0089] Furthermore, in some other embodiments, the piston displacement can be calculated using the position sensor of the motor, and the value measured by the force sensor can be used as a different source value for cross-verification, thereby achieving EMB functional safety.
[0090] In this embodiment, by setting contact points, the piston retraction can be controlled more accurately, avoiding excessive separation between the brake actuator and the brake disc, resulting in a large gap between them, which can improve the timeliness of braking response during subsequent braking.
[0091] Furthermore, based on the above embodiments, the braking actuator can continue to clamp the brake disc if any of the following preset conditions are met. These preset conditions include at least one of the following: driving status data recovers to the target value, there is a pressure build-up requirement, estimated braking parameters are greater than or equal to a third threshold, and the piston position is less than or equal to a third position.
[0092] For example, continuing to refer to Figure 4 above, the target force threshold A is used to determine whether there is a pressure build-up requirement in the current upper-level command. The actual force threshold B is used to determine whether the wheel has been depressurized under the braking force collected by the sensor. The piston position threshold C can be used to determine whether the piston needs to retract during this process.
[0093] One issue is that the braking force collected by the sensor may be incorrect due to the influence of accuracy and error. For example, the sensor may collect zero braking force, but the wheel may actually still have braking force. This could cause the electromechanical braking system to misjudge that the wheel has been depressurized.
[0094] For example, when a vehicle is in special operating conditions, such as when ABS, VDC, or TCS are activated, it is necessary to quickly reduce the braking force on the wheels to restore wheel dynamics. However, if the target force detected by the sensor is zero, the wheels cannot continue to retract to the braking gap in order to build up pressure later. But at this point, the wheels still actually have braking force, which means that although the force sensor displays an actual force value of 0, the wheel speed / slip ratio of a particular wheel recovers more slowly. This indicates a mismatch between the force sensor reading and the actual braking force at the wheel end.
[0095] In this embodiment, by setting the aforementioned preset conditions, it is possible to accurately determine whether the force sensor display matches the actual braking force at the wheel end. When the aforementioned preset conditions are met, the braking actuator continues to clamp the brake disc.
[0096] In this embodiment of the application, by determining whether the force sensor display matches the actual braking force at the wheel end, the influence caused by sensor error can be resolved, thereby improving the vehicle's braking performance.
[0097] Furthermore, based on the above embodiments, in some other embodiments, the transmission mechanism includes a speed reduction and torque amplification mechanism, a ball screw, and a screw nut. The motor drives the speed reduction and torque amplification mechanism, which in turn drives the ball screw, which in turn drives the piston. The position of the piston can be calculated using the following steps:
[0098] Step (1): Obtain the mechanical angle of motor rotation, the transmission ratio of the speed reduction and torque increase mechanism, the thread pitch of the lead screw nut, and the pitch circle radius;
[0099] Step (2) Determine the position of the piston based on the mechanical angle, transmission ratio, thread pitch and pitch circle radius.
[0100] In this embodiment, since the motor position sensor can sense the motor angle in real time, the piston position can be obtained by integrating the actuator parameters:
[0101] In the above formula, A is the piston position, φ is the mechanical angle of motor rotation, K is the transmission ratio of the reduction and torque-increasing mechanism, p is the thread pitch, and r is the pitch circle radius.
[0102] Furthermore, in some embodiments, the slip ratio of the wheel can be determined by the following steps:
[0103] Step 1: After the vehicle brakes, obtain the angular velocity of the wheels, the wheel radius, and the vehicle speed. Step 2: Determine the slip ratio based on the angular velocity, wheel radius, and vehicle speed.
[0104] In this embodiment, when the driver depresses the brake pedal, the wheel speed decreases. However, due to the vehicle's inertia, the actual vehicle speed and wheel speed are no longer equal, resulting in a slip ratio. Different slip ratio values result in different levels of adhesion between the wheels and the road surface. For example, when the slip ratio is approximately 20%, the adhesion between the wheels and the road surface is at its maximum, resulting in the greatest braking force and optimal braking effect.
[0105] In this embodiment, as the output force of the vehicle's brake pedal changes, the degree of wheel slippage also changes. The specific formula for calculating the wheel slip ratio is as follows:
[0106] S=(Vw*r) / V
[0107] In the above formula, S is the slip ratio, V is the vehicle speed, w is the angular velocity of the wheel, and r is the wheel radius.
[0108] In some embodiments, as the piston drives the brake actuator to release the brake disc, the braking force gradually decreases to zero. When the braking force reaches zero, the vehicle's driving status data returns to the target value. At this point, it can be further determined whether the vehicle's brake disc requires pressure build-up.
[0109] When there is a pressure build-up requirement, the motor drive transmission mechanism continues to drive the piston, so that the piston drives the brake actuator to clamp the brake disc.
[0110] For example, continuing to refer to Figure 4 above, it is determined whether the current target force is less than the set threshold A, whether the braking force collected by the sensor is less than the set threshold B, and whether the current piston position is greater than the threshold C. When the above conditions are met, a retraction speed D is output, at which point the piston begins to retract from its current position, and the actual braking force at the wheel end decreases. When the piston position is less than C, the retraction scheme ends, and the wheel end braking force enters the subsequent upper-level control process.
[0111] Specifically, taking an anti-lock braking system (ABS) scenario as an example, after the initial braking, the brake actuator needs to release the brake disc as quickly as possible to prevent locking and restore the wheels to dynamic state. Immediately afterwards, the brake actuator needs to clamp the brake disc again as quickly as possible to continue providing braking force. This process repeats to achieve safe braking of the vehicle within a short time. This process requires controlling the motor-driven transmission mechanism to move the piston, causing the piston to rapidly switch between clamping and releasing the brake disc.
[0112] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.
[0113] Figure 5 is a schematic diagram of the brake gap compensation device provided in the embodiment of this application. As shown in Figure 5, the brake gap compensation device 500 may include an acquisition module 510, a data determination module 520, a demand determination module 530, a parameter acquisition module 540, and a control module 550.
[0114] The acquisition module 510 is configured to acquire the driving state data of the wheels after vehicle braking. The data determination module 520 is configured to determine whether the driving state data has recovered to a target value, which is correlated with the driving state data of the wheels before braking. The demand determination module 530 is configured to determine whether there is a pressure build-up requirement for the vehicle's brake discs based on the vehicle's control commands. The parameter acquisition module 540 is configured to acquire estimated braking parameters of the wheels when the driving state data has not recovered to the target value and there is no pressure build-up requirement for the brake discs. The control module 550 is configured to control the motor to drive the transmission mechanism to drive the piston when the estimated braking parameters are less than a second threshold, so that the piston drives the brake actuator to release the brake discs.
[0115] Optionally, the demand determination module 530 is configured to: obtain the target braking force and / or the target torque of the motor according to the vehicle's control command; determine that there is no pressure build-up requirement for the brake disc when the target braking force is less than a first threshold, and / or determine that there is no pressure build-up requirement for the brake disc when the target torque is less than a torque threshold.
[0116] Optionally, the estimated braking parameters are the braking forces collected by the wheel sensors. The control module 550 is configured to: if the estimated braking parameters are less than a second threshold, determine whether the position of the piston is greater than a third threshold; if the position of the piston is greater than the third threshold, control the motor to drive the transmission mechanism to move the piston back to the target position point at the target speed, so that the piston drives the braking actuator to release the brake disc.
[0117] Optionally, the brake clearance compensation device 500 further includes a position determination module, configured to obtain the contact point between the brake actuator and the brake disc; and determine whether the position of the piston is greater than a third threshold based on the position of the contact point and the position of the piston.
[0118] Optionally, the brake clearance compensation device 500 also includes a brake maintenance module, configured to continue to maintain the brake actuator clamping the brake disc when any preset condition is met. The preset conditions include the driving status data being restored to the target value, the presence of pressure build-up demand, the estimated brake parameters being greater than or equal to a third threshold, and the piston position being less than or equal to a third position.
[0119] Optionally, the transmission mechanism includes a speed reduction and torque amplification mechanism, a ball screw, and a screw nut. The motor drives the speed reduction and torque amplification mechanism, which in turn drives the ball screw, which in turn drives the piston. The brake clearance compensation device 500 also includes a position determination module, configured to acquire the mechanical angle of the motor rotation, the transmission ratio of the speed reduction and torque amplification mechanism, and the thread pitch and pitch circle radius of the screw nut; and to determine the position of the piston based on the mechanical angle, transmission ratio, thread pitch, and pitch circle radius.
[0120] Optionally, the driving status data includes wheel speed and / or slip ratio. The data determination module 520 is configured to: acquire the wheel angular velocity, wheel radius, and vehicle speed after vehicle braking; and determine the slip ratio based on the angular velocity, wheel radius, and vehicle speed.
[0121] Optionally, the brake clearance compensation device 500 also includes a clamping control module, configured to determine whether there is a pressure build-up requirement for the vehicle's brake disc when the driving status data is restored to the target value; if there is a pressure build-up requirement, continue to control the motor drive transmission mechanism to drive the piston, so that the piston drives the brake actuator to clamp the brake disc.
[0122] The apparatus provided in this application embodiment can be used to execute the methods in the above embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.
[0123] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, the acquisition module can be a separate processing element, or it can be integrated into a chip in the above device. Alternatively, it can be stored as program code in the memory of the above device, and its function can be called and executed by a processing element. The implementation of other modules is similar. Moreover, these modules can be fully or partially 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 of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.
[0124] Figure 6 is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. This electronic device can be integrated into a vehicle. As shown in Figure 6, the electronic device 600 may include a processor 601 and a memory 602 storing computer program instructions.
[0125] Specifically, the processor 601 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.
[0126] Memory 602 may include mass storage for data or instructions. For example, and not limitingly, memory 602 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one instance, memory 602 may include removable or non-removable (or fixed) media, or memory 602 may be non-volatile solid-state memory. Memory 602 may be internal or external to the integrated gateway disaster recovery device.
[0127] In one instance, memory 602 may be read-only memory (ROM). In one instance, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.
[0128] Memory 602 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.
[0129] The processor 601 implements the method described above by reading and executing computer program instructions stored in the memory 602.
[0130] In one example, the electronic device 600 may further include a communication interface 603 and a bus 604. As shown in FIG6, the processor 601, memory 602, and communication interface 603 are connected via bus 604 and communicate with each other. Communication interface 603 is mainly used to realize communication between various modules, devices, units, and / or devices in the embodiments of this application. Bus 604 includes hardware, software, or both, coupling the components of the online data traffic billing device together. For example, and not as a limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 604 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.
[0131] In addition, in conjunction with the methods in the above embodiments, this application embodiment can provide a vehicle that includes the above-described electronic equipment.
[0132] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.
[0133] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.
[0134] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.
[0135] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.
[0136] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
Claims
1. A method for compensating brake clearance in an electromechanical braking system, the electromechanical braking system comprising a motor, a transmission mechanism, a piston, and a brake actuator, wherein the motor is configured to drive the transmission mechanism to move the piston, and the piston is configured to drive the brake actuator to clamp or release the brake disc of a wheel, the method comprising: Acquire data on the driving status of the wheels after the vehicle brakes; Determine whether the driving status data has recovered to a target value, which is associated with the driving status data of the wheels before braking; Based on the vehicle's control commands, determine whether the vehicle's brake discs require pressure build-up. If the driving status data has not recovered to the target value and the brake disc does not have the pressure build-up requirement, obtain the estimated braking parameters of the wheel; If the estimated braking parameter is less than the second threshold, the motor is controlled to drive the transmission mechanism to move the piston, so that the piston moves the braking actuator to release the brake disc.
2. The method according to claim 1, wherein, The step of determining whether the vehicle's brake discs require pressure build-up based on the vehicle's control commands includes: According to the control command of the vehicle, the target braking force and / or the target torque of the motor are obtained; If the target braking force is less than a first threshold, it is determined that the brake disc does not have a pressure build-up requirement, and / or if the target torque is less than a torque threshold, it is determined that the brake disc does not have a pressure build-up requirement.
3. The method according to claim 1, wherein, The estimated braking parameters are the braking force collected by the sensors on the wheels. Controlling the motor to drive the transmission mechanism to move the piston, so that the piston moves the braking actuator to release the brake disc, includes: If the estimated braking parameters are less than the second threshold, determine whether the position of the piston is greater than the third threshold. When the piston is in a position greater than the third position, the motor is controlled to drive the transmission mechanism to move the piston back to the target position point at the target speed, so that the piston drives the braking actuator to release the brake disc.
4. The method according to claim 3, further comprising: Obtain the contact point between the braking actuator and the brake disc; Based on the position of the contact point and the position of the piston, determine whether the position of the piston is greater than the third threshold.
5. The method according to claim 3, further comprising: Under any preset condition, the braking actuator continues to clamp the brake disc. The preset conditions include the driving status data recovering to the target value, the existence of the pressure build-up requirement, the estimated braking parameters being greater than or equal to the third threshold, and the piston position being less than or equal to the third position.
6. The method according to claim 3, wherein, The transmission mechanism includes a speed reduction and torque amplification mechanism, a ball screw, and a screw nut. The motor drives the speed reduction and torque amplification mechanism, which in turn drives the ball screw, which in turn drives the piston. The method further includes: Obtain the mechanical angle of the motor rotation, the transmission ratio of the reduction and torque amplification mechanism, and the thread pitch and pitch circle radius of the lead screw nut; The position of the piston is determined based on the mechanical angle, the transmission ratio, the thread pitch, and the pitch circle radius.
7. The method according to claim 1, wherein, The driving status data includes wheel speed and / or slip ratio, and the acquisition of wheel driving status data after vehicle braking includes: After the vehicle brakes, the angular velocity of the wheels, the wheel radius, and the vehicle speed are obtained. The slip ratio is determined based on the angular velocity, wheel radius, and vehicle speed.
8. The method according to claim 1, wherein after controlling the motor to drive the transmission mechanism to drive the piston, so that the piston drives the brake actuator to release the brake disc, the method further includes: If the driving status data recovers to the target value, determine whether the vehicle's brake discs require pressure build-up. When the pressure build-up requirement exists, the motor continues to drive the transmission mechanism to move the piston, so that the piston moves the brake actuator to clamp the brake disc.
9. A brake clearance compensation device for an electromechanical braking system, comprising: The acquisition module is configured to acquire data on the driving status of the wheels after the vehicle has braked. The data determination module is configured to determine whether the driving state data has recovered to a target value, wherein the target value is associated with the driving state data of the wheels before braking; The demand determination module is configured to determine whether the brake discs of the vehicle have a pressure build-up requirement based on the control commands of the vehicle. The parameter acquisition module is configured to acquire the estimated braking parameters of the wheel when the driving status data has not recovered to the target value and the brake disc does not have the pressure build-up requirement. The control module is configured to control the motor to drive the transmission mechanism to drive the piston when the estimated braking parameter is less than the second threshold, so that the piston drives the braking actuator to release the brake disc.
10. An electronic device, comprising: Processor, and memory storing computer program instructions; The processor reads and executes the computer program instructions to implement the method as described in any one of claims 1-8.
