Full Diagnostic Guide — SPN 171 FMI 13
1. What does SPN 171 FMI 13 mean?
SPN 171 FMI 13 indicates an out-of-calibration error for the ambient air temperature sensor. This means the sensor’s signal is valid but its reported temperature deviates from the expected calibrated range by more than the allowable tolerance, typically ±5°C compared to a reference value. The ECM flags this fault when the sensor data does not match the internal calibration model after a replacement or ECM update.
2. What are the most common symptoms when this code is active?
Common symptoms include inaccurate ambient temperature readings on the dash, engine torque derating (typically reducing power by up to 25% to protect the engine), increased fuel consumption by 5-10% due to improper air-fuel mixture adjustments, and illumination of the check engine or amber warning lamp. Operators may also notice poor cold-start behavior or altered fan clutch engagement timing.
3. How does the ECM determine that this specific failure (FMI 13) has occurred?
The ECM compares the ambient air temperature sensor’s output voltage (typically 0.5–4.5 V for -40°C to +125°C range) against a stored calibration table. If the sensor reads a temperature that is consistently offset by more than 3 standard deviations from the expected value during key-on or steady-state conditions, the ECM sets FMI 13. The fault is confirmed after two consecutive drive cycles with the deviation present.
4. What is the difference between FMI 13 and other common FMIs for SPN 171?
FMI 13 is an out-of-calibration error, meaning the sensor is electrically functional but provides inaccurate data. In contrast, FMI 3 (voltage above normal) indicates a short to high voltage (>4.8 V), FMI 4 (voltage below normal) indicates a short to ground or open circuit (<0.2 V), and FMI 2 (data erratic) indicates intermittent signal issues. FMI 13 specifically requires calibration verification, not just electrical repair.
5. What are the most probable root causes?
The most probable root causes are: failure to recalibrate the ambient temperature sensor after ECM software updates or sensor replacement; sensor misalignment or improper mounting causing thermal mass errors; corroded or damaged connector pins (especially pin 1 and 2) causing signal drift; and ECM software glitches that corrupt calibration data. A loose mounting bracket can also cause intermittent calibration mismatches.
6. Can a purely mechanical issue cause this code without a faulty component?
Yes. Mechanical issues such as a sensor mounted too close to a heat source (e.g., exhaust manifold or radiator), obstructed airflow around the sensor, or a sensor not fully seated in its grommet can cause thermal offset errors that trigger FMI 13. Also, debris or ice buildup on the sensor housing can alter its thermal response time, leading to calibration mismatches without an electrical fault.
7. What default actions does the ECM take when this code is active?
The ECM defaults to a substitute ambient temperature value, typically 25°C (77°F), and may enable engine torque derating (up to 40% reduction in severe cases) to prevent damage from incorrect air-fuel ratios. The ECM also disables any temperature-dependent strategies like intake air heater control and fan clutch modulation. The amber warning lamp is illuminated, and the fault is logged in non-volatile memory.
8. How do I perform a basic functional test for this component?
With the ignition on and engine off, measure the sensor voltage at the ECM connector (pins for sensor signal and ground). Compare the reading to a known ambient temperature using a calibrated thermometer. For a NTC-type sensor, voltage should decrease as temperature rises. If the voltage corresponds to a temperature more than ±4°C from actual ambient, the sensor may be out of calibration.
9. What specific electrical checks should I run before replacing parts?
Measure the sensor’s resistance at two known temperatures (e.g., ice water at 0°C and boiling water at 100°C) and compare to the manufacturer’s resistance-temperature curve. Check for voltage drop across the ground circuit (should be <0.1 V). Inspect connector pins for corrosion or bent terminals. Verify that the sensor’s 5V reference supply is stable within ±0.1 V at the sensor connector.
10. Is it possible that the ECM itself is responsible for this fault?
Yes. A corrupted calibration table in the ECM due to a failed software update or memory corruption can cause the ECM to misinterpret valid sensor data as out-of-calibration. This is more common after reflashing. Check for ECM software version mismatches and review manufacturer service bulletins. If all sensor and wiring checks pass, an ECM reflash or replacement may be necessary.
11. What is the complete step-by-step diagnostic procedure?
1. Record freeze frame data. 2. Visually inspect sensor mounting and connector integrity. 3. Compare sensor reading to a reference thermometer at key-on. 4. Measure sensor resistance at two known temperatures. 5. Check 5V reference and ground circuits. 6. Perform a wiggle test on wiring. 7. Verify ECM calibration version. 8. Recalibrate sensor per manufacturer procedure (often via scan tool). 9. Clear code and test drive. 10. If code returns, replace sensor and recalibrate.
12. How can I prevent this fault from recurring?
Always perform a recalibration procedure after replacing the ambient temperature sensor or updating ECM software. Ensure the sensor is mounted in a location with free airflow, away from heat sources, and that its mounting bracket is tight. Use dielectric grease on connectors to prevent corrosion. Regularly inspect the sensor for debris or ice buildup. Follow OEM service bulletins for calibration updates.
13. Does this fault affect fuel economy, emissions, or engine lifespan?
Yes. Incorrect ambient temperature data can cause the ECM to command a richer air-fuel mixture, increasing fuel consumption by 5-10% and raising NOx and particulate emissions. Prolonged operation can lead to increased cylinder temperatures and potential damage to aftertreatment systems. Engine derating reduces performance but may protect the engine from catastrophic failure if the mixture is excessively off.
14. Can I clear the code and continue operating the vehicle temporarily?
You can clear the code with a diagnostic tool, but it will likely reappear within one drive cycle if the underlying calibration issue is not resolved. Temporary operation is possible, but engine derating and increased fuel consumption will persist. For safety, avoid heavy loads or extended operation. The fault will not cause immediate engine failure, but it should be addressed within 50 operating hours.
15. When should I choose to replace the component versus repairing the wiring?
Replace the sensor if its resistance deviates more than 5% from the specification at any test temperature, or if the sensor housing is physically damaged. Repair wiring only if you find corroded pins, broken wires, or damaged insulation causing intermittent signals. If the sensor passes electrical tests but the fault persists, replace the sensor first, as internal calibration drift is common in aged sensors.
16. What type of diagnostic tool do I need to read this fault code?
You need a J1939-compatible diagnostic tool, such as a Noregon JPRO, Cummins INSITE, or a generic SAE J1939 scanner with DTC reading capability. A basic OBD-II reader will not work, as heavy-duty vehicles use the J1939 protocol. The tool must support reading SPN 171 and FMI 13, as well as live data for ambient temperature and calibration status.
17. What can a professional J1939 scanner do that a basic reader cannot?
A professional J1939 scanner can display live sensor voltage and temperature values, perform bidirectional recalibration of the ambient temperature sensor, read freeze frame data for SPN 171 FMI 13, monitor CAN bus traffic to detect signal integrity issues, and access ECM calibration parameters. It can also run component tests (e.g., forcing a temperature value) and log data over time to identify intermittent calibration drift.
18. What are the key CAN bus parameters I should monitor when diagnosing this code?
Monitor PGN 65269 (Ambient Conditions) which contains SPN 171 (Ambient Air Temperature). Also monitor PGN 65270 (Engine Temperature 1) for comparison. Check the signal’s update rate (should be 1 Hz ±20%) and the raw voltage value from the sensor if your tool supports it. Watch for any bus errors (e.g., PGN 65235) that could indicate wiring issues affecting the sensor circuit.
19. What is a PGN and how does it relate to SPN 171?
A PGN (Parameter Group Number) is a 19-bit identifier that groups related parameters on the J1939 bus. SPN 171 (Ambient Air Temperature) is transmitted within PGN 65269 (Ambient Conditions). The PGN defines the message structure and priority, while the SPN identifies the specific data parameter. To read SPN 171, your tool must decode PGN 65269 and extract the 16-bit temperature value from the correct byte position.
20. What components make up a complete J1939 Diagnostic Trouble Code (DTC)?
A complete J1939 DTC consists of four parts: the Suspect Parameter Number (SPN), which identifies the component or parameter (e.g., 171 for ambient air temperature); the Failure Mode Identifier (FMI), which describes the fault type (e.g., 13 for out-of-calibration); the Occurrence Count (OC), indicating how many times the fault has been detected; and the SPN Conversion Method (CM), which defines how the SPN data is interpreted. Together, these four fields uniquely identify the fault.