Diagnosing Electronic Brake Servo and Pedal Simulator Systems

The short version — the module always reads pedal input (position/force) before it commands any actuator or pump output, and your job is to prove sensor input, module logic, and actuator/pump response all line up — using a scan tool for live data and bi-directional tests, while respecting stored high pressure as a serious safety hazard.

How the system replaces the vacuum booster

Traditional vacuum boost is gone or backed up in these designs. Instead, an electric motor/actuator or a high-pressure hydraulic pump and accumulator, commanded by a control module, generates or modulates the brake apply force. Because the pedal may be mechanically or hydraulically disconnected from the master cylinder or wheel brakes, the driver needs something to push against — that's the pedal simulator, which gives a normal pedal feel even though the pedal isn't directly building hydraulic pressure itself.

Two main architectures show up on the test:

• Motor-driven ball-screw or gear actuator — the motor physically pushes the master cylinder piston. Direction of actuator travel corresponds directly to increasing or decreasing hydraulic pressure. When you diagnose this type, you confirm the actuator moves the commanded direction that matches what the pedal is asking for — push pedal, actuator drives pressure up; ease pedal, actuator backs off.
• Electric pump + high-pressure accumulator — the pump charges the accumulator, and a pressure sensor tells the module to cycle the pump on and off to keep pressure inside a set range. Proportioning/control valves then meter accumulator pressure to the wheel circuits based on how much braking force is commanded. This is closer to a "pressure reservoir on demand" setup than a direct push-motor setup.

Know which architecture you're working on before you interpret a symptom — a slow-building actuator on a ball-screw system points to motor/screw wear, while a slow-building system on an accumulator design points to pump or accumulator trouble instead.

The signal path: sensors in, command out

The control logic always runs in the same order, and this sequence itself is testable:

1. Pedal position and force sensors measure driver input first.
2. The module reads those signals and calculates the required brake output.
3. Only then does the module command the servo actuator or hydraulic control unit to apply boosted pressure — either to the master cylinder or directly into the hydraulic circuit.

Driver input is always sensed before any hydraulic or motor output is generated — there's no scenario where the actuator moves before the module has pedal data to act on. This ordering is why a bad pedal sensor causes system-wide brake problems even though the actuator itself might be perfectly healthy.

Diagnostic workflow

Work it like any other input-processor-output system:

• Pull DTCs and freeze-frame data with a scan tool first — this tells you what the module thought was wrong and under what conditions.
• Check pedal position sensor and pressure sensor values live, and correlate them against actual pedal travel and actual force you apply by hand. If the sensor signal doesn't track what your foot/hand is doing, that's your fault — not the actuator.
• Use bi-directional scan tool commands to verify actuator or pump response. This is how you separate a module/command problem from a mechanical actuator/pump problem — command it to move or cycle and watch/feel for the expected result.
• Inspect wiring and connectors for both the sensor circuits and the actuator/pump circuits — corrosion, chafing, or a loose pin can mimic a failed component.

Common failure modes and what they look like

• Pedal position sensor drift or failure → erratic brake response or none at all, and it sets a DTC. This is a sensor-side fault, so scan data comparison against actual pedal motion is how you catch it.
• Simulator valve sticking → spongy or hard pedal feel. The simulator's job is pedal feel, so when it misbehaves the complaint is about how the pedal feels, not necessarily stopping power.
• Accumulator pressure leak or pump failure → long pump run time, a warning light, and reduced or no power assist. Long run time is the pump working overtime trying to hold pressure it can't hold — that's your tip-off to check for a leak before condemning the pump.
• Actuator motor or ball-screw wear/binding → grinding noise, inconsistent boost, and ABS/ESC fault codes. Mechanical wear inside the actuator shows up as noise plus inconsistency, not a clean on/off failure.

Safety cautions — non-negotiable

• High-pressure accumulator systems hold stored pressure even with the vehicle off. Always follow the manufacturer's depressurization procedure before opening any hydraulic line or servicing the unit — skipping this step means you're opening a line under stored pressure.
• Disconnect and lock out high-voltage/high-current actuator circuits per manufacturer service information before working on the actuator.
• Never bleed or service the brake circuit with the system energized unless the procedure specifically tells you to do it that way.

Easy to mix up

• Ball-screw/gear actuator systems vs. pump/accumulator systems — one moves a motor directly against the master cylinder piston (direction = pressure direction); the other cycles a pump to keep an accumulator within a pressure range and doles it out through control valves. Don't diagnose one like the other.
• Simulator valve problems vs. sensor problems — a sticking simulator valve gives bad pedal feel (spongy/hard); a bad pedal position sensor gives bad brake response (erratic or none) and sets a DTC. Feel complaint = simulator; response/DTC complaint = sensor.
• Long pump run time can look like "the pump is failing" when the real cause is an accumulator leak — check for the leak first before you replace the pump.

Check yourself

Question: In a brake-by-wire system, what happens first — pedal sensing or actuator command?

Pedal position and force sensors are read first. The module calculates the needed output from those signals, then commands the actuator or hydraulic control unit. Driver input is always sensed before any output is generated.

Question: Technician A says long pump run time on an accumulator-based system always means the pump motor itself is worn out. Technician B says long pump run time can be caused by an accumulator pressure leak, since the pump has to work harder to maintain pressure. Who is right?

Technician B is right. Long pump run time is listed as a symptom of accumulator pressure leak or pump failure — the leak makes the pump cycle more to hold pressure in range. You shouldn't assume the pump motor is bad without first checking for a leak.

Question: You're testing a motor-driven ball-screw actuator system. What specific check confirms the actuator is working correctly in relation to pedal input?

Confirm the actuator moves in the commanded direction that matches the pedal input polarity — since actuator travel direction corresponds directly to increasing or decreasing hydraulic pressure, pushing the pedal should drive the actuator toward more pressure, and releasing it should drive the actuator back.