Brake-by-wire

Brake-by-wire technology in the automotive industry is the ability to control brakes through electrical means. It can be designed to supplement ordinary service brakes or it can be a standalone brake system.

The technology replaces traditional components such as the pumps, hoses, fluids, belts and vacuum servos and master cylinders with electronic sensors and actuators. Drive-by-wire technology in automotive industry replaces the traditional mechanical and hydraulic control systems with electronic control systems using electromechanical actuators and human-machine interfaces such as pedal and steering feel emulators.

Some x-by-wire technologies have been already installed on commercial vehicles such as steer-by-wire, and throttle-by-wire. Brake-by-wire technology is still under development by some automobile and automotive parts manufacturers industry worldwide and has not been widely commercialized yet. This is mainly due to the safety-critical nature of brake products.

EBS

Brake-by-wire exists on heavy duty commercial vehicles under the name Electronic Braking System (EBS). This system provides electronic activation of all braking system components including retarder and engine brake. EBS also supports trailers and communicates between the towing vehicle and trailer using the ISO 11992 protocol. The communication between trailer and towing vehicle shall be done through a specific connector dedicated to ABS/EBS following either ISO 7638-1 for 24V systems or ISO 7638-2 for 12V systems.

EBS still relies on compressed air for braking and is only controlling the air through valves which means that it is not depending on higher voltages used by the electromechanical or electrohydraulical brake systems where electric power also is used to apply the brake pressure.

EBS enhances the precision of the braking over conventional braking, which shortens the braking distance. This essentially means that what EBS provides is icing on the cake of an already powerful brake system. The fall back of an EBS system in case of failure is to use the ordinary air brake control pressure, so even in the event of a failure of the electronics the vehicle shall be able to make a safe stop.

Electromechanical Braking System architecture

Fig. 1. General architecture of an EMB system.

General architecture of an electromechanical braking (EMB) system in a drive-by-wire car is shown in Fig. 1. The system mainly comprises five types of elements:

  1. Processors including an Electronic Control Unit (ECU) and other local processors
  2. Memory (mainly integrated into the ECU)
  3. Sensors
  4. Actuators
  5. Communication network(s).

Once the driver inputs a brake command to the system via a human-machine interface - HMI (e.g. the brake pedal), four independent brake commands are generated by the ECU based on high level brake functions such as anti-lock braking system (ABS) or vehicle stability control (VSC). These command signals are sent to the four electric calipers (e-calipers) via a communication network. As this network might not be able to properly communicate with the e-calipers due to network faults, HMI sensory data are also directly transmitted to each e-caliper via a separate data bus.

In each e-caliper a controller uses the brake command (received from ECU) as a reference input. The controller provides drive control commands for a power control module. This module controls three phase drive currents for the brake actuator which is a permanent magnet DC motor, energised by 42V sources. In addition to tracking its reference brake command, the caliper controller also controls the position and speed of the brake actuator. Thus, two sensors are vitally required to measure the position and speed of the actuator in each e-caliper. Because of the safety critical nature of the application, even missing a limited number of samples of these sensory data should be compensated for.

Voting

A brake-by-wire system, by nature, is a safety critical system and therefore fault tolerance is a vitally important characteristic of this system. As a result, a brake-by-wire system is designed in such way that many of its essential information would be derived from a variety of sources (sensors) and be handled by more than the bare necessity hardware. Three main types of redundancy usually exist in a brake-by-wire system:

  1. Redundant sensors in safety critical components such as the brake pedal.
  2. Redundant copies of some signals that are of particular safety importance such as displacement and force measurements of the brake pedal copied by multiple processors in the pedal interface unit.
  3. Redundant hardware to perform important processing tasks such as multiple processors for the electronic control unit (ECU) in Fig. 1.

In order to utilize the existing redundancy, voting algorithms need to be evaluated, modified and adopted to meet the stringent requirements of a brake-by-wire system. Reliability, fault tolerance and accuracy are the main targeted outcomes of the voting techniques that should be developed especially for redundancy resolution inside a brake-by-wire system.

Example of a solution for this problem: A fuzzy voter developed to fuse the information provided by three sensors devised in a brake pedal design.

Missing data compensation

In a by-wire car, some sensors are safety-critical components, and their failure will disrupt the vehicle function and endanger human lives. Two examples are the brake pedal sensors and the wheel speed sensors. The electronic control unit must always be informed of the driver’s intentions to brake or to stop the vehicle. Therefore, missing the pedal sensor data is a serious problem for functionality of the vehicle control system. Wheel speed data are also vital in a brake-by-wire system to avoid skidding. The design of a by-wire car should provide safeguards against missing some of the data samples provided by the safety-critical sensors. Popular solutions are to provide redundant sensors and to apply a fail-safe mechanism. In addition to a complete sensor loss, the electronic control unit may also suffer an intermittent (temporary) data loss. For example, sensor data can sometimes fail to reach the electronic control unit. This may happen due to a temporary problem with the sensor itself or with the data transmission path. It may also result from an instantaneous short circuit or disconnection, a communication network fault, or a sudden increase in noise. In such cases, for a safe operation, the system has to be compensated for missing data samples.

Example of a solution for this problem: Missing data compensation by a predictive filter.

Accurate estimation of position and speed of brake actuators in the e-calipers

The caliper controller controls the position and speed of the brake actuator (besides its main task which is tracking of its reference brake command). Thus, position and speed sensors are vitally required in each e-caliper and an efficient design of a measurement mechanism to sense the position and speed of the actuator is required. Recent designs for brake-by-wire systems use resolvers to provide accurate and continuous measurements for both absolute position and speed of the rotor of the actuators. Incremental encoders are relative position sensors and their additive error needs to be calibrated or compensated for by different methods. Unlike the encoders, resolvers provide two output signals that always allow the detection of absolute angular position. In addition, they suppress common mode noise and are especially useful in a noisy environment. Because of these reasons, resolvers are usually applied for the purpose of position and speed measurement in brake-by-wire systems. However, nonlinear and robust observers are required to extract accurate position and speed estimates from the sinusoidal signals provided by resolvers.

Example of a solution for this problem: A hybrid resolver-to-digital conversion scheme with guaranteed robust stability and automatic calibration of the resolvers used in an EMB system.

Measurement and/or estimation of clamp force in the electromechanical calipers

A clamp force sensor is a relatively expensive component in an EMB caliper. The cost is derived from its high unit value from a supplier, as well as marked production expenses because of its inclusion. The later emanates from the complex assembly procedures dealing with small tolerances, as well as on-line calibration for performance variability from one clamp force sensor to another. The successful use of a clamp force sensor in an EMB system poses a challenging engineering task. If a clamp force sensor is placed close to a brake pad, then it will be subjected to severe temperature conditions reaching up to 800 Celsius that will challenge its mechanical integrity. Also temperature drifts must be compensated for. This situation can be avoided by embedding a clamp force sensor deep within the caliper. However, embedding this sensor leads to hysteresis that is influenced by friction between the clamp force sensor and the point of contact of an inner pad with the rotor. This hysteresis prevents a true clamp force to be measured. Due to the cost issues and engineering challenges involved with including the clamp force sensor, it might be desirable to eliminate this component from the EMB system. A potential opportunity to achieve this presents itself in accurate estimation of the clamp force based on alternative EMB system sensory measurements leading to the omission of a clamp force sensor.

Example of a solution for this problem: Clamp force estimation from actuator position and current measurements using sensor data fusion.

See also

References

    Further reading

    This article is issued from Wikipedia - version of the Monday, April 18, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.