Skip to main content

XPeng G6 odometer not updating via Enode on Premium

Bug Reports

I have subscribed to ABRP Premium and connected my XPeng G6 to the XPeng Cloud via Enode.

However, the odometer value is not updating. ABRP currently shows 5,303 km, while the car actually has 5,396 km, which is also the correct mileage currently displayed in the XPeng app.

The odometer value in ABRP seems to remain stuck at 5,303 km and does not change even after driving the car.

I have also noticed that the vehicle data takes a very long time to update in ABRP.

Could you please check whether there is an issue with the Enode integration for the XPeng G6?

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

Log in to comment and vote

Comments2

  • Nikola changed status to Awaiting Clarification
    Team•

    Aug 11

    Pinned

    Hello @Jouking,

    Can you try unlinking and linking again to Enode and check if that fixes it?

  • Jouking

    •

    Aug 11

    Hello,

    I have tried unlinking Enode and linking it again, but unfortunately the issue is still the same.

    I’m attaching screenshots showing:

    ● Enode being unlinked.

    ● Enode being linked again.

    ● ABRP showing that the vehicle is online and connected via Enode.

    As you can see in the ABRP screenshot, the connection with Enode is working and the SoC is being reported correctly. However, the odometer value is still incorrect and does not update to match the actual mileage shown by the vehicle/Xpeng app.

    So it seems that ABRP is receiving live vehicle data from Enode, including the correct SoC, but the odometer data is either not being received or not being updated.

    Please let me know if you need any additional information or screenshots from my side to investigate this.

    Thank you.