Patent Grant
10471947
The disclosure relates to vehicle brake systems.
During periodic maintenance, the amount of wear on a vehicle's braking assembly is manually assessed by a maintenance technician. On an aircraft, for example, the remaining life of the braking assembly is determined by observing the length of a wear indicator pin, also known as a wear pin.
In general, this disclosure describes systems and methods for automated measurements of the remaining use of a vehicle's braking assembly. The measurement of the remaining use may indicate the number of remaining braking events (e.g., aircraft landings) with optimal braking without replacing the braking lining. A transceiver connected to processing circuitry can determine an estimate of the remaining use. The transceiver sends signals and receives reflections of the signals. The processing circuitry determines an estimated remaining use of the braking assembly based on the time of transmission and the time of receipt by the transceiver. The difference between the time of transmission and the time of receipt may also indicates, or relates to, the distance between the transceiver and the wear pin and the length of the wear pin, which the processing circuitry can use to estimate a remaining use or a remaining life for the braking assembly.
In some examples, a device is configured to determine an estimated remaining use of a brake assembly. The device includes a transceiver configured to transmit a signal towards a wear pin in the brake assembly at a first time and receive a reflection of the signal from the wear pin at a second time. The device also includes processing circuitry configured to determine a difference of the first time and the second time and determine the estimated remaining use of the brake assembly based on the difference of the first time and the second time.
In some examples, a method includes causing a transceiver to transmit a signal towards a wear pin in a brake assembly at a first time and causing the transceiver to receive a reflection of the signal from the wear pin at a second time. The method also includes determining a difference of the first time and the second time and determining an estimated remaining use of a brake assembly based on the difference of the first time and the second time.
In some examples, a device includes a computer-readable medium having executable instructions stored thereon, wherein the instructions are configured to be executable by one or more processors for causing the one or more processors to cause a transceiver to transmit a signal towards a wear pin in a brake assembly at a first time. The instructions are also configured to cause the one or more processors to cause the transceiver to receive a reflection of the signal from the wear pin at a second time. The instructions are further configured to cause the one or more processors to determine a difference of the first time and the second time and determining an estimated remaining use of a brake assembly based on the difference of the first time and the second time.
This disclosure describes techniques for determining an estimated remaining use of a brake assembly based on signals transmitted towards a wear pin (e.g., a “wear indicator” or a “wear indicator pin”) in the brake assembly. In some examples, a device includes a transceiver configured to transmit a signal and receive a reflection of the signal. The device also includes processing circuitry configured to determine the time difference between the transmission and receipt of the signal. The processing circuitry is configured to determine an estimated remaining use of the brake assembly based on the time difference. In some examples, the processing circuitry is configured to determine the distance between the transceiver and the wear pin based on the time difference and determine the length of the wear pin based on the distance between the transceiver and the wear pin. The processing circuitry may be configured to determine the estimated remaining use based on an estimated rate of wear for a brake lining of the braking assembly.
The techniques described herein may be described with respect to determining a length of a wear pin with the understanding that the length of the wear pin corresponds to the amount of use or estimated life of the brake assembly. It should be understood however that when implemented by processing circuitry, the processing circuitry does not necessarily need a length and may just map a time to the estimated life of the brake assembly. The mapping, which may be stored to a memory device, can associate times and estimated remaining uses for the brake assembly. The mapping can be based on an equation, a lookup table, or a data structure and may include data such as times, distances, lengths, remaining uses, and wear rates.
The device can be installed in an existing brake assembly as a retrofit sensor (e.g., an after-market product), or the device can be built into a new brake assembly. In some examples, the device is installed such that the transceiver does not touch the wear pin. The processing circuitry may be configured to determine and track the length of the wear pin as the length declines over the life of the brake assembly. The processing circuitry may also be configured to output data indicating the length(s) of the wear pin and/or estimate(s) of the remaining life of the brake assembly.
Other methods of assessing the length of a brake assembly's wear indicator pin are not proactive, as they require a second person in the cockpit of the aircraft to apply the brakes or to set the parking brake before the pin can be observed. Thus, the techniques of this disclosure may enable a technician to more easily determine the length of the wear pin. Additionally, because the brakes are replaced when a technician observes that the wear pin is flush or nearly flush with the surface of the brake carrier, the brakes may not be used to the fullest extent of their remaining lifespan. A device of this disclosure may output indications of the distance between the transceiver and the wear pin, the length of the wear pin, the remaining use of the braking assembly, an alert, and/or other data determined by the processing circuitry. The device may generate more accurate notifications of the remaining life of a brake assembly, as compared to a caliper measurement, allowing maintenance workers to change the brakes at an appropriate time. Accurate notifications can allow maintenance workers to get all of the useful life out of the brakes, without the risk that replacement will be postponed too long. In some examples, one-tenth of one inch of length on the wear pin may last approximately one hundred braking events.
A monolithic construction of the proposed device can be placed on top of the brake system's carrier, surrounding the brake wear pin indicator. Opposite the brake wear pin, a laser transmitter and receiver can be installed. The laser transmitter and receiver may not physically contact the brake wear pin in order to conduct a measurement. A transceiver sends pulsed signals on the transmitter and receives the signals on the receiver. Processing circuitry may then measure the time taken for the light to travel from transmitter to receiver. Using the known speed of light, or any other applicable speed of the signals, the processing circuitry can determine the distance between the laser unit and the tip of the brake wear pin. The processing circuitry can interpret this information to show the brake wear pin length. Using a molding manufacturing process, the proposed device can be constructed so that the device can withstand the harsh environment conditions of an aircraft wheel. This method of measuring the length of the wear pin may not require human intervention because the processing circuitry may be configured to output an indication of the estimated remaining use and/or the length of the wear pin. The processing circuitry can measure and log data automatically and more frequently than other brake wear devices. This device may enable a vehicle operator, through a computing system located in an avionics bay, to apply algorithms on the measured data and predict the wear remaining on a brake assembly and plan for maintenance more efficiently.
Device 100 may be attached to brake assembly 170 by mounting, gluing, taping, soldering, and/or any other attaching technique. In some examples, transceiver 110 is attached to brake assembly 170 such that transceiver 110 does not move. Therefore, as the length of wear indicator pin 160 decreases, the difference in time between transmission of signal 140 and receipt of reflected signal 150 may increase, indicating an increased distance between transceiver 110 and wear indicator pin 160. The increased distance may indicate a reduction in the length of wear indicator pin 160, which indicates the remaining use of brake assembly 170.
Transceiver 110 includes both transmitting and receiving capabilities and can be directed toward an exposed tip of wear indicator pin 160. A transmitting component of transceiver 110 is capable of emitting a signal, such as transmitted signal 140, toward the tip of wear indicator pin 160. A receiving component of transceiver 110 is capable of sensing or detecting a signal, such as reflected signal 150, returning from wear indicator pin 160. Transceiver 110 may include a laser, an ultrasonic sensor, or any other sensor capable of sending and receiving signals.
Transmitted signal 140 may consist of an electromagnetic wave of a specific frequency, for example, light emitted from a laser or a radio-frequency (RF) wave. Transmitted signal 140 reflects off of the tip or surface of wear indicator pin 160, becoming reflected signal 150 having the same or similar frequency as transmitted signal 140. Transceiver 110 may transmit signal 140 at a first time and receive reflected signal 150 at a second time. For example, the first time and the second time may be one millisecond apart. The difference between the first time and the second time, along with the speed of signals 140 and 150 may indicate the distance between transceiver 110 and wear pin 160.
Processing circuitry 120 is configured to determine an estimated remaining use of brake assembly 170. Processing circuitry 120 may be configured to determine the estimated remaining use based directly on the time difference of signals 140 and 150, or processing circuitry 120 may first determine the length of wear indicator pin 160. Processing circuitry 120 can determine the length of wear indicator pin 160 based on the time difference and determine the remaining use of brake assembly 170 based on the length of wear indicator pin 160. Processing circuitry 120 may divide the length by an estimate of the wear (e.g., reduction in length) per braking event to determine the remaining use. Processing circuitry 120 can use the specifications for brake assembly 170 to determine the estimate of wear per braking event (e.g., rate of wear). Alternatively or additionally, processing circuitry 110 can use measurements of the length of wear indicator pin 160, along with the number of braking events between measurements, to determine the estimate of wear per braking event.
Processing circuitry 120 is configured to cause transceiver 110 to emit transmitted signal 140, and to subsequently receive from transceiver 110 a set of time data indicative of the time at which transceiver 110 received reflected signal 150. Processing circuitry 120 is further configured to determine a difference in time between the transmission of transmitted signal 140 and receipt of reflected signal 150, and to use this time difference along with a known signal velocity to determine the distance travelled by transmitted signal 140. Using this distance, processing circuitry 120 may be configured to determine the remaining length of wear indicator pin 160 by comparing the current distance measurement to an initial or previous distance or length. Processing circuitry 120 may also be configured to transmit the determined current length of wear indicator pin 160, along with a timestamp indicative of the time at which the length was measured, to be stored within memory device 130.
Processing circuitry 120 may further be configured to retrieve from memory device 130 a previous set of wear pin length and time data and use the data in conjunction with a current measurement in order to determine a rate of change of the length of wear pin 160 during the time between which the different measurements were conducted. Processing circuitry 120 may then transmit the rate of change data to be stored in memory device 130 along with the length and time data. Processing circuitry 120 may determine if the length of the wear pin is less than a threshold length and generate an alert in response to determining that the length of the wear pin is less than the threshold length. Such an alert may be an audio alert, such as a recorded verbal message or a tone, or alternatively or additionally, a visual alert, such as a displayed phrase, message, symbol, or color.
In some examples, processing circuitry 120 may perform data analysis on the data indicating the length of wear indicator pin 160. For example, processing circuitry 120 may use data indicating the number of braking events, the weather conditions during each braking event, the vehicle operator during each braking event, the type of surface for each braking event (asphalt, concrete, etc.), and/or any other data stored to memory device 130. Processing circuitry 120 may determine metrics such as the rate of wear and the estimated remaining life of wear indicator pin 160. Processing circuitry 120 may also determine when and whether to generate alerts regarding the status of wear indicator pin 160 and/or brake assembly 170. Alternatively or additionally, processing circuitry 120 may output the data to an external computing system, such as the avionics bay of an aircraft, to perform the data analysis on data relating to wear indicator pin 160 and/or brake assembly 170.
Memory device 130 is a non-transitory computer-readable medium capable of storing information indicative of the length of wear indicator pin 160 along with a timestamp indicating the time at which the measurement was made. Memory device 130 may be further configured to store multiple sets of length and time data, as well as rates of change of the length of wear pin 160 between subsequent measurements. Memory device 130 may also store threshold lengths and threshold distances that processing circuitry 120 may use to determine if wear pin 160 is approaching an end of useful life. In some examples, memory device 130 stores data relating to braking events, such as a measurement conducted when the brakes are applied, and weather or climate conditions.
Processing circuitry 120 may be configured to determine the estimated remaining use of brake assembly 170 directly based on the time difference of signals 140 and 150, for example, based on a mapping of time differences to remaining-use estimates stored to memory device 130. The mapping may take the form a data structure such as an array or a lookup table that associates estimated remaining uses with time differences. Processing circuitry 120 may use the mapping stored to memory device 130 to directly determine the estimated remaining use of brake assembly 170, or processing circuitry 120 may first determine the distance between transceiver 110 and wear indicator pin 160. Processing circuitry 120 may be configured to update the mapping stored to memory device 130 by storing the new value of the time difference and the new estimated remaining use of brake assembly 170 to memory device 130.
Device 100 may also include a communication module (e.g., communication module 240 shown in
Wear indicator pin 160 is a component whose exposed length represents the remaining lifespan of brake assembly 170 of a vehicle. Wear indicator pin 160 is also referred to herein as “wear pin 160.” In some examples, when the tip of wear indicator pin 160 is flush with the brake carrier, the vehicle's brakes may need replacement due to excessive wear. Wear indicator pin 160 may have any suitable shape, such as a cylinder or a rectangle, where the length of wear indicator pin 160 may decrease over time. As a cylinder, wear indicator pin 160 may have a radius of a few millimeters. Wear indicator pin 160 can also include a material layer, a coating, and/or a covering that indicates the wear of brake assembly 170.
Brake assembly 170 may include braking elements for slowing the speed of rotation of vehicle wheels, such as automobile wheels or aircraft landing gear. Brake assembly 170 may be mounted to or built in to the wheels. Device 100 may be mounted to a part of brake assembly 170, such as a brake carrier. Brake assembly 170 may also be referred to herein as a “braking assembly” or as a “braking system.” As used herein, the term “the remaining use of brake assembly 170” may refer to the remaining use of brake lining 190.
Wear indicator pin 160 is mounted on plate 180 (e.g., by a rivet), which holds brake lining 190 on the other side of plate 190. Plate 180 may include metal material. Pressure plate 320 shown in
In accordance with the techniques of this disclosure, processing circuitry 120 may determine the estimated remaining use of brake assembly 170 based on the time of transmission of signal 140 and the time of receipt of reflected signal 150. Device 100 may perform a measurement of the estimated remaining use of brake assembly 170 automatically (e.g., without a human operator). For example, a measurement of the estimated remaining use of brake assembly 170 may occur when the brakes of brake assembly 170 are applied. Processing circuitry 120 may be configured to determine when the brakes are applied and to cause, without human intervention, transceiver 110 to transmit and receive signals 140 and 150 when the brakes are applied.
The techniques of this disclosure may be especially useful for after-market devices that can be installed on existing brake assemblies. An after-market device may be installed on a brake carrier such that the device does not contact wear indicator pin 160.
Transceiver 210 includes both transmitting and receiving capabilities and can be directed toward an exposed tip or surface of the brake assembly's wear indicator pin. Transceiver 210 is an example of transceiver 110. A transmitting component of transceiver 210 is capable of emitting a signal toward the tip or surface of the wear indicator pin. A receiving component of transceiver 210 is capable of sensing or detecting a reflected signal returning from the wear indicator pin. Transceiver 210 may incorporate a laser, an ultrasonic sensor, or any other sensor capable of sending and receiving signals.
Processing circuitry 220 is configured to determine the length of a brake assembly's wear indicator pin. Processing circuitry 220 is configured to cause transceiver 210 to emit a signal, and to subsequently receive from transceiver 210 a reflection of that signal. Processing circuitry 220 can determine the remaining use based on the length of the wear pin and a rate of wear stored to memory device 230. Processing circuitry 220 may determine the remaining use in terms of the number of braking events.
Timer 222 is configured to transmit to processing circuitry 220 a first timestamp indicative of the time at which the signal was emitted. Timer 222 is further configured to transmit to processing circuitry a second timestamp indicative of the time at which the reflected signal was received or detected. In some examples, timer 222 may include a counter configured to increment a number stored to a register based on a clock signal. Processing circuitry 220 may be configured to reset timer 222 at the time that transceiver 210 transmits a signal towards a wear pin. Processing circuitry 220 may check the timer value when transceiver 210 receives a reflected signal to determine the time at which the reflected signal is received.
Processing circuitry 220 is further configured to determine a difference in time between the first timestamp, indicative of the transmitted signal, and the second timestamp, indicative of the reflected signal, and to use this time difference along with a known signal velocity to determine the distance travelled by the transmitted signal. Using this determined distance, processing circuitry 220 may be configured to determine the remaining length of the wear indicator pin by comparing the current distance measurement to an initial or previous distance or length measurement. Processing circuitry 220 may also be configured to transmit the determined current length of the wear indicator pin, along with a timestamp indicative of the time at which the current length measurement was made, to be stored within memory device 230.
Processing circuitry 220 may further be configured to retrieve from memory device 230 a previous set of estimated remaining use data and use the data in conjunction with a current measurement in order to determine a rate of change of the estimated remaining use during the time between which the different measurements were conducted. Processing circuitry 220 may then transmit the rate-of-change data to be stored in memory device 230 along with the current estimated remaining use and time data. Processing circuitry 220 may determine whether the estimated remaining use is less than a threshold amount and/or the length of the wear pin is less than a threshold length stored to memory device 230, and processing circuitry 220 may generate an alert in response to determining that the estimated remaining use is less than a threshold amount and/or the length of the wear pin is less than the threshold length. Processing circuitry 220 may cause communication module 240 to transmit the alert to an external device. Processing circuitry 220 may also be configured to determine that the estimated remaining use is less than a threshold amount and/or the length of the wear pin is greater than the threshold length and refrain from generating the alert in response to determining that the estimated remaining use is less than a threshold amount and/or the length of the wear pin is greater than the threshold length. In some examples, a determination that the estimated remaining use is less than a threshold amount and/or the length is less than the threshold length includes a determination that the estimated remaining use and/or the length is less than or equal than the threshold amount or the threshold length.
In some examples, processing circuitry 220 may perform data analysis on the data indicating the length of the wear indicator pin. For example, processing circuitry 220 may use data indicating the number of braking events, the weather conditions during each braking event, the vehicle operator during each braking event, the type of surface for each braking event (asphalt, concrete, etc.), and/or any other data stored to memory device 230. Processing circuitry 220 may determine metrics such as the rate of wear and the estimated remaining life of the wear indicator pin. Processing circuitry 220 may also determine whether and when to generate alerts regarding the status of the wear indicator pin and/or the vehicle's brake assembly.
Processing circuitry 220 may be further configured to cause device 200 to perform a measurement of the length of the wear indicator pin automatically (e.g., without a human operator). For example, a measurement of the length of the wear indicator pin may occur automatically when the brakes of the brake assembly are applied. Processing circuitry 220 may be configured to determine when the brakes are applied and to cause, without human intervention, transceiver 210 to transmit and receive signals when the brakes are applied.
Memory device 230 is a non-transitory computer-readable medium capable of storing information indicative of the length of wear indicator pin along with a timestamp indicating the time at which the measurement was made. Memory device 230 may be further configured to store multiple sets of length and time data, as well as rates of change of the length of wear pin between subsequent measurements. Memory device 230 may also store threshold amounts, threshold lengths, and threshold distances that processing circuitry 220 may use to determine if the wear indicator pin is approaching the end of its useful life. In some examples, memory device 230 stores data relating to braking events and weather conditions. Memory device 230 may also store reference data indicating an initial remaining use and/or an initial length of the wear pin or a distance between transceiver 210 and a brake carrier. In some examples, it may be acceptable for the surface of the wear pin to reach the edge of the brake carrier, or there may a particular distance from the edge of the brake carrier at which the wear pin indicates that the brakes should be replaced.
Communication module 240 may output any or all of the collected measurements, determined data, and/or generated alerts to an external receiver (e.g., an external device). An external receiver may consist of a computing system, such as the avionics bay of an aircraft, to perform data analysis on data relating to the wear indicator pin and/or the vehicle's brake assembly. Alternatively or additionally, communication module 240 may output the data or generated alerts to a display device, to be observed by, for example, a pilot, driver, or mechanic. Communication module 240 may consist of a hard-wired system, such as wires or fiber-optic cable and/or a wireless communication system, such as Wi-Fi, Bluetooth, radio-frequency identification (RFID), near-field communication (NFC), or any other electromagnetic signal.
Attachment element 250 connects device 200 to the external carrier of a vehicle's brake assembly, such that transceiver 210 is not capable of moving with respect to the external carrier. The connection between device 200 and the brake assembly may be a rigid connection or there may be some flexibility to the connection. Attachment element 250 may be connected to the brake assembly by any appropriately permanent means, for example, by mounting, screwing, welding, gluing, taping, soldering, and/or any other attaching technique. In some examples, attachment element 250 includes an electro-mechanical element, such as a solenoid configured to provide attachment means in response to an electrical current.
There are different types of brake systems available depending on the type of aircraft, ranging from single disc brakes to segmented rotor brakes and carbon brakes. For simple brake systems, wear determination can include visually inspecting the brake disc. For complex brake systems, the brake assembly may include a wear indicator pin to help device 200 to determine the brake wear. The brake wear pin protrudes out via brake carrier or a carrier element. Device 200 can be mounted on the brake carrier or the carrier element rigidly such that the device 200 does not move and transceiver 210 is positioned directly above the wear pin and configured to transmit and receive the return signal.
Power supply 260 delivers electrical power to drive device 200. Power supply 260 may consist of an external battery, such as a lithium-ion battery or any lithium-based chemistry battery. Alternatively, power supply 260 may consist of an existing power source that is delivering power to the rest of the wheel-and-brake assembly. Alternatively, power supply 260 may consist of a system for passively harvesting energy emitted by the rest of the brake assembly. An example of such a passive energy source may include thermo-electric generators (TEG) or vibration or electro-magnetic power sources. Additionally, capacitors (e.g., supercapacitors) may be used as an energy storage device and auxiliary power source for the system. Device 200 may be configured to use low amounts of power, operating only in conjunction with a harvested energy source or with a battery. For example, the sampling period of any sensor output monitoring may be optimized to save energy by drawing power only during the sampling period, and the sensor may operate in a “sleep mode” at all other times.
The vehicle brake assembly includes pressure plate 320, wear indicator pin 340, and brake carrier 350. Pressure plate 320 is configured to move with respect to brake carrier 350 as the vehicle's brakes wear down through use over time. Pressure plate 320 is an example of plate 180 shown in
Because wear indicator pin 340 is physically coupled to pressure plate 320, wear indicator pin 340 likewise moves with respect to brake carrier 350, and with respect to device 330, which is physically coupled to brake carrier 350 through attachment element 390. In the example of
Device 330 is configured to accurately measure and monitor remaining wear length 360 of wear indicator pin 340, by measuring distance 362 between the tip of wear pin 340 and transceiver 310, positioned opposite the tip of wear pin 340.
Transceiver 310 is configured to transmit emitted signal 370 at a first time toward the tip of wear pin 340. Emitted signal 370 then reflects off the tip of wear pin 340 and becomes reflected signal 380. Transceiver 310 is configured to receive or detect reflected signal 380 at a second time. In some examples, device 330 is then configured to determine distance 362 between transceiver 310 and the tip of wear pin 340, which is equivalent to the distance travelled by emitted signal 370, which is also equivalent to the distance travelled by reflected signal 380. This measurement may be determined by the relation
where:
Over time, the tip of wear indicator pin 340 moves in the positive y-axis direction towards the edge of brake carrier 350. As wear indicator pin 340 moves, distance 362 increases, and remaining wear length 360 decreases. Device 330 may be configured to store a threshold length for wear indicator pin 340, where the threshold length may indicate remaining wear length 360 when the brakes should be replaced. As an alternative or additional technique, device 330 may determine the remaining use of the brake assembly directly from the time difference of signals 370 and 380.
Number of remaining braking events=L/(Wear per braking event) (3)
Wear per braking event=Loriginal/(Original number of braking events) (4)
Using Equation (3), the processing circuitry of device 330 may be configured to then determine an estimate of the number of remaining braking events (e.g., landings) that can occur with optimal braking before replacing the brake lining. The processing circuitry can determine the number of remaining braking events by dividing the remaining wear length 360 (L) by the wear per braking event (e.g., rate of wear). The processing circuitry can determine the wear per braking event by dividing the original length (Loriginal) of wear indicator pin 340 by the original number of braking events specified by the part supplier, using Equation (4).
For example, if the original length of wear indicator pin 340 is one inch (e.g., approximately twenty-five millimeters), and the part supplier states that the new brake lining can perform for one thousand braking events, the processing circuitry determines that the wear per braking event is 0.001 inches or 0.025 millimeters. If the processing circuitry of device 330 later determines that a new length of wear indicator pin 340 is ten millimeters less than the original, the processing circuitry may determine that the new length is fifteen millimeters. Using a rate of wear of 0.025 millimeters per braking event and Equation (3), the processing circuitry determines that the remaining use of the brake lining is six hundred braking events.
For example, the wear pin length and a corresponding predicted remaining brake lifespan, or an estimated remaining number of braking events, may be transmitted for display in avionics bay of an aircraft on which the brake assembly on which the measurement was made. A log of wear pin measurements may be stored to analyze braking and wear trends over time. This data may be kept in storage 562 or transferred offsite to cloud storage 564 for wider access by the airline. The wear pin measurement data can be used by airlines or the operators of other vehicles for further analytics 566, monitoring the rate and trend at which brake wear is happening per landing. Based on the trend data airline can predict how many more takeoffs or landings can be performed before brake maintenance or brake replacements are required.
Another example application of enhanced data analytics 566 is to design a customized training plan for pilots for cases where considerable amount of brake pin wear is observed frequently during landings and are attributed to judgment error of vehicle operators, for example, landing the aircraft long and applying hard brakes to stop the aircraft under normal weather conditions. Data analytics 566 may associate each braking event with data such as vehicle operator, weather conditions, runway length, runway surface type (asphalt, concrete, etc.), runway conditions, and/or other relevant data. Data analytics 566 may determine which vehicle operators are “hard brakers” based on the rate of wear associated with each vehicle operator and each braking event.
Another example application of enhanced data analytics 566 is to design and implement an improved pricing mechanism. The wear pin measurement trend data, combined with operating conditions data, for example, runway data, contamination data, weather, and climate conditions, may be used by brake suppliers to design a better pricing mechanism. For example, if the brake system is used in harsh or severe weather or runway conditions, the tendency of hard braking would be higher, and the brakes would wear down faster. Knowing such details, a brake supplier could implement a pricing system based on an estimated cost per braking event. The pricing system can be tailored to the individual needs and environments of each customer. For example, an original equipment manufacturer (OEM) may determine pricing and the terms of annual maintenance contracts based on data determined by processing circuitry 540.
Another application of the wear pin measurement data is for use by a maintenance technician or group 580. Determined brake data may be sent to handheld device 570, for example a device dedicated solely to brake assembly data, or alternatively, a multi-purpose device such as a smartphone. Maintenance operations 580 may use the information to monitor when the brake assembly is due for maintenance or replacement, and prepare the replacement parts, thereby reducing the turnaround time and aircraft downtime.
In some examples, a computing device (e.g., processing circuitry 540, the computing system(s) of avionics bay 560, or handheld device 570) and/or an application (e.g., cloud application 564 or data analytics 566) may be configured to determine multiple lengths of the wear pin over time. For example, processing circuitry 540 may be configured to cause transceiver 510 to transmit and receive signals at a first time and a second time, where processing circuitry 540 determines a first length of the wear pin based on the first time and the second time. Processing circuitry 540 may be further configured to cause transceiver 510 to transmit and receive signals at a third time and a fourth time, where processing circuitry 540 determines a second length of the wear pin based on the third time and the fourth time. Processing circuitry 540 may perform additional measurements of the length of the wear pin.
Based on the multiple measurements of the length, the computing device and/or the application may determine a number of braking events between measurements based on records of the vehicle operation. The computing device and/or the application may determine a rate of wear based on the lengths and the number of braking events. The rate of wear may indicate whether the vehicle operator is a hard braker. The presence or absence of other factors such as weather, surface type, and/or surface conditions can also affect the rate of wear. The computing device and/or the application may store the lengths and the rate of wear to storage 562. If the computing device and/or the application determines that the rate of wear exceeds a threshold rate, the computing device and/or the application can generate an alert.
The computing device and/or the application may determine an estimated remaining use on brake assembly 550 based on the length(s) and/or the rate of wear. Other factors that affect the estimated remaining use include the expected type of operation in the future, the expected weather conditions in the future (e.g., based on location and time of year), and expected surface types in the future. The computing device and/or the application may determine the remaining use in terms of time (e.g., a number of days or weeks) or in terms of the number of remaining braking events (e.g., ten remaining landings before replacement).
In the example of
In the example of
The techniques of this disclosure may be implemented in a device or article of manufacture including a computer-readable storage medium. The term “processing circuitry,” as used herein may refer to any of the foregoing structure or any other structure suitable for processing program code and/or data or otherwise implementing the techniques described herein. Elements of processing circuitry 120 and 220 may be implemented in any of a variety of types of solid state circuit elements, such as CPUs, CPU cores, GPUs, digital signal processors (DSPs), application-specific integrated circuits (ASICs), a mixed-signal integrated circuits, field programmable gate arrays (FPGAs), microcontrollers, programmable logic controllers (PLCs), programmable logic device (PLDs), complex PLDs (CPLDs), a system on a chip (SoC), any subsection of any of the above, an interconnected or distributed combination of any of the above, or any other integrated or discrete logic circuitry, or any other type of component or one or more components capable of being configured in accordance with any of the examples disclosed herein.
Devices 100 and 200 may include one or more memory devices, such as memory devices 130 and 230, that include any volatile or non-volatile media, such as a RAM, ROM, non-volatile RAM (NVRAM), electrically erasable programmable ROM (EEPROM), flash memory, and the like. Memory devices 130 and 230 may store computer-readable instructions that, when executed by processing circuitry, cause the processing circuitry to implement the techniques attributed herein to processing circuitry 120 and 220.
Elements of processing circuitry 120 and 220 and/or memory device 130 and 230 may be programmed with various forms of software. The processing circuitry and/or the transceiver may be implemented at least in part as, or include, one or more executable applications, application modules, libraries, classes, methods, objects, routines, subroutines, firmware, and/or embedded code, for example. Elements of processing circuitry 120 and 220 and/or memory device 130 and 230 as in any of the examples herein may be implemented as a device, a system, an apparatus, and may embody or implement a method of determining an estimated altitude of a melting layer.
The techniques of this disclosure may be implemented in a wide variety of computing devices. Any components, modules or units have been described to emphasize functional aspects and does not necessarily require realization by different hardware units. The techniques described herein may be implemented in hardware, software, firmware, or any combination thereof. Any features described as modules, units or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. In some cases, various features may be implemented as an integrated circuit device, such as an integrated circuit chip or chipset.
Various examples of the disclosure have been described. Any combination of the described systems, operations, or functions is contemplated. These and other examples are within the scope of the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 576671 | Hamlin | Feb 1897 | A |
| 2522181 | Krikorian | Sep 1950 | A |
| 3604865 | Bricker | Sep 1971 | A |
| 4013143 | Juhasz | Mar 1977 | A |
| 4107604 | Bernier | Aug 1978 | A |
| 4184145 | Fima | Jan 1980 | A |
| 4279214 | Thorn | Jul 1981 | A |
| 4318955 | Kulakov et al. | Mar 1982 | A |
| 4495464 | Kozai et al. | Jan 1985 | A |
| 4520661 | Tamai et al. | Jun 1985 | A |
| 4550815 | Gale | Nov 1985 | A |
| 4583071 | Sebalos et al. | Apr 1986 | A |
| 4642603 | Martinez, Jr. | Feb 1987 | A |
| 4658936 | Moseley | Apr 1987 | A |
| 4664239 | Symes et al. | May 1987 | A |
| 4757300 | Sebalos | Jul 1988 | A |
| 4776438 | Schandelmeier | Oct 1988 | A |
| 4852404 | Catanese | Aug 1989 | A |
| 4855712 | Wiley, Jr. et al. | Aug 1989 | A |
| 4989537 | Hutchinson, Sr. et al. | Feb 1991 | A |
| 5035303 | Sullivan | Jul 1991 | A |
| 5044302 | Goldfein et al. | Sep 1991 | A |
| 5087907 | Weiler et al. | Feb 1992 | A |
| 5125280 | Koscinski et al. | Jun 1992 | A |
| 5133431 | Braun | Jul 1992 | A |
| 5148107 | Finger et al. | Sep 1992 | A |
| 5186284 | Lamela et al. | Feb 1993 | A |
| 5228541 | Plude | Jul 1993 | A |
| 5251729 | Nehl et al. | Oct 1993 | A |
| 5255760 | Lamb et al. | Oct 1993 | A |
| 5255761 | Zaremsky | Oct 1993 | A |
| 5310023 | Martinez | May 1994 | A |
| 5327782 | Sato et al. | Jul 1994 | A |
| 5338320 | Fukuda et al. | Aug 1994 | A |
| 5388320 | Smith et al. | Feb 1995 | A |
| 5410293 | Angerfors | Apr 1995 | A |
| 5433296 | Webberley | Jul 1995 | A |
| 5450930 | Martens et al. | Sep 1995 | A |
| 5474154 | Coale | Dec 1995 | A |
| 5494138 | Scelsi et al. | Feb 1996 | A |
| 5717174 | Ramos | Feb 1998 | A |
| 5767768 | DiSaverio | Jun 1998 | A |
| 5825287 | Zarybnicky, Sr. et al. | Oct 1998 | A |
| 5848672 | Brearley | Dec 1998 | A |
| 5882781 | Lawton et al. | Mar 1999 | A |
| 5906253 | Rancourt et al. | May 1999 | A |
| 5934415 | Preston et al. | Aug 1999 | A |
| 5952075 | Clarke et al. | Sep 1999 | A |
| 5967266 | Carnegie | Oct 1999 | A |
| 5973996 | Zhevelev | Oct 1999 | A |
| 6003640 | Ralea | Dec 1999 | A |
| 6077464 | Murdie et al. | Jun 2000 | A |
| 6112859 | Shuck et al. | Sep 2000 | A |
| 6183583 | Duval et al. | Feb 2001 | B1 |
| 6202811 | Wallrafen | Mar 2001 | B1 |
| 6237723 | Salsman | May 2001 | B1 |
| 6257374 | Strzelczyk et al. | Jul 2001 | B1 |
| 6328144 | Hayakawa et al. | Dec 2001 | B1 |
| 6342171 | Murdie et al. | Jan 2002 | B1 |
| 6352137 | Stegall et al. | Mar 2002 | B1 |
| 6356072 | Chass | Mar 2002 | B1 |
| 6365257 | Hecht | Apr 2002 | B1 |
| 6366201 | Hanisko | Apr 2002 | B1 |
| 6411206 | Weant et al. | Jun 2002 | B1 |
| 6460659 | Schaffer et al. | Oct 2002 | B1 |
| 6537470 | Wood et al. | Mar 2003 | B1 |
| 6634465 | Tuschen | Oct 2003 | B1 |
| 6659233 | DeVlieg | Dec 2003 | B2 |
| 6691393 | James et al. | Feb 2004 | B2 |
| 6696937 | Kiefer | Feb 2004 | B1 |
| 6702069 | Ralea et al. | Mar 2004 | B2 |
| 6719102 | Takanashi | Apr 2004 | B2 |
| 6753771 | Lesesky | Jun 2004 | B2 |
| 6776266 | Fuglewicz et al. | Aug 2004 | B2 |
| 6929333 | DeVlieg | Aug 2005 | B2 |
| 6939490 | La Forest et al. | Sep 2005 | B2 |
| 7014016 | Morris et al. | Mar 2006 | B2 |
| 7025913 | La Forest et al. | Apr 2006 | B2 |
| 7086503 | Miller et al. | Aug 2006 | B2 |
| 7108107 | Ralea et al. | Sep 2006 | B2 |
| 7114596 | Borugian | Oct 2006 | B2 |
| 7172408 | Wood et al. | Feb 2007 | B2 |
| 7252499 | La Forest et al. | Aug 2007 | B2 |
| 7322447 | Deckhut et al. | Jan 2008 | B2 |
| 7374709 | Bauer | May 2008 | B2 |
| 7525062 | Adam et al. | Apr 2009 | B2 |
| 7535131 | Safieh, Jr. | May 2009 | B1 |
| 7610998 | Baumgartner et al. | Nov 2009 | B2 |
| 7673721 | Bailey et al. | Mar 2010 | B2 |
| 7766130 | Walker et al. | Aug 2010 | B2 |
| 7877216 | Wright et al. | Jan 2011 | B2 |
| 8207729 | Erickson | Jun 2012 | B2 |
| 8405386 | Erickson et al. | Mar 2013 | B2 |
| 8717159 | Todd et al. | May 2014 | B2 |
| 9017761 | La Forest et al. | Apr 2015 | B2 |
| 9146308 | Mahajan | Sep 2015 | B2 |
| 9353816 | La Forest et al. | May 2016 | B2 |
| 9441692 | Schaefer | Sep 2016 | B2 |
| 9482301 | Lamkin et al. | Nov 2016 | B2 |
| 20010019752 | Purdy et al. | Sep 2001 | A1 |
| 20020089327 | Spellman | Jul 2002 | A1 |
| 20020170787 | James et al. | Nov 2002 | A1 |
| 20030100239 | Gaffney et al. | May 2003 | A1 |
| 20030214064 | Shin et al. | Nov 2003 | A1 |
| 20040105969 | Huang et al. | Jun 2004 | A1 |
| 20040251090 | Morris et al. | Dec 2004 | A1 |
| 20050054301 | Brown | Mar 2005 | A1 |
| 20050168721 | Huang | Aug 2005 | A1 |
| 20050269873 | DeVlieg | Dec 2005 | A1 |
| 20060042734 | Turner | Mar 2006 | A1 |
| 20060046059 | Arico et al. | Mar 2006 | A1 |
| 20060108182 | Walker | May 2006 | A1 |
| 20060151912 | Bauer | Jul 2006 | A1 |
| 20060177663 | Simpson et al. | Aug 2006 | A1 |
| 20060191751 | Miller et al. | Aug 2006 | A1 |
| 20060219487 | Wille et al. | Oct 2006 | A1 |
| 20060232392 | Emmett et al. | Oct 2006 | A1 |
| 20060279012 | Simpson et al. | Dec 2006 | A1 |
| 20070125607 | Ralea et al. | Jun 2007 | A1 |
| 20070186396 | Linck et al. | Aug 2007 | A1 |
| 20070251308 | Canterbury | Nov 2007 | A1 |
| 20070270069 | Lee et al. | Nov 2007 | A1 |
| 20080041674 | Walker et al. | Feb 2008 | A1 |
| 20080073161 | Pettersson et al. | Mar 2008 | A1 |
| 20080090064 | James et al. | Apr 2008 | A1 |
| 20080190712 | Hagberg | Aug 2008 | A1 |
| 20080202865 | Pradier et al. | Aug 2008 | A1 |
| 20090050418 | Vargas et al. | Feb 2009 | A1 |
| 20090084637 | Bailey | Apr 2009 | A1 |
| 20090120735 | DeVlieg | May 2009 | A1 |
| 20090177362 | Schmitt et al. | Jul 2009 | A1 |
| 20090194895 | La Forest et al. | Aug 2009 | A1 |
| 20090205910 | Cahill | Aug 2009 | A1 |
| 20090229926 | Schaefer | Sep 2009 | A1 |
| 20100207608 | Erickson et al. | Aug 2010 | A1 |
| 20100250028 | DeVlieg | Sep 2010 | A1 |
| 20100286881 | Cahill | Nov 2010 | A1 |
| 20110013173 | Luo | Jan 2011 | A1 |
| 20110033622 | La Forest et al. | Feb 2011 | A1 |
| 20110111123 | La Forest et al. | May 2011 | A1 |
| 20120132488 | Seglo | May 2012 | A1 |
| 20120226457 | Erickson et al. | Sep 2012 | A1 |
| 20130261890 | Roberts | Oct 2013 | A1 |
| 20160041058 | Georgin | Feb 2016 | A1 |
| 20160225130 | Venkatesha | Aug 2016 | A1 |
| 20160281808 | Lamkin | Sep 2016 | A1 |
| 20190018107 | Warke | Jan 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 102874247 | Jan 2013 | CN |
| 3220773 | Dec 1983 | DE |
| 102005013142 | Sep 2006 | DE |
| 1538364 | Jun 2005 | EP |
| 1724245 | Nov 2006 | EP |
| 1911990 | Apr 2008 | EP |
| 1911990 | Apr 2009 | EP |
| 2093453 | Aug 2009 | EP |
| 2874675 | Mar 2006 | FR |
| 2302574 | Jan 1997 | GB |
| 2386951 | Oct 2003 | GB |
| 2470098 | Nov 2010 | GB |
| 2013088196 | May 2013 | JP |
| 9827023 | Jun 1998 | WO |
| 9849382 | Nov 1998 | WO |
| 0061518 | Oct 2000 | WO |
| 2004106766 | Dec 2004 | WO |
| 2006101799 | Jun 2006 | WO |
| 2017149276 | Sep 2017 | WO |
| Entry |
|---|
| U.S. Appl. No. 16/129,316, by Honeywell International Inc. (Inventors: Muniraju, Raghavendra et al.), filed Sep. 12, 2018. |
| “Multiple-Disk Brake Assembly of Boeing 737,” Flight Mechanic, retrieved from http://www.flight-mechanic.com/wp-content/uploads/2017/11/13-88.jpg, Nov. 13, 2017, 1 pp. |
