Fault Code 171: Engine Speed

J1939: SA 3 SPN 190 FMI 9, 13, 19

Overview

The Transmission Control Module (TCM) receives the vehicle's Engine Speed message from a vehicle Electronic Control Unit (ECU) over the Primary Data Link (J1939A). This information is used to determine transmission operation.

The TCM also receives the Engine Speed message over the Secondary Data Link (J1939B). The Secondary Data Link is used in the event that the Primary Data Link is inoperative and allows the transmission to operate in a degraded mode.

The Primary Data Link (J1939A) is connected to the TCM at the 20-Way TCM Vehicle Harness Connector. The Secondary Data Link (J1939B) is connected to the TCM at the 20-Way TCM Body Harness Connector.

Detection

The TCM monitors Engine Speed messages on the Primary Data Link (J1939A). If messages are not received or are invalid, the fault is set Active.

Conditions to Set Fault Code Active

FMI 9 - Abnormal Update Rate: Engine Speed message not received for 5 seconds.

FMI 13 – Out Of Calibration: Engine Speed message not available for 5 seconds.

FMI 19 – Received Network Data In Error: Engine Speed messages invalid for 5 seconds.

Fallback

FMI 9, 13, 19:

  • Amber warning lamp on
  • Coast Mode and Neutral Coast prohibited
  • Urge to Move and Creep Mode prohibited
  • Inertia Brake activation prohibited
  • Upshifts prohibited
  • Clutch engagements prohibited
  • Non-Neutral modes prohibited
  • PTO mode prohibited
  • Hill Start Aid prohibited
  • If vehicle is moving:
    • Red stop lamp on

Note: Vehicle may have additional fallback modes. Refer to OEM.

Conditions to Set Fault Code Inactive

FMI 9, 13, 19: Engine Speed messages received and valid for 10 seconds.

Possible Causes

FMI 9, 13, 19:

  • Vehicle Components
    • Engine Speed message not enabled on Primary Data Link (J1939A)
    • Other vehicle ECU(s) faulted
  • Vehicle Harness - Primary Data Link (J1939A)
    • Wiring shorted to power, shorted to ground or open
    • Terminals bent, spread, corroded, or loose

Note: Refer to OEM for troubleshooting a failed system.

Additional Tools

  • None

Fault Code 171 Troubleshooting

A
Purpose:Check for Active or Inactive fault codes.
  1. Set vehicle parking brake and chock wheels.

  2. Record transmission fault codes, FMIs, occurrences, and timestamps from Service Activity Report created during the Diagnostic Procedure.

  • If Fault Code 171 is Inactive and there are other Active vehicle or transmission fault codes, troubleshoot all Active fault codes. Go to Step V

  • If Fault Code 171 FMI 9, 19 is Active or Inactive, Go to Step B

  • If Fault Code 171 FMI 13 is Active, refer to OEM and enable vehicle Engine Speed message (SPN 190).Go to Step V

  • If Fault Code 171 FMI 13 is Inactive, Go to Step V

B
Purpose:Verify Engine speed signal message.
  1. Key on with engine on at idle.

  2. Connect ServiceRanger.

  3. Go to “Data Monitor”.

  4. Select “Speed”.

  5. Select “Engine speed”.

  6. Select all “- 190” SPN sources.

    Note: Not all sources will indicate a value.

  7. Monitor 190 - Engine speed value. Record reading in table.

  8. Monitor vehicle tachometer engine idle RPM value. Recording reading in table.

  9. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair of the vehicle Engine Speed message (SPN 190) on Primary Data Link (1939A). Go to Step V

  • If readings are in range and no fault was found, the intermittent nature of the fault makes it likely that the problem is in the vehicle Engine Speed message (SPN 190) on Primary Data Link (J1939A). Contact OEM for further diagnostic instructions. Go to Step V

Engine Speed Signal SourceRangeReading(s)
Vehicle TachometerIdle RPM
190 - Engine SpeedWithin 150 RPM of Engine Idle
V
Purpose:Verify repair.
  1. Key off.

  2. Reconnect all connectors and verify all components are properly installed.

  3. Key on with engine off.

  4. Connect ServiceRanger.

  5. Go To “Fault Codes”.

  6. Select “Clear All Faults”.

  7. Operate vehicle and attempt to reset the fault code or duplicate the previous complaint.

  8. Check for fault codes using ServiceRanger.