Have something to say?

Tell us how we can make ABRP even better for you! ⚡️

Awaiting Clarification

Custom stop-over charge -> reduces DCFC 🤔

As part of my trip have a Supercharger bringing us to 80% and then a stop-over at Miette, which we were supposed to arrive with 40% SOC before continuing our journey. Repro: I wanted to try the “covert waypoint to charging stop feature” and using the “until xx%” I converted the Miette stop-over into a charging stop by setting it to “5kW till 45% SOC” I was expecting it to suggest ~1hr of staying at this location. Instead, it showed 4+ hrs because it dramatically cut the prior supercharging stop down. This effectively doubled my trip duration. Side-note: I also saw that the total trip charge duration did not include the 4hrs which seems like a separate bug.

ABRP User #1774603 1 day ago

1

Battery/distance estimates always off, as much as 30%

This happens all the time regards of web/mobile/planning. Been on countless trips all of the UK, often have to add 30% to the arrival estimate. This is not a cold battery situation, been happening throughout Winter 2025, Spring and through until today. Take Thursday for example, travelled from Lincolnshire to Llandrindod Wells in Wales. I got to Tesla at Cannock, 'filled' up as instucted, told I would arrive at Evolt In LLandrindd Wells with 6% left, used to not believe any of it I arrived with over 30% left! This is not an isolated incident, happens every journey the 'arrive with' battery life constantly creeps upwards. What can I do about this? It was one of the central reasons why I signed up to ABRP in the first place because of the dongle/ABRP solution. Otherwise love it - but this kinda important problem!

Richard Lake 1 day ago

Awaiting Clarification

ABRP repeatedly routes through exit and entrance lanes without leaving the motorway

On several recent trips using ABRP Premium with CarPlay, the navigation repeatedly instructed me to take a motorway exit. Instead of actually leaving the motorway, the route continued on the parallel exit lane and then immediately merged back onto the same motorway via the entrance lane. These detours were unnecessary, as I effectively remained on the same motorway the entire time. Initially, I followed the instructions without questioning them, but after reviewing the route more closely on subsequent occasions, I noticed that this behaviour occurred multiple times and appears to be a routing bug. My assumption is that these locations often experience heavy traffic, and some drivers may use the exit and re-entry lanes as a shortcut to bypass congestion. However, this is only speculation on my part. I wanted to mention it in case it helps identify the cause of the routing behaviour.

ABRP User #38200 1 day ago

1

Awaiting Clarification

OBD/BLE support for Audi A6 Avant e-tron

Hello ABRP Support Team, I am contacting you regarding OBD/BLE live data support for my vehicle in A Better Routeplanner. I currently drive an Audi A6 Avant e-tron (2024 100kWh 428ch Quattro) and I am trying to connect it to ABRP using a Vgate vLinker MC+ BLE / Bluetooth OBD dongle on Android. I previously used the same vLinker MC+ dongle successfully with my former Audi e-tron, and ABRP was able to retrieve live data such as battery state of charge and remaining range reliably through OBD/BLE. With the Audi A6 Avant e-tron, however, I cannot get the OBD/BLE connection to work. Here is what I have observed: When I select an older Audi e-tron model in ABRP, the usual simple OBD/BLE connection menu appears, and I can attempt to connect to the vLinker dongle. When I select the Audi A6 Avant e-tron, the simple OBD/BLE connection flow does not appear. Instead, I only see advanced PID / OBD settings. This makes me think that the Audi A6 Avant e-tron may currently not have a complete or verified OBD/BLE profile in ABRP. I was initially using the beta version of ABRP, but I have left the beta program, uninstalled the beta app, and reinstalled the stable version from Google Play. The behavior is the same in the stable version. I also ran a PID test from the advanced OBD settings. The BLE connection to the vLinker appears to start correctly, but the PID/data command test fails. The relevant log is: connecting to E1:FF:F1:6F:C6:92 connected to E1:FF:F1:6F:C6:92 on vehicle 574071107599 start writing custom unverified init commands error writing init commands Error: could not get commands for type init from [object Object] audi:a6:24:95:avant start writing custom unverified data commands error writing data commands Error: not connected to any ble device {"name":"Error","message":"not connected to any ble device","stack":"Error: not connected to any ble device ..."} Could you please confirm whether OBD/BLE live data is currently supported for the Audi A6 Avant e-tron in ABRP? If it is supported, could you let me know the correct setup procedure and recommended settings, especially: whether protocol 6, protocol 7, or generic/auto should be used; whether the Vgate vLinker MC+ is expected to work with this vehicle; whether I should select a specific BLE device name such as vLinker MC-iOS / IOS-Vlink; whether there are known working PID settings for this vehicle. If it is not yet supported, could you tell me whether support is planned, or whether there are any community-provided or experimental PID profiles available for the Audi A6 Avant e-tron / PPE platform? I would be happy to provide additional logs, screenshots, or run further tests if that helps. Best regards, PL

ABRP User #839707 2 days ago

1

Awaiting Clarification

Unable to Use ABRP with Tesla Model Y (2023) in Web Browser and Send Destinations to Vehicle

Hello ABRP Support, I am experiencing a persistent issue with ABRP Premium on my Tesla Model Y Standard Range (2023). I have been using ABRP Premium successfully for approximately three years. However, for the past few months, the integration has become unreliable and is currently no longer working properly. The main issue is that I cannot send destinations from the ABRP app to my Tesla. In addition, the ABRP web interface is no longer functioning correctly with my vehicle connection. To troubleshoot the problem, I have already tried the following: Logging out and back into ABRP. Reinstalling the ABRP mobile application. Removing the vehicle and adding it again from scratch. Revoking and reauthorizing Tesla access. Clearing browser cache and website data. Restarting the Tesla vehicle. Testing from different browsers. Despite all these steps, the issue remains unresolved. Vehicle: Tesla Model Y Standard Range (2023) Subscription: ABRP Premium Could you please investigate this issue and advise on any additional troubleshooting steps or check whether there is a problem with my vehicle connection on your side? Thank you for your assistance. Best regards,

Florin Stancu 2 days ago

1