FMC003 (FW 04.02.00 Rev.602) – VW e-up!: DID 6 (HV Battery Charge Level) reads val:0 due to missing BMS ECU mapping in Profile File 1 (Ver: 5)

Environment & Device Details

  • Device: Teltonika FMC003
  • Firmware: 04.02.00.Rev.602 (Branch: E.OBDRefine_R.2)
  • Configurator: 1.8.25_E.OBDRefine_R.2
  • Vehicle: Volkswagen e-up! (Pure EV / BEV, Model Year 2021)
  • VIN Mask: WVWZZZAAZMDxxxxxx
  • Telemetry Server: Traccar (Codec 8 Extended, TCP)
  • Active OEM Profile (oeminfo):
    ReqErr:0 Err:0 St:5 File:1 VIN:WVWZZZAAZMDxxxxxx(by1) DIDs:28 Ver:5

Issue Description

On previous firmware versions (such as 03.29.00.Rev.358), the FMC003 reliably reported the High-Voltage Battery Charge Level (SoC %) via AVL ID 411 / Parameter 40580 while driving (e.g. valid values like 26%, 27%, 53% in incoming AVL packets).

Immediately following the update to firmware 04.02.00.Rev.602, AVL ID 411 is no longer transmitted in AVL records because the tracker internally reads a value of 0 (and Parameter 40011 is set to 0 / Don’t Send zeros).


Steps Already Taken (Referencing Related Topics)

I reviewed related community threads regarding EV OEM parameter issues on FW 04.02.00.Rev.602:

  1. Topic 19994 (Hyundai Kona EV):
    I followed the official recommendation provided by @Imran.S:
    • Configured Manual VIN mode via GPRS (setparam 40005:1;40003:WVWZZZAAZMDxxxxxx).
    • Switched vehicle ignition ON and executed oemreset while actively driving.
    • oeminfo confirmed successful manual VIN binding (by1) and state St:5 (Active Data Requesting, 0 errors).
  2. Topic 19706 (VW ID.3 / Škoda Enyaq MEB):
    While Topic 19706 describes EV parameters dropping only when stationary/charging, in my VW e-up! the High-Voltage Battery SoC (DID 6) fails to populate even during active driving.

Diagnostic Proof via obdoemdatasource:get

I executed live diagnostic queries while the vehicle was actively driving on the road to inspect ECU source mappings:

Parameter / DID Command Tracker Response Analysis
DID 1 (Odometer) obdoemdatasource:get:1 Sources: 1. val:0 2. val:92030 3. val:0 4. val:0 Source 2 correctly returns real vehicle mileage (~92,030 km).
DID 9 (HV Battery Temp) obdoemdatasource:get:9 Sources: 1. val:4294967258 2. val:13 Source 2 correctly returns real traction battery temp (13 °C, transmitted as AVL ID 1152).
DID 16 (HV Battery Voltage) obdoemdatasource:get:16 Sources: 1. val:3255 2. val:3253 Source 2 correctly returns real traction battery voltage (325.3 V).
DID 17 (HV Battery Current) obdoemdatasource:get:17 Sources: 1. val:4294967204 Live traction battery current measurement working (-9.2 A discharge).
DID 6 (HV Battery Charge Level) obdoemdatasource:get:6 Sources: 1. val:0 Only Source 1 is polled, which returns 0. Source 2 is completely absent!

When attempting to manually remap DID 6 to the working BMS ECU source via:
obdoemdatasource:set:6:2
The device rejects it with:
Failed to set OEM source for argument: 6
(because Source 2 was never populated into DID 6’s candidate source list during profile compilation).


Root Cause Analysis

All genuine high-voltage battery telemetry on the VW e-up! (Cell Temperature, Pack Voltage, Current) resides on Source 2 (the HV BMS ECU).

In Profile File: 1 (Ver: 5) on FW 04.02.00.Rev.602:

  • DIDs 9, 16, and 17 correctly discover and poll the BMS ECU (Source 2).
  • DID 6 (Battery Charge Level %), however, is erroneously restricted to querying only Source 1 (the default gateway/ECU), which answers with 0.

Questions & Request to Teltonika Team

  1. Could the Telematics / OEM profile development team please update OEM Profile File 1 (VW e-up!) on FOTA WEB so that DID 6 includes the BMS ECU (Source 2) in its query definitions?
  2. Is there an intermediate SMS/GPRS command, engineering command, or test profile available to force DID 6 to bind to Source 2?

Thank you very much for your support!

Update: Exact Root Cause Identified via .dmp Log Comparison (VER: 4 vs. VER: 5)

By comparing the internal [OBD.OEM] dump logs from the exact same vehicle (Volkswagen;up!;2021;vw_up_aa) captured under FW 03.29.00.Rev.358 (VER: 4) right before the update against FW 04.02.00.Rev.602 (VER: 5), I found the exact regression in the compiled OEM database (DB source: 0, Total OEM DIDs: 28):

When the vw_up_aa profile was updated from VER: 4 (GenTime: 1702684338) to VER: 5 (GenTime: 1793864948) (to add the Altelium HV battery health entries Entry ID: 1691–1699), three working EV entries (Entry ID: 1001, 998, and 997) were accidentally deleted from the profile:

Parameter / Function Internal DID Working in VER: 4 (03.29.00.Rev.358) Broken/Removed in VER: 5 (04.02.00.Rev.602)
OEM Battery Charge Level (SoC %)
(AVL ID 411 / Param 40580)
DID: 0x128 Entry ID: 944 (Valid: 0, Val: 0)
:white_check_mark: Entry ID: 1001 (Prot: 2/0, ECU 7E5/7ED, UDS 22028C $\rightarrow$ 62 02 8C XX, formula raw * 0.4, Valid: 1, Res: 1, Val: 53)
Only Entry ID: 944 (Valid: 0, Val: 0) remains.
:cross_mark: Entry ID: 1001 was completely removed!
OEM Remaining Distance (km)
(AVL ID 755 / Param 40520)
DID: 0x108 Entry ID: 945 (Val: 0), Entry ID: 996 (Val: 0)
:white_check_mark: Entry ID: 998 (Prot: 2/0, ECU 714/77E, UDS 2222E0 $\rightarrow$ 62 22 E0 XX XX, Valid: 1, Res: 1, Val: 125)
Entry ID: 945 + new Entry ID: 2051 & 2053 (all fail with Valid: 0, Res: -5, Val: 0).
:cross_mark: Entry ID: 998 was removed!
OEM Battery Charge State
(AVL ID 410 / Param 40570)
DID: 0x129 :white_check_mark: Entry ID: 997 (Prot: 2/0, ECU 714/77E, UDS 2222E3 $\rightarrow$ 62 22 E3 00 82, Valid: 1, Res: 1, Val: 0) :cross_mark: Entry ID: 997 was completely removed!

Dump Excerpt from VER: 4 (03.29.00.Rev.358 – Working):

[OBD.OEM] Vehicle data:
	VER:4
	DB source: 0 (0)
	Description: volkswagen;up!;2021;vw_up_aa,vw_up_aa
	GenTime: 1702684338
[OBD.OEM] Total OEM DIDs:28
	6:  Entry ID: 944,  DID: 0x128, Valid: 0, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 0, Val:0   IO: 0x35(53)
	7:  Entry ID: 945,  DID: 0x108, Valid: 0, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 0, Val:0   IO: 0x7D(125)
	9:  Entry ID: 996,  DID: 0x108, Valid: 0, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 0, Val:0   IO: 0x7D(125)
	10: Entry ID: 997,  DID: 0x129, Valid: 1, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 1, Val:0   IO: 0x0(0)
	11: Entry ID: 998,  DID: 0x108, Valid: 1, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 1, Val:125 IO: 0x7D(125)
	13: Entry ID: 1001, DID: 0x128, Valid: 1, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 1, Val:53  IO: 0x35(53)

Dump Excerpt from VER: 5 (04.02.00.Rev.602 – Broken):

[OBD.OEM] Vehicle data:
	VER:5
	DB source: 0 (0)
	Description: Volkswagen;up!;2021;vw_up_aa,vw_up_aa
	GenTime: 1793864948
[OBD.OEM] Total OEM DIDs:28
	4:  Entry ID: 944,  DID: 0x128, Valid: 0, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 1,  Val:0 IO: 0x0(0)
	5:  Entry ID: 945,  DID: 0x108, Valid: 0, Fail Cnt: 0, Valid State: 0, Prot:2/0, Res: 1,  Val:0 IO: 0x0(0)
	26: Entry ID: 2051, DID: 0x108, Valid: 0, Fail Cnt: 1, Valid State: 0, Prot:2/1, Res: -5, Val:0 IO: 0x0(0)
	27: Entry ID: 2053, DID: 0x108, Valid: 0, Fail Cnt: 1, Valid State: 0, Prot:2/0, Res: -5, Val:0 IO: 0x0(0)

Meanwhile, the new Altelium entries on 0x7E5 / 0x7ED in VER: 5 do work when enabled via setparam:

  • Entry ID: 1696 / 1699 (PID 22 1E 3B / 22 1E 3C → AVL ID 1381, Param 505150): returns valid HV pack voltage (3217 = 321.7 V)
  • Entry ID: 1695 (PID 22 1E 3D → AVL ID 1380, Param 505140): returns valid HV pack current (65521 = -1.5 A)
  • Entry ID: 1698 & 1697 (PID 22 1E 34 / 22 1E 33 → AVL ID 1378 / 1379, Params 505120 / 505130): return valid min/max cell voltages (380 = 3.80 V, 383 = 3.83 V)

Requested Fix for the Vehicle Database Team

Please restore Entry ID: 1001 (DID: 0x128), Entry ID: 998 (DID: 0x108), and Entry ID: 997 (DID: 0x129) into the Volkswagen;up!;2021;vw_up_aa profile in the next OEM database revision (VER: 6) alongside the 1691–1699 entries.

Hi @Imran.S,

Could you or someone from the Telematics / Vehicle Database team please take a look at the findings in post #2 above?

The exact regression between VER: 4 and VER: 5 is clearly identified: restoring Entry IDs 1001 (SoC % via UDS 22028C), 998 (Remaining Range), and 997 in the vw_up_aa profile for the next database revision (VER: 6) will completely resolve the issue for all VW e-up! users on FW 04.02.

Thank you very much for your help!