Fault Code 702: Driveline Engagement

J1939: SA 3 SPN 560 FMI 2, 11, 12, 14, 20, 21, 31

Overview

The Endurant HD transmission is equipped with solenoids to direct pneumatic flow to actuate the clutch and shift rails and sensors to monitor the clutch and shift rail positions. The Transmission Control Module (TCM) compares the clutch and shift rail commands with the clutch and shift rail positions including speed sensors (ratio calculation) to ensure proper operation. The solenoids, sensors, Linear Clutch Actuator (LCA) and shift rails are located in the Mechatronic Transmission Module (MTM) and connected to the TCM at the 74-Way Transmission Harness Connector.

The TCM monitors the clutch and shift rail operation. If a system failure is detected, the fault is set active.

Conditions to Set Fault Code Active

FMI 2 – Data Erratic: During a Clutch Calibration, the speed sensors could not confirm the main shaft was neutralized while Rail C or D Position Sensor reported neutral.

FMI 11 - Root Cause Unknown: Transmission output shaft speed sensor direction mismatch with counter shaft speed sensor for 2 seconds.

FMI 12 – Bad Intelligent Device or Component: Speed sensors did not confirm the main shaft was neutralized during clutch engagement.

FMI 14 – Special Instructions: Shift rail engagement was commanded that would result in a drive line engagement with the vehicle stationary.

FMI 20 – Data Drifted High: Rail C or E Position Sensors indicated gear engagement when not expected for 2 seconds.

FMI 21 – Data Drifted Low: Rail D or E Position Sensors indicated gear engagement when not expected for 2 seconds.

FMI 31 – Condition Exists: Urge to Move and Creep Mode were not commanded when expected.

Fallback

FMI 2, 11:

  • Amber warning lamp on
  • Non neutral modes prohibited
  • Clutch engagement prohibited
  • PTO Mode prohibited
  • Urge to Move and Creep Mode prohibited
  • If vehicle is moving
    • Red stop lamp on

FMI 12, 31:

  • Amber warning lamp on
  • Clutch engagement prohibited
  • Rail B, C and D shift to neutral
  • PTO Mode prohibited
  • Urge to Move and Creep Mode prohibited
  • If vehicle is moving
    • Red stop lamp on

FMI 20, 21:

  • Amber warning lamp on
  • Clutch engagement prohibited
  • Rail B shifts to neutral
  • PTO Mode prohibited
  • Urge to Move and Creep Mode prohibited
  • If vehicle is moving
    • Red stop lamp on

FMI 14:

  • Amber warning lamp on
  • Red stop lamp on
  • Rail C and D shift to neutral

Conditions to Set Fault Code Inactive

FMI 2, 12, 14, 31: Power down (key cycle)

Possible Causes

FMI 2:

  • Rail C or D Position Sensors

FMI 11:

  • Counter Shaft or Output Speed Sensors

FMI 12, 14:

  • TCM
    • Internal failure
    • Software issue

FMI 20, 21:

  • Rail C, D or E Position Sensors

FMI 31:

  • Parking Brake Switch/signal
    • Vehicle Parking Brake Set and the driver selected a Reverse or Drive Mode
    • Internal failure
  • TCM
    • Internal failure
    • Software issue

Additional Tools

  • None

Fault Code 702 Troubleshooting

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

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

  • If Fault Code 702 FMI 2, 11, 14, 20, 21 is Active or Inactive, contact Eaton Cummins Automated Transmission Technologies at 800-826-4357 for further diagnostic instructions. Go to Step V

  • If Fault Code 702 FMI 31 is Active or Inactive, Go to Step B

  • If Fault Code 702 FMI 12 is Active or Inactive, Go to Step D

B
Purpose:Verify TCM Software.
  1. Key off.

  2. Allow TCM to perform a complete power down.

  3. Key on with engine off.

  4. Connect ServiceRanger.

  5. Go to “Programming”.

  6. Under “Software Information”, record TCM software in table.

  • If TCM software is less than 5516036, update TCM software to latest available version. Go to Step V

  • If TCM software is 5516036 or greater, Go to Step C

C
Purpose:Verify Vehicle Parking Brake Switch signal with ServiceRanger.
  1. Key on with engine running.

  2. Allow air pressure to build to governor cut off.

  3. Key off.

  4. Key on with engine off.

  5. Connect ServiceRanger.

  6. Go To “Data Monitor”.

  7. From the “Default Parameter Files” tab, select “Vehicle Brake Messages”.

  8. Monitor 70 - Parking brake switch status. Record reading in table.

  9. Depress and hold service brake.

  10. Release vehicle parking brake.

  11. Monitor 70 - Parking brake switch status value. Record reading in table.

  12. Set vehicle parking brake.

  13. Monitor 70 - Parking brake switch status. Record reading in table.

  14. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of the Parking Brake Switch/signal. Go to Step V

  • f readings are in range, Contact Eaton Cummins Automated Transmission Technologies for further diagnostic instructions. For Help Line phone numbers, go to Contact Information. Go to Step V

Parking Brake StateParameterRangeReading(s)
Set70-Parking brake switch statusSet
Not set70-Parking brake switch statusNot set
Set70-Parking brake switch statusSet
D
Purpose:Verify TCM Software
  1. Key off.

  2. Allow TCM to perform a complete power down.

  3. Key on with engine off.

  4. Connect ServiceRanger.

  5. Go to “Programming”.

  6. Under “Software Information”, record TCM software in table.

  • If the TCM software is less than 5516018, update the TCM software to latest available version. Go to Step V

  • If the TCM software is equal to or greater than 5516018, Contact Eaton Cummins Automated Transmission Technologies for further diagnostic instructions. For Help Line phone numbers, go to Contact Information. Go to Step V

TCM Software Version
V
Purpose:Verify repair.
  1. Key off.

  2. Reconnect all connectors and verify that 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.