Patent Description:
Modern aircraft braking systems often provide greater control, reliability and flexibility than systems of previous generations. However, to ensure optimum operation, the various components of modern braking systems should undergo regular testing. In this regard, regular testing may detect the need to replace wear items, identify components with the potential for malfunction, and identify potential areas for recalibration.

Conventional testing of an aircraft brake system involves taking the aircraft out of service and either physically inspecting components and/or using the brake system while the aircraft remains grounded and parked. Such methods necessitate the loss of use of the aircraft during testing, while involving the labor and cost of technicians that detect potential issues.

Accordingly, there exists a need for testing systems and methods that allow for real time brake system testing.

<CIT> teaches a system for testing a brake system controller using built-in test equipment.

A method is provided as defined by claim <NUM>.

The detailed description of exemplary embodiments herein makes reference to the accompanying drawings, which show exemplary embodiments by way of illustration and its best mode. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, it should be understood that other embodiments may be realized and that logical, electrical and mechanical changes may be made without departing from the scope of the invention as defined by the appended claims. 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. Moreover, many of the functions or steps may be outsourced to or performed by one or more third parties. Also, any reference to attached, fixed, connected or the like may include permanent, removable, temporary, partial, full and/or any other possible attachment option.

Systems and methods are disclosed herein that provide for testing a brake control system. In accordance with various embodiments, by testing a brake control system, the brake control system may be calibrated appropriately and/or potential areas of concern may be revealed. The systems and methods disclosed herein are suitable for use with various aircraft braking systems, although there may be utility for use with other braking systems.

During conventional testing of an aircraft brake system, an aircraft is typically taken out of service and either physically inspected or the brake control system is tested while the aircraft remains grounded and parked. However, as noted above, such methods necessitate the loss of use of the aircraft during testing, while involving the labor and cost associated with technicians to detect potential issues.

However, as it has been presently found by the present inventor, a brake control system may be wrapped in (or encompassed by) a BITE system for in-use testing of the brake control system. In various embodiments, the BITE system may control I/O channels to various components of the brake control system and may sever/reestablish those channels so that testing may occur in real time, and often, without the need (or minimal need) to take an aircraft out of service. Accordingly, by using a BITE system, an aircraft brake control system may be appropriately maintained without excess down time.

Moreover, in accordance with various embodiments, it has been found that in electric brake systems, the BITE system may include a safety interlock surrounding an electromechanical actuator controller ("EMAC"). In that regard, the BITE system may test various brake functions without the need to burden a BSC with handling built in testing, which tends to reduce processor load on the BSC, among other benefits. In various embodiments, the BITE system retains emergency braking functionality and may interrupt or terminate built in testing procedures in response to a command from an emergency braking system.

Systems and methods disclosed herein may be useful for brake disk stacks for use in aircraft. Aircraft may comprise one or more types of aircraft wheel and brake assemblies. For example, an aircraft wheel and brake assembly may comprise a non-rotatable wheel support, a wheel mounted to the wheel support for rotation, and a brake disk stack (also referred to as a brake assembly). An aircraft brake disk stack generally comprises a friction brake mechanism including a pressure plate that is adjacent to a means, device or other mechanism for exerting force such as a hydraulic piston motor or one or more electromechanical actuators. Force may be exerted through, for example, one or more rams. As referred to herein, "electric brake systems" employ one or more electromechanical actuators to drive the one or more rams.

An aircraft brake typically further comprises an end plate distal from the means for exerting force and a plurality of interleaved rotor disks and stator disks which together form the brake heat sink. Each rotor disk may be coupled to the wheel for rotation therewith and each stator disk is coupled to the wheel support against rotation. The friction brake mechanism also generally includes a torque tube and a back leg on which a pressure plate, end plate and stator disks are slidably mounted against rotation relative to the wheel and rotor disks. The stator disks may comprise two wear faces and the pressure plate may comprise a single wear face. The rotors disks and stator disks may be formed of a friction material, such a carbon/carbon or a carbon metallic matrix material. A brake head may house the piston motor or one or more rams that extend to move the pressure plate and axially compress the brake disk stack against the end plate.

The actuator rams may be electrically operated actuator rams or hydraulically operated actuator rams, although some brakes may use pneumatically operated actuator rams. In electric brake systems, a BSC is coupled to one or more EMACs for a brake, which drives one or more electromechanical brake actuators. The BSC may be in communication with a brake pedal, and thus may control the EMACs in accordance with pilot/copilot braking commands.

With reference to <FIG>, aircraft braking control system <NUM> includes at least one BSC <NUM>, and frequently, at least two brake system controllers may be used for redundancy purposes. BSC <NUM> may contain various information pertaining to an aircraft, such as weight, make, model, and aircraft brake system configuration to assist in making this determination. BSC <NUM> is in communication with various components that relay pilot input <NUM> to BSC <NUM>. For example, pilot input <NUM> may comprise a signal produced by one or more aircraft brake indicators. In addition to pilot input <NUM>, input from other aircraft systems (not shown) may be relayed to BSC <NUM>.

In this regard, an aircraft brake indicator may be any device that allows a pilot to input braking commands. For example, an aircraft brake indicator may be one or more aircraft brake pedals.

BSC <NUM> may provide an input/output interface ("I/O interface") to other components of an aircraft braking system. An I/O interface may comprise one or more I/O channels. For example, BSC <NUM> may be in communication (e.g., electrical communication) with components in a cockpit of the aircraft (e.g., an aircraft brake pedal) and/or other portions of an aircraft braking system (e.g., electromechanical actuator controller <NUM>). Such communication may be provided by, for example, the I/O interface (implemented using, for example, a bus or a network). Signals from a brake pedal (e.g., in response to pilot input <NUM>) may be received by the BSC <NUM> via one or more I/O channels. An I/O channel may be any means of electrical communication. For example, an I/O channel may comprise a wire connection or a wireless connection (e.g., via an RF transceiver). An I/O channel may be severed transiently by interrupting an electrical connection, for example, by canceling the interruption. Accordingly, the severing of an I/O channel may be a reversible process. One or more I/O channels of an I/O interface may be reversibly severed at a given time.

In addition, BSC <NUM> may contain a computing device (e.g., a processor) and an associated memory. The associated memory may contain executable code for performing braking control. The associated memory may comprise an article of manufacture including a computer-readable medium having instructions stored thereon that, if executed by a computing device (e.g., a processor), cause the computing device to perform various methods.

As noted above, in an embodiment and with reference to <FIG>, a BSC may be in communication with one or more EMACs. For example, BSC <NUM> may be in communication with EMAC <NUM>. An EMAC, such as EMAC <NUM>, may contain a computing device (e.g., a processor) and an associated memory. The associated memory may comprise an article of manufacture including a computer-readable medium having instructions stored thereon that, if executed by a computing device (e.g., a processor), cause the computing device to perform various methods. The associated memory may contain executable code for converting braking commands into a motor current command.

An EMAC, such as electromechanical actuator controller <NUM>, may provide a drive signal to one or more electromechanical actuators (e.g., electromechanical actuator <NUM>, also referred to as "EA" <NUM>) of an aircraft brake to drive an electromechanical actuator to a commanded position. Thus, electromechanical actuator <NUM> may apply braking force directly.

In various embodiments, EMAC <NUM> may communicate with EA <NUM> by sending a command signal to EA <NUM> via an I/O interface. The command signal may contain one or more commands and/or a drive signal/drive voltage. For example, a drive signal may command a certain amount of force to be applied by EA <NUM>.

In various embodiments, feedback <NUM> may be generated by electromechanical actuator <NUM> and by electromechanical actuator controller <NUM>.

A BITE system (also referred to herein as a BITE region) may be any system that allows any portion of a brake control system (e.g., EMAC) to be at least partially and reversibly disconnected from another aircraft system or component. With reference again to <FIG>, BITE region <NUM> is shown with BITE components <NUM>. A BITE system may allow for the severing and reestablishing of I/O channels or an I/O interface. A BITE system may comprise one or more switches, connectors, gateways, or other devices that allow for the selective, reversible severing of an I/O channel. For example, BITE components <NUM> allow for the selective, reversible severing of an I/O channel.

A BITE system may further comprise a testing module. A testing module may contain a computing device (e.g., a processor) and an associated memory. The associated memory may contain executable code for performing various actions, including the sending and receiving of test signals and the creation and execution of test scripts. The associated memory may comprise an article of manufacture including a computer-readable medium having instructions stored thereon that, if executed by a computing device (e.g., a processor), cause the computing device to perform various methods. In various embodiments, a brake system controller may comprise a testing module and, in such embodiments, the BITE system need not necessarily comprise a testing module.

In various embodiments, a testing module may be configured to send and receive test signals. A test signal may be any signal that encodes a command for an action performed for testing, calibration, optimizing, or other purposes that are not, at the time the testing signal is sent, needed for the immediate operation of an aircraft. In this regard, a test signal may command an aircraft component to perform a task. For example, a test signal may command an electromechanical actuator to actuate and/or may command a servo valve to perform a task. In various embodiments, two or more test signals may be arranged in a particular order to comprise a test script.

In various embodiments, a testing module may also be configured to receive feedback (also referred to herein as a feedback signal or output signal) from an aircraft component and/or brake system controller and/or EMAC. Feedback may be delivered electronically, for example. Feedback may comprise any information relating to an aircraft component, such as its history, current status, or intended future status. Feedback may be sent to a testing module or, with reference to <FIG>, to BSC <NUM> or EMAC <NUM>, for example, in response to a test signal.

Feedback may be used to calibrate, tune, optimize, or otherwise alter the performance of various aircraft components. For example, feedback may comprise the actual pressure applied at an actuator. Feedback may also be used to detect when a component may require maintenance or a corrective action such as a repair. Feedback may also comprise a signal that encodes a component failure.

A testing module or other BITE system component may receive feedback to determine the appropriateness of the feedback. Appropriateness, as used herein, includes determining if feedback is consistent with a set of predetermined, "expected" feedback values. As feedback may represent a real-world event, result or condition, it may be useful to determine if the feedback result comports with the expected event, result or condition. Feedback that does not comport with the expected event, result or condition may be labeled as a failure, while feedback that does comport with the expected event, result or condition may be labeled as a pass.

For example, if a test signal commanded a braking pressure of, for example, <NUM> kPa (<NUM> lbs/in<NUM>) within a <NUM> kPa (<NUM> lbs/in<NUM>) tolerance and a feedback signal indicated that only <NUM> kPa (<NUM> lbs/in<NUM>) was actually applied, the testing module or other BITE system component may determine that the feedback is inconsistent with the "expected" value of the feedback. The testing module or other BITE system component may then report this inconsistency (i.e., failure) to other aircraft components, such as a cockpit component. Alternatively, using the same situation, if a feedback signal returned a value of <NUM> kPa (<NUM> lbs/in<NUM>), then the testing module or other BITE system component may determine that the feedback was appropriate and may record this in a log.

In various embodiments, a testing module or EMAC <NUM> may send a test signal to an aircraft component (e.g., an actuator), the aircraft component may take an action based upon the test signal, and feedback may be sent to the testing module or EMAC or BSC for analysis.

For example, a testing module or EMAC <NUM> may send a test signal to drive EA <NUM> to a commanded position. Data collected during testing may include phase lag (lag from command to response), step response (e.g., <NUM>% commanded to x% commanded), and final position. These data may be used to determine the functional status of EA <NUM>. For example, the final position may be recorded and performance may be compared to one or more of the following: <NUM>) known test cases (i.e., experimentally derived data), <NUM>) predicted envelopes based on envelopes of operation, <NUM>) trends based on past performance, and <NUM>) performance compared to "peer" electromechanical actuators within the same aircraft (i.e., other EAs).

In further embodiments, a testing module or BSC <NUM> or EMAC <NUM> may send a test signal simulating a sensor failure. For example, BSC <NUM> may receive a signal indicating a brake pressure of <NUM> psi when there is no input command for braking, thus indicating an uncommanded braking failure. BSC <NUM>, if functioning as designed, should identify the uncommanded braking failure and respond accordingly.

With reference to <FIG>, aircraft braking control system <NUM> is illustrated. According to the present invention, brake input <NUM> is received by BSC <NUM>. BSC <NUM> determines an appropriate braking response to the brake input <NUM> and forward such commands to EMAC <NUM>. EMAC <NUM> may in turn provide a drive signal or other command signal to EA <NUM>, which is one of several electromechanical actuators on electric brake <NUM>. Testing module <NUM> is in electrical communication with EMAC <NUM>. Safety interlock <NUM> is disposed around EMAC <NUM>, allowing one or more I/O channels to EMAC <NUM> to be selectively severed and re-established. In that regard, I/O channels from BSC <NUM> to EMAC <NUM> may be selectively severed and re-established. During a test, safety interlock <NUM> severs I/O channels from BSC <NUM> to EMAC <NUM> and testing module <NUM> injects testing commands to EMAC <NUM>. EMAC <NUM> may respond to those commands, for example, by sending a command signal and/or drive signal to EA <NUM>.

Emergency brake system <NUM> may comprise any system configured to relay emergency braking commands. An emergency braking command may be any command that requests braking without regard to BITE status. In other words, an emergency braking command requests the cessation of testing and the application of braking force. Emergency brake system <NUM> may comprise one or more emergency brake input devices (e.g., pedal, handles, switches, button, etc.). According to the present invention, the emergency brake system <NUM> also comprises an I/O channel that connects BSC <NUM> to EMAC <NUM> through a channel that is not able to be severed by safety interlock <NUM>. Emergency brake system <NUM> is in electrical communication with EMAC <NUM> in a manner that bypasses safety interlock <NUM>.

According to the present invention, in response to an emergency braking command from emergency brake system <NUM>, EMAC <NUM> ceases testing that may be in progress and may issue a braking command to EA <NUM> in accordance with the emergency braking command.

In various embodiments, emergency brake system <NUM> may receive an indication from an aircraft component that is indicative of wheel touchdown upon landing. For example, a landing gear WOW ("weight-on-wheel") signal, landing gear downlock signal, TQA ("Throttle Quadrant Assembly") signal, throttle position signals, a signal indicating that wheel speed is accelerating at a rate consistent with touchdown, and the like may be sent by emergency brake system <NUM> to EMAC <NUM> According to the present invention, EMAC <NUM> ceases in that regard may cease testing and safety interlock <NUM> restores I/O channels.

Now referring to <FIG>, BITE system <NUM> is illustrated. BITE region <NUM> is shown wrapping EMAC <NUM>. I/O channels <NUM> and <NUM> are shown entering BITE region <NUM> and connecting to EMAC <NUM>. BITE region <NUM> may reversibly sever I/O channels <NUM> and <NUM>. While severed, BITE region <NUM> may (through, for example a testing module) send test signals through I/O channels <NUM> and <NUM> to EMAC <NUM>.

In certain situations, for safety, it is desirable to ensure that testing may be interrupted by external factors (e.g., pilot input). For example, there may be situations where a pilot may need to unexpectedly command braking. If testing is in progress and such a situation arises, it is advantageous to have a system by which testing could be interrupted and the brake control system could return to pilot control. In various embodiments, safety interlock <NUM> allows EMAC <NUM> to communicate with other aircraft components. For example, safety interlock <NUM> may communicate directly with emergency aircraft signals, without intervention of BITE region <NUM>. Thus, safety interlock <NUM> may comprise I/O channels between aircraft components that BITE region <NUM> may not sever, thus providing uninterruptible I/O channels. In such embodiments, safety interlock <NUM> may thus comprise I/O channels that are redundant with respect to the severable I/O channels of BITE region <NUM>. In various embodiments, such redundancy enhances safety and ensures that signals, such as emergency signals, have an alternate pathway that bypasses BITE region <NUM>. In various embodiments, BITE region <NUM> may detect the use of safety interlock <NUM> and thus determine that any testing may be ceased. Accordingly, BITE region <NUM> may reestablish one or more severed I/O channels responsive to the use of safety interlock <NUM>.

In various embodiments, with reference to <FIG>, BSC <NUM> and EMAC <NUM> may agree that present conditions are suitable to commence testing. For example, EMAC <NUM> may communicate with BSC <NUM> to determine if it is appropriate to begin testing. In addition, BSC <NUM> may command EMAC <NUM> to commence testing.

Safety interlock <NUM> may also detect signals from other aircraft components and detect patterns indicative of a scenario where testing may cease. For example, if a pilot depresses a brake pedal during flight and aircraft altitude is dropping, the safety interlock <NUM> may notify the BITE region <NUM> to reestablish I/O channels and cease testing.

In various embodiments, BITE region <NUM> may determine that one or more tests may be performed. For example, tests may be programmed to occur over varying time intervals. Testing may be performed using test scripts that arrange several testing procedures into a particular order.

Prior to conducting a test, BITE region <NUM> (through, for example, a testing module), may determine if an aircraft's current state will accept the request for the test of the aircraft's brake control system. For example, a BITE system may determine if the aircraft is parked, taxiing, taking off, flying, landing, or on approach for landing. In certain instances, the BITE system may determine that testing should not occur.

If it is appropriate to run a test, BITE region <NUM> may then reversibly sever one or more I/O channels (e.g., I/O channels <NUM> and <NUM>) to prepare for testing. Testing may comprise generating and sending test signals. For example, test signals may comprise signals encoding commands typically associated with parking, taxiing, taking off, flying, landing, or on approaching for landing. In various embodiments, test signals may also encode various data related to aircraft status. For example, test signals may comprise wheel speed signals, landing gear WOW signals, landing gear downlock signals, TQA signals, throttle position signals, and the like.

In various embodiments, a testing may occur when the aircraft is parked. In that regard, one or more EAs on a wheel may be commanded to apply pressure sufficient to keep the aircraft parked, while the remaining EAs undergo testing. Upon completion of the testing, the one or more EAs that underwent testing may be commanded to apply pressure sufficient to keep the aircraft parked and the one or more EAs that had been applying parking pressure may undergo testing. Testing may continue in this "round robin" format until all EAs on a wheel have been tested. In that regard, parking functionality is maintained while testing occurs.

Moreover, for aircraft with multiple wheel bogie gears, the "round robin" can be performed on a brake-by-brake scheme (a "round robin" of brakes). For example, on a <NUM>-wheel bogie gear with brakes <NUM>-<NUM>, brake <NUM> may be tested while brakes <NUM>-<NUM> are increased in pressure to assure the aircraft does not move. Then, brake <NUM> may be tested while pressure is increased at brakes <NUM>, <NUM> and <NUM> to maintain the aircraft in park. Testing may proceed until all brakes are tested.

In various embodiments, and as described herein, BITE region <NUM> may then receive feedback. Feedback may be used to compare and evaluate actual system responses to expected responses. BITE region <NUM> may then record, communicate and/or summarize the results of the test.

With reference to <FIG>, brake control system <NUM> is shown. The brake control system comprises an EMAC <NUM>, labeled as processor <NUM>. The brake control system also comprises sensor and inputs <NUM> and signal conditioning circuits <NUM>, each of which is in electrical communication with BITE system <NUM>. The brake control system further comprises signal conditioning circuits <NUM> and actuator outputs <NUM>, each of which is in electrical communication with BITE system <NUM>. Safety interlock <NUM> is in electrical communication with sensor and inputs <NUM> and, as shown, this connection is not made via BITE <NUM>.

As shown in <FIG>, BITE system <NUM> is in communication with various brake control system components (e.g., signal conditioning circuits <NUM>) and may, accordingly, selectively sever or reestablish I/O channels of a brake control system. The BITE system may selectively sever or reestablish I/O channels directly to or from an EMAC, as shown in the interaction between BITE <NUM> and EMAC <NUM>, or the BITE system may selectively sever or reestablish I/O channels of other brake control system components, as shown in the interaction between BITE <NUM> and sensor and inputs <NUM>. Also as shown, safety interlock <NUM> may bypass BITE <NUM> so that operation of BITE <NUM> may be modified should safety reasons so require.

For example, when it is determined that running a test is appropriate, a BITE system may sever I/O channels and a test script may be executed. The test script may comprise test signals that command taxi stops, so the brake control system would function as if the aircraft were in a taxi maneuver on a runway. The test script may then indicate that the throttles are moved forward for takeoff power and that the wheel speed has increased, simulating a takeoff. The test script may further comprise a test signal encoding a weight on wheels signal that reports that the wheels have left the ground, further simulating takeoff. Further, a test signal may indicate that the landing gear has been retracted. A test signal may indicate that the aircraft flaps have been lowered and that the throttles have been set to idle, indicating an imminent landing. In response, the brakes may be applied. The aircraft's responses to these events may be recorded and evaluated to determine abnormalities or other areas of concern.

An example of BITE operation <NUM> is shown in <FIG>. EMAC Input <NUM> is forwarded to BITE Enabled decision point <NUM>. If BITE is enabled, it is understood that EMAC Input <NUM> is a simulation per BITE simulation point <NUM>. Accordingly, in a simulation, EMAC Input <NUM> comprises a test signal. If BITE is not enabled, EMAC Input may proceed to the brake control system <NUM>. Within brake control system <NUM>, EMAC hardware and software <NUM> process the EMAC Input <NUM> and determine an appropriate response. BITE monitoring and evaluation <NUM> monitors EMAC hardware and software <NUM> and EMAC Input <NUM> when BITE is enabled.

EMAC hardware and software <NUM> may prepare a signal responsive to EMAC Input <NUM>. Such a signal may be passed to BITE Enabled decision point <NUM>. If BITE is not enabled, the signal may be forwarded to another aircraft component as EMAC output <NUM>. If BITE is enabled, BITE may intervene at BITE Test Signal Intervention <NUM> to monitor and/or alter the output signal. The output of BITE Test Signal Intervention <NUM> is EMAC output <NUM>.

With reference to <FIG>, BITE operation example <NUM> is shown. I/O channel <NUM> exists between an aircraft component and tested component <NUM>. I/O channel <NUM> exists between tested component <NUM> and an aircraft component, which may or may not be the same aircraft component involved with I/O channel <NUM>. I/O channel <NUM> may be selectively severed at point <NUM> while I/O channel <NUM> may be selectively severed at point <NUM>. Points <NUM> and <NUM> may provide access to a BITE region (not shown) comprising one or more BITE components. As described above, various BITE components may generate test signals, receive feedback signals, and evaluate feedback signals.

During testing, I/O channel <NUM> may be selectively severed at point <NUM>. The BITE region may introduce test signal <NUM> at point <NUM>. Test signal <NUM> is relayed to tested component <NUM>. Tested component <NUM> may then respond to test signal <NUM> and produce feedback signal <NUM>. Feedback signal <NUM> may be routed to the BITE region at point <NUM>. The BITE region may then record feedback signal <NUM> and evaluate it accordingly.

Evaluation of feedback signals may be performed in any suitable manner, as elsewhere described herein. For example, <FIG> depicts test evaluation <NUM>. Test evaluation <NUM> comprises a comparison of a properly functioning ram position response (top graph) and a malfunctioning ram position response (bottom graph). One or more properly functioning ram position response profiles may be stored in a BITE region's memory for comparisons to future testing. The stored properly functioning ram position response profiles may be derived from experimental data or may comprise previous "known good" results of the same tested electromechanical actuator. In <FIG>, an EMAC may command an EA to move a ram to a predetermined position. The movement of the ram may be considered the response.

With continued reference to the top graph of <FIG>, a properly functioning ram position response is shown. Time is shown on the x axis while response is shown on the y axis. Response may be determined by feedback signals. The command box <NUM> illustrates the commanded time and commanded position. For demonstration purposes, response is depicted as a generic indicator for the action of a tested component, although, in various embodiments, response could represent, for example, applied brake force.

Lag <NUM> illustrates the lag time between test signal transmission and the beginning of a response. Overshoot <NUM> illustrates the difference between the commanded response and the response produced. In various embodiments, an overshoot and/or a lag within a certain range is considered acceptable.

With reference now to the bottom graph of <FIG>, a malfunctioning ram position response is shown. Time is again shown on the x axis while response is again shown on the y axis.

Lag <NUM> illustrates the lag time between test signal transmission and the beginning of a response. As shown, lag <NUM> is larger than lag <NUM>, which may indicate a problem with the tested component. Overshoot <NUM> illustrates the difference between the commanded response and the response produced. As shown, overshoot <NUM> is greater than overshoot <NUM>. The BITE region may then determine that a malfunction is occurring. Point <NUM> illustrates an aberration in the response. In a test of an electromechanical actuator, such an aberration may indicate a mechanical issue involving the electromechanical actuator. The BITE region may use this information to determine that a malfunction is occurring and, moreover, to identify the type of malfunctioning occurring.

More specifically, there are a number of tests contemplated herein. For example, force, position and motor current may be manipulated for testing purposes. The velocity and acceleration in both linear and angular modes may be measured in testing. For example, an EMAC may be commanded to send drive power to an EA. The output of the EMA (i.e., the volt/current waveform) may be observed and compared to a standard or expected test result.

In additional testing modes, an EA's deadband (i.e., time to get started), rise time to a position, force or motor current, etc. can be analyzed to assure proper functioning. Tests may occur in closed loop control or open loop control.

Test command inputs may include EMAC-to-EMAC communications (i.e., commands and responses) may be tested, as well as EA to EMAC communications (commands and responses). System voltage, system current, motor voltage, motor current, position: angular and linear (angular on the motor or linear from a different EMA linear sensor), velocity (angular and linear), acceleration (angular and linear), EMA force. Test command outputs may include EMAC commands and responses, motor drive voltage, motor drive current, motor angular position, velocity, and acceleration.

As described above, the use of a safety interlock surrounding an EMAC may provide improved efficiencies in testing while maintaining emergency braking functionality. In various embodiments, a BSC and an EMAC may be integrated as a single unit. In such configurations, a safety interlock may be disposed around the integrated BSC/EMAC.

With reference to <FIG>, brake system <NUM> is illustrated. Brake input <NUM> may be received by integrated BSC <NUM> and EMAC <NUM>. Though integrated, functionally integrated BSC <NUM> and EMAC <NUM> is illustrated as BSC <NUM> and EMAC <NUM>, even though both BSC <NUM> and EMAC <NUM> are configured as an integrated unit. BSC <NUM> may determine an appropriate braking response to the brake input <NUM> and forward such commands to EMAC <NUM>. EMAC <NUM> may in turn provide a drive signal or other command signal to EA <NUM>, which is one of several electromechanical actuators on electric brake <NUM>. Testing module <NUM> may be in electrical communication with EMAC <NUM>. Safety interlock <NUM> may be disposed around integrated BSC <NUM> and EMAC <NUM>, allowing one or more I/O channels to integrated BSC <NUM> and EMAC <NUM> to be selectively severed and re-established. In that regard, I/O channels from brake input <NUM> may be selectively severed and re-established. During a test, safety interlock <NUM> may sever I/O channels from brake input <NUM> to integrated BSC <NUM> and EMAC <NUM> and testing module <NUM> may inject testing commands to integrated BSC <NUM> and EMAC <NUM>. Integrated BSC <NUM> and EMAC <NUM> may respond to those commands, for example, by sending a command signal and/or drive signal to EA <NUM>.

Emergency brake system <NUM> may comprise any system configured to relay emergency braking commands. Emergency brake system <NUM> may be in electrical communication with EMAC <NUM> in a manner that bypasses safety interlock <NUM>.

In response to an emergency braking command from emergency brake system <NUM>, EMAC <NUM> may cease testing that may be in progress and may issue a braking command to EA <NUM> in accordance with the emergency braking command.

In various embodiments, emergency brake system <NUM> may receive an indication from an aircraft component that is indicative of wheel touchdown upon landing. For example, a WOW signal or a signal indicating that wheel speed is accelerating at a rate consistent with touchdown may be sent by emergency brake system <NUM> to EMAC <NUM>. In that regard, EMAC <NUM> may cease testing and safety interlock <NUM> may restore I/O channels.

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 embodiments encompassed by this disclosure. The scope of the claimed matter in the disclosure is accordingly to be limited by nothing other than the appended claims.

In the detailed description herein, references to "various embodiments", "one embodiment", "an embodiment", "an example embodiment", 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.

Claim 1:
A method comprising:
disposing a selectively severable I/O channel between an electromechanical actuator controller, EMAC (<NUM>), and a brake system controller, BSC (<NUM>) that is responsive to a brake input (<NUM>);
disposing, as part of an emergency brake system (<NUM>), a non-severable I/O channel between the EMAC (<NUM>) and the BSC (<NUM>);
coupling the EMAC with a testing module (<NUM>) of a built in test equipment, BITE, region, wherein the testing module (<NUM>) is separate from the BSC and is capable of sending a test signal to the EMAC;
disposing a safety interlock (<NUM>) of the BITE region around the EMAC wherein the safety interlock allows one or more I/O channels to EMAC to be selectively severed and re-established;
during a test, severing, by safety interlock (<NUM>), severable I/O channels from the BSC (<NUM>) to the EMAC (<NUM>) and injecting, by the testing module (<NUM>), testing commands to the EMAC (<NUM>); and
responsive to receiving a signal via the emergency brake system (<NUM>), ceasing, by the EMAC (<NUM>), the testing and restoring, by the safety interlock (<NUM>), the I/O channels.