Jump to content
Arni_90

ZOE Ph2 ZE50 R135: Which OBD dongle is compatible w/ android and ABRP live SoC?

Recommended Posts

Hi everyone,

I used the KONWEI KW902 OBD adapter for a while with CANZE but recently struggled with connection faults.

Therefore, I am looking for a new OBD adapter for my 2019 Renault ZOE R135 in combination with an Android phone (Samsung S21).

Has anyone of you already used the new ABRP live SoC feature with the 2nd generation ZOE and can share some experience?

Thanks in advance! 

Link to comment
Share on other sites

On 2/21/2022 at 9:14 PM, Arni_90 said:

Hi everyone,

I used the KONWEI KW902 OBD adapter for a while with CANZE but recently struggled with connection faults.

Therefore, I am looking for a new OBD adapter for my 2019 Renault ZOE R135 in combination with an Android phone (Samsung S21).

Has anyone of you already used the new ABRP live SoC feature with the 2nd generation ZOE and can share some experience?

Thanks in advance! 

You need a Bluetooth BLE dongle NOT the classic Bluetooth.

I have Vgate iCar pro working in my Renault Zoe R135.

I also have an Android mobile

Edited by Rob Tunru
Link to comment
Share on other sites

Hi, thanks for the hints.

I ordered the Vgate vLinker MC+ and after some trial and error selecting it in ABRP, it actually works.

I am wondering about a slight difference between the SoC % shown in the car and the SoC % in the app, which tends to be 1% ... 3% lower.

Is this a fault or does the app calculate the SoC itself, based on the batt. voltage level?

 

Will do further testing, but for now it seems to work.

Link to comment
Share on other sites

On some cars we only have the raw soc and only estimate the display soc based on data we collected. There might be cases where this does not work perfectly well. If you find information for a specific car where this happens on how to get the real display SoC let us know.

Link to comment
Share on other sites

Hi again,

first experiences from today. The connection is lost when the screen of the smartphone turns off. Reactivating the phone triggers a reconnection, which takes 10-20 seconds, but works reliably.

 

I am wondering, that the current SoC in the Burn-Down diagram is jumping up and down between the calculated and the measured SoC. This influences also the expected target-SoC, which is jumping up and down.

Is this a bug or a feature?

 

Wish you a good weekend.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...