Fault Code 960: Neutral Status 2

J1939: SA 3 SPN 6159 FMI 12

Overview

The Endurant HD Series transmissions are equipped with position sensors to monitor shift rail positions and speed sensors to monitor shaft speeds. The sensor information is provided to the Transmission Control Module (TCM) for the purpose of making shift decisions, confirming gear engagement, and monitoring shift rail positions.

The TCM is configured to accept Shift Mode request messages from the vehicle Driver Interface Device over the Primary Data Link (J1939A). A second Shift Mode request signal from the vehicle Driver Interface Device is also provided on a separate circuit.

The TCM compares Shift Mode requests to the shift rail positions and shaft speeds (ratio calculation) to ensure the transmission is operating properly.

Detection

The TCM monitors Shift Mode request messages and gear position. If a system failure is detected, the fault is set Active.

Conditions to Set Fault Code Active

FMI 12 – Bad Intelligent Device: Failed to disengage gear when Neutral Shift Mode was requested.

Fallback

FMI 12:

  • Urge to Move and Creep Mode prohibited
  • Non-Neutral modes prohibited
  • Clutch engagement prohibited
  • PTO Mode prohibited

Conditions to Set Fault Code Inactive

FMI 12: Key cycle and fault condition no longer exist.

Possible Causes

FMI 12:

  • TCM
    • Software issue
    • Internal failure

Additional Tools

  • None

Fault Code 960 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.

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.