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:
- 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
oemresetwhile actively driving. oeminfoconfirmed successful manual VIN binding (by1) and stateSt:5(Active Data Requesting, 0 errors).
- Configured Manual VIN mode via GPRS (
- 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
- 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?
- 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!