Skip to main content

Volkswagen ID.4 Enode ref consumption off

Bug Reports

Have been having consistent issues with live ref consumption. Post multiple consumption resets and re- logging into Enode with little resolve. Best I can tell, any time I swap vehicles in ABRP it will disrupt the data somewhere. Default ref consumption is around 3.4 mi/kWh for the vehicle, Enode has been showing 2.0 to 2.2 mi/kWh with massive real world disparities on the most familiar drives, such consumption mimics a full size AWD EV pick-up truck.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Zim ·
Status: Awaiting Clarification4 comments

Log in to comment and vote

Comments4

  • Katya S. changed status to Awaiting Clarification
    Team•

    Feb 10, 2025

    Pinned

    Hi @Zim,

    Your current calibrated ref cons for your ID.4 is 3.18 mi/kWh, did you just reset it?

    • Zim

      •

      Feb 10, 2025

      Yes, I did reset it recently. Default was 3.4 dropped down slightly with a few drives.

      I can attempt to recreate the issue (swapping vehicles) and leave it alone the next time I have the car for a few days. Vehicle swapping is the only association I can observe leading to the issue.

    • Zim

      •

      Mar 20, 2025

      Update 2.0 (5.7.1 version)

      So, I'm completely at a loss with what to expect with this calibrated ref consumption. My previous update was at 2.84 mi/kWh ref. Now updated to 2.82 mi/kWh.

      Under fair weather planning (dry roads, light winds and moderate temps) I'm finding a manual input of 3.3 will lead to an accurate route planning solution. However, with less ideal conditions (rain, wet roads, winds and cooler temperatures) the semi calibrated ref consumption will return a more reliable solution. Im comparing real world arrival levels to both the internal vehicle nav and ABRP (calibrated & manual ref).

      I guess my question is, when can we expect the calibration to complete? Will the software require snapshots throughout the year using various seasons weather conditions to complete? Because all I'm witnessing currently is a continuous reduction in ref consumption leading to fairly pessimistic solutions in fair conditions. I hate to admit it, but as of this writing, the vehicles own route planning has been more accurate over ABRP.

  • Zim

    •

    Mar 18, 2025

    Update: I haven't noticed any erroneous ref consumption changes (lately) with swapping vehicles within the app. However, current calibration is approaching 50% returning approximately 2.8* mi/kWh, a figure which has been consistently pessimistic with real world driving (approximately a 5% SOC Delta ABRP vs reality). A manual 3.3 mi/kWh has been more consistent.

    BMS Observation: The 22 PRO S AWD ID4 appears to work in a buffer approaching a lower SOC. Displayed SOC will begin to fall rapidly towards the end while the BMS SOC remains steady. I'm curious if Enode references this sudden displayed SOC drop to calculate higher consumption. Unfortunately, for ABRP live data route planning, well within the middle of the pack, the application will use the pessimistic Enode observed data to calculate a pessimistic arrival figure (for trips ending within the middle of the pack or a good amount above 0%)

    If ABRP can only reference DISPLAYED SOC to calibrate a reference consumption figure, then that data will consistently be in error given the non linear trend of the displayed figure. Is it possible to use vehicle BMS SOC figures to derive a more realistic calibrated ref figure?