Full Diagnostic Guide — SPN 147 FMI 2
1. What does SPN 147 FMI 2 mean?
SPN 147 FMI 2 indicates that the Engine Average Fuel Economy (Gaseous) signal is erratic, intermittent, or incorrect. The ECM detects that the signal from the fuel flow sensor (typically a mass flow or volumetric sensor) is unstable, fluctuating outside the expected 0.5–4.5V range, or providing data that does not correlate with other engine parameters like fuel pressure (SPN 94) or injection timing.
2. What are the most common symptoms when this code is active?
Common symptoms include fuel economy fluctuation on the dash display, an amber warning lamp, torque derate up to 25% to prevent lean combustion, and intermittent power loss during steady-state cruising. Drivers may also notice hesitation or surging due to incorrect fuel metering. The fault is often logged in ECM memory and may cause the engine to enter a reduced-power mode until the signal stabilizes.
3. How does the ECM determine that this specific failure (FMI 2) has occurred?
The ECM monitors the fuel economy sensor signal for erratic changes. If the signal voltage fluctuates more than 0.3V within a 100ms window, or if the calculated fuel economy deviates by more than 20% from the expected value based on engine speed and load, the ECM sets FMI 2. The ECM also compares the signal against fuel pressure (SPN 94) and injection quantity to confirm inconsistency.
4. What is the difference between FMI 2 and other common FMIs for SPN 147?
FMI 2 (Erratic/Intermittent/Incorrect) indicates an unstable signal, while FMI 1 (Data Valid But Below Normal) means the signal is too low but steady, and FMI 0 (Data Valid But Above Normal) means the signal is too high. FMI 2 is unique because the signal is not consistently out of range but rather jumps or drops unpredictably, often due to wiring issues or sensor degradation.
5. What are the most probable root causes?
Root causes include a faulty fuel flow sensor with corroded or damaged elements, wiring harness chafing causing intermittent short-to-ground or open circuits, ECM software glitches from outdated calibration firmware that fails to filter noise, and poor ground connections at the ECM ground pin with resistance above 0.1 ohms. Aftermarket repairs like forced DPF regeneration or ECM replacement without recalibration are common triggers.
6. Can a purely mechanical issue cause this code without a faulty component?
Yes, mechanical issues such as a restricted fuel filter or air in the fuel lines can cause erratic fuel flow, leading to sensor signal instability. However, the code specifically targets the electrical signal from the sensor. If the sensor is mechanically intact but the fuel system has air or debris, the sensor may output erratic data, triggering FMI 2. Always check fuel system condition before replacing the sensor.
7. What default actions does the ECM take when this code is active?
The ECM logs the fault and illuminates the amber warning lamp. It may reduce engine torque by up to 25% to prevent lean combustion and protect the aftertreatment system. The ECM may also substitute a default fuel economy value based on engine speed and load, which can cause unstable readings on the dash. In severe cases, the engine may enter a derate mode limiting speed to 1200 RPM.
8. How do I perform a basic functional test for this component?
With the ignition on and engine off, probe the sensor signal wire with a multimeter. The voltage should be stable between 0.5V (low flow) and 4.5V (high flow). If the voltage fluctuates more than 0.2V without engine operation, the sensor or wiring is faulty. Start the engine and monitor the voltage at idle; it should change smoothly with throttle. Erratic jumps indicate a failing sensor or poor connection.
9. What specific electrical checks should I run before replacing parts?
Measure resistance between the ECM ground pin and battery negative; must be below 0.1 ohms. Check the sensor signal wire for continuity and shorts to ground or power. Inspect the connector for bent pins, corrosion, or moisture. Measure the 5V reference voltage at the sensor connector; it should be stable within 4.9–5.1V. If reference voltage is erratic, check the ECM power supply and ground.
10. Is it possible that the ECM itself is responsible for this fault?
Yes, an ECM with outdated calibration firmware can misinterpret sensor noise as erratic data, especially after a forced DPF regeneration or ECM replacement. A poor ECM ground connection can also cause reference voltage instability. If all wiring and sensor checks pass, reflash the ECM with the latest calibration from the manufacturer. If the fault persists, the ECM may have internal damage.
11. What is the complete step-by-step diagnostic procedure?
1. Connect a J1939 scanner and record all active codes. 2. Inspect sensor connector for corrosion or bent pins. 3. Measure signal voltage at idle; should be stable 0.5–4.5V. 4. Check ground integrity; resistance must be below 0.1 ohms. 5. Perform a wiggle test on the wiring harness to reproduce the fault. 6. If intermittent, use a scope to capture glitches. 7. Reflash ECM if calibration is outdated. 8. Replace sensor if electrical tests pass but signal remains erratic.
12. How can I prevent this fault from recurring?
Ensure all wiring harnesses are securely routed and not chafing against sharp edges. Use dielectric grease on sensor connectors to prevent corrosion. After ECM replacement or forced DPF regeneration, always recalibrate the fuel flow sensor using the manufacturer’s software. Regularly check ground connections and tighten ECM ground bolts to specification. Update ECM firmware to the latest version to improve noise filtering.
13. Does this fault affect fuel economy, emissions, or engine lifespan?
Yes, it directly affects fuel economy because the ECM uses the sensor data to calculate injection quantities. Erratic signals can cause over-fueling or under-fueling, increasing fuel consumption and emissions (especially NOx and particulate matter). Torque derate and intermittent power loss stress the engine, potentially reducing lifespan if the fault persists. Long-term operation may damage the aftertreatment system.
14. Can I clear the code and continue operating the vehicle temporarily?
You can clear the code with a diagnostic tool, but the fault will likely return if the root cause is not addressed. Temporary operation is possible, but the ECM may continue to derate torque or substitute incorrect fuel values, affecting drivability and emissions. If the fault is intermittent, clearing the code may restore normal operation temporarily, but the underlying issue should be repaired as soon as possible.
15. When should I choose to replace the component versus repairing the wiring?
Replace the fuel flow sensor if the signal voltage is erratic even when the wiring checks out (good continuity, no shorts, stable ground). Repair wiring if you find chafing, corrosion, or a broken wire during inspection. If the connector has bent pins or moisture damage, replace the connector or pigtail. Always repair wiring first if it is the obvious cause, as sensors are expensive and may be falsely condemned.
16. What type of diagnostic tool do I need to read this fault code?
You need a J1939-compatible diagnostic tool, such as a heavy-duty scan tool (e.g., Noregon JPRO, Cummins INSITE, or CAT ET) or a generic J1939 adapter with software like CANoe or PCAN-View. Basic OBD-II readers do not support J1939 protocols. The tool must be able to read SPN 147 and FMI 2 from the engine ECU on the CAN bus at 250 kbps.
17. What can a professional J1939 scanner do that a basic reader cannot?
A professional J1939 scanner can display live data from multiple ECUs simultaneously, log intermittent faults with timestamps, perform bidirectional tests (e.g., command the fuel flow sensor to output a test signal), and view detailed PGN data. It can also reflash ECM firmware, recalibrate sensors, and monitor CAN bus traffic for noise or errors. Basic readers only show fault codes without live data or advanced diagnostics.
18. What are the key CAN bus parameters I should monitor when diagnosing this code?
Monitor SPN 147 (Engine Average Fuel Economy) for erratic changes. Also watch SPN 94 (Fuel Pressure) and SPN 102 (Engine Fuel Rate) to see if the fuel economy signal correlates with actual fuel flow. Check SPN 190 (Engine Speed) and SPN 91 (Accelerator Pedal Position) to ensure the sensor data matches driver demand. Monitor CAN bus load and error frames; excessive errors can cause signal corruption.
19. What is a PGN and how does it relate to SPN 147?
A PGN (Parameter Group Number) is a 19-bit identifier in J1939 that defines a group of related parameters transmitted in a single CAN message. SPN 147 is part of PGN 65266 (Engine Fuel Economy) or PGN 65270 (Engine Fluid Level/Pressure). The PGN carries the data for SPN 147 along with other parameters like fuel rate and pressure. To read SPN 147, the tool must decode the correct PGN on the CAN bus.
20. What components make up a complete J1939 Diagnostic Trouble Code (DTC)?
A complete J1939 DTC consists of four parts: SPN (Suspect Parameter Number) identifies the specific parameter, FMI (Failure Mode Indicator) describes the type of fault, CM (Conversion Method) indicates how the data is scaled, and OC (Occurrence Count) tracks how many times the fault has been detected. For SPN 147 FMI 2, the CM is typically 0 (linear scaling) and the OC increments each time the fault reoccurs.