EP3032234A1 - Open loop load force estimation systems and methods - Google Patents

Open loop load force estimation systems and methods Download PDF

Info

Publication number
EP3032234A1
EP3032234A1 EP15198705.4A EP15198705A EP3032234A1 EP 3032234 A1 EP3032234 A1 EP 3032234A1 EP 15198705 A EP15198705 A EP 15198705A EP 3032234 A1 EP3032234 A1 EP 3032234A1
Authority
EP
European Patent Office
Prior art keywords
actuator
force
mode
current
amount
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP15198705.4A
Other languages
German (de)
French (fr)
Other versions
EP3032234B1 (en
Inventor
Sameep Singh
Richard Kolk
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Goodrich Corp
Original Assignee
Goodrich Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Goodrich Corp filed Critical Goodrich Corp
Publication of EP3032234A1 publication Critical patent/EP3032234A1/en
Application granted granted Critical
Publication of EP3032234B1 publication Critical patent/EP3032234B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G01MEASURING; TESTING
    • G01LMEASURING FORCE, STRESS, TORQUE, WORK, MECHANICAL POWER, MECHANICAL EFFICIENCY, OR FLUID PRESSURE
    • G01L5/00Apparatus for, or methods of, measuring force, work, mechanical power, or torque, specially adapted for specific purposes
    • G01L5/22Apparatus for, or methods of, measuring force, work, mechanical power, or torque, specially adapted for specific purposes for measuring the force applied to control members, e.g. control members of vehicles, triggers
    • G01L5/225Apparatus for, or methods of, measuring force, work, mechanical power, or torque, specially adapted for specific purposes for measuring the force applied to control members, e.g. control members of vehicles, triggers to foot actuated controls, e.g. brake pedals
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01RMEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
    • G01R19/00Arrangements for measuring currents or voltages or for indicating presence or sign thereof
    • G01R19/0092Arrangements for measuring currents or voltages or for indicating presence or sign thereof measuring current only

Definitions

  • the present disclosure relates to aircraft brakes, and more particularly, to a system for determining a braking force applied to an outer disc of an aircraft brake.
  • Aircraft brakes include alternating stators and rotating discs that rotate about an axis. Wheels of the aircraft are coupled to the rotating discs.
  • the stators and rotating discs are axially enclosed by two outer discs.
  • force is applied to at least one of the outer discs, forcing the outer discs, the stators and the rotating discs together. When forced together, friction reduces the angular speed of the rotating discs.
  • a motor converts electrical energy into mechanical energy that causes the force to be applied to the outer disc using an actuator. It is desirable to determine the amount of force applied to the outer disc.
  • An actuator may include a force sensor to determine this amount of force.
  • a system for determining a force applied to an outer disc of an aircraft brake by an actuator includes a current sensor coupled to the actuator and configured to detect a detected amount of current applied to the actuator.
  • the system also includes a controller coupled to the current sensor and configured to determine an estimate of the force applied to the outer disc based on the detected amount of current and a plurality of predetermined input parameters.
  • the method includes receiving, at a controller and by a current sensor, a detected amount of current applied to the actuator.
  • the method also includes receiving, at the controller, the detected amount of current and input parameters including a maximum force of the actuator, a maximum current of the actuator and an efficiency fraction of the actuator.
  • the method also includes determining, by the processor, a mode of operation of the actuator.
  • the mode of operation may include a first mode indicating that the force applied to the outer disc increases proportionally as the amount of current applied to the actuator increases, a second mode indicating that the force applied to the outer disc remains substantially constant as the amount of current applied to the actuator decreases a first amount and a third mode indicating that the force applied to the outer disc decreases proportionally as the amount of current applied to the actuator decreases a second amount.
  • the method also includes determining, by the processor, an estimated amount of force applied to the outer disc of the aircraft brake by the actuator based on the input parameters and the detected amount of current.
  • FIG. 1 illustrates an aircraft brake 100 in accordance with various embodiments.
  • Aircraft brake 100 includes a plurality of actuator motors 102A, 102B, a plurality of electromechanical brake actuators 104A, 104B, a plurality of ball nuts 106A, 106B, a plurality of pucks 108A, 108B, an outer disc 111 and an outer disc 110, and a plurality of rotating discs 112A, 112B, 112C, 112D and stators 114A, 114B, 114C positioned in an alternating fashion between outer disc 111 and outer disc 110.
  • Rotating discs 112A, 112B, 112C, 112D may rotate about an axis 115 and the stators 114A, 114B, 114C may have no angular movement relative to axis 115. Wheels may be coupled to rotating discs 112A, 112B, 112C, 112D such that a linear speed of the aircraft is proportional to the angular speed of rotating discs 112A, 112B, 112C, 112D. As force is applied to outer disc 110 towards outer disc 111 along the axis of rotation 115, rotating discs 112 and stators 114 are forced together in an axial direction.
  • rotating discs 112A, 112B, 112C, 112D This causes the rotational speed of rotating discs 112A, 112B, 112C, 112D to become reduced (i.e., causes braking effect) due to friction between rotating discs 112A, 112B, 112C, 112D , stators 114A, 114B, 114C , outer disc 111 and outer disc 110.
  • the rotating discs 112A, 112B, 112C, 112D will stop rotating.
  • actuator motor 102A may cause corresponding electromechanical brake actuators 104A to actuate.
  • Actuator motor 102A may be a brushless motor, such as a permanent magnet synchronous motor (PMSM), a permanent-magnet motor (PMM) or the like.
  • PMSM permanent magnet synchronous motor
  • PMM permanent-magnet motor
  • electromechanical brake actuator 104A actuates, it causes ball nut 106A to extend towards outer disc 110, thus applying force on outer disc 110 towards outer disc 111.
  • Puck 108A is positioned between ball nut 106A and outer disc 110.
  • Puck 108A may be constructed of a softer and/or more compliant material than ball nut 106A such that when ball nut 106A is forced towards outer disc 110, puck 108A prevents outer disc 110 from becoming damaged.
  • Electromechanical brake actuator 104A is actuated in response to current being applied to actuator motor 102A.
  • the amount of force applied by electromechanical brake actuator 104A is related to the amount of current applied to actuator motor 102A. It is desirable to determine this amount of force.
  • One way to determine this force is to use a force sensor within aircraft brake 100. However, it may be desirable to determine this force without the use of a force sensor.
  • Aircraft brake 100 may include a current sensor (such as current sensor 208 of FIG. 2 ) to detect an amount of current provided to actuator motor 102A. Because the amount of force applied by electromechanical brake actuator 104A is related to the current applied to actuator motor 102A, it is possible to estimate the force using the detected amount of current. Thus, a controller or processor may receive the detected current and estimate a force based on the detected current.
  • a current sensor such as current sensor 208 of FIG. 2
  • a controller or processor may receive the detected current and estimate a force based on the detected current.
  • FIG. 2 illustrates a block diagram of an aircraft electromechanical brake actuator control system in accordance with various embodiments.
  • Block 205 includes mechanical components. The other blocks may be implemented on one or more controllers and/or processors. For example, the blocks other than block 205 may be stored in a non-transitory storage medium and performed by a processor, may be stored in a special-use processor, may be implemented in a field programmable gate array (FPGA), or the like.
  • a current sensor 208 is coupled to an actuator motor 206 (similar to actuator motor 102A). Current sensor 208 is configured to detect an amount of current supplied to actuator motor 206.
  • a resolver 214 is also coupled to actuator motor 206. Resolver 214 measures the rotational position and speed of actuator motor 206. Actuator motor 206 is also coupled to a gear transmission 210 and a ball screw 212.
  • a force observer module 216 is coupled to block 205. Force observer module 216 is configured to estimate the force of actuator 104A based on data from current sensor 208 and/or resolver 214. Force observer module 216 may be a controller and/or processor or may be implemented in a controller and/or processor.
  • the estimated force is compared with a force command signal.
  • the output of block 217 is provided to a force/position control module 200.
  • Output from force/position control module 200 is summed with the rotational speed of actuator motor 206 in block 201.
  • the result of the summation in block 201 is provided to a velocity control module 202.
  • the output from velocity control module 202 is summed with the detected current from current sensor 208 in block 203.
  • the output from block 203 is provided to a current control module 204.
  • the output of current control module 204 is provided to actuator motor 206 as a control signal.
  • FIGs. 3A through 3E illustrate logic within force observer module 216 in accordance with various embodiments.
  • the logic may be implemented in hardware and/or software.
  • the logic may be stored as machine-readable instructions on a non-transitory memory and performed by a processor.
  • the logic may be stored on a special-use processor or a field programmable gate array.
  • FIG. 3A illustrates input parameters 390 to force observer module 216.
  • Input parameters 390 may be known parameters for the given motor and thus be predetermined.
  • Input parameters 390 include a max force 300, which may be measured in pound force (lbf), newtons, or the like.
  • Max force 300 represents the maximum force that can be applied by actuator 205.
  • Another input is a max current 302, which may be measured in amps.
  • Max current 302 represents the amount of current to be applied to actuator motor 206 to cause actuator 205 to apply the maximum amount of force.
  • Another input is an efficiency fraction 304.
  • Efficiency fraction 304 indicates the efficiency of the actuator. In the example illustrated in FIG. 3A , max force 300 is given to be 7,857 pounds, max current 302 is given to be 6.5 amps and efficiency fraction 304 is given to be 0.65.
  • FIG. 3B illustrates a system 391 for determining a constant K-nominal 306.
  • K-nominal indicates a relationship between applied force and applied current for actuator 205, such that a current may be multiplied by K-nominal 306 to determine a force and a force can be divided by K-nominal 306 to determine a current.
  • System 391 utilizes max force 300 and max current 302 as inputs. In block 305, the max force 300 is divided by the max current 302, resulting in K-nominal 306.
  • FIG. 3B also illustrates a system 392 for determining a mode of actuator 205 of FIG. 2 .
  • Plot 400 illustrates the estimated force using the methods described herein and plot 402 illustrates the measured force.
  • plot 400 includes a first part 404 corresponding to a first mode, a second part 406 corresponding to a second mode and a third part 408 corresponding to a third mode.
  • first mode the amount of current applied to actuator motor 206 is increasing and the force is increasing substantially proportionally.
  • the amount of current applied to actuator motor 206 is decreasing a first amount.
  • the force does not decrease significantly.
  • the force In the second mode, the force remains substantially constant - it may be less than fifty percent (50%) as much per amp as the force decreases per amp while actuator 205 is operating in the third mode. This is a result of "stiction” (e.g., static friction) in actuator 205.
  • the force In the third mode, once the "stiction" is overcome, the force is reduced substantially proportionally to the current as the current decreases a second amount.
  • system 392 is designed to determine in which mode actuator 205 is operating.
  • the system 392 utilizes measured current 308 as an input. Measured current 308 may be provided by current sensor 208. Measured current 308 is applied to calculate mode of operation block 310, which generates mode 312 as an output. Mode 312 indicates the mode in which actuator 205 is operating.
  • FIG. 3C illustrates the logic within calculate mode of operation block 310.
  • measured current 308 is utilized as an input.
  • the first portion of the calculate mode of operation block 310 is to calculate a filtered derivative of the current, or iDot 326.
  • iDot 326 represents the estimated time rate of change of current.
  • Blocks 316, 318, 324, 322, 320 and 328 represent a low pass filtered differentiator used to calculate iDot 326.
  • iDot 326 is then compared to zero in block 330, block 332 and block 334. If iDot 326 is greater than 0, then block 330 will output a 1, otherwise block 330 will output a 0. This 1 output corresponds to the first mode, indicating that the current is increasing and the force will increase proportionally to the current. If iDot 326 is equal to 0, then block 332 will output a 2. Otherwise, block 332 will output 0. This 2 output corresponds to the second mode, indicating that the force will not be greatly reduced as the current decreases. If iDot 326 is less than 0, then block 334 will output a 3. Otherwise, block 334 will output 0. The 3 output corresponds to the third mode, indicating that the force will be reduced substantially proportionately to the current as the current is reduced.
  • Block 336 receives the input from block 330, block 332 and block 334 and adds them together. The resulting sum indicates the mode 312. If the mode is equal to 1, then actuator 205 is in the first mode. If the mode is equal to 2, then actuator 205 is operating in the second mode. If the mode is equal to 3, then actuator 205 is operating in the third mode.
  • FIG. 3D illustrates a system 393 for determining a variable ForceMaxLimit 350, indicating the maximum force applied during the most recent iteration of the first mode in accordance with various embodiments.
  • ForceMaxLimit 350 will be used in the force estimation during the second mode.
  • the input to system 393 is mode 312.
  • a true signal will be generated.
  • the true signal generated from block 338 will cause a sample and hold block 346 to become active.
  • Sample and hold block 346 also receives a force previous value (ForcePV 342) signal.
  • ForcePV 342 represents an estimated force that has been delayed.
  • a unit delay block 367 in a system 395 of FIG. 3E receives the estimated force and provides the estimated force as ForcePV 342 after a predetermined delay.
  • sample and hold block 346 When block 338 outputs a true signal, sample and hold block 346 will store and output ForcePV 342 until a new true signal is generated in block 338. Sample and hold block 346 will generate the stored ForcePV 342 as ForceMAXLimit 350. ForceMAXLimit 350 corresponds to the maximum estimated force during the first mode or the second mode.
  • FIG. 3D also illustrates a system 394 for calculating another variable, ForceMINLimit 352, indicating the minimum force applied during the most recent iteration of the third mode.
  • ForceMINLimit 352 will be used in the force estimation during the second mode.
  • Mode 312 is an input to system 394.
  • a true signal is generated in response to the current beginning to increase.
  • Sample and hold block 348 also receives ForcePV 342. When the output from block 340 is true, ForcePV 342 will be stored in block 348, and block 348 will output the value as ForceMINLimit 352 until a new "true" signal is generated in block 340.
  • FIG. 3E illustrates a system 395 that is used to calculate an estimated force 380.
  • Estimated force 380 may be provided as the output of force observer module 216 of FIG. 2 .
  • Efficiency fraction 304 is a normalized value that ranges from 0 to 1. A value of one is ideal, meaning that actuator 205 is completely efficient and has no losses.
  • the slope of first part 404 is equal to measured current 308 multiplied by efficiency fraction 304.
  • the slope of third part 408 is equal to measured current 308 divided by efficiency fraction 304.
  • measured current 308 is multiplied by efficiency fraction 304.
  • the output of block 354 represents the relationship of the current and force measurements during the first mode.
  • measured current 308 is divided by efficiency fraction 304. The resulting value represents the relationship of the current and the force during the third mode.
  • Block 356 represents a case statement to be used for a selection of a relationship of the current and the force based on the mode.
  • the mode 312 is provided as a selecting variable and the output of block 354 and block 376 are provided as selectable inputs.
  • block 356 will output the output of block 354.
  • block 356 will output the output of block 376.
  • block 356 will output a value calculated elsewhere in system 395 (output of block 374).
  • the output of block 356 is multiplied with K-nominal 306, the value calculated in system 391.
  • K-nominal is multiplied with the output of block 356, the resulting signal indicates a force value.
  • the value of force is stored as force1 360.
  • Block 368 will output a true signal if mode 312 is not equal to 1.
  • the logic in block 368 is used to initialize system 395.
  • Block 370 will output a true signal if ForceMAXLimit 350 is greater than 0. If block 370 and block 368 both output a true signal, then block 372 will output a true signal.
  • Block 362 compares ForceMAXLimit 350 and force1 360 and outputs the smaller of the two signal values.
  • Block 364 compares force1 360 and ForceMINLimit 352 and outputs the larger of the two signal values.
  • block 366 While the output of block 372 is true, block 366 will output the signal generated in block 362. When the output of block 372 is false, block 366 will output the signal generated in block 364.
  • the logic implemented in block 368, 370, 372, 362, 364 and 366 generates the estimated force when the mode is equal to 2.
  • Block 378 is a limiter, which prevents the output of block 366 from dropping below 0.
  • the output of block 378 is estimated force 380, and may correspond to the output of force observer module 216.
  • the output of block 366 is driven through unit delay block 367, which delays the input signal (corresponding to the estimated force) by a predetermined period of time, such as one clock cycle, two clock cycles, 1 millisecond, etc.
  • the output of block 367 is ForcePV 342, the previous value of the estimated force.
  • ForcePV 342 is divided by K-nominal 306.
  • the output of block 356 is multiplied by K-nominal 306 to result in a force value. Because ForcePV 342 is already a force value, it is divided by K-nominal 306 prior to entering case block 356 so that it can be converted back to a force value in block 358 via multiplication with K-nominal 306.
  • FIG. 4A illustrates plot 402 that represents a measured value of the force applied by actuator 205 as a current is applied to actuator motor 206 in accordance with various embodiments.
  • Plot 400 represents the estimated value of the force using system 395. In FIG. 4A , up to 6.5 amps is applied to the actuator motor 206. As illustrated, the estimated force is similar to the measured force.
  • FIG. 4B illustrates a plot 412 that represents the measured force when a current up to 3 amps is applied to actuator motor 206.
  • Plot 410 illustrates the estimated force using system 395. As illustrated, the estimated force is similar to the measured force during a first part 414 representing the first mode, a second part 416 representing the second mode and a third part 418 representing the third mode in accordance with various embodiments.
  • references to "one embodiment”, “an embodiment”, “various embodiments”, etc. indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.

Abstract

What is described is a system for determining a force applied to an outer disc of an aircraft brake by an actuator motor (206). The system includes a current sensor (208) coupled to the actuator motor (206) and configured to detect an amount of current applied to the actuator motor (206). The system also includes a controller coupled to the current sensor (208). The controller is configured to determine an estimate of the force applied to the outer disc based on the detected amount of current and predetermined input parameters.

Description

    Field
  • The present disclosure relates to aircraft brakes, and more particularly, to a system for determining a braking force applied to an outer disc of an aircraft brake.
  • Background
  • Aircraft brakes include alternating stators and rotating discs that rotate about an axis. Wheels of the aircraft are coupled to the rotating discs. The stators and rotating discs are axially enclosed by two outer discs. In order to cause the rotating discs to slow down or stop rotating (i.e., brake), force is applied to at least one of the outer discs, forcing the outer discs, the stators and the rotating discs together. When forced together, friction reduces the angular speed of the rotating discs.
  • A motor converts electrical energy into mechanical energy that causes the force to be applied to the outer disc using an actuator. It is desirable to determine the amount of force applied to the outer disc. An actuator may include a force sensor to determine this amount of force.
  • Summary
  • The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be understood, however, the following description and drawings are intended to be exemplary in nature and non-limiting.
  • In accordance with various embodiments, a system for determining a force applied to an outer disc of an aircraft brake by an actuator is disclosed. The system includes a current sensor coupled to the actuator and configured to detect a detected amount of current applied to the actuator. The system also includes a controller coupled to the current sensor and configured to determine an estimate of the force applied to the outer disc based on the detected amount of current and a plurality of predetermined input parameters.
  • Also disclosed is an exemplary method for determining a force applied to an outer disc of an aircraft brake by an actuator. The method includes receiving, at a controller and by a current sensor, a detected amount of current applied to the actuator. The method also includes receiving, at the controller, the detected amount of current and input parameters including a maximum force of the actuator, a maximum current of the actuator and an efficiency fraction of the actuator. The method also includes determining, by the processor, a mode of operation of the actuator. The mode of operation may include a first mode indicating that the force applied to the outer disc increases proportionally as the amount of current applied to the actuator increases, a second mode indicating that the force applied to the outer disc remains substantially constant as the amount of current applied to the actuator decreases a first amount and a third mode indicating that the force applied to the outer disc decreases proportionally as the amount of current applied to the actuator decreases a second amount. The method also includes determining, by the processor, an estimated amount of force applied to the outer disc of the aircraft brake by the actuator based on the input parameters and the detected amount of current.
  • Brief Description of the Drawings
  • The subject matter of the present disclosure is particularly pointed out and distinctly claimed in the concluding portion of the specification. A more complete understanding of the present disclosure, however, may best be obtained by referring by way of example only to the detailed description and claims when considered in connection with the drawing figures, wherein like numerals denote like elements.
    • FIG. 1 illustrates an aircraft brake in accordance with various embodiments;
    • FIG. 2 illustrates a block diagram of an electromechanical brake actuator control system, in accordance with various embodiments;
    • FIG. 3A illustrates input parameters to a force observer module, in accordance with various embodiments;
    • FIG. 3B illustrates a system for determining a constant K-nominal, in accordance with various embodiments;
    • FIG. 3C illustrates logic for determining a mode of operation of an actuator, in accordance with various embodiments;
    • FIG. 3D illustrates a system for determining a variable ForceMaxLimit, in accordance with various embodiments;
    • FIG. 3E illustrates a system that is used to calculate an estimated force, in accordance with various embodiments;
    • FIG. 4A illustrates a plot that represents a measured value of force applied by an actuator as a current is applied to an actuator motor and a plot that represents the estimated value of the force using the system of FIG. 3E, in accordance with various embodiments; and
    • FIG. 4B illustrates another plot that represents a measured value of force applied by an actuator as a different current is applied to an actuator motor than in FIG. 4A and another plot that represents the estimated value of the force using the system of FIG. 3E, in accordance with various embodiments.
    Detailed Description
  • The detailed description of exemplary embodiments herein makes reference to the accompanying drawings, which show exemplary embodiments by way of illustration and their best mode. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical, chemical, and mechanical changes may be made without departing from the scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not necessarily limited to the order presented. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component or step may include a singular embodiment or step. Also, any reference to attached, fixed, connected or the like may include permanent, removable, temporary, partial, full and/or any other possible attachment option. Additionally, any reference to without contact (or similar phrases) may also include reduced contact or minimal contact.
  • FIG. 1 illustrates an aircraft brake 100 in accordance with various embodiments. Aircraft brake 100 includes a plurality of actuator motors 102A, 102B, a plurality of electromechanical brake actuators 104A, 104B, a plurality of ball nuts 106A, 106B, a plurality of pucks 108A, 108B, an outer disc 111 and an outer disc 110, and a plurality of rotating discs 112A, 112B, 112C, 112D and stators 114A, 114B, 114C positioned in an alternating fashion between outer disc 111 and outer disc 110. Rotating discs 112A, 112B, 112C, 112D may rotate about an axis 115 and the stators 114A, 114B, 114C may have no angular movement relative to axis 115. Wheels may be coupled to rotating discs 112A, 112B, 112C, 112D such that a linear speed of the aircraft is proportional to the angular speed of rotating discs 112A, 112B, 112C, 112D. As force is applied to outer disc 110 towards outer disc 111 along the axis of rotation 115, rotating discs 112 and stators 114 are forced together in an axial direction. This causes the rotational speed of rotating discs 112A, 112B, 112C, 112D to become reduced (i.e., causes braking effect) due to friction between rotating discs 112A, 112B, 112C, 112D , stators 114A, 114B, 114C , outer disc 111 and outer disc 110. When sufficient force is exerted on rotating discs 112 via outer disc 110, the rotating discs 112A, 112B, 112C, 112D will stop rotating.
  • In order to exert this force onto outer disc 110, actuator motor 102A may cause corresponding electromechanical brake actuators 104A to actuate. Actuator motor 102A may be a brushless motor, such as a permanent magnet synchronous motor (PMSM), a permanent-magnet motor (PMM) or the like. When electromechanical brake actuator 104A actuates, it causes ball nut 106A to extend towards outer disc 110, thus applying force on outer disc 110 towards outer disc 111. Puck 108A is positioned between ball nut 106A and outer disc 110. Puck 108A may be constructed of a softer and/or more compliant material than ball nut 106A such that when ball nut 106A is forced towards outer disc 110, puck 108A prevents outer disc 110 from becoming damaged.
  • Electromechanical brake actuator 104A is actuated in response to current being applied to actuator motor 102A. The amount of force applied by electromechanical brake actuator 104A is related to the amount of current applied to actuator motor 102A. It is desirable to determine this amount of force. One way to determine this force is to use a force sensor within aircraft brake 100. However, it may be desirable to determine this force without the use of a force sensor.
  • Aircraft brake 100 may include a current sensor (such as current sensor 208 of FIG. 2) to detect an amount of current provided to actuator motor 102A. Because the amount of force applied by electromechanical brake actuator 104A is related to the current applied to actuator motor 102A, it is possible to estimate the force using the detected amount of current. Thus, a controller or processor may receive the detected current and estimate a force based on the detected current.
  • FIG. 2 illustrates a block diagram of an aircraft electromechanical brake actuator control system in accordance with various embodiments. Block 205 includes mechanical components. The other blocks may be implemented on one or more controllers and/or processors. For example, the blocks other than block 205 may be stored in a non-transitory storage medium and performed by a processor, may be stored in a special-use processor, may be implemented in a field programmable gate array (FPGA), or the like. A current sensor 208 is coupled to an actuator motor 206 (similar to actuator motor 102A). Current sensor 208 is configured to detect an amount of current supplied to actuator motor 206. A resolver 214 is also coupled to actuator motor 206. Resolver 214 measures the rotational position and speed of actuator motor 206. Actuator motor 206 is also coupled to a gear transmission 210 and a ball screw 212.
  • A force observer module 216 is coupled to block 205. Force observer module 216 is configured to estimate the force of actuator 104A based on data from current sensor 208 and/or resolver 214. Force observer module 216 may be a controller and/or processor or may be implemented in a controller and/or processor.
  • In block 217, the estimated force is compared with a force command signal. The output of block 217 is provided to a force/position control module 200. Output from force/position control module 200 is summed with the rotational speed of actuator motor 206 in block 201. The result of the summation in block 201 is provided to a velocity control module 202. The output from velocity control module 202 is summed with the detected current from current sensor 208 in block 203. The output from block 203 is provided to a current control module 204. The output of current control module 204 is provided to actuator motor 206 as a control signal.
  • FIGs. 3A through 3E illustrate logic within force observer module 216 in accordance with various embodiments. The logic may be implemented in hardware and/or software. In various embodiments, the logic may be stored as machine-readable instructions on a non-transitory memory and performed by a processor. In various embodiments, the logic may be stored on a special-use processor or a field programmable gate array.
  • FIG. 3A illustrates input parameters 390 to force observer module 216. Input parameters 390 may be known parameters for the given motor and thus be predetermined. Input parameters 390 include a max force 300, which may be measured in pound force (lbf), newtons, or the like. Max force 300 represents the maximum force that can be applied by actuator 205. Another input is a max current 302, which may be measured in amps. Max current 302 represents the amount of current to be applied to actuator motor 206 to cause actuator 205 to apply the maximum amount of force. Another input is an efficiency fraction 304. Efficiency fraction 304 indicates the efficiency of the actuator. In the example illustrated in FIG. 3A, max force 300 is given to be 7,857 pounds, max current 302 is given to be 6.5 amps and efficiency fraction 304 is given to be 0.65.
  • FIG. 3B illustrates a system 391 for determining a constant K-nominal 306. K-nominal indicates a relationship between applied force and applied current for actuator 205, such that a current may be multiplied by K-nominal 306 to determine a force and a force can be divided by K-nominal 306 to determine a current. System 391 utilizes max force 300 and max current 302 as inputs. In block 305, the max force 300 is divided by the max current 302, resulting in K-nominal 306.
  • FIG. 3B also illustrates a system 392 for determining a mode of actuator 205 of FIG. 2. With brief reference to FIG. 4A, two plots are shown illustrating the relationship of force and current as current is applied to actuator 205 in accordance with various embodiments. Plot 400 illustrates the estimated force using the methods described herein and plot 402 illustrates the measured force. As illustrated, plot 400 includes a first part 404 corresponding to a first mode, a second part 406 corresponding to a second mode and a third part 408 corresponding to a third mode. In the first mode, the amount of current applied to actuator motor 206 is increasing and the force is increasing substantially proportionally. In the second mode, the amount of current applied to actuator motor 206 is decreasing a first amount. However, the force does not decrease significantly. In the second mode, the force remains substantially constant - it may be less than fifty percent (50%) as much per amp as the force decreases per amp while actuator 205 is operating in the third mode. This is a result of "stiction" (e.g., static friction) in actuator 205. In the third mode, once the "stiction" is overcome, the force is reduced substantially proportionally to the current as the current decreases a second amount.
  • Returning to FIG. 3B, system 392 is designed to determine in which mode actuator 205 is operating. The system 392 utilizes measured current 308 as an input. Measured current 308 may be provided by current sensor 208. Measured current 308 is applied to calculate mode of operation block 310, which generates mode 312 as an output. Mode 312 indicates the mode in which actuator 205 is operating.
  • FIG. 3C illustrates the logic within calculate mode of operation block 310. As illustrated, measured current 308 is utilized as an input. The first portion of the calculate mode of operation block 310 is to calculate a filtered derivative of the current, or iDot 326. iDot 326 represents the estimated time rate of change of current. Blocks 316, 318, 324, 322, 320 and 328 represent a low pass filtered differentiator used to calculate iDot 326.
  • iDot 326 is then compared to zero in block 330, block 332 and block 334. If iDot 326 is greater than 0, then block 330 will output a 1, otherwise block 330 will output a 0. This 1 output corresponds to the first mode, indicating that the current is increasing and the force will increase proportionally to the current. If iDot 326 is equal to 0, then block 332 will output a 2. Otherwise, block 332 will output 0. This 2 output corresponds to the second mode, indicating that the force will not be greatly reduced as the current decreases. If iDot 326 is less than 0, then block 334 will output a 3. Otherwise, block 334 will output 0. The 3 output corresponds to the third mode, indicating that the force will be reduced substantially proportionately to the current as the current is reduced.
  • Block 336 receives the input from block 330, block 332 and block 334 and adds them together. The resulting sum indicates the mode 312. If the mode is equal to 1, then actuator 205 is in the first mode. If the mode is equal to 2, then actuator 205 is operating in the second mode. If the mode is equal to 3, then actuator 205 is operating in the third mode.
  • FIG. 3D illustrates a system 393 for determining a variable ForceMaxLimit 350, indicating the maximum force applied during the most recent iteration of the first mode in accordance with various embodiments. ForceMaxLimit 350 will be used in the force estimation during the second mode. The input to system 393 is mode 312. In block 338, in response to the current beginning to decrease, a true signal will be generated. The true signal generated from block 338 will cause a sample and hold block 346 to become active. Sample and hold block 346 also receives a force previous value (ForcePV 342) signal. ForcePV 342 represents an estimated force that has been delayed. A unit delay block 367 in a system 395 of FIG. 3E receives the estimated force and provides the estimated force as ForcePV 342 after a predetermined delay.
  • When block 338 outputs a true signal, sample and hold block 346 will store and output ForcePV 342 until a new true signal is generated in block 338. Sample and hold block 346 will generate the stored ForcePV 342 as ForceMAXLimit 350. ForceMAXLimit 350 corresponds to the maximum estimated force during the first mode or the second mode.
  • FIG. 3D also illustrates a system 394 for calculating another variable, ForceMINLimit 352, indicating the minimum force applied during the most recent iteration of the third mode. ForceMINLimit 352 will be used in the force estimation during the second mode. Mode 312 is an input to system 394. In block 340, a true signal is generated in response to the current beginning to increase. Sample and hold block 348 also receives ForcePV 342. When the output from block 340 is true, ForcePV 342 will be stored in block 348, and block 348 will output the value as ForceMINLimit 352 until a new "true" signal is generated in block 340.
  • FIG. 3E illustrates a system 395 that is used to calculate an estimated force 380. Estimated force 380 may be provided as the output of force observer module 216 of FIG. 2.
  • Efficiency fraction 304 is a normalized value that ranges from 0 to 1. A value of one is ideal, meaning that actuator 205 is completely efficient and has no losses. With brief reference to FIG. 4A, the slope of first part 404 is equal to measured current 308 multiplied by efficiency fraction 304. The slope of third part 408 is equal to measured current 308 divided by efficiency fraction 304.
  • Returning to FIG. 3E, in block 354, measured current 308 is multiplied by efficiency fraction 304. The output of block 354 represents the relationship of the current and force measurements during the first mode. In block 376, measured current 308 is divided by efficiency fraction 304. The resulting value represents the relationship of the current and the force during the third mode.
  • Block 356 represents a case statement to be used for a selection of a relationship of the current and the force based on the mode. The mode 312 is provided as a selecting variable and the output of block 354 and block 376 are provided as selectable inputs. During the first mode (when mode = 1), block 356 will output the output of block 354. During the third mode (when mode = 3), block 356 will output the output of block 376. During the second mode (when mode = 2), block 356 will output a value calculated elsewhere in system 395 (output of block 374).
  • In block 358, the output of block 356 is multiplied with K-nominal 306, the value calculated in system 391. When K-nominal is multiplied with the output of block 356, the resulting signal indicates a force value. The value of force is stored as force1 360.
  • Block 368 will output a true signal if mode 312 is not equal to 1. The logic in block 368 is used to initialize system 395.
  • Block 370 will output a true signal if ForceMAXLimit 350 is greater than 0. If block 370 and block 368 both output a true signal, then block 372 will output a true signal.
  • Block 362 compares ForceMAXLimit 350 and force1 360 and outputs the smaller of the two signal values. Block 364 compares force1 360 and ForceMINLimit 352 and outputs the larger of the two signal values.
  • While the output of block 372 is true, block 366 will output the signal generated in block 362. When the output of block 372 is false, block 366 will output the signal generated in block 364. The logic implemented in block 368, 370, 372, 362, 364 and 366 generates the estimated force when the mode is equal to 2.
  • Block 378 is a limiter, which prevents the output of block 366 from dropping below 0. The output of block 378 is estimated force 380, and may correspond to the output of force observer module 216.
  • The output of block 366 is driven through unit delay block 367, which delays the input signal (corresponding to the estimated force) by a predetermined period of time, such as one clock cycle, two clock cycles, 1 millisecond, etc. The output of block 367 is ForcePV 342, the previous value of the estimated force. In block 374, ForcePV 342 is divided by K-nominal 306.
  • The output of block 356 is multiplied by K-nominal 306 to result in a force value. Because ForcePV 342 is already a force value, it is divided by K-nominal 306 prior to entering case block 356 so that it can be converted back to a force value in block 358 via multiplication with K-nominal 306.
  • FIG. 4A illustrates plot 402 that represents a measured value of the force applied by actuator 205 as a current is applied to actuator motor 206 in accordance with various embodiments. Plot 400 represents the estimated value of the force using system 395. In FIG. 4A, up to 6.5 amps is applied to the actuator motor 206. As illustrated, the estimated force is similar to the measured force.
  • FIG. 4B illustrates a plot 412 that represents the measured force when a current up to 3 amps is applied to actuator motor 206. Plot 410 illustrates the estimated force using system 395. As illustrated, the estimated force is similar to the measured force during a first part 414 representing the first mode, a second part 416 representing the second mode and a third part 418 representing the third mode in accordance with various embodiments.
  • Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. The scope of the disclosure is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." Moreover, where a phrase similar to "at least one of A, B, or C" is used in the claims, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Different cross-hatching is used throughout the figures to denote different parts but not necessarily to denote the same or different materials.
  • Systems, methods and apparatus are provided herein. In the detailed description herein, references to "one embodiment", "an embodiment", "various embodiments", etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.
  • Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. As used herein, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

Claims (15)

  1. A system for determining a force applied to an outer disc of an aircraft brake by an actuator, the system comprising:
    a current sensor (208) coupled to the actuator and configured to detect a detected amount of current applied to the actuator (206); and
    a controller coupled to the current sensor (208) and configured to determine an estimate of the force applied to the outer disc based on the detected amount of current and a plurality of predetermined input parameters.
  2. The system of claim 1, wherein the plurality of predetermined input parameters include a maximum force of the actuator, a maximum current of the actuator and an efficiency fraction of the actuator.
  3. The system of claim 2, wherein the controller is further configured to determine a constant K-Nominal that can be used to convert a force value into a current value or the current value into the force value by dividing the maximum force of the actuator (206) by the maximum current of the actuator (206).
  4. The system of any preceding claim, wherein the actuator (206) may operate in a first mode indicating that the force applied to the outer disc increases proportionally as the amount of current applied to the actuator increases, a second mode indicating that the force applied to the outer disc remains substantially constant as the amount of current applied to the actuator (206) decreases a first amount and a third mode indicating that the force applied to the outer disc decreases proportionally as the amount of current applied to the actuator decreases a second amount.
  5. The system of claim 4, wherein the controller is further configured to determine a filtered derivative of the detected amount of current and determine whether the actuator is operating in at least one of the first mode, the second mode or the third mode by comparing the filtered derivative with zero.
  6. The system of claim 5, wherein the controller is further configured to select at least one of a first input in response to the actuator operating in the first mode, a second input in response to the actuator operating in the second mode or a third input in response to the actuator operating in the third mode.
  7. The system of claim 6, wherein the plurality of predetermined input parameters include an efficiency fraction and the controller is configured to determine the first input by multiplying the detected amount of current with the efficiency fraction, determine the second input by delaying the estimate of the force and dividing a delayed estimate of the force by a constant value and determine the third input by dividing the detected amount of current by the efficiency fraction.
  8. The system of claim 6, wherein the controller is further configured to convert the selected input from a current value to a force value by multiplying the selected input by a constant value.
  9. The system of claim 4, wherein the controller is further configured to determine a largest estimate of the force during a most recent iteration of the first mode and determine a smallest estimate of the force during a most recent iteration of the third mode.
  10. The system of claim 9, wherein the controller is further configured to select a selected mode and, based on the selected mode, determine the estimate of the force by selecting at least one of a minimum of the largest estimate of the force during the most recent iteration of the first mode and a calculated force value or a maximum of the smallest estimate of the force during the most recent iteration of the third mode and the calculated force value.
  11. A method for determining a force applied to an outer disc of an aircraft brake by an actuator, the method comprising:
    receiving, at a controller and by a current sensor (208), a detected amount of current applied to the actuator (206);
    receiving, at the controller, the detected amount of current and input parameters including a maximum force of the actuator (206), a maximum current of the actuator and an efficiency fraction of the actuator;
    determining, by the processor, a mode of operation of the actuator including a first mode indicating that the force applied to the outer disc increases proportionally as the amount of current applied to the actuator increases, a second mode indicating that the force applied to the outer disc remains substantially constant as the amount of current applied to the actuator decreases a first amount and a third mode indicating that the force applied to the outer disc decreases proportionally as the amount of current applied to the actuator decreases a second amount; and
    determining, by the processor, an estimated amount of force applied to the outer disc of the aircraft brake by the actuator based on the input parameters and the detected amount of current.
  12. The method of claim 11, wherein determining the mode of operation includes determining, by the processor, a filtered derivative of the detected amount of current and comparing the filtered derivative with zero, such that the first mode is determined in response to the filtered derivative being greater than zero, the second mode is determined in response to the filtered derivative being equal to zero and the third mode is determined in response to the filtered derivative being less than zero.
  13. The method of claims 11 or 12, further comprising determining, by the processor, a largest calculated force during a most recent iteration of the first mode and determining a smallest calculated force during a most recent iteration of the third mode.
  14. The method of claim 13, further comprising determining, by the processor, a constant K-Nominal that can be used to convert a force value into a current value or the current value into the force value by dividing the maximum force of the actuator by the maximum current of the actuator.
  15. The method of claim 14, wherein determining the estimated amount of force applied to the outer disc of the aircraft brake by the actuator includes:
    selecting, by the processor, at least one of a first input equal to the detected amount of current multiplied by the efficiency fraction in response to the first mode being determined, a second input being equal to a delayed value of the estimated amount of force divided by the constant K-Nominal in response to the second mode being determined or a third input equal to the detected amount of current divided by the efficiency fraction in response to the third mode being determined;
    determining, by the processor, a value Force1 to be equal to the selected input multiplied by the constant K-Nominal; and
    determining, by the processor, the estimated amount of force to be equal to at least one of a smaller value of the largest calculated force during the most recent iteration of the first mode and the value Force1 or a larger value of the smallest calculated force during the most recent iteration of the third mode and the value Force1 based on the mode of operation.
EP15198705.4A 2014-12-09 2015-12-09 Open loop load force estimation systems and methods Active EP3032234B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/564,545 US9506826B2 (en) 2014-12-09 2014-12-09 Open loop load force estimation systems and methods

Publications (2)

Publication Number Publication Date
EP3032234A1 true EP3032234A1 (en) 2016-06-15
EP3032234B1 EP3032234B1 (en) 2020-05-06

Family

ID=54848426

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15198705.4A Active EP3032234B1 (en) 2014-12-09 2015-12-09 Open loop load force estimation systems and methods

Country Status (2)

Country Link
US (1) US9506826B2 (en)
EP (1) EP3032234B1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3272601A1 (en) * 2016-07-21 2018-01-24 Goodrich Corporation Arrangement and method for clamping force estimation in electromechanical brake systems
IT201600131985A1 (en) * 2016-12-29 2018-06-29 Freni Brembo Spa Method of controlling a braking action that can be exercised by a brake caliper on a mechanical movement organ of a vehicle and its control system.

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9534971B2 (en) 2014-12-09 2017-01-03 Goodrich Corporation Closed loop load force estimation systems and methods

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4577497A (en) * 1983-11-11 1986-03-25 Vickers Public Limited Company Dynamometers
WO2001045245A1 (en) * 1999-12-14 2001-06-21 Delphi Technologies, Inc. Estimated electric caliper clamp force based upon actuator motor position

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6003640A (en) 1997-05-09 1999-12-21 The B.F. Goodrich Company Electronic braking system with brake wear measurement and running clearance adjustment
EP1032518B1 (en) 1997-11-22 2003-05-28 Continental Teves AG & Co. oHG Electromechanical brake system
US6848756B2 (en) * 2000-03-15 2005-02-01 Continental Teves Ag & Co., Ohg Method and control system for applying defined clamping forces
EP1826081B1 (en) 2003-10-15 2011-04-20 Honeywell Inc. Method of boosting a motor torque command based on transient position error signal
US20060108867A1 (en) 2004-09-17 2006-05-25 Mihai Ralea Electromechanical braking system with electrical energy back-up and regenerative energy management
DE102005030618A1 (en) * 2004-10-13 2006-04-20 Knorr-Bremse Systeme für Nutzfahrzeuge GmbH Disc brake in self-reinforcing design and control method for a self-energizing brake
US7317981B2 (en) 2004-11-19 2008-01-08 Honeywell International, Inc. Aircraft brake actuation system and method including anti-hysteresis control
FR2882541B1 (en) 2005-02-25 2009-01-16 Messier Bugatti Sa ASSEMBLY METHOD IN AN ELECTRIC BRAKE VEHICLE BRAKING SYSTEM
FR2888917B1 (en) 2005-07-21 2009-11-20 Valeo Vision LIGHTING OR SIGNALING DEVICE, IN PARTICULAR FOR A MOTOR VEHICLE
EP1746399A1 (en) 2005-07-22 2007-01-24 Delphi Technologies, Inc. Estimating torque/force exerted by a load against a motor-driven actuator
US20080284358A1 (en) 2005-11-30 2008-11-20 Mihai Ralea Controller for Electromechanical Braking System with Power Demand Control and Method
US7353101B2 (en) 2006-04-18 2008-04-01 Honeywell International Inc. Methods and apparatus to control electro-mechanical brakes
US7630813B2 (en) 2006-06-06 2009-12-08 Delphi Technologies, Inc. Method for controlling electromechanical brakes using parameter identification and no additional sensors
JP2010203561A (en) 2009-03-05 2010-09-16 Kayaba Ind Co Ltd Electric brake
US8180548B2 (en) 2009-04-24 2012-05-15 Goodrich Corporation Deceleration controlled braking
US20100292889A1 (en) * 2009-05-14 2010-11-18 Cahill Eric D Brake operation built-in test equipment
US8393203B2 (en) * 2010-03-08 2013-03-12 Goodrich Corporation Systems and methods for built in test equipment for a brake control system
US9028014B2 (en) 2010-12-08 2015-05-12 Goodrich Corporation System and method for providing indication of braking for electric brakes
US9669810B2 (en) 2012-01-10 2017-06-06 Honeywell International Inc. Brake assembly including independently activatable brake actuators
CA2902662C (en) 2013-03-06 2020-08-04 Bombardier Inc. Electric braking system and method relying on voltage hysteresis for applied brake power control
US9534971B2 (en) 2014-12-09 2017-01-03 Goodrich Corporation Closed loop load force estimation systems and methods

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4577497A (en) * 1983-11-11 1986-03-25 Vickers Public Limited Company Dynamometers
WO2001045245A1 (en) * 1999-12-14 2001-06-21 Delphi Technologies, Inc. Estimated electric caliper clamp force based upon actuator motor position

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3272601A1 (en) * 2016-07-21 2018-01-24 Goodrich Corporation Arrangement and method for clamping force estimation in electromechanical brake systems
US9995354B2 (en) 2016-07-21 2018-06-12 Goodrich Corporation Systems and methods for clamping force estimation in electromechanical brake systems
IT201600131985A1 (en) * 2016-12-29 2018-06-29 Freni Brembo Spa Method of controlling a braking action that can be exercised by a brake caliper on a mechanical movement organ of a vehicle and its control system.
WO2018122741A1 (en) * 2016-12-29 2018-07-05 Freni Brembo S.P.A. Method for controlling a braking action applicable by a brake caliper on a mechanical movement member of a vehicle and system thereof
US11643059B2 (en) 2016-12-29 2023-05-09 Brembo S.P.A. Method for controlling a braking action applicable by a brake caliper on a mechanical movement member of a vehicle and system thereof

Also Published As

Publication number Publication date
EP3032234B1 (en) 2020-05-06
US9506826B2 (en) 2016-11-29
US20160161351A1 (en) 2016-06-09

Similar Documents

Publication Publication Date Title
EP3032234B1 (en) Open loop load force estimation systems and methods
EP3031682B1 (en) Closed loop load force estimation systems and methods
US9701290B2 (en) Method and apparatus for operating a braking device, braking device
CN101627532B (en) Control method and motor starter device
KR101958503B1 (en) Method, regulating and/or control unit, and parking brake having a regulating and/or control unit of said type for adjusting a parking brake in a vehicle
CN104859624B (en) Method for adjusting the parking brake in vehicle
JP6811101B2 (en) Electric parking brake device and brake device
US9725077B2 (en) Method for providing a clamping force generated by an automatic parking brake
CN105711574B (en) Method and device for operating a brake device, brake device
US10498265B2 (en) Motor drive control device and motor drive control method
US9545903B2 (en) Electromechanical brake actuator with variable speed epicyclic gearbox
US9610927B2 (en) Systems and methods for electric brake force estimation tolerant to drivetrain stiction
EP3072759B1 (en) Brake force measurement techniques
EP3118076A2 (en) Electromechanical braking systems and methods with power demand control
CN105523027B (en) Method and device for operating a brake mechanism, brake mechanism
EP3272601B1 (en) Arrangement and method for clamping force estimation in electromechanical brake systems
CN108292554B (en) Current monitoring on a consumer
JP6477534B2 (en) Vehicle motor control device
US10486666B2 (en) Method for determining a position and/or change in position of a hydraulic pump of a motor vehicle brake system and motor vehicle brake system
US10246063B2 (en) Wheel reference balance estimator
EP3434541B1 (en) System and method for emi reduction in an electric braking system
JP7155055B2 (en) electric parking brake device
Ki et al. Fault-tolerant control of EMB systems
US11565671B2 (en) Method for monitoring an electric motor, electronic control module, hydraulic brake system and storage medium
KR101991138B1 (en) Apparatus and Method for detecting speed of motor in electro-hydraulic control system

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20161213

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602015052081

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G01L0005280000

Ipc: G01L0005220000

RIC1 Information provided on ipc code assigned before grant

Ipc: G01L 5/22 20060101AFI20191023BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200107

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1267541

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200515

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015052081

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200806

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200906

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200807

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200907

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200806

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1267541

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015052081

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20210209

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602015052081

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201209

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201209

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201231

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201231

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210701

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201231

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230522

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231121

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231122

Year of fee payment: 9