Can I drive with MID 128 PID 103 FMI 1?

Usually yes for a short distance, but fix it soon. Warning faults like MID 128 PID 103 FMI 1 commonly escalate into torque derate if ignored. The scan-tool checks below help determine urgency.

How do I fix MID 128 PID 103 FMI 1?

Start with: Check for boost leaks. Then follow the diagnostic steps and scan-tool checks on this page.

What tools help diagnose MID 128 PID 103 FMI 1?

A quality J1939 scan tool and, when available, OEM diagnostic software (examples: Cummins INSITE, Detroit DDDL, PACCAR DAVIE4) for actuator tests and live data.

Jump to

Share ↓

Fitments Meaning How it works Images Detailed guide OEM/Engine notes Location hint Scan tool checks Step-by-step diagnostic Decision guide Misdiagnosis Derate/inducement Checklist Tools Prevention Community notes Share

Level: Warning

MID 128 PID 103 FMI 1: Turbocharger Speed - Too Low (Volvo Underboost)

MID 128 PID 103 FMI 1: Turbocharger Speed - Too Low (Volvo Underboost). Symptoms (5), causes (7), and fixes (6). What to check first to prevent derate and downtime.

Code	MID 128 PID 103 FMI 1
Severity	Warning
Applies to	Varies by OEM configuration (confirm your exact calibration)
Can I drive?	Usually yes for a short distance, but fix it soon. Warning faults like MID 128 PID 103 FMI 1 commonly escalate into torque derate if ignored. The scan-tool checks below help determine urgency.

Symptoms

Likely causes

Fixes

Ad - helps keep this content free

What does MID 128 PID 103 FMI 1 mean?

When MID 128 PID 103 FMI 1 sets, the ECM is indicating a fault condition that affects performance, protection strategy, or emissions (depending on calibration).

OEM definitions can vary slightly, so confirm your exact meaning with your service manual or diagnostic tool.

Treat repeat faults as ACTIVE and diagnose using a scan tool and basic inspections before replacing parts.

How this system works (why MID 128 PID 103 FMI 1 happens)

Most modern fault logic is based on expected vs actual sensor readings, timing windows, and plausibility checks.

A single event might store a code, but repeated events across drive cycles are what typically trigger warnings, derate strategies, or inducement (emissions systems).

Your goal is to identify the failure mode (electrical, mechanical, sensor drift, or upstream cause) rather than “parts cannon” replacement.

Detailed guide for MID 128 PID 103 FMI 1

MID 128 PID 103 FMI 1 - Turbocharger Speed Too Low

**Real-World Scenario**: This fault triggers when turbo speed is at least 25% less than target for measured boost [citation:3]. On Volvo D13 engines, this is often accompanied by low power complaints.

🚛 Case Study from the Field

A 2007 Volvo with CM870 showed "Turbo Speed, Value Too Low" active. The truck had:

Fluctuating boost pressure (15-35 PSI erratic)
Power loss, then recovery
Increased fuel mileage (ironically) [citation:9]

After extensive diagnosis, the issue turned out to be:

1. First thought: delete programming issues

2. Checked: VGT air actuator circuit for leaks

3. Found: Rebuilt turbo had internal failure

4. Solution: Replaced with OEM Cummins turbo [citation:9]

🔍 Diagnostic Path

**Step 1 - Check for Boost Leaks**

Inspect all charge air boots
Listen for hissing under load
Use smoke machine if available

**Step 2 - VGT Actuator Test**

Check air/vacuum lines for leaks (even tiny leaks matter)
Verify actuator rod moves freely
Run actuator test with diagnostic tool

**Step 3 - Turbo Speed Sensor**

Verify sensor is properly seated
Check for damaged sensor or tone wheel
Monitor speed reading at idle vs under load

📸 Image Search

"Turbo speed sensor location" (generic turbo)
"Boost leak test smoke machine" (automotive repair)

💬 Mechanic Wisdom

*"On air-controlled VGT systems, even the smallest leak in the actuator circuit will mess with boost control. I've seen a pinhole in a rubber line cause intermittent underboost for months before someone found it."* — Diesel specialist

Location hint for MID 128 PID 103 FMI 1

Component location varies by OEM and chassis. Use your engine’s service manual to confirm the sensor/valve location before replacing parts.

Tip: Inspect connectors and harness routing before replacing parts.

Scan tool checks for MID 128 PID 103 FMI 1

Check status: ACTIVE vs INACTIVE / stored. If it’s not active, look at last occurrence conditions (freeze-frame if available).
Record companion codes. Fixing the “first” code often makes others disappear.
Clear and re-test under similar conditions. If it returns quickly, you have a repeatable fault (good for diagnosis).

If your tool can’t run actuator tests, you can still diagnose a lot with careful inspection + repeatability testing.

Step-by-step diagnostic for MID 128 PID 103 FMI 1

Visual inspection (fast wins). Harness routing, connector pins, hoses/lines (if applicable), and obvious damage.
Check fluid sanity. Not applicable unless your fault is fluid-related. Focus on inspections + repeatability.
Confirm the fault is ACTIVE. Stored-only faults can be old events.
Run actuator tests (if supported). Use OEM diagnostic software (examples: Cummins INSITE, Detroit DDDL, PACCAR DAVIE4) (or a capable J1939 tool) to command tests when available.
Verify after repair. Clear codes, road test, confirm it stays inactive.

Decision guide (fast path) for MID 128 PID 103 FMI 1

If the fault is STORED only → inspect, clear, and monitor. If it returns, treat it as active.
If ACTIVE → check connector/harness first → then confirm sensor values and plausibility → then consider component testing.
If you have multiple codes → diagnose the earliest/most upstream code first.

Common misdiagnosis mistakes for MID 128 PID 103 FMI 1

Replacing sensors without checking wiring, grounds, and connector pin fitment.
Clearing codes repeatedly without confirming whether the fault is ACTIVE and repeatable.
Missing companion codes that point to the real upstream problem.

Will MID 128 PID 103 FMI 1 cause derate or inducement?

Warning aftertreatment faults often start as an emissions warning, then progress to torque derate if the fault remains active over multiple drive cycles. If ignored, many platforms can eventually enter inducement and severe speed limiting.

Exact behavior depends on ECM calibration and which companion faults are active.

“Do this first” checklist for MID 128 PID 103 FMI 1

Scan for companion/derate codes and record freeze-frame data (if available).
Inspect connectors, harness rub points, and pins for corrosion.
Check for other active faults that may be upstream causes (communications, sensors, air/fuel issues).
After repair, clear codes and confirm the fault stays inactive after a drive cycle.

Tools needed to diagnose MID 128 PID 103 FMI 1

Basic hand tools + good lighting for inspection
Multimeter for connector/power/ground checks (if wiring suspected)
OEM diagnostic software (examples: Cummins INSITE, Detroit DDDL, PACCAR DAVIE4) (or equivalent scan tool) for actuator tests and live data

Prevention tips to avoid repeat MID 128 PID 103 FMI 1

Fix small wiring/connector issues early before they become repeat faults.
During service, inspect harness routing and clamp points near heat/vibration.
Don’t ignore intermittent faults. “Erratic” usually gets worse.

What to check first for MID 128 PID 103 FMI 1

Inspect connectors and harness near the affected component for corrosion, rubbing, or loose pins.
Check for upstream causes (communications, sensors, air/fuel issues).
Check for other active faults that may be upstream causes (communications, sensors, air/fuel issues).

If the fault repeats after clearing, diagnose it as ACTIVE. Many faults escalate into derate when ignored.

Related fault codes

No related faults found yet. Commonly seen with: SPN 5246, SPN 1569, SPN 4364, SPN 3719.

Mechanic community notes for MID 128 PID 103 FMI 1

Real-world tips from technicians. Submissions are moderated to keep spam and “my cousin fixed it with duct tape” content out.

No community notes yet. Be the first to add a practical fix that actually works in real life.

Share your fix / advice

Keep it useful: symptoms, what you checked, what fixed it, and whether the code stayed inactive after a drive cycle.