Method for providing correct brake request when electronic pedal is stuck

By using the combination of the first and second sensors and the baseline and auxiliary lookup tables in the traditional wifi control system, the problem of braking torque smoothness when the brake pedal travel is limited or the sensor is inaccurate, and the safety of the vehicle is achieved and stabilize braking effect.

CN119018108APending Publication Date: 2024-11-26FORD GLOBAL TECH LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410567125.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2024-05-09
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

When the brake pedal stroke is limited or the sensor is inaccurate, it is difficult to ensure the smooth and continuous braking torque, which may lead to non-optimal braking effects and sudden step phenomena.

Method used

Using a combination of the first sensor and the second sensor, through the use of the baseline lookup table and the auxiliary lookup table, the controller commands the braking torque according to different signal conditions to ensure that redundant signals are provided when mechanical obstacles or sensors are inaccurate to ensure that Smoothness of brake torque.

Benefits of technology

The braking torque smooth and continuous under the condition of limited stroke of the brake pedal or inaccurate sensor is achieved, avoiding non-optimal braking effects and sudden step phenomena, ensuring safe and stable braking of the vehicle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119018108A_ABST
    Figure CN119018108A_ABST
Patent Text Reader

Abstract

The present disclosure provides a method for providing a correct brake request when an electronic pedal is stuck. A vehicle includes a brake-by-wire system having a brake pedal and first and second sensors. The first sensor is configured to output a first signal indicative of a position of the brake pedal, and the second sensor is configured to output a second signal indicative of the position. A controller is programmed to command a brake torque based only on the first signal when a stroke of the brake pedal is limited to a first range.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a vehicle having a brake-by-wire system. Background Art

[0002] The vehicle includes friction brakes at the wheels for decelerating the vehicle based on input from the brake pedal. Traditionally, hydraulic systems provide the braking force. Advances in electronics have enabled brake-by-wire systems in which the brake pedal is no longer directly connected to the hydraulic system. Summary of the invention

[0003] According to one embodiment, a vehicle includes a brake-by-wire system having a brake pedal and a first sensor and a second sensor. The first sensor is configured to output a first signal indicating a position of the brake pedal, and the second sensor is configured to output a second signal indicating the position. A controller is programmed to command a braking torque based only on the first signal when the travel of the brake pedal is limited to a first range.

[0004] According to another embodiment, a vehicle includes a brake-by-wire system having a brake pedal and a first sensor and a second sensor. The first sensor is configured to output a first signal indicative of a position of the brake pedal, and the second sensor is configured to output a second signal indicative of the position. A controller is in communication with the sensors and is programmed to: in response to applying the brake pedal, command a brake torque according to a baseline lookup table based on the first signal, the second signal, or both, and in response to detecting a difference in the first signal, command a brake torque according to an auxiliary lookup table based only on the second signal.

[0005] According to another embodiment, a method for controlling a vehicle's brake-by-wire system includes: in response to applying a brake pedal of the brake-by-wire system, commanding a braking torque according to a baseline lookup table based on a signal from a first brake pedal position sensor, a second brake pedal position sensor, or both; and in response to the brake pedal being unable to achieve full travel, commanding a braking torque according to an auxiliary lookup table based on the signal from the first brake pedal position sensor or the signal from the second brake pedal sensor rather than the signals from both the first brake pedal position sensor and the second brake pedal position sensor. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 A schematic diagram of an exemplary electrified vehicle is shown.

[0007] Figure 2A An electronic brake pedal is shown according to one example.

[0008] Figure 2B An electronic brake pedal according to another example is shown.

[0009] Figure 3 is a graph showing brake pedal sensor readings and the resulting brake torque command.

[0010] Figure 4 is a baseline lookup table associated with the first brake pedal sensor.

[0011] Figure 5 is a secondary lookup table associated with the first brake pedal sensor.

[0012] Figure 6 is a baseline lookup table associated with the second brake pedal sensor.

[0013] Figure 7 is a secondary lookup table associated with the second brake pedal sensor.

[0014] Figure 8 is a flow chart of an algorithm for controlling braking torque in an exemplary brake-by-wire system. DETAILED DESCRIPTION

[0015] Embodiments of the present disclosure are described herein. However, it should be understood that the disclosed embodiments are merely examples, and other embodiments may take on various forms and alternative forms. The drawings are not necessarily drawn to scale; some features may be enlarged or minimized to show the details of a particular component. Therefore, the specific structural details and functional details disclosed herein are not to be interpreted as limiting, but only as a representative basis for teaching those skilled in the art to adopt the present invention in various ways. As will be understood by those of ordinary skill in the art, the various features shown and described with reference to any one of the drawings may be combined with the features shown in one or more other drawings to produce embodiments that are not explicitly shown or described. The combination of features shown provides representative embodiments for typical applications. However, for specific applications or embodiments, various combinations and modifications of features consistent with the teachings of the present disclosure may be desired.

[0016] refer to Figure 1 , the electrified vehicle 20 is shown as a pure electric vehicle, but in other embodiments, the vehicle 20 may be a hybrid electric vehicle including an internal combustion engine, or a conventionally powered vehicle including only an engine. The vehicle 20 is shown as two-wheel drive (such as front-wheel drive or rear-wheel drive), but in other embodiments may be all-wheel drive (AWD). The vehicle 20 may include a powertrain 24 that includes a power device, such as an electric machine 34 or an engine.

[0017] The motor 34 is operably coupled to the driven wheels 30 and 32. A gearbox (not shown) may be included to change the gear ratio between the motor 34 and the wheels 30, 32. The motor may be one or more motors. The motor 34 can act as a motor to provide positive torque to propel the vehicle 20, and can act as a generator to provide negative torque to brake the vehicle, for example, via regenerative braking. The motor 34 may be a permanent magnet three-phase alternating current (AC) electric motor or other suitable type.

[0018] The motor 34 is powered by one or more traction batteries (e.g., traction battery 36). The traction battery 36 stores energy that can be used by the motor 34. The traction battery 36 can provide a high-voltage direct current (DC) output from one or more battery cell arrays (sometimes referred to as battery cell stacks) within the traction battery 36. The battery cell array includes one or more battery cells. The battery cell (such as a square, pouch, cylindrical, or any other type of cell) converts the stored chemical energy into electrical energy. The cell may include a housing, a positive electrode (cathode), and a negative electrode (anode). The electrolyte allows ions to move between the anode and the cathode during discharge, and then return during recharging. The terminals allow current to flow out of the cell for use by the vehicle 20. Different battery pack configurations can be used to meet various vehicle variables, including packaging constraints and power requirements. The battery cell can be thermally regulated using a thermal management system.

[0019] The traction battery 36 may be electrically connected to one or more power electronics modules via one or more contactors. The modules may be electrically connected to the motor 34 and may provide the ability to transfer electrical energy bidirectionally between the traction battery 36 and the motor 34. For example, the traction battery 36 may provide a DC voltage, while the motor 34 may require three-phase AC. The power electronics module may convert the DC voltage into a three-phase AC voltage as required by the motor. In a generator mode, which may be in the process of regenerative braking, the power electronics module may convert the three-phase AC voltage from the motor 34 acting as a generator into the DC voltage required by the traction battery 36.

[0020] The vehicle 20 includes one or more controllers 40 that are in electrical communication with a plurality of vehicle systems and are configured to coordinate the functions of the vehicle. The controller 40 may be a vehicle-based computing system that includes one or more controllers that communicate via a serial bus (e.g., a controller area network (CAN)) or via a dedicated electrical conduit. The controller 40 generally includes any number of microprocessors, ASICs, ICs, memories (e.g., FLASH, ROM, RAM, EPROM, and / or EEPROM) and software code to perform a series of operations in cooperation with each other. The controller 40 also includes predetermined data or a "lookup table" based on calculation and test data and stored in the memory. The controller 40 may communicate with other vehicle systems and controllers through one or more wired or wireless vehicle connections using a common bus protocol (e.g., CAN and LIN). Any reference to a "controller" used herein refers to one or more controllers. The controller 40 may include a battery energy control module (BECM) that operates at least a traction battery, a powertrain control module (PCM) that operates at least an electric motor, and a brake control module that controls the braking system 38.

[0021] The controller communicates with various vehicle sensors and actuators via an input / output (I / O) interface, which may be implemented as a single integrated interface that provides various raw data or signal conditioning, processing and / or conversion, short circuit protection, etc. Alternatively, one or more dedicated hardware or firmware chips may be used to condition and process specific signals before supplying them to the CPU. Although not explicitly shown, one of ordinary skill in the art will recognize the various functions or components that may be controlled by the controller within each of the above-described subsystems.

[0022] The brake system 38 can be a hydraulic system, an electric system, or a combination of electric and hydraulic. The brake system 38 is a wire control brake system that uses pedal sensors (S1 and S2) and actuators instead of the conventional direct mechanical connection between the brake pedal and the master cylinder to engage the brakes. The pedal sensors (S1 and S2) are configured to sense the movement of the brake pedal 44 and output a signal. The sensors (S1 and S2) can be packaged with the brake pedal 44 as a brake pedal assembly. The signal includes data indicating the position of the brake pedal 44, which can be expressed as a percentage of depression, etc. The pedal sensors (S1 and S2) output the data to the brake control module of the controller 40.

[0023] The braking system 38 may include one or more master cylinders 47, which are in fluid communication with a plurality of friction brakes 42 located at each wheel. The one or more master cylinders 47 are actuated by the controller 40 based on data received from the pedal sensors (S1 and S2) and other factors. This is only one example, and other types of wire control brake systems, such as electromechanical brakes, are conceivable. These systems may not include a master cylinder. Modern vehicles typically have disc brakes; however, other types of friction brakes are also available, such as drum brakes. In an exemplary embodiment, each of the brakes 42 is in fluid communication with a valve body (not shown) via a brake line, which is configured to deliver fluid pressure from the master cylinder 47 to the brake caliper of the brake 42. The valve body may include a plurality of valves, which are configured to provide independent fluid pressure to each of the brakes 42, and such a system is generally referred to as ABS. The braking system 38 also includes associated wheel speed sensors 46, each of which is located at one of the wheels. Each sensor 46 is configured to output a wheel speed signal indicating the measured wheel speed to the controller 40.

[0024] The vehicle 20 is configured to brake using powertrain braking (e.g., regenerative braking), friction braking, or a combination thereof, depending on the vehicle's powertrain. The brake control module includes programming for aggregating the requested braking torque between the motor 34 and the friction brake 42. The requested braking torque may be based on driver input, such as the position of the brake pedal 44, or controlled by the controller 40. The aggregator may be programmed to use regenerative braking to decelerate the vehicle whenever possible, and to apply the friction brake 42 when necessary.

[0025] The vehicle 20 includes an accelerator pedal 45. The accelerator pedal 45 includes a range of travel from a release position to a fully depressed position and an indeterminate position therebetween. The release position may be considered a zero percent position, and the fully depressed position may be considered a 100% position. Releasing the pedal may be referred to as lowering the accelerator pedal position, and applying the pedal may be referred to as raising the accelerator pedal position. The accelerator pedal 45 includes an associated sensor (not shown) that senses the position of the pedal 45. The sensor is configured to output a pedal position signal indicating the sensed position of the pedal 45 (i.e., the accelerator pedal position) to the controller 40. The driver uses the accelerator pedal 45 to command the desired speed and torque of the vehicle. That is, the driver uses the accelerator pedal 45 to set the driver demand torque. The driver demand torque may be a positive or negative value. A positive value indicates a propulsion torque, while a negative value indicates a braking torque. The controller 40 may be programmed to receive the accelerator pedal position signal and determine the driver demand torque based on the accelerator pedal position and other factors (such as vehicle speed).

[0026] Figure 2A and Figure 2BAn exemplary embodiment of a brake pedal 44 is shown. Figure 2A , the brake pedal assembly 50 of the wire control brake system includes a pedal 52, which is pivotally mounted to a support 54 of the vehicle body about a pivot axis 56. The pedal 52 includes a foot portion 58 attached to a rod portion 60. The foot portion 58 can move relative to the rod portion 60. For example, the foot portion 58 can be slidably received in a guide member and have a first stroke 59. The movement of the foot portion 58 relative to the rod portion 60 can be sensed by a first sensor 62. That is, the first sensor 62 senses the first stroke 59 of the brake pedal 52. The pivoting of the rod portion 60 relative to the support 54 about the pivot axis 56 can be measured by a second sensor 64. When the driver depresses the brake pedal 52, the foot portion 58 is first depressed toward the rod portion 60, which is still stationary. Once the foot portion 58 reaches the end of the first stroke 59, the rod portion 60 begins to rotate around the axis 56 through the second stroke 66. (In other embodiments, the rod portion 60 may begin to move before the foot portion bottoms out). In this example, the first travel 59 is a linear distance and the second travel is an angular distance.

[0027] refer to Figure 2B , another brake pedal assembly 70 includes a pedal 71 having a rod portion 72 pivotally connected to a support member 74 about a pivot axis 76. A foot portion 78 is rigidly attached to the rod portion 72. The brake pedal assembly 70 is an example of a dual-angle electronic pedal, in which both the first sensor and the second sensor measure the movement angle. The pedal assembly 70 includes an intermediate member 80 pivotally attached about the pivot axis 76. A first link 82 is connected between the rod portion 72 and the intermediate member 80. A second link 84 is connected between the intermediate member 80 and the support member 74. The pedal 71 is designed to move in two stages: during the first stage, the rod portion 72 rotates through its stroke (the first stroke 86), while the intermediate member 80 remains stationary. At the end of the first stroke 86, the rod portion 72 begins to drive the intermediate member 80 toward the support member 74 through the second stroke range 88. (In other embodiments, the intermediate member 80 may begin to move before the rod portion reaches the end of the first stroke 86).

[0028] The first sensor 90 measures the angle (α) between the rod portion 72 and the intermediate member 80. The second sensor 92 measures the angle (β) between the support 74 and the intermediate member 80. When the pedal 71 is stepped on from full release, the rod portion 72 moves toward the intermediate member 80, which is stationary at this time. Here, the movement of the pedal is sensed only by the first sensor 90. As the driver further depresses the pedal, the intermediate member 80 begins to pivot, and the second sensor 92 senses the pedal movement (in some embodiments, both sensors 90 / 92 will measure the pedal movement during this movement phase).

[0029] Figure 3 A graph of first sensor data 100, second sensor data 102, and requested brake torque 104 during a braking event of a vehicle in which the brake pedal assembly is functioning normally is shown. As shown in the graph, the first sensor 100 senses the initial movement of the brake pedal, and the second sensor 102 senses the final movement of the brake pedal. In this example, the first sensor and the second sensor have significant overlap during the middle portion of the pedal travel. The brake torque 104 is based on data from the first sensor and the second sensor. In this example, the brake torque 104 is primarily based on the reading from the first sensor 100 during the first half of the brake pedal travel. Similarly, the brake torque 104 is primarily based on the reading from the second sensor 102 during the second half of the brake pedal travel.

[0030] If one or more movable parts of the brake pedal become mechanically stuck or one or more of the sensors become inoperable or inaccurate, the data received by the controller may no longer be accurate. This may result in a non-optimal brake torque command 104 and / or result in a sudden step in brake torque 104 instead of Figure 3 For example, if the controller does not receive the S1 signal correctly, the controller may command a lower braking torque during the first half of the pedal travel, and then suddenly jump to a higher braking torque once the second sensor becomes dominant. The control described below provides redundancy to ensure that the braking torque curve is smooth.

[0031] The controller 40 may include memory storing a mapping or lookup table and arbitration logic to output the desired brake torque 104 based on at least data from the first sensor, the second sensor, both, and / or potentially other factors. Figure 4 A simplified example of a baseline lookup table 110 is shown (for descriptive purposes). In this example, a first sensor S1 measures a first travel of a pedal. Figure 5 A simplified example of an auxiliary lookup table 112 is shown (for illustration purposes) which is used when a difference is sensed relative to the second sensor S2 (S1 is still operating normally). When comparing these lookup tables, it can be seen that for the auxiliary lookup table 112, the pedal output contribution is increased to account for the inaccurate information received from the second sensor S2. By using the auxiliary lookup table, 100% of the pedal contribution can come from S1, so that full brake torque can be commanded without an accurate signal from the second sensor S2.

[0032] Figure 6 and Figure 7 A baseline brake-torque lookup table and an auxiliary brake-torque lookup table for sensor S2 are shown. Figure 6A simplified example of a baseline lookup table 114 is shown (for descriptive purposes). In this example, a first sensor S1 measures a first travel of the pedal. Figure 7 A simplified example of an auxiliary lookup table 116 is shown (for illustration purposes) which is used when a difference is sensed relative to the second sensor S1 (S2 is still operating normally). When comparing these lookup tables, it can be seen that for the auxiliary lookup table 116, the pedal output contribution is initially reduced to account for the inaccurate information received from the second sensor S1. By using the auxiliary lookup table, the sudden spike in braking torque does not occur, while still providing full braking torque based solely on the second sensor S2.

[0033] The controller can be programmed to utilize a baseline lookup table when it is determined that the pedal is operating normally. That is, the pedal is mechanically sound and the sensors are outputting accurate information. If the controller determines that one or more portions of the pedal are stuck and inhibiting proper movement of the pedal within its various ranges of travel, or that one or more of the sensors are outputting inaccurate information, an auxiliary lookup table is used to account for the problem and provide redundancy. For example, the controller can be programmed to command braking torque based only on a first signal when the travel of the brake pedal is limited to a first range, and / or to command braking torque based only on a second signal when the travel of the brake pedal is limited to a second range.

[0034] The control logic or functions performed by the controller 40 may be represented by a flowchart or similar diagram in one or more of the accompanying drawings. These drawings provide representative control strategies and / or logic that can be implemented using one or more processing strategies (such as event-driven, interrupt-driven, multi-tasking, multi-threading, etc.). Thus, the various steps or functions shown may be performed in the order shown, may be performed in parallel, or may be omitted in some cases. Although not always explicitly shown, it will be recognized by those of ordinary skill in the art that one or more of the steps or functions shown may be repeatedly performed depending on the specific processing strategy used. Similarly, the processing order is not necessarily required to achieve the features and advantages described herein, but is provided for ease of illustration and description. The control logic may be implemented primarily in software executed by a microprocessor-based vehicle, engine and / or powertrain controller (such as controller 40). Of course, depending on the specific application, the control logic may be implemented in software, hardware, or a combination of software and hardware in one or more controllers. When implemented in software, the control logic may be provided in one or more computer-readable storage devices or media, which store data representing codes or instructions executed by a computer to control a vehicle or a vehicle subsystem. The computer-readable storage device or medium may include one or more of several known physical devices that use electrical, magnetic, and / or optical storage to hold executable instructions and associated calibration information, operating variables, and the like.

[0035] Figure 8 2 is a flow chart of an algorithm for controlling a brake-by-wire system. At operation 202, the driver depresses the pedal to initiate a braking event. At operation 204, the controller receives data from pedal sensors S1, S2, or both. At operation 206, the controller determines whether a mechanical obstruction or an inaccurate pedal sensor is detected. If not, the pedal assembly operates normally, and a baseline lookup table is used at operation 208 to determine the driver's requested braking torque. If the received sensor data indicates a problem with the brake pedal or sensor, control passes to operation 210, and the controller uses an auxiliary lookup table to determine the driver's requested braking torque.

[0036] When the auxiliary table is used, the controller can be programmed to command the braking torque based only on the first signal when the travel of the brake pedal is limited to the first range, or to command the braking torque based only on the second signal when the travel of the brake pedal is limited to the second range. In addition or alternatively, the controller is further programmed to command the braking torque according to the auxiliary lookup table based only on the second signal in response to detecting a difference in the first signal, and / or to command another braking torque according to another auxiliary lookup table based only on the first signal in response to detecting a difference in the second signal.

[0037] The controller may determine a discrepancy in the sensor data by comparing the sensor data to an expected value. If the sensor data does not match the expected value, this indicates a discrepancy. Alternatively, the control may compare the pedal movement of a first stroke to the pedal movement of a second stroke. For example, if the S1 data increases while the S2 data is static, this indicates a discrepancy. In yet another example, the controller flags a discrepancy in response to S1 or S2 failing to reach its maximum value. These are merely some examples and are not an exhaustive list of ways to detect anomalies in brake pedal operation.

[0038] Although exemplary embodiments are described above, these embodiments are not intended to describe all possible forms covered by the claims. The words used in the specification are descriptive rather than limiting words, and it should be understood that various changes can be made without departing from the spirit and scope of the present disclosure. As previously described, the features of the various embodiments can be combined to form other embodiments of the present invention that may not be explicitly described or shown. Although the various embodiments may have been described as providing advantages or being superior to other embodiments or prior art implementations in terms of one or more desired characteristics, it will be appreciated by those of ordinary skill in the art that one or more features or characteristics may be compromised to achieve the desired overall system properties, depending on the specific application and implementation. These properties may include, but are not limited to, strength, durability, marketability, appearance, packaging, size, maintainability, weight, manufacturability, ease of assembly, etc. For this reason, embodiments described as less desirable than other embodiments or prior art implementations in terms of one or more characteristics are within the scope of the present disclosure and may be desirable for specific applications.

[0039] According to the present invention, a vehicle is provided, which has: a wire control brake system, the wire control brake system including a brake pedal and a first sensor and a second sensor, the first sensor being configured to output a first signal indicating a position of the brake pedal and the second sensor being configured to output a second signal indicating the position; and a controller programmed to command a braking torque based only on the first signal when the travel of the brake pedal is limited to a first range.

[0040] According to one embodiment, the controller is further programmed to command the braking torque based on both the first signal and the second signal when the travel of the brake pedal is unimpeded.

[0041] According to one embodiment, the controller is further programmed to command the braking torque based only on the second signal when the travel of the brake pedal is limited to a second range.

[0042] According to one embodiment, the first range does not overlap with the second range.

[0043] According to one embodiment, the first sensor is configured to sense movement of the brake pedal within the first range but not within the second range, and the second sensor is configured to sense movement of the brake pedal within the second range but not within the first range.

[0044] According to one embodiment, the first sensor senses the angular position of the brake pedal.

[0045] According to one embodiment, the second sensor senses a linear movement of the brake pedal or a pressure applied to the brake pedal.

[0046] According to one embodiment, the second sensor senses the angular position of the brake pedal.

[0047] According to the present invention, a vehicle is provided, which has: a wire-controlled brake system, the wire-controlled brake system including a brake pedal and a first sensor and a second sensor, the first sensor being configured to output a first signal indicating a position of the brake pedal and the second sensor being configured to output a second signal indicating the position; and a controller communicating with the sensors, the controller being programmed to: in response to applying the brake pedal, command a braking torque according to a baseline lookup table based on the first signal, the second signal, or both, and in response to detecting a difference in the first signal, command a braking torque according to an auxiliary lookup table based only on the second signal.

[0048] According to one embodiment, the controller is further programmed to, in response to detecting a difference in the second signal, command another braking torque according to another auxiliary look-up table based only on the first signal.

[0049] According to one embodiment, the first sensor measures a first travel range of the brake pedal and the second sensor measures a second travel range of the brake pedal.

[0050] According to one embodiment, the auxiliary look-up table is associated with the other of the first signal and the second signal.

[0051] According to one embodiment, for the same value of the second signal, the baseline lookup table and the auxiliary lookup table output different braking torque values.

[0052] According to one embodiment, the invention also features a memory associated with the controller and storing thereon the baseline lookup table, the auxiliary lookup table, and another auxiliary lookup table associated with the first signal.

[0053] According to one embodiment, the first sensor senses the angular position of the brake pedal and the second sensor senses the pressure applied to the brake pedal or the linear movement of the brake pedal.

[0054] According to the present invention, a method for controlling a vehicle's brake-by-wire system includes: in response to applying the brake pedal of the brake-by-wire system, commanding a braking torque according to a baseline lookup table based on a signal from a first brake pedal position sensor, a second brake pedal position sensor, or both; and in response to the brake pedal being unable to achieve full travel, commanding a braking torque according to an auxiliary lookup table based on the signal from the first brake pedal position sensor or the signal from the second brake pedal sensor rather than the signals from both the first brake pedal position sensor and the second brake pedal position sensor.

[0055] According to one embodiment, the first sensor measures a first travel range of the brake pedal and the second sensor measures a second travel range of the brake pedal.

[0056] According to one embodiment, for the same value of the first sensor, the baseline lookup table and the auxiliary lookup table output different brake torque values.

[0057] According to one embodiment, for the same value of the first sensor, the baseline lookup table outputs a first braking torque value and the auxiliary lookup table outputs a second, larger braking torque value.

[0058] According to one embodiment, the method is performed by a vehicle controller.

Claims

1. A vehicle comprising: a brake-by-wire system comprising a brake pedal and a first sensor and a second sensor, the first sensor being configured to output a first signal indicative of a position of the brake pedal and the second sensor being configured to output a second signal indicative of the position; as well as A controller is programmed to command a braking torque based only on the first signal when the travel of the brake pedal is limited to a first range. 2 . The vehicle of claim 1 , wherein the controller is further programmed to command the braking torque based on both the first signal and the second signal when the travel of the brake pedal is unimpeded. 3 . The vehicle of claim 1 , wherein the controller is further programmed to command the braking torque based only on the second signal when the travel of the brake pedal is limited to a second range. The vehicle of claim 3 , wherein the first range does not overlap with the second range. 5 . The vehicle of claim 1 , wherein the first sensor is configured to sense movement of the brake pedal within the first range but not within the second range, and the second sensor is configured to sense movement of the brake pedal within the second range but not within the first range. The vehicle of claim 1 , wherein the first sensor senses an angular position of the brake pedal. 7 . The vehicle of claim 6 , wherein the second sensor senses linear movement of the brake pedal or pressure applied to the brake pedal.

8. The vehicle of claim 6, wherein the second sensor senses an angular position of the brake pedal.

9. A vehicle comprising: a brake-by-wire system comprising a brake pedal and a first sensor and a second sensor, the first sensor being configured to output a first signal indicative of a position of the brake pedal and the second sensor being configured to output a second signal indicative of the position; as well as A controller in communication with the sensor, the controller being programmed to: In response to applying the brake pedal, commanding a brake torque according to a baseline lookup table based on the first signal, the second signal, or both, and In response to detecting an error in the first signal, a braking torque is commanded according to an auxiliary lookup table based solely on the second signal.

10. The vehicle of claim 9, wherein the controller is further programmed to, in response to detecting an anomaly in the second signal, command another braking torque according to another auxiliary lookup table based solely on the first signal. 11 . The vehicle of claim 9 , wherein the first sensor measures a first range of travel of the brake pedal and the second sensor measures a second range of travel of the brake pedal.

12. The vehicle of claim 9, wherein the auxiliary lookup table is associated with the other of the first signal and the second signal.

13. The vehicle of claim 12, wherein the baseline lookup table and the auxiliary lookup table output different brake torque values ​​for the same value of the second signal.

14. The vehicle of claim 12 further comprising a memory associated with the controller and storing thereon the baseline lookup table, the auxiliary lookup table, and another auxiliary lookup table associated with the first signal.

15. A method for controlling a brake-by-wire system of a vehicle, the method comprising: responsive to application of a brake pedal of a brake-by-wire system, commanding a brake torque according to a baseline lookup table based on a signal of a first brake pedal position sensor, a second brake pedal position sensor, or both; as well as In response to the brake pedal being unable to achieve full travel, braking torque is commanded according to an auxiliary lookup table based on the signal of the first brake pedal position sensor or the signal of the second brake pedal position sensor, but not both.