Commercial J1939 (truck/bus)

SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-25

⚡ At a glance

SPN	5246 (Aftertreatment 1 Diesel Exhaust Fluid Tank Level)
FMI	2 (Data erratic, intermittent, or incorrect)
Vehicle	BharatBenz (commercial diesel)
Protocol	SAE J1939
Standard connector	9-pin Deutsch (green for J1939)

What is SPN 5246 FMI 2 on a BharatBenz?

Real-world context. Budget honestly for ~Rs 1,500 to Rs 30,000 INR for parts plus labour (around $18 to $360 USD), because the cheap path looks tempting until a part shows up wrong. You will burn ~30 to 120 minutes hands-on hands-on and roughly ~half a day including a road test once verification is done. Before you touch anything, line up an OBD-II scanner, the service manual, and a torque wrench — those three are what saves you when the first attempt does not stick.

SPN 5246 (Aftertreatment 1 Diesel Exhaust Fluid Tank Level) with FMI 2 (Data erratic, intermittent, or incorrect) is a J1939 diagnostic trouble code on your BharatBenz. BharatBenz trucks use Daimler's Truck Tool diagnostic platform. SPN/FMI codes follow standard J1939.

The SAE J1939 standard is used across all commercial diesel vehicles in India — trucks, buses, tractors, gensets. because it allows the same scanner to talk to engines from any manufacturer (Cummins, FPT, John Deere, BharatBenz, Tata DI). The 9-pin Deutsch connector (green plastic = 250 kbps J1939) is the standard diagnostic port.

When does SPN 5246 FMI 2 appear?

The ECM sets this code when the parameter monitored by SPN 5246 exceeds the threshold described by FMI 2. For aftertreatment 1 diesel exhaust fluid tank level with data erratic, intermittent, or incorrect, the most common real-world triggers are:

Failure of the sensor measuring aftertreatment 1 diesel exhaust fluid tank level
Wiring fault (open / short / chafed) between the sensor and the ECM
The actual underlying mechanical or fluid condition reported (e.g. truly low oil pressure for SPN 100)
Sensor connector corrosion (very common in monsoon / wash-down environments)
ECM software / calibration issue

In Indian commercial-vehicle fleets, fuel quality variation and dust ingress are leading causes of sensor failures.

Signal review

You need a J1939 scanner

Generic OBD-II tools (ELM327) will not read J1939, the protocol and connector are different. You need:

NEXIQ USB-Link 2 / 3 (industry standard, ~₹45,000)
JPRO Commercial Vehicle Diagnostics (US import, ~₹85,000)
Bosch ESI[truck] (₹65,000+)
Or the BharatBenz dealer scanner

# Connection
# 1. Locate the 9-pin Deutsch diagnostic connector
#    - Usually in the dash, under the steering column, or near the driver seat
#    - Green plastic = J1939 (250 kbps); black = J1708 (legacy)
# 2. Connect the scanner adapter
# 3. Power up the ignition (no need to crank)

# Reading the code
# - Pull active + previously-active DTCs from every ECU on the bus
#   (engine ECM, transmission TCM, aftertreatment ACM, brake ABS, instrument)
# - For each: note SPN, FMI, occurrence count, first/last seen
# - Pull freeze-frame data for SPN 5246

# Live data essentials
# - SPN 190 (RPM)
# - SPN 100 (oil pressure)
# - SPN 110 (coolant temp)
# - SPN 102 (boost)
# - SPN 1569 (engine protection torque derate)

How to fix SPN 5246 FMI 2 on BharatBenz

Confirm the fault is real. FMI 2 indicates data erratic, intermittent, or incorrect. Verify with a multimeter or pressure gauge on the actual sensor before replacing.
Inspect wiring + connector. Most J1939 sensor faults trace to corroded Deutsch connector pins: clean with electrical contact cleaner.
Check the upstream condition. If SPN 5246 is reporting an out-of-range condition for a real reason (low oil, overheat, etc.), fix the root cause, not the sensor.
Replace the sensor if testing confirms it has failed. OEM sensors via BharatBenz parts; aftermarket Bosch / Continental / Stemco may be acceptable for non-emissions sensors.
Clear the DTC with the scanner.
Road test or PTO test to verify the code does not return.

Common-cause table by FMI

FMI	Likely fix
0	Address the actual high reading (overpressure, overtemp). Don't blame the sensor first.
1	Address the actual low reading. Don't blame the sensor first.
2	Sensor signal erratic, likely a chafed wire or bad ground.
3	Open circuit or short to +12V. check wiring back to the ECM.
4	Short to ground, check wiring; sensor is often still good.
5	Open circuit: connector unplugged or wire broken.
16 / 18	Moderate severity over-/under-range, recalibrate or replace the sensor.

Costs in India (commercial-vehicle market)

Item	Approx. cost (₹)
J1939 scanner rental (per day, Bangalore/Pune)	1,500–4,000
Sensor (oil press, boost, NOx, DPF)	2,500–35,000 depending on type
OEM ECM (rare to replace; usually re-flashable)	65,000+ + coding
BharatBenz authorised service rate per hour	800–1,800

If you cannot fix it now

J1939 codes related to engine protection (SPN 1569) will trigger torque derate or engine shutdown. you may not be able to drive far. Fleet vehicles should be towed to avoid further damage.

Non-critical codes (e.g. SPN 411 EGR diff pressure, FMI 2) usually let the vehicle keep running with reduced emissions performance.

Repair sequence

Clear the active DTC with the scanner (not just reset the cluster).
Start the engine and let it reach operating temperature.
Run the OBD readiness monitors if your BharatBenz supports them.
For aftertreatment codes, run a DPF regen or SCR system check via the scanner if available.
Test drive (or stationary PTO load test) for at least 30 minutes.
Re-scan. The DTC should remain cleared.

Frequently asked questions

Can I use a generic OBD-II scanner for SPN 5246 on my BharatBenz?

No. Commercial vehicles use J1939, not OBD-II. You need a J1939-capable scanner with a 9-pin Deutsch cable.

Will SPN 5246 cause torque derate or engine shutdown?

Depends on the FMI. FMI 0 / 1 on critical SPNs (oil pressure, coolant temp, exhaust temp) typically derates torque and may shut down the engine if the condition persists.

How is SPN 5246 different from a P-code?

SAE J2012 P-codes are the passenger-car / light-vehicle OBD-II standard. SAE J1939 SPNs are the commercial / heavy-duty equivalent. They cover similar systems but use different numbering and protocols.

Do BS6 trucks have J1939?

Yes, plus additional ISO 14229 (UDS) for the aftertreatment system. BharatBenz / Volvo-Eicher / Tata BS6 trucks all use J1939 over a 9-pin Deutsch.

See more J1939 SPN/FMI codes at the BharatBenz commercial vehicle index
For passenger-car (P-code) faults, see the P-code guide

References

SAE J1939 (Heavy-Duty Vehicle Network)
SAE J1939-71 (Vehicle Application Layer)
BharatBenz service manual / dealer portal
BS6 emission standards (CMVR, India)

Reference material, not professional advice. J1939 work on commercial vehicles often requires manufacturer-specific calibrations, when in doubt, visit a BharatBenz authorised service centre.

Field notes from real incidents on BharatBenz (commercial diesel)

When I work on SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. Freeze frame data is the cheapest forensic record on a modern vehicle: capture it before you clear, every time. A wiring diagram and a meter answer 90% of intermittent electrical complaints; the parts cannon answers none of them.

Mode 06 is the most underused OBD-II surface; the monitor pass/fail status tells you what the ECU itself believes about the system, not what the test bench believes. Most no-start diagnostics resolve at the basics, compression, spark, fuel, in that order. not at the scan tool screen.

Tools I actually reach for

For SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix on BharatBenz (commercial diesel) the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with manufacturer wiring diagram and service procedure because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to OBD-II scanner with mode 06 access (live data + freeze frame), bidirectional scan tool for active tests (Autel, Snap-on, Launch), oscilloscope for sensor signal analysis (Picoscope or Snap-on Vantage), multimeter with min/max recording for intermittents, and finally to manufacturer factory scan tool (where available) only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on BharatBenz (commercial diesel) units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.

Verification I run before I close the ticket

Before I mark SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix resolved on a BharatBenz (commercial diesel) unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.

Mode 06 monitor status, confirm the monitor for the affected system has run and passed

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Capture freeze frame for the active DTC before you clear anything

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Read all DTCs across all modules, not just engine; the originating fault often lives in body or chassis

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.

Where I check first when the docs disagree

When two sources contradict each other on a BharatBenz (commercial diesel) detail, the disambiguation order I lean on is stable across products and across years. Identifix or Mitchell1 service bulletins is where I start for the ground-truth view. manufacturer service information portal (Ford Workshop, Mitchell1, AllData, Autodata) is where I start for the ground-truth view. manufacturer technical service bulletins (TSBs) is where I start for the ground-truth view. iATN (International Automotive Technicians Network) is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix have a habit of biting back. The pitfalls below are the ones I have personally walked into on a BharatBenz (commercial diesel) unit, not things I read about. A wiring diagram and a meter answer 90% of intermittent electrical complaints; the parts cannon answers none of them. Reading a DTC and replacing the named component is how parts cannons get built; the DTC names the circuit, not the failed part. Mode 06 is the most underused OBD-II surface; the monitor pass/fail status tells you what the ECU itself believes about the system, not what the test bench believes. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on BharatBenz (commercial diesel) - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For SPN 5246 FMI 2 on BharatBenz: Truck/Bus Fault & Fix on a BharatBenz (commercial diesel) unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.

Related guides worth a look while you sort this one out: