OBD2 & ABRP on Megane e-Tech
Hi.
I have a car Renault Mégane e-Tech.
I use a dongle OBD2 Vgate iCare Pro.
I can connect my phone with this dongle and use Car Scanner.
But I can not connect OBD dongle with ABRP. The Connexion is not possible at the step 3.
Please help or tell if another dongle can work.
Thanks.
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments25
ABRP User #2840152
Jul 6
I was referred to this existing report after my own report was closed as a duplicate/related issue. I would like to add my test results here, because my case seems similar but not fully identical.
The same OBDLink CX (latest firmware) works perfectly with my Renault Zoe ZE50. ABRP connects successfully, Step 3 ("Connect vehicle") succeeds, and live SoC is shown via the Bluetooth icon.
On my Renault Megane E-Tech EV60 (2023), however, the behaviour is completely different:
ABRP always fails at Step 3 ("Connect vehicle").
The OBDLink app can connect, but it only reads basic OBD data, such as vehicle speed and 12 V battery voltage.
It does not read EV-specific values such as HV battery SoC, battery temperature or power.
Car Scanner also cannot establish a working connection on this vehicle.
The same phone, the same OBDLink CX, and the same firmware work perfectly on the Zoe.
Therefore, I believe this is not just a Bluetooth or hardware problem. It seems that the Megane does not provide the EV-specific diagnostic data expected by ABRP, or there is an incompatibility with the diagnostic communication of the Megane E-Tech.
Additional information:
Renault Megane E-Tech EV60, 2023
Android
ABRP 7.12.x
OBDLink CX with latest firmware
Original Renault tow bar, factory option, installed before delivery in Germany
If you need debug logs or if there is a beta version with improved Megane support, I would be happy to test it.
Linda ABRP
Jun 12
Hi
It needs to be an OBD that uses BLE for example Vgate iCar Pro BLE 4.0. You can also find other OBDs here Choosing an OBD device
ABRP User #2757256
Jun 12
Vgate iCare Pro is alreadu BLE dongle. Just for information my Renault Megane e-tech is model 2022.
Linda ABRP
Jun 12
To help us figure out what happens we need you to send a bug report. First you need to enable the bug button in the settings. Go to the settings → Display & appearance and scroll all the way down.
The bug button will show on your screen. When the OBD is connected to your car and the car is in drive mode click at the button. Then let me know when you have done this.
ABRP User #2757256
Jun 12
Ok, it is done.
ABRP User #2757256
Jun 12
When I click on the debug button, I have this:
https://api.iternio.com/1/?eventlog_uuid=9aca95ba-6f24-43af-b561-08885b81ab3c
ABRP User #2757256
Jun 17
Please, can you help me?
Linda ABRP
Jun 17
Was the car turned on when you sent the bug report? We get NODATA from the report.
ABRP User #2757256
Jun 17
Yes, the car is turn on.
Linda ABRP
Jun 18
Does the OBD have the latest firmware? If it has then it’s probably something wrong with the OBD since we don’t get any data.
ABRP User #2757256
Jun 18
Yes, the OBD has the latest firmware.
The car is on. I just click on bug button again.
Linda ABRP
Jun 18
We can’t see anything more on that report. My colleague think it’s a problem with the OBD because have other users with the same car that gets data with an OBD.
ABRP User #2757256
Jun 18
I bought another OBD dongle Maclean MCE200 and I have the same issue with the same message at the step 3 of the connexion. So, it is not a problem of OBD.
ABRP User #2757256
Jun 20
ABRP User #2757256
Jun 20
Same issue with 2 different OBD dongle.
ABRP User #2757256
Jun 22
I have a car Renault Mégane e-Tech model 2022. I tried with 3 dongles: . Vgate icar Pro . Vgate Blinker MC+ . Maclean MCE200.
OBD dongles can connect with Car Scanner. But it fail with ABRP.
The email I am trying to login with is:
To: premium@abetterrouteplanner.com App version: 7.1.2 Build number: 5875 Platform: android
Linda ABRP
Jun 24
Can you send us the car scanner logs? In car scanner → settings → adapter → Export logs.
ABRP User #2757256
Jun 27
log.txt
152.9 KB• Text
Please check the file. Thanks
Linda ABRP
Jun 29
Thanks. I have sent it to my colleague.
ABRP User #2818963
Jun 28
As I have the same car, here is my contribution:
https://abrp.featurebase.app/p/obd2-and-abrp-on-megane-e-tech/comment/6a40ec90ec301b469e910fe0
ABRP User #2786391
Jun 23
•Merged request
•1 vote
Mégane e-tech . Obdlink cx.
Hello, I'm having trouble connecting my OBDLink CX in my Megane E-Tech to the ABRP application to retrieve live data. My OBDLink has been updated, but I'm stuck at the third step and can't find a solution.
Could you please help me?
Linda ABRP
Jun 16
Hi
To help us figure out what happens we need you to send a bug report. First you need to enable the bug button in the settings. Go to the settings → Display & appearance and scroll all the way down.
The bug button will show on your screen. When the OBD is connected to your car and the car is in drive mode click at the button. Then let me know when you have done this.
ABRP User #2818963
Jun 28
b64u-bG9nLnR4dA.txt
688.7 KB• Text
Hi, I also have a Renault Megane E-Tech from June 2022 and a VGate Vlinker MC+. I have the exact same problem as you. Step 1 and 2 are green but step 3 fails all the time. CarScanner works well through the Android (standard Bluetooth) connexion though. ABRP with the “IOS” connexion (= BLE) does not. My phone is Android 16. I removed all Bluetooth pairings, restart my phone multiple times and made sure that ABRP is always the first Bluetooth device to access my OBD dongle but step 3 never passes green.
10a7a6f0-9105-4210-9edf-e407fd1b7454
ABRP User #2223049
Sep 21
Did you ever get a response to this?
I have exactly the same problem - Cannot get Step 3 to pass
ABRP User #2840152
Jul 27
Additional observation:
If I run the native ABRP application on Android Automotive (using my phone as a Wi-Fi hotspot), Enode reports the correct SoC all the time.
If I start ABRP via Android Auto, the SoC immediately changes to 1%.
If both applications are running simultaneously, the displayed SoC continuously switches between:
Enode → correct SoC
Android Auto → 1%
This strongly suggests that the Android Auto implementation is overriding the correct Enode value with an incorrect Android Auto SoC value.