Jump to content
Uwe-EV6

NEW Direct OBD Integration (Vers. 4.11.) doesn‘t work (KIA EV6)

Recommended Posts

Driving Model:

KIA EV6 AWD, Battery 77,4 kWh

 

I bought TWO OBD-BT LE-Dongles which are enlisted as „compatible & works fine“ with ABRP. But NONE works.

I got a KIA EV6 - which should be supported.

Binding Procedure:

I disconnected all other Live-Data connections - especially the evNotify-binding.

Then plugged in the OBD Dongle (vgate iCar Pro OBD2 Bluetooth 4.0(BLE) ), started the car. OBD-Dongle is ready for connection.

NO OTHER APPS connected to the Dongle.

Opened ABRP. Car->Settings->OBD-Connection. OBD Dongle was found. Pressed the Dongle Named there. 

 

Problem:

First (of three) Connection Points went to green (and acknowledged)

But, as soon as the Installation went automatically to the 2nd Point, after about 2 Seconds later the App crashed, and produces a whole blank white Screen.

Waiting for 5 Minutes. Nothing changes. Restart of ABRP reopens the „Connect to OBD“-Page.

No matter, if trying to install on an Android (Samsung Galaxy Note 10+) or an iOS-System (iPhone 12 pro max or iPad Pro 2021, all Systems with newest Software / with proper Dongle selected working for Android or iOS), the result was always the same.

The Dongle works on both systems, which I tried with other apps i tested (proof if Dongle is working).

I also tried the Veepeak OBDCheck BLE+ Bluetooth OBD 2, and the Vgate vLinker MC OBDII Bluetooth OBD2 

Am I doing sth. wrong?

At least ONE of the Dongles should have worked.

Probably a bug (at this time)?

Help would be very welcome !!

Perhaps you could post an „Step-by-Step Connection procedure“?

THX in advance !!!

 

I tried the following Dongles for connection. All of them were recognized bei ABRP. Installation stopped each time at Point 2 of the automatic procedure, with a blank white Screen

C22D648D-8F18-4FD3-899A-CA0BA79B1223.jpeg

336E16B4-C72E-42D3-AD97-29890E486EB7.jpeg

D9CBCCDA-3318-41AF-A423-01458F53E4AB.jpeg

Link to comment
Share on other sites

Please don't ask for support in forum. Use the support&feedback functionality from the app. There you can also create bugs.

On Android make sure you are on the latest version 4.1.11 which was released today. The earlier version had a problem. 

If the app screen goes blank it means there is an error, which we need to find. For that please use the bug report.

Link to comment
Share on other sites

MANY THANKS for your work, even for Christmas without a break.  My highest appreciation for that 🙏♥️🙏

 I'll try again this afternoon.

Should I disconnect the EVNotify connection within ABRP before („Disconnect Live Data“), or is this not necessary as long as I do not start EVNotify?

Link to comment
Share on other sites

3 hours ago, Samuel-ABRP said:

@Uwe-EV6 i pushed an updated pid list so it should work now, could you please try again?

 

PERFECT!!!

THX A LOT!!!

Your Workaround about the Hyundai Ioniq5 800V PID is successful 👍👍 (works also with the KUA EV6).

Now it works on both Systems Android and iOS!!!

 

Merry Christmas and a happy new year 

🍀🙏🍀

 
  •  
  • Like 1
Link to comment
Share on other sites

3 hours ago, Uwe-EV6 said:

Should I disconnect the EVNotify connection within ABRP before („Disconnect Live Data“), or is this not necessary as long as I do not start EVNotify?

Doesn't matter, we always take the latest data, wherever they come from. So if you want to keep EVNotify as Backup you should leave it connected.

Link to comment
Share on other sites

Pairing is necessary with Android and iOS Devices (Dongle connected to car, car switched „on“):


1. Press Pairing Button on Dongle

2. Search for new Device in BT-Settings of Android Smartphone

3. The „VLinker MC+ for Android“ should be found -> Click / tap Pairing

4. Open ABRP -> Car Settings -> Connect to OBD -> Click listed (actual paired) Device

 

Same Dongle with iOS (Dongle connected to car, car switched „on“):

1. Press Pairing Button on Dongle

2. just open ABRP (NOT BT-Settings on Phone!)

3. Goto Car Settings -> Connect to OBD -> Click listed Device „VLinker iOS“

 

At least this procedures worked for me.

As far as I noticed, without pressing the pairing button, only the Device „VLinker MC+“ will be listed in the smartphones BT-device list. The additional Version „…for Android“ or „…for iOS“ is missing.

Therefor you‘ll get a „connection failure“, if the Version is not determined.

This will only happen after pressing the pairing button (as far as I noticed on my devices)

So, THIS OBD Dongle seems to be secure 👍

Edited by Uwe-EV6
  • Like 1
Link to comment
Share on other sites

This was indeed a Christmas present.  I was able to connect directly using https://www.amazon.com/gp/product/B08LDBYTFP/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1.  It was what I could find as the preferred OBDLink CX was out of stock.  While I have not had occasion to road test it yet, it quickly connected directly to ARBP.  Main thing I had to do is to uninstall ABRP and reinstall it in order to obtain the latest version.  Thank you very much for your work on this.  I sincerely appreciate the upgrade.  I now have a much better handle on how far my Bolt will go.

Link to comment
Share on other sites

I have ordered the vLinker MC+ and it works fine with my car (Škoda Enyaq) and two Android phones that I tried it with. It didn't work at the first time (ABRP found it, but threw an error message when trying to connect several times), but after unplugging it for a few seconds and retrying, all went fine.  

However:

On 12/25/2021 at 9:10 PM, Uwe-EV6 said:

2. Search for new Device in BT-Settings of Android Smartphone

3. The „VLinker MC+ for Android“ should be found -> Click / tap Pairing

On both Android phones, my device shows up as "vLinker MC-IOS", not as „VLinker MC+ for Android“. 

I'm not a pro in IT security, but from what I can tell, it seems to be a rather secure option due to its button and encryption.

From my point of view this device seems to be the best option, as it is affordable and probably secure to leave plugged in. 

Link to comment
Share on other sites

3 hours ago, Inigo_Montoya said:

How do you get car settings in the app to appear in order to link the OBD?

Nevermind. I figured out what I did wrong. I did not realize you need to utilize something like EVNotify to pull the data from. All good.

I bought the VLinker MC+ and it's working. Thanks.

Link to comment
Share on other sites

You don't need Evnotify to link OBD data in app (if you want to use the native OBD support). Just go to car settings (⚙️ icon behind car) and then you can link a supported car with ABRP OBD Connection. If it does not show up your car is not supported. In that case you could go to support & feedback in the app, request a feature and then you get redirected to our new request board and ask for support for your car.

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...