What Source Address Is and Where It Comes From
Source address (SA) is the J1939 network identifier for the module that sent a specific message. When an ECM, ABS controller, transmission TCM, or any other module broadcasts data or fault codes on the J1939 bus, it includes its source address in the message frame. This allows any receiving module — and any connected diagnostic tool — to identify which specific controller produced the message.
J1939 defines a source address range from 0 to 253, with certain values reserved for specific module types by convention. SA 0 is conventionally used for the engine ECM on many North American trucks; SA 11 is commonly used for ABS controllers; SA 3 is commonly used for transmission controllers. However, these are conventions, not universal standards — OEM implementations can vary, and the actual SA assignments should be confirmed using the OEM diagnostic tool's module identification screen.
Why Source Address Distinguishes Faults That Look the Same
The same SPN and FMI combination can appear from multiple different source addresses on the same vehicle, and the repair path is different for each. SPN 3364 FMI 1 (downstream NOx) from the engine ECM at SA 0 and the same SPN/FMI from an aftertreatment control module at a different SA are different fault events, potentially from different sensors or different monitoring systems. Without the source address, the two codes appear identical in a flat list.
On Freightliner Cascadia trucks, SPN codes from the Detroit DD15 engine ECM (SA 0) and codes from the chassis body controller (a different SA) appear on the same instrument cluster display. Without source address data, a chassis body controller code might be misidentified as an engine fault. A diagnostic tool that shows source addresses with each code prevents this confusion.
How to Find the Source Address
Source addresses are visible in the full J1939 fault code record captured by a diagnostic tool. Most dedicated J1939 scan tools and all OEM diagnostic software (Cummins Insite, Detroit DiagnosticLink, PACCAR ESA) display the source address alongside the SPN and FMI. Some fleet telematics systems capture source addresses in their fault code logs; others capture only the SPN/FMI.
The driver's instrument cluster display typically does not show the source address to keep the display readable. The source address becomes visible when a diagnostic tool is connected and reads the full fault record. For fleets that want to capture source addresses without a connected laptop, some telematics systems that have a J1939 adapter at the 9-pin port include SA in their transmitted fault data — checking the telematics system documentation confirms whether SA is captured.
Source Address in Multi-Module Fault Situations
In situations with multiple active faults, grouping codes by source address reveals the diagnostic structure. All codes from SA 0 (engine ECM) are engine or aftertreatment faults; all codes from the ABS module's SA are ABS faults; all codes from the transmission's SA are transmission faults. When multiple source addresses are involved in a single incident, the codes can be evaluated as a group to determine whether a common cause (J1939 bus fault, power supply fault) produced faults across all modules or whether each module's faults are independent.
A practical field use of source address: when a driver reports 'multiple warning lights,' looking at the source addresses of all active codes tells the technician whether they are looking at multiple independent issues or one root cause with cascade effects. Multiple codes from multiple source addresses that all appeared at exactly the same time and all involve communication — this is a network event, not multiple hardware failures.
Related Pages
Sources
- SAE J1939 Standards Collection SAE International · official · accessed 2026-05-05 · confidence medium
Source: SAE International, SAE J1939 Standards Collection. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation Electronic Code of Federal Regulations · government · accessed 2026-05-05 · confidence high
Source: Electronic Code of Federal Regulations, 49 CFR Part 393 - Parts and Accessories Necessary for Safe Operation. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Can two different modules on the same truck report the same SPN?
Yes. Multiple modules can monitor the same parameter type and each can broadcast its own reading. For example, both the engine ECM and an aftertreatment control module may broadcast SPN 110 (coolant temperature). A fault code from each would have the same SPN and possibly the same FMI but different source addresses. Without the SA, you cannot confirm which module flagged the condition.
My display shows a code but no source address is visible. Does that mean SA is zero?
Not necessarily — the display may simply not show the SA field even though it was transmitted. SA 0 is typically the engine ECM on most heavy trucks, but this varies by manufacturer. If the SA is important for your diagnosis, connect a diagnostic tool that shows source address in its fault code view rather than relying solely on the dash display.
If I do not know the source address, can I still look up a fault code on this site?
Yes, source address is not required to search or read pages on this site. However, knowing the SA helps you choose the right OEM documentation and diagnostic tool for the repair. Without SA, a shop may still find the relevant code through their tool's full fault code list, where SA is displayed alongside SPN and FMI.