J1939 Vehicle Data Link Test

Overview

This symptom driven test is performed if the J1939 Vehicle Data Link is failing to function in some way without setting transmission Fault Code 35. Proper operation of the J1939 Vehicle Data Link is critical for proper transmission operation.

Detection

  • Various communication problems between vehicle ECUs.
  • ServiceRanger or other diagnostic software may not be able to communicate with TECU or vehicle ECUs.
  • If vehicle is configured for the J1939 Start Enable feature the engine may not crank.

Possible Causes

  • J1939 Vehicle Data Link
    • Wiring shorted to ground, shorted to power or open
    • Bent, spread, corroded or loose terminals
    • Excessive electrical noise
    • Missing or additional terminating resistors
  • Various Vehicle ECUs
    • Internal Failure
    • Loss of Power Supply to ECU
    • Poor connection to J1939 Vehicle Data Link
    • Wiring shorted to ground, shorted to power or open

Component Identification

_Graphics/LineArt/TRTS0940_FC35-36_ID1.png

1. 38-Way Vehicle Harness Connector

2. Transmission Electronic Control Unit (TECU)

3. 9-Way Diagnostic Connector (in cab)

_Graphics/LineArt/TRTS0940_FC35_Wiring.png

1. Transmission Electronic Control Unit (TECU)

2. 38-Way Vehicle Harness Connector

3. 9-Way Diagnostic Connector (Black) - OEM Specific CD (in cab)

4. 9-way Diagnostic Connector (Green) - OEM Specific CD (in cab)

5. 9-way Diagnostic Connector (Green) - OEM Specific FG (in cab)

_Graphics/LineArt/Wiring-Key-EPS.png

J1939 Vehicle Data Link Test

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

  2. Key on with engine off.

  3. Connect ServiceRanger.

  4. Update transmission software to latest available level.

    Note: To avoid damaging the TECU, use an approved communications adapter and ensure all satellite systems are disabled before updating software.

  5. Retrieve and record the transmission fault codes and FMIs, and their occurrences and timestamps.

  • If Fault Code 35 is Active or Inactive, troubleshoot per Fault Code Isolation Procedure Index on page 13.

  • If another Fault Code is Active, troubleshoot per Fault Code Isolation Procedure Index on page 13.

  • If Fault Codes 35 is not present and there are no other Active fault codes, Go to Step B

  • If ServiceRanger does not connect, Go to Step C

B
Purpose:Use Product Diagnostic (PD) Mode to locate intermittent failures.
  1. Set parking brake and chock wheels.

  2. Place transmission in PD Mode. See more about Product Diagnostic (PD) Mode.

    Note: Transmission does not enter PD Mode when Active fault codes exist.

    Note: Solid “PD” in display when test is active.

    _Common/_Graphics/PD_GearDisplay.png
  3. Wiggle wiring and connections through out the entire J1939 Vehicle Data Link up to the 38-Way TECU Vehicle Harness. Look for any obvious signs of rubbing or chafing on any of the wires. Consult OEM for specific wire routing locations.

  4. Exit PD Mode.

  • If the ServiceRanger connection to the vehicle was lost or Fault Code 35 became Active while wiggling the J1939 Vehicle Data Link, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If no fault code set active, Go to Step C

C
Purpose:Identify TECU location on J1939 Vehicle Data Link.
  1. Key off.

  2. Refer to the OEM and identify the TECU location on the J1939 Vehicle Data Link at the 9-Way Diagnostic Connector.

  • If Black 9-Way Diagnostic Connector, Go to Step D

  • If Green 9-Way Diagnostic Connector on Pin C and Pin D, Go to Step D

  • If Green 9-Way Diagnostic Connector on Pin F and Pin H, Go to Step H

D
Purpose:Verify resistance of J1939 Vehicle Data Link at 9-Way Diagnostic Connector (CD).
  1. Key off.

  2. Measure resistance between 9-Way Diagnostic Connector Pin C and Pin D. Record reading in table.

    _Graphics/LineArt/TRTS0940_FC35_DiagPinCandD-Ohms.png
  3. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If readings are in range, Go to Step E

PinsRangeReading(s)
C to D50–70 Ohms
E
Purpose:Verify 38-Way TECU Vehicle Harness Connector condition.
  1. Key off.

  2. Disconnect the 38-Way TECU Vehicle Harness Connector.

  3. Inspect the 38-Way TECU Vehicle Harness Connector for contamination, corrosion, damage, loose, bent or spread terminals.

  4. Inspect the TECU side of the 38-Way TECU Vehicle Harness Connector for contamination, corrosion, damage, loose, bent or spread terminals.

  • If any contamination or damage is found, refer to OEM guidelines for repair or replacement of the 38-Way TECU Vehicle Harness Connector.

  • If no contamination or damage is found, Go to Step F

F
Purpose:Verify TECU connection across J1939 Vehicle Data Link Positive (+/High) to 9-Way Diagnostic Connector.
  1. Key off.

  2. Measure resistance between 38-Way TECU Vehicle Harness Connector Pin 3 and 9-Way Diagnostic Connector Pin C. Record reading in table.

    _Graphics/LineArt/TRTS0940_FC35_DiagPinCVPin3.png
  3. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If readings are in range, Go to Step G

PinsRangeReading(s)
3 to C0–0.3 Ohms
G
Purpose:Verify TECU connection across J1939 Vehicle Data Link Negative (-/Low) to 9-Way Diagnostic Connector.
  1. Key off.

  2. Measure resistance between 38-Way TECU Vehicle Harness Connector Pin 2 and 9-Way Diagnostic Connector Pin D. Record reading in table.

    _Graphics/LineArt/TRTS0940_FC35_DiagPinDVPin2.png
  3. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If readings are in range, Go to Step L

PinsRangeReading(s)
2 to D0–0.3 Ohms
H
Purpose:Verify resistance of J1939 Vehicle Data Link at 9-Way Diagnostic Connector (FG).
  1. Key off.

  2. Measure resistance between 9-Way Diagnostic Connector Pin F and Pin G. Record reading in table.

    _Graphics/LineArt/TRTS0940_J1989_DiagPinFandG.png
  3. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If readings are in range, Go to Step I

PinsRangeReading(s)
F to G50–70 Ohms
I
Purpose:Verify 38-Way TECU Vehicle Harness Connector condition.
  1. Key off.

  2. Disconnect the 38-Way TECU Vehicle Harness Connector.

  3. Inspect the 38-Way TECU Vehicle Harness Connector for contamination, corrosion, damage, loose, bent or spread terminals.

  4. Inspect the TECU side of the 38-Way TECU Harness Connector for contamination, corrosion, damage, loose, bent or spread terminals.

  • If any contamination or damage is found, refer to OEM guidelines for repair or replacement of the 38-Way TECU Vehicle Harness Connector.

  • If no contamination or damage is found, Go to Step J

J
Purpose:Verify TECU connection across J1939 Vehicle Data Link Positive (+/High) to 9-Way Diagnostic Connector.
  1. Key off.

  2. Measure resistance between 38-Way TECU Vehicle Harness Connector Pin 3 and 9-Way Diagnostic Connector Pin F. Record reading in table.

    _Graphics/LineArt/TRTS0940_FC35_DiagPinFVPin3.png
  3. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If readings are in range, Go to Step K

PinsRangeReading(s)
3 to F0–0.3 Ohms
K
Purpose:Verify TECU connection across J1939 Vehicle Data Link Negative (-/Low) to 9-Way Diagnostic Connector.
  1. Key off.

  2. Measure resistance between 38-Way TECU Vehicle Harness Connector Pin 2 and 9-Way Diagnostic Connector Pin G. Record reading(s) in table.

    _Graphics/LineArt/TRTS0940_FC35_DiagPinGVPin2.png
  3. Compare reading(s) in table.

  • If readings are out of range, refer to OEM guidelines for repair or replacement of J1939 Vehicle Data Link. Go to Step V

  • If readings are in range, Go to Step L

PinsRangeReading(s)
2 to G0–0.3 Ohms
L
Purpose:Use ServiceRanger to monitor ECUs communication on the J1939 Vehicle Data Link.
  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 “Data Monitor”.

  6. Select “Components” tab.

  7. Monitor the roster of vehicle ECUs currently communicating on the J1939 Vehicle Data Link.

  8. Compare this list to the roster of vehicle ECUs that should be communicating on the J1939 Vehicle Data Link.

    Note: Contact the OEM for information about which vehicle ECUs should be on the J1939 Vehicle Data Link.

  • If no vehicle ECUs are present on the ServiceRanger roster, Go to Step M

  • If all vehicle ECUs are present on the ServiceRanger roster, no problem was found during testing. Test complete. Contact the OEM if further diagnostics are required.

  • If any vehicle ECU is missing from the ServiceRanger roster, investigate that device to verify that it is properly powered and wired to the J1939 Vehicle Data Link. Repair or replace any component or wiring per OEM requirements. Go to Step V

M
Purpose:Remove vehicle devices from the J1939 Vehicle Data Link.
  1. Key on with engine off.

  2. Connect ServiceRanger.

  3. Go To “Data Monitor”.

  4. Select “Components” tab.

  5. Monitor the roster of vehicle ECUs currently communicating on the J1939 Vehicle Data Link.

  6. Individually remove each vehicle ECU from the J1939 Vehicle Data Link.

  7. After removing each device, monitor the ServiceRanger ECU roster.

  8. If the removal of an ECU from the J1939 Vehicle Data Link allows other ECUs to appear in the ServiceRanger ECU roster, the removed ECU may have been shorting out the J1939 Data Link or otherwise preventing communication.

  • If a problem is found, repair or replace the wiring or component per OEM requirements. Go to Step V

  • If no problems are found, contact the OEM for further diagnostics.

V
Purpose:Verify repair.
  1. Key off.

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

  3. Key on.

  4. Clear fault codes using ServiceRanger.

  5. Drive vehicle and attempt to reset the code or duplicate the previous complaint.

  6. Check for fault codes using ServiceRanger: