Skip to main content

Read error of OBD information on VW ID4

Questions
Hi! I have purchased recently an OBD BLE adapter (a model recommended on your site - Veepeak OBDCheck BLE+) and ABRP is connecting to it, nevertheless there is a deviation of 1-2% between what ABRP reports and what the car displays or the OBD application (in the sense that ABRP is always reporting 1-2% on top of what car or the OBD plug app are reporting (e.g. the car displays 74% battery, OBD app, 74,4% and ABRP displays 76% on the phone and on car‘s display). As a result of that ABRP estimated SoC at destination is also 2% off the reality. Is there a fix available?
Posted by ABRP User #1112419 ·
Status: Awaiting Clarification6 comments

Log in to comment and vote

Comments6

  • Katya S.

    Team•

    Jan 27, 2025

    Hi @florin.deaconu,

    I’m confused, while we do not officially recommend ANY device this is the only model we do NOT recommend, see;

    https://www.iternio.com/abrp-obd

    • ABRP User #1112419

      •

      Jan 27, 2025

      Sorry, I was referring to the second OBD plug on your list (on the page you mentioned, there are 4 bullets). Also, if you do not support OBD-based connectivity, why is your app supports it?

      The car is a VW ID4.

      Best regards,

      Florin Deaconu

      • Katya S.

        Team•

        Jan 27, 2025

        Ok, you mean the Vgate vLinker MC+ instead?

        Could you clarify what you mean by us not supporting OBD connectivity?

        The ID.4 is supported for linking via OBD as we list here;

        https://abetterrouteplanner.com/compare/livedata/

        You mention; “the car displays 74% battery, OBD app, 74,4%”
        This is an acceptable difference, the can may round off the value differently.

        • ABRP User #1112419

          •

          Jan 27, 2025

          So, the situation is like this: ID4 shows that I have 74% battery left, the Car Scanner app, tells me that there is 74.4% battery left (which perfectly fine), but ABRP shows on the map navigation screen that I have 76% percent battery left and when planning the trip, it will use that 76% as a reference to calculate the SoC at destination. Since ABRP is linked with the OBD, and the OBD‘s app displays the correct battery SoC, I am wondering what is preventing ABRP to also display and use the correct SoC values.

          • Katya S.

            Team•

            Jan 27, 2025

            Looking at your vehicle it is linked via both OBD and Enode. But you shouldn’t be able to keep a connection to both CarScanner and ABRP active at the same time.

            Thus I suspect that Enode / the VW API provides a slightly outdated value, and the ABRP OBD connection isn’t actually active, since CarScanner is using the OBD connection.

            • ABRP User #1112419

              •

              Jan 27, 2025

              There is no simultaneous connection to both ABRP and Car Scanner: I have installed and connected only once to Car Scanner app only to check where is the source of false information in ABRP. The conclusion is that the OBD plug delivers correct information, very much aligned with what the car displays. On the other hand, ABRP is „creative“ with the information.