Implementation of BLE Live Data for Smart #1 and #3
🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/obd-requests/implement-ble-live-data-for-smart-1/
———————————————————————————
It would be nice if ABRP can implement a BLE live data connection for all Smart #1 and #3 car models.
The CarScanner App with database 1.105.7 is already able to read live data from the CANBus of Smart #1 and #3 cars (and Volvo EX30) via BLE.
Therefore I think it would be possible for ABRP to use the informations out of the CarScanner profile for Smart #1/Volvo EX30 and implement it into the ABRP app.
The available Smart model variants are:
47kWh useable LFP battery, RWD:
1 Pro, #3 Pro
62kWh useable NCM battery, RWD:
1 Pro+, #3 Pro+
62kWh useable NCM battery, RWD, Silizium-Carbid inverter:
1 Premium, #3 Premium
62kWh useable NCM battery, AWD, Silizium-Carbid inverter:
1 Pulse, #1 Brabus, #3 Brabus
Please note that #3 has significantly lower air resistance than #1.
All Smart #1 and #3 owners would be very grateful for that!
Log in to comment and vote
Comments8
ABRP User #6560
Feb 28
At the beginning of the month, I was able to add the SOH to the HV battery temperature in the ABRP OBD configuration, so that the degradation of the HV battery can now also be read via the BLE dongle on #1 and #3.
On my #1, the SOH is 99.28%, which means a rounded 0.7% degradation.
So if you haven't re-established the BLE connection since February 18, 2026, and therefore haven't received the new OBD configuration with the degradation displayed, you should now delete the ABRP BLE connection and re-establish it. After that, the degradation of the HV battery will also be displayed and used by ABRP.
To all Smart #1 and #3 users: Please try out the new OBD configuration.
Feedback on how it works is welcome.
ABRP User #6560
Apr 21, 2025
I have now driven twice for half an hour with iOS ABRP V5.7.4 (3338), logged the outward journey with the vGate VLinker MC+ BLE dongle and the return journey with the Veepeak OBDCheck BLE+.
Both times, the Bluetooth dongles were immediately connected successfully and then provided new data every 10 seconds.
Many thanks to ABRP and the user RiotCop from the Smart 1 forum, who has provided ABRP Support with several bug reports for troubleshooting in recent weeks.
ABRP User #6560
Apr 18, 2025
Today, more or less by chance, I tried the OBD connection with the latest iOS ABRP V5.7.4 and my Veepeak OBDCheck BLE+ dongle and linked it again.
The first thing I noticed was that the screen now displays the ODB values read out when the OBD dongle is successfully linked.
With my Smart #1 with SmartOS 1.5.2 and ABRP 5.7.4 and the Veepeak OBDCheck BLE+ dongle, I now get new OBD values every 10 seconds for the first time. The test function of the PIDs in the PID Editor now also works successfully every time.
Does the OBD connection now also work for you with the latest ABRP version 5.7.4 if you delete the old OBD link and reconnect it?
Tomorrow I'll go for a long drive and see if it's a coincidence or if the OBD connection (at least in my configuration) actually works immediately and permanently.
Marcus Krämer
Jan 21, 2025
If along with a OBD connection within ABRP there is also a connection to the Hello# app, then the priority of the two data sources is wrong: Hello# seems to have a higher priority than the local OBD connection. This results in ABRP always showing lagging data (higher battery SoC) or worse of all if Hello# is not sending updates it might even stay stuck with a very old battery SoC. And the live OBD data is ignored
ABRP User #6560
Nov 6, 2024
Based on the post here, in which it was written that the OBD initiation sequence was adapted (ATST64 was replaced by ATSTFF) and then it worked, I have linked the ABRP BLE Live connection again and now also have the changed initiation sequence.
At first I only got read write connected read write connected a few times until I only got write connected write connected.
But strangely enough, after a while it got through and then read out the data.
Unfortunately, after I restart ABRP (with VLinker MC+ and iOS), it stutters with the new parameter just as it did before with the original one and then stops reading. Too bad.
Who of you voters has set up the OBD BLE link again and can report positive or unchanged effects?
Stephan Sickert
Dec 4, 2024
I have the same issue even after setting up the BLE connection again (and again). No data is read from the car (but ABRP says, it's connected!).