Join our newly restarted iOS Beta and try out new features sooner: https://testflight.apple.com/join/PDzBYbJw
Read more about ABRP beta at Installing the ABRP Beta version
Tell us how we can make ABRP even better for you! ⚡️
Completed
ODB Compatibility Question 2025 Genesis GV70
Does ABRP support OBD live battery data for the U.S.-market 2025 Genesis Electrified GV70, using the OBDLink CX? The Genesis profile only shows the option for a Tri Motor AWD, so I checked the Hyundai IONIQ 5 instead which is built with similar hardware. Can I use its OBD profile, or does the GV70 require different PIDs?
Awaiting Clarification
Subject: Toyota Proace City Verso Electric 2025 – OBD PID compatibility and safety issue
Subject: Toyota Proace City Verso Electric 2025 – OBD PID compatibility and safety issue Hello ABRP Support Team, I own a 2025 Toyota Proace City Verso Electric with a 50 kWh battery. I would like to connect my vehicle to ABRP to automatically retrieve the battery State of Charge (SOC). I previously attempted to use an OBDLink MX+ adapter, but the vehicle experienced serious issues when the OBD connection became active: Loss of READY mode Vehicle electronics restarting or shutting down Collision prevention system warnings Other dashboard errors The problems disappeared after disconnecting the OBD adapter. I also attempted to connect through Enode using MyToyota, but no vehicles were found. Could you please confirm: Is my exact 2025 vehicle model officially supported by ABRP via OBD? Which ECU addresses, OBD commands and PIDs are verified for this vehicle? Is there a known issue involving ECU resets or loss of READY mode on Stellantis K9-based electric vehicles? Is there a confirmed safe configuration for reading SOC? Is there a way to read SOC passively without sending diagnostic requests? I do not want to reconnect the OBD adapter until the safety issue has been investigated. Thank you for your assistance.
Awaiting Clarification
Live data SOC switches between source with differing values, affecting route planning
So my car (Peugeot e-5008) shows a tampered SOC on the dashboard and in Android Auto. I know it is “corrected” to provide some sort of user experience improvement, because I can read the actual SOC using my OBD reader. At full charge, the SOC reported by OBD is between 90 and 97% (depending on temperature), while the dashboard always shows 100% at full charge. As I start a trip, the SOC from the OBD decreases as expected while the dashboard SOC stays at 100 for an unrealistically long time, until it suddenly decreases to sort of match the OBD SOC. I say sort of matches, since there is almost always a difference between the two values, of up to 5%. The difference depends on temperature and the SOC ( the difference is least around 50% SOC), and it can be both positive and negative. My Abrp live data streams data from CarScanner, which reads the OBD SOC. Sometimes it also reads from Android Auto. Because the two values often differ, ABRP thinks the SOC switches back and forth, which negatively influences the route planning while driving. Sometimes a new route is suggested because of this. I suggest to provide an option to block specific data streams (like Android Auto SOC) if a more reliable source is available (like OBD SOC).
Completed
Fisker Ocean Live Data
Please support the Fisker Ocean with these PIDs (FO_CustomPID.json). They have been tested and verified via the OBDII port, covering key live telemetry.
Custom Local Telemetry Provider (HTTP/MQTT)
Feature Request: Custom Local Telemetry Provider (HTTP/MQTT) Description Allow ABRP to retrieve live vehicle telemetry directly from a configurable local HTTP endpoint or MQTT broker, without requiring telemetry to be uploaded to ABRP's cloud servers. Use Case Some vehicles, particularly BYD models running Android, already have applications capable of reading vehicle telemetry locally. For example, BYD Trip Stats provides: A local HTTP server (Web Companion). MQTT telemetry publishing. Real-time vehicle data, including SoC, speed, power consumption, and GPS. Currently, integrating this data with ABRP requires sending telemetry through the cloud API, even when both applications are running on the same Android device. Proposed Solution Add a Custom Local Telemetry Provider supporting: HTTP: Configurable endpoint (e.g., http://127.0.0.1:8888/api/telemetry). MQTT: Configurable broker address and topic. Configurable polling intervals. JSON field mapping for SoC, speed, power, GPS, etc. Optional authentication. Benefits No mobile data required for live telemetry. Lower latency. Better privacy by keeping vehicle telemetry local. Compatibility with existing telemetry applications. Support for offline telemetry when Internet connectivity is unavailable. This would make ABR
Completed
How to get live data as quest user in VW Id.3
Hi I'm a premium user of ABRP, but I can't figure out how to get live data via enode working as a quest user in my VW Id.3. It's only possible to have 1 primary user on the VW. I'm on Android 15 and got the newest version of ABRP 7.1.8
Completed
Deepal S05 add SOH and EFC
Please look into the info provided by me at https://github.com/jpires71/Deepal_S05_PIDs/blob/main/README.md and improve the live data adding more accurate SOH and EFC for this model and eventually for others too when possible.
Completed
Volvo EX60 data
This weekend we got our 2027 Volvo EX 60. I’ve been a user of ABRP for six or seven years. I’m familiar with the interface and yet must be missing something. I am not getting love data through the android system in the Volvo (with ABRP installed from Play store), nor am I getting the option in the app to use Encode. Please advise on either approach to getting live data. Thank you!
VW transporter ABTe 2021
Would like android auto or odb live data connection. It was available about 3 months ago but there is no longer any way to connect to the app.
Completed
2026 Trailseeker Touring - OBD support
Awaiting live data tailored to my 2026 Trailseeker Touring. Currently using Solterra as a workaround, which is close-ish. But they are different vehicles. To clarify, I understand that I can identify the vehicle, but in Live Data options I only see Enode and Generic as a Trailseeker. I have to set it to Solterra to see the ABRP Live Data options.
OBD Support for Cupra Raval Endurance with OBDLink CX
I have this vehicle model configured based on manufacturer data: https://abetterrouteplanner.com/home/app/vehicles/import/01a09b42-ae0c-78cd-89ca-31f6711400df I purchased a OBDLink CX with the expectation that I could just simply link it via ABRP (similar to what is possible with the Cupra Born). I only have the options Encode, Car Scanner and Generic. What is the correct way to configure this and what is necessary to have the Raval show the OBD Connection mode?
Awaiting Clarification
Add the Support for soc and range from the new Škoda b2c api
Allow users to integrate with škoda b2c api for soc and range
OBD/BLE live data support for 2026 Mercedes-Benz GLB 200+
Hello, I own a 2026 Mercedes-Benz GLB 200+ Electric, based on the new 800V platform. The vehicle model is already available in ABRP, but under Live Data the only available option is “Generic”. There is currently no ABRP OBD connection option. I have a Vgate iCar Pro 2S v2.3 Bluetooth 5.2 BLE adapter which worked successfully with ABRP in my previous BMW iX1. Could you please add OBD/BLE live data support for the 2026 GLB 200+? I would be happy to help test the integration and provide diagnostic/PID data from the vehicle if needed. The most useful parameters would be: Battery SoC BMS SoC Battery temperature Battery voltage/current Charging power DC charging status Vehicle speed Consumption Thank you.
Enode doesn't work in Brazil
You need to set the “Brazil” option in enode to integrate with the BYD app