Jump to content
JB_Sullivan

OBD Dongel & Enyaq iV with ABRP 4.1.10 not found

Recommended Posts

Has anyone been able to get the live data collection function working with an OBD dongle using Android 11 (Xiaomi M11 MIUI 12.5.8) and the Enyaq 80 IV? 

I was previously paired with Tronity. Then I disconnected and tried to find my OBD dongle. No chance. ABRP does not find my dongle.
( https://www.obdlink.com/products/obdlink-lx/)

The following statement is made in the description of the dongel. I would have interpreted this as Bluetooth Low Energy.

- BatterySaver™ Technology low power mode

Dongel was in pairing mode and had no other pairing to other apps.

Is it the dongle itself? But it should work, because it is a higher quality OBD adapter and it has worked with all apps so far, except ABRP.

I am in the Android beta programme version 4.1.10.

Edited by JB_Sullivan
  • Like 1
Link to comment
Share on other sites

Good Morning,

sorry to say that but to support both Android and iOS we aimed for BLE OBD dongles only. The OBDLink LX is a classic BT device. So far we can confirm that the OBDLihnk CX is working fine.
Check out this site to see all currently supported dongles:
https://iternio.com/index.php/iternio-telemetry-api/abrp-obd-connection-for-live-vehicle-data/

Link to comment
Share on other sites

Additional question:

Which of these four recommended BLE Dongles is switching on and off automatically. 

My current Veepeak works like a charm, but is not BLE. 

I do not want to fiddle around with the dongle. Plug in and forget.

Thanks 

  • Like 1
Link to comment
Share on other sites

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.

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. 

First (of three) Connection Points went to green.

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, with other apps i tested instead (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 bei appreciated !!

THX in advance !!!

 

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

 

B6A76B59-A1CE-4A7D-817F-B0E711020EC1.jpeg

8CBF4DBD-1284-4916-A1FB-D996F7979534.jpeg

8376AECE-975D-4CF7-9DDC-6FCF2BAC4181.jpeg

Link to comment
Share on other sites

Both the VLinker MC+ and the iCar pro will shut down after several Minutes, and will wake up by opening a connected App which sends signals  to reconnect.

As it is a little more expensive & works well, but WITH safety Features as described by ABPR, I‘ll personally recommend the VGate VLinker MC+ (it has to be the „+“-Version!)
 

https://www.amazon.de/gp/slredirect/picassoRedirect.html/ref=pa_sp_phone_search_atf_aps_sr_pg1_1?ie=UTF8&adId=A000139039VUHKIJHH0IG&url=%2FTONWON-vLinker-Bluetooth-Diagnosescanner-Android%2Fdp%2FB089KGPDS6%2Fref%3Dmp_s_a_1_2_sspa%3Fcrid%3D3EQTAAZTMOZ1N%26keywords%3Dvlinker%2Bmc%2B%2Bwifi%26qid%3D1640435215%26sprefix%3Dvlinker%2Bmc%2Caps%2C136%26sr%3D8-2-spons%26psc%3D1&qualifier=1640435215&id=3372171526882167&widgetName=sp_phone_search_atf

 

I use an Obd switch /Splitter to which 2 dongles can be connected at the same time.  Available from Amazonas, for example:

https://www.amazon.de/gp/slredirect/picassoRedirect.html/ref=pa_sp_phone_search_atf_aps_sr_pg1_1?ie=UTF8&adId=A0322034Q28HKTRUR35T&url=%2FLoongGate-OBD-II-Splitter-Kabel-Diagnose%2Fdp%2FB076HKB9RF%2Fref%3Dmp_s_a_1_1_sspa%3Fcrid%3D24YPSD2TG9XAF%26keywords%3Dobd2%2Bsplitter%26qid%3D1640435099%26sprefix%3Dobd%2Bsplitter%2Caps%2C150%26sr%3D8-1-spons%26psc%3D1&qualifier=1640435099&id=2949990980126521&widgetName=sp_phone_search_atf

 

One is connected with iOS and CarScanner-App ( to watch Battery Temp and other PIDS for my car) and one is connected with android for use now with direct OBD-Connection to ABRP.

Works perfectly Fine!

 

Hope I could be helpful👍

Link to comment
Share on other sites

On 12/23/2021 at 2:47 AM, Manuel-ABRP said:

Good Morning,

sorry to say that but to support both Android and iOS we aimed for BLE OBD dongles only. The OBDLink LX is a classic BT device. So far we can confirm that the OBDLihnk CX is working fine.
Check out this site to see all currently supported dongles:
https://iternio.com/index.php/iternio-telemetry-api/abrp-obd-connection-for-live-vehicle-data/

For what it's worth, the OBDLink MX+ device doesn't seem to want to work either. Their website claims it's classic BT one page, and then BLE on another, so I'm starting an argument with their support team. In the end, I don't think it's going to work until ABRP implements support for classic BT.

I didn't buy the device with ABRP in mind, but ABRP seems to be the best solution currently on the market. Hopefully, OBDLink respects the "No Questions Asked" money back guarantee.

Link to comment
Share on other sites

Hold on, you wrote, that it wakes up, if a connection is requested, right? Not switching the car on?

Does ABRP requests a connection?

When? At startup, at the beginning of routing, during the calculation of the route?

Thanks

Link to comment
Share on other sites

Hello

Thanks for the info, but the Dongle is not waking up.

After it shuts down, when I enter the car, non of the LEDs is on, completely dark. It doesn't matter, if I push the brake pedal to set the car active or if I press the "start"-button, the Dongle remains dark.

If I unplug it and replug it, it lightens up, the LEDs are going and it's connected within seconds with ABRP.

Please make normal Bluetooth Dongles possible, my Veepeak works like a charm in the past waking up.

Thanks

 

 

 

Link to comment
Share on other sites

Not sure if classic BT would help here - does it wake up when phone is nearby? You can still use all the existing solutions with classic BT, like Evnotify or ABetterObdReader. They all have the same accuracy. We might eventually add support for that as well but it does not have the highest priority right now, as there are lots of solutions that do that already.

Link to comment
Share on other sites

Hello Samuel

My Veepeak goes to sleep and wakes up without any problems. If it's a Bluetooth connection reception or just getting switched power from the OBD port, I don't know.

Using third party apps is not nice. Remember, we are already using ABRP (second party), then we use AA (third party), so ABOR would be forth party. Even using ABRP is already a hassle. The less apps, the better.

Following your new feature request tracker, implementing normal Bluetooth Dongles is top priority for your (paying) Users. What should the voting button do, if not setting your priorities?

Thanks

Link to comment
Share on other sites

AA is not another app, you don't use ABRP and AA simultaneously normally anyways, it's also more or less the same. Also ABOR runs in background automatically, so not really worth mentioning. I think you are trying to create a problem that does not exist. If it is already a hassle to use ABRP, you maybe have the wrong car? There are cars that can do automatic planning with charge stops.

Don't want to offend you, sorry if it sounds like this, but we also have lots of other stuff todo and the current solution works very well. If you don't like it, don't use it, no difference to the version before where OBD support was not available - also worked for most people.

The other solutions were used for many years now, so no real rush for us to remove them by implementing it ourself as they also work pretty well.

We check the community demands, that still does not mean we will do whatever you propose ;). Most important things come first, and classic BT right now is not one of them as there are lots of other apps that do it for us. However we will consider it and once we have time for it we will most likely also add it.

Link to comment
Share on other sites

Hello Samuel

Thanks for your open words.

I could now write a long story, but I save us the time.

ABRP is great, I love it, I want to see it getting even better, sooner than later. You are currently ahead of the game. Please work on the reliability (less bugs, better tests before releases) and make it more convenient and easier to use.

Keep up the good work.

Know I have to test your new release 4.1.12 ;-).

Bye

 

 

  • Like 1
Link to comment
Share on other sites

On 12/23/2021 at 7:59 AM, JB_Sullivan said:

Has anyone been able to get the live data collection function working with an OBD dongle using Android 11 (Xiaomi M11 MIUI 12.5.8) and the Enyaq 80 IV? 

I have an Enyaq 80 and a Xiaomi Mi 11 Ultra (MIUI 12.5.20) and it is running well with a vLinker MC+. I have to say however that I have received the device only yesterday and haven't tested it much yet. 

I can fully recommend the vLinker MC+ as it seems to be the only affordable device that can stay plugged in without security concerns.

Edited by Hosinus
Link to comment
Share on other sites

Hello @Hosinus

Please test in specific, if the Dongle wakes up by its own, without switching it on or something like that.

After a long night, you should enter your car, open ABRP in Android Auto, start a navigation and you should have live SoC right away.

If that works, then everything is fine with it.

Thanks

Link to comment
Share on other sites

Hello

I contacted the supplier of the iCar Pro Dongle, that I bought on Amazon. It was delivered here to Germany from a German location, but on the package, everything is in Chinese and the support also answered in a chinese manner.

Because the Dongle should wake up, but it doesn't, they sent me a new one. Also this second one is not waking up in my Enyaq.

So I would not recommend the iCar Pro Dongle for now. 

I will test the VLinker MC+ next.

Bye

Link to comment
Share on other sites

Did you try any third party apps? We do not actively trigger a connection, but wait until the dongles get found by the app. So it might not be a problem with the dongle. The OBDLink CX for example still seems to broadcast some data in Standby which is received by the app and then a connection is established, but other dongles might require a connection attempt to wake up. 

Link to comment
Share on other sites

Hello,

I also got the vgate iCar Pro OBD2 Bluetooth 4.0(BLE) and it works like a charm as long as it is connected.

I have experienced the same that the dongle is dark when you enter the car and the app is on.

But I am too curious now so I have to do a test at once and see if the dongle wakes up after a while.

I use the latest version 4.1.12

Here's my report.

I sat in the car for at least 4 minutes and the dongle didn't wake up.

I had to disconnect and connect it and in just 5 seconds it was alive again.

 

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