AUSTRALIA, BAHAMAS, BOLIVIA, BRAZIL, BELIZE,
CANADA, CHILE, TAIWAN, COLOMBIA, COSTA RICA,
DOMINICAN REPUBLIC, ECUADOR, EL SALVADOR,

Countries: GUAM, GUATEMALA, GUYANA, HalT!, HONDURAS, Document iiggoo9g0
JAMAICA, KOREA, SOUTH KOREA, MEXICO, ARUBA, 1D:
NEW ZEALAND, NICARAGUA, PANAMA, PERU, PUERTO.

RICO, SOUTH AFRICA, TRINIDAD AND TOBAGO, UNITED
STATES, URUGUAY, VENEZUELA, Curagao
| Availability: ISIS, Bus ISIS, Flest!SIS, Body Builder, 'sSIR Revision: 42
Major Created: 8/22/2007

ELECTRICAL SYSTEM

Knowledge Base on Lact
urrent ast
Language: &nglish Modified: 8/14/2023
Other . ean
Languages: F'ancais, Espafol, Portuguese, Author: $20,
Viewed: 189218
¥
Copy Link Copy Relative Link Bookmark Add to Favorites Print Provide Feedback Helpful Not Helpful

View My Bookmarks

6 C 10878 7063

Title: J1939 Data Link Troubleshooting

Applies To: All Models with 250k Baud Data Link (Black 9-Pin Diagnostic Connector); Overview information for
500k Baud Data Link

Change Log

Dealers: Please refer to the change log text box below for recent changes to this article:

08/09/2023 - Added N2 module and RP1226 Connectors to SOOK Phase 2 diagram.
401/18/2022 - Republished for feedback purposes. No content change.
101/04/2022 - Republished for feedback purposes. No content change.
{08/24/2020 - Added printable POF of 500k topology. Added PSI ECM terminal numbers. No connector composite is available at this time.
108/04/2020 - Added connector view for 9511A TRW ABS EHCU (TerraStar / AE Bus), and added more detail to terminating resistor locations. =
02/27/2020- Added information on Nexiq Device Tester's ability to monitor datalink voltages

* This article is for general J1939 troubleshooting on 250k baud data link vehicles. They will have a black 9-pin diagnostic connector. The
information provided applies to all models. Check the Fault Code Action Plan for the faults you are diagnosing, there may be model
specific FCAP diagnostic information available.

* You MUST review the "Service Information (Known Issues)" section of this iKNow article PRIOR to troubleshooting anything on the truck.

Related troubleshooting information: For 500k baud vehicles (with a green diagnostic connector) refer to the appropriate
troubleshooting manual found in Master Service Information.

© The Nexiq Device Tester application with datalink voltage monitoring works on all J1939 datalinks. See here

Data Link Sniffer Information:

INTUNE - Modules drop offline or come online live while watching the screen. Will only work on 250k baud rate vehicles.

Helios - Modules are shown using a message counter. If the counter stops, the module is offline. You can also open a new modules tab
using ‘Tools - Modules' to see which modules are currently communicating.

Nexiq Device Tester - You must choose which channel to connect to when using as a sniffer. Channel 1 or Channel 2. This tool also allows
you to monitor datalink voltages without the need for a multimeter. See here

Click Here for a printable PDF version of this article.

Table of Contents

500k Baud (Phase 1) Vehicle

Description Service Part(s) Information ( )
Architecture

symptom(s) Additional Resources 500k Baud (Phase 2) Vehicle
Architecture

|Special Tool(s) or

Connector Views
Software

Service Information (Known

Diagnostic Steps Issues)

Related iKNow Article: IK1200921 - ISX, N13, and N9 / N10 Aftertreatment Private Data Link Troubleshooting

Related troubleshooting information: For 500k baud vehicles (with a green diagnostic connector) refer to the appropriate troubleshooting
manual found in Master Service Information.

Description
There are a few things that you need to understand before troubleshooting the 1939 data link.

1. First, the drivetrain J1939 data link, J1939 body builder data link, and J1939 engine data link are three completely separate data links.

© For specific examples of modules on each different data link Click Here
The different J1939 data links work the same way, but the wiring for them is not connected.
The troubleshooting below is geared towards the drive train J1939 data link, but the same principles apply to the body builder and engine
data link.
The J1939 data link consists of a twisted pair of yellow and green wires that all the modules on the truck use to communicate with each
other.
. Two 120 ohm terminating resistors are wired in parallel on the data link. Total resistance on a properly working data link is 60 ohms.

© When measuring resistance, the batteries must be disconnected.

. When you are checking the data link, if the problem is not present, the data link will show good.
The J1939 data link may be referred to as data bus, or CAN as well.
A module is capable of being connected to the public and private data link, but the information remains separate.

© Example: The Body Controller communicates on the public drivetrain data link, but also has the private body builder data link wired

toit.

»N

>

w

a

oN

°

Example: The EIM communicates on the drivetrain data link, but also communicates with the ECM and ACM on the engine private
data link.

The MaxxForce 7 TMV (Thermal Management Valve) is on the Public data link. This module will not show up on the sniffer.
The ECM Engine and Chassis connector's data link terminals are connected internally to the module.
£13 and C53 are internally connected. E14 and C54 are internally connected.

For Post-2007 vehicle 1939 troubleshooting, click on the appropriate link below:

* The troubleshooting cards give a good overview of the data link. This will help show you the backbone of the data link (main data link
wiring between 1st terminating resistor to 2nd terminating resistor) and the stubs of the data link (wiring from the backbone to each
possible module)

Basic example of Public J1939 data link |
Transmission ABS Electronic Secondary 7 Ate .
Control Control Gauge Instrument ConEar
Module Module Cluster Cluster Module
Stub Stub ‘Stub Stub Stub]
CANH ANH
CAN LL Backbone Backbone CAN:
Terminator Ti
1200 Stub Stub Stub Stub ison"
Brine Body Electronic Telematics
Modiile Controller Shifter Device

« The J1939 Splice Adapters (1024, 1025, 1026) are part of the backbone of the data link (The backbone will come in on 2 terminals and
leave on 2 different terminals). The wiring from the connector to each module is a stub.

© 2007 - HPV (medium duty) 1939 Troubleshooting Card

© 2007 - CE/ BE Bus 1939 Troubleshooting Card

© 2007 - ProStar 1939 Troubleshooting Card

These cards are 11" x 17" so they may not print well on regular size paper.
Many of the 2010 and newer models have troubleshooting information and CAN network layout in the Technician Manuals, and the engine
wiring schematics.

There are the most current troubleshooting cards that are available for printing. For more information specific to ProStar and LoneStar refer to
the Data Link Service Procedure found in the 2010-2016 ProStar® Technician Manual 0000863170. If you wish to order the above cards, you
can order them through the Navistar Print Portal from the Service Portal - Dealer Menu. The part numbers are:

Vehicle Model Part Number
a
CE / BE Bus Card $00154

( Back to Top )

Symptoms

Diagnostic Trouble Code(s) & Dashboard Indicator Light(s):

[sen ][ rt | Module and Source Address (SA) __|| Description

ProStar/LoneStar J1939 Fault Code Combination

PRO100 0 Synthetic Fault Code Occurred

proi00 |1 synthetic Fault Code ProStar/LoneStar J1939 Fault Code Combination

[2000 [2 [Gauge Cluster (23) / Body Controller (33) |Loss of data link from the Engine Controller

[2003 lo [Gauge Cluster (23) / Body Controller (33) | Loss of data link from the Transmission Controller

Occurred
[cen200 fo _ [synthetic Fault Code |[A combination of 11939 Fault Codes Occurred
[SeN100 [ 1 [synthetic Fault Code [A combination of J1939 Fault Codes Occurred |
[cen100 [2 [synthetic Fault Code |[A combination of 11939 Fault Codes Occurred
[639 | | Body Controller (33) | Drivetrain message timeout
[639 [24 [Body Controtter (33) [Drivetrain message timeout
[2000 [19 _ [Body controtter (33) |[P1c1 (PGN 64892) not Received from Engine
[2023 lo | Body Controller (33) | EGC data link communication failure
|
|

)
[2011 [2__[[Gauge Cluster (23) / Body Controller (33) Loss of data link from the ABS Controller
)

[2023 | 14 |[cauge Cluster (23, | Gauge cluster lost communication with the ESC

2023/14 ||cauge cluster (23) Gauge cluster lost communication with the Engine