KEY TAKEAWAYS
- Every Class 7 and Class 8 diesel truck built for the US since 2010 broadcasts DEF tank level, dosing rate, and SCR NOx data on the J1939 CAN bus, whether or not a telematics system is reading it.
- Intangles’ InGenious reads these J1939 parameters directly through the vehicle’s existing diagnostic connector, without cutting a DEF line or adding a tank sensor.
- InRoute turns raw signal data into alerts that fire well before torque derate begins, turning a roadside surprise into a scheduled repair.
- The OBDonUDS transition, beginning with the 2027 model year, changes how that same aftertreatment data gets accessed on newer trucks.
A truck can run for weeks with a DEF system already signaling trouble, long before the dashboard shows a warning light. That data exists the moment the engine turns over. Whether anyone is actually reading it is a separate question.
Every Class 7 and Class 8 diesel truck built for US operation since 2010 runs a Selective Catalytic Reduction system, and that system generates a constant stream of DEF-related data on the vehicle’s J1939 CAN bus. Tank level, dosing rate, and NOx readings update every second, broadcast across the network at 250 kbaud, whether or not a telematics device happens to be listening.
This blog covers how DEF signals travel from the aftertreatment control module to InRoute, the specific parameters involved, and what changes when the industry shifts to OBDonUDS in 2027.
Why US class 7-8 trucks generate DEF data
Since the 2010 model year, the EPA has required all heavy-duty diesel engines above its NOx emissions threshold to include SCR aftertreatment systems, which is why every Class 7-8 truck built for US roads since then carries an aftertreatment control module that never stops talking. That module continuously tracks DEF tank level, dosing rate, and NOx conversion efficiency, and broadcasts all of it to every node on the J1939 network.
Federal rules also require onboard diagnostics to monitor that same SCR system and catch low-DEF conditions before they become a bigger problem. That’s the exact layer a telematics gateway can tap into, provided it knows which parameters to listen for.
The J1939 data source: Which CAN Bus parameters carry DEF information
SPN 1761 carries DEF tank level as a percentage, updated once a second. It’s the same value the instrument cluster shows the driver, and Intangles’ InGenious reads it straight off the J1939 bus, without a tank sensor or a cut fuel line.
SPN 5246 reports the Aftertreatment 1 DEF consumption rate in liters per hour. When that number drifts from what a route and load would normally call for, it flags a dosing anomaly worth a closer look.
SPN 3226 and SPN 3227 report SCR inlet and outlet NOx concentration. The gap between the two tells the real story. A narrowing gap points to a catalyst losing conversion efficiency, sometimes weeks before a fault code ever appears.
SPN 4342 is a calculated SCR efficiency value, updated continuously rather than sampled at intervals. For a fleet manager, this is the single clearest early warning in the whole DEF data set: a sustained drop below roughly 95 percent tends to show up days or weeks before any diagnostic trouble code fires, which turns a catalyst replacement into a scheduled shop visit instead of a roadside failure.
Class 3-6 medium-duty trucks run OBD-II instead of J1939, and the same category of information shows up as diagnostic codes: P20EE for catalyst efficiency below threshold, P2202 for a NOx sensor circuit fault, and P2BAD for reductant quality issues. InGenious reads these directly from the vehicle’s OBD-II diagnostic buffers.
J1939 itself covers over 8,000 standardized parameters across every vehicle system, far more ground than DEF alone. Fleets running a mixed roster of light and heavy-duty trucks often need visibility into both protocols at once, which is exactly where the difference between the two becomes worth understanding in full.
How InGenious captures CAN Bus DEF signals without modifying the vehicle
InGenious connects through the vehicle’s 9-pin J1939-13 diagnostic connector, the same port a roadside inspector plugs into during a DOT check. Access is read-only. The device listens to the 250 kbaud CAN stream and pulls the DEF-relevant parameters out of the aftertreatment broadcasts. It never injects a signal, alters the bus, or touches the dosing control logic itself.
That distinction matters more than it might seem. A truck’s warranty stays intact because nothing about the DEF system changes. No tank sensor gets installed. No fuel line gets cut. Standalone DEF-level products that require cutting into the supply line to fit an ultrasonic sensor solve the same problem in a far more invasive way, and usually need a shop visit to install. InGenious, by comparison, calibrates to a vehicle in minutes through the existing diagnostic port.
A quad-core processor inside InGenious parses the J1939 frames as they arrive, filters out the DEF-specific parameters, and pushes structured data to InRoute over 4G/LTE roughly every 10 to 30 seconds. When a truck rolls through a cellular dead zone on a rural stretch or an interstate gap, InGenious buffers the DEF readings locally instead of dropping them. The DEF level history stays intact even after hours off the grid.
From raw SPN data to InRoute alerts: What fleet managers see
A tank reading alone doesn’t tell the whole story. A truck sitting at 18 percent DEF that has been burning through it at twice the normal rate for the last three hours needs attention sooner than a truck at 10 percent that topped off four hours earlier. The current percentage is a snapshot; the trend behind it is what actually predicts what happens next, and InRoute is built to surface that trajectory alongside the raw number, not just the number alone.
Alert thresholds are configurable, and most fleet managers set the low-level warning somewhere between 10 and 15 percent. That alert fires well before the engine management system begins torque derate, which typically triggers around 5 percent on most Class 8 configurations. The gap between those two numbers, roughly 10 percentage points, is the actual service window the data creates.
A separate alert covers NOx efficiency. When SPN 3226 and 3227 show conversion efficiency slipping across multiple trips, InRoute flags it as SCR degradation, a different repair than a simple DEF top-off.
Routing matters too. A fleet manager sees aggregate DEF health across the whole roster. A dispatcher gets vehicle-specific low-DEF alerts timed against a route’s remaining stops. A driver sees the in-cab warning the moment a threshold gets crossed.
DEF data connected to predictive vehicle health monitoring
A sustained drop in NOx conversion efficiency, tracked through SPN 3226 and 3227, often shows up weeks before any fault code fires. A DTC reports something that has already broken. The SPN trend is closer to a warning about what’s about to happen.
This distinction shapes the alert itself. When InRoute sees normal DEF tank levels alongside declining NOx efficiency, it raises a catalyst inspection flag rather than a refill reminder, since a driver glancing at the dashboard would have no way to tell those two problems apart.
Connecting DEF signals to Intangles’ broade predictive vehicle health monitoring is where this pays off at fleet scale. One logistics fleet running DEF data through that same platform cut unexpected breakdown events by 75 percent, not by adding sensors, but by finally reading data the trucks had been generating the whole time. Results vary from fleet to fleet, but the underlying pattern holds: the data was always there.
OBDonUDS 2027: What the protocol shift means for DEF Monitoring
Starting with the 2027 model year, heavy-duty vehicles begin moving away from the SAE J1979 protocol that has handled OBD-II diagnostics since the mid-1990s, toward SAE J1979-2, known as OBDonUDS. CARB’s OBDonUDS guidance confirms the transition applies specifically to heavy-duty manufacturers currently certified under J1979, with a small subset of Volvo and Mack models and engine families already having made the switch early, starting with the 2024 model year.
For DEF monitoring, the practical change sits in the PID structure. Data that currently lives under J1979 Mode 0x01 parameters shifts to UDS service identifiers under the new standard. InGenious is being updated to read both protocols side by side, so a mixed fleet, older trucks on J1979 and newer 2027-model-year vehicles on OBDonUDS, still reports into the same InRoute dashboard without a gap.
Across every layer covered here, from the SPN broadcast to the InRoute alert to the coming protocol shift, the pattern stays the same: the truck was already telling the fleet what it needed to know. The only question was whether anything was set up to listen.
Intangles DEF monitoring solution is built on exactly that idea. InGenious reads every SPN and DTC covered in this blog through the vehicle’s existing diagnostic port, with no extra sensors, no tank modification, and no warranty impact, and InRoute turns that raw signal into alerts a fleet manager can act on before a derate instead of after one.
Discover how Intangles’ DEF monitoring solution brings this same visibility to your fleet and speak with our team today.
KNOW MORE
Frequently Asked Questions
How does DEF monitoring data reach a fleet telematics platform?
DEF monitoring data starts on the vehicle’s CAN bus, where the aftertreatment control module broadcasts tank level, dosing rate, and NOx readings continuously. A telematics device connected to the J1939 or OBD-II diagnostic port reads those parameters directly, without any additional wiring. The device then transmits that data over a cellular connection, typically every 10 to 30 seconds, so a fleet manager sees near-real-time DEF status on a dashboard instead of waiting on a driver report.
What is the difference between reading DEF data from J1939 and OBD-II?
J1939 is the protocol used on Class 7 and Class 8 heavy-duty trucks, reporting DEF and SCR data through Suspect Parameter Numbers such as SPN 1761 for tank level. OBD-II covers Class 3-6 medium-duty vehicles and reports the same category of information as diagnostic trouble codes, like P20EE or P2202. The two protocols use different data structures entirely, which is why a scan tool built for one usually can’t read the other.
Does Intangles require additional DEF tank sensors to monitor DEF levels?
No. Intangles’ DEF monitoring solution reads the SPNs and DTCs that a truck already broadcasts on its CAN bus, so no ultrasonic tank sensor or cut fuel line is required. InGenious connects through the existing 9-pin diagnostic port and pulls tank level, dosing rate, and NOx data directly from there. This keeps the vehicle’s warranty intact and gets a fleet running with a calibration that takes minutes rather than a shop visit.
What DEF-related alerts can InRoute generate from CAN bus data?
InRoute generates alerts for low DEF tank level, typically configurable between 10 and 15 percent, which fires before the engine’s torque derate threshold near 5 percent. It also flags abnormal DEF consumption rate deviations and declining SCR NOx efficiency, with the latter pointing to a catalyst issue rather than a simple refill. Alerts route differently depending on the recipient: fleet managers see aggregate fleet health, dispatchers get vehicle-specific warnings, and drivers get in-cab notifications the moment a threshold is crossed.
How does the OBDonUDS 2027 transition affect DEF monitoring for newer trucks?
Starting with the 2027 model year, heavy-duty vehicles begin transitioning from the SAE J1979 protocol to SAE J1979-2 (OBDonUDS), which changes how aftertreatment data is structured and accessed. Fleet monitoring platforms are being updated to support both the legacy J1979 protocol and the newer OBDonUDS standard, helping maintain uninterrupted DEF monitoring across mixed fleets. Fleets with a mix of older and newer vehicles may need to review their OBDonUDS migration strategy as the transition progresses.
We’re looking forward to meeting you