Hello,

I've bought the vLinker MC+ wich supports automatic wake-up with my electric vehicle to replace iCar pro BLE.
I want to use it with ABRP on my Android smartphone but I can't get the OBD connection for the moment.

The pairing is successful with Android bluetooth (after pushing device button and entering code 1234).

I got a successful upgrade with VgateFwUpdate Tool. The new available version of the vLinker MC+ is 2.2.90 now.

The vLinker MC+ run on Car Scanner App with a Bluetooh connection, no running with Bluetooth LE connection.

With a bluetooth scanner utility, I don't detect any Bluetooth LE device nearby.

In this status, ABRP can't detect this OBD device.

What can I do other ?


Nota : the ref on the box of the device is B088LW211V.

Thank you in advance for your answer.

(06-21-2024, 11:30 PM)jlneveu Wrote: Hello,

I've bought the vLinker MC+ wich supports automatic wake-up with my electric vehicle to replace iCar pro BLE.
I want to use it with ABRP on my Android smartphone but I can't get the OBD connection for the moment.

The pairing is successful with Android bluetooth (after pushing device button and entering code 1234).

I got a successful upgrade with VgateFwUpdate Tool. The new available version of the vLinker MC+ is 2.2.90 now.

The vLinker MC+ run on Car Scanner App with a Bluetooh connection, no running with Bluetooth LE connection.

With a bluetooth scanner utility, I don't detect any Bluetooth LE device nearby.

In this status, ABRP can't detect this OBD device.

What can I do other ?


Nota : the ref on the box of the device is B088LW211V.

Thank you in advance for your answer.

Hello

ABRP connects via BLE, and the BLE Bluetooth name of vLinker MC+ is "vLinker MC-IOS", you need to select vLinker MC-IOS instead of vLinker MC-Android when connecting in Android.

OK thank you very much. It works perfectly like that.

Ensure you select the correct Bluetooth name, you should be able to establish a successful connection between the vLinker MC+ and the ABRP app.
io games

Since you successfully updated to firmware 2.2.90, check with Vgate’s customer support to see if there’s a specific setting to enable BLE mode.

To resolve the issue with ABRP not detecting your vLinker MC+, try the following:

1. Check ABRP Settings: Ensure the correct OBD device type and connection method are selected in the app.
2. Bluetooth Settings: Disconnect other Bluetooth devices to avoid interference. 
3. App Permissions: Verify ABRP has permissions for Bluetooth and location services.
4. Device Compatibility: Confirm the firmware version is compatible with ABRP.
5. Restart Devices: Restart both your smartphone and vLinker MC+.
6. Contact Support: If the issue persists, reach out to ABRP support with your device and firmware details.

These steps should help establish a connection. 
TRANSLATE with x
English
Arabic
Hebrew
Polish
Bulgarian
Hindi
Portuguese
Catalan
Hmong Daw
Romanian
Chinese Simplified
Hungarian
Russian
Chinese Traditional
Indonesian
Slovak
Czech
Italian
Slovenian
Danish
Japanese
Spanish
Dutch
Klingon
Swedish
English
Korean
Thai
Estonian
Latvian
Turkish
Finnish
Lithuanian
Ukrainian
French
Malay
Urdu
German
Maltese
Vietnamese
Greek
Norwegian
Welsh
Haitian Creole
Persian


var LanguageMenu; var LanguageMenu_keys=["ar","bg","ca","zh-CHS","zh-CHT","cs","da","nl","en","et","fi","fr","de","el","ht","he","hi","mww","hu","id","it","ja","tlh","ko","lv","lt","ms","mt","no","fa","pl","pt","ro","ru","sk","sl","es","sv","th","tr","uk","ur","vi","cy"]; var LanguageMenu_values=["Arabic","Bulgarian","Catalan","Chinese Simplified","Chinese Traditional","Czech","Danish","Dutch","English","Estonian","Finnish","French","German","Greek","Haitian Creole","Hebrew","Hindi","Hmong Daw","Hungarian","Indonesian","Italian","Japanese","Klingon","Korean","Latvian","Lithuanian","Malay","Maltese","Norwegian","Persian","Polish","Portuguese","Romanian","Russian","Slovak","Slovenian","Spanish","Swedish","Thai","Turkish","Ukrainian","Urdu","Vietnamese","Welsh"]; var LanguageMenu_callback=function(){ }; var LanguageMenu_popupid='__LanguageMenu_popup';
[/url] [url=javascript:Microsoft.Translator.FloaterShowEmbed()] [url=javascript:Microsoft.Translator.FloaterShowSharePanel()][/url]

TRANSLATE with
COPY THE URL BELOW

[url=javascript:Microsoft.Translator.FloaterOnShareBackClick()]Back[/url]

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal
[url=javascript:Microsoft.Translator.FloaterOnEmbedBackClick()]Back[/url]
var intervalId = setInterval(function () { if (MtPopUpList) { LanguageMenu = new MtPopUpList(); var langMenu = document.getElementById(LanguageMenu_popupid); var origLangDiv = document.createElement("div"); origLangDiv.id = "OriginalLanguageDiv"; origLangDiv.innerHTML = "<span id='OriginalTextSpan'>ORIGINAL: </span><span id='OriginalLanguageSpan'></span>"; langMenu.appendChild(origLangDiv); LanguageMenu.Init('LanguageMenu', LanguageMenu_keys, LanguageMenu_values, LanguageMenu_callback, LanguageMenu_popupid); window["LanguageMenu"] = LanguageMenu; clearInterval(intervalId); } }, 1);

---

7. Firmware Recheck: Double-check if there are any additional firmware updates available for the vLinker MC+ that might improve compatibility.
Alternative Apps: Test the vLinker MC+ with another OBD app to ensure the device is functioning correctly.
9. Bluetooth LE: Since the device doesn't appear as a Bluetooth LE device, ensure ABRP is set to use standard Bluetooth, not BLE.
10. Device Reset: Perform a factory reset on the vLinker MC+ if possible, and then re-pair it with your smartphone.
These additional steps might help in resolving the connection issue with ABRP.
TRANSLATE with x
English
Arabic
Hebrew
Polish
Bulgarian
Hindi
Portuguese
Catalan
Hmong Daw
Romanian
Chinese Simplified
Hungarian
Russian
Chinese Traditional
Indonesian
Slovak
Czech
Italian
Slovenian
Danish
Japanese
Spanish
Dutch
Klingon
Swedish
English
Korean
Thai
Estonian
Latvian
Turkish
Finnish
Lithuanian
Ukrainian
French
Malay
Urdu
German
Maltese
Vietnamese
Greek
Norwegian
Welsh
Haitian Creole
Persian


var LanguageMenu; var LanguageMenu_keys=["ar","bg","ca","zh-CHS","zh-CHT","cs","da","nl","en","et","fi","fr","de","el","ht","he","hi","mww","hu","id","it","ja","tlh","ko","lv","lt","ms","mt","no","fa","pl","pt","ro","ru","sk","sl","es","sv","th","tr","uk","ur","vi","cy"]; var LanguageMenu_values=["Arabic","Bulgarian","Catalan","Chinese Simplified","Chinese Traditional","Czech","Danish","Dutch","English","Estonian","Finnish","French","German","Greek","Haitian Creole","Hebrew","Hindi","Hmong Daw","Hungarian","Indonesian","Italian","Japanese","Klingon","Korean","Latvian","Lithuanian","Malay","Maltese","Norwegian","Persian","Polish","Portuguese","Romanian","Russian","Slovak","Slovenian","Spanish","Swedish","Thai","Turkish","Ukrainian","Urdu","Vietnamese","Welsh"]; var LanguageMenu_callback=function(){ }; var LanguageMenu_popupid='__LanguageMenu_popup';
[/url] [url=javascript:Microsoft.Translator.FloaterShowEmbed()] [url=javascript:Microsoft.Translator.FloaterShowSharePanel()][/url]

TRANSLATE with
COPY THE URL BELOW

[url=javascript:Microsoft.Translator.FloaterOnShareBackClick()]Back[/url]

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal
[url=javascript:Microsoft.Translator.FloaterOnEmbedBackClick()]Back[/url]
var intervalId = setInterval(function () { if (MtPopUpList) { LanguageMenu = new MtPopUpList(); var langMenu = document.getElementById(LanguageMenu_popupid); var origLangDiv = document.createElement("div"); origLangDiv.id = "OriginalLanguageDiv"; origLangDiv.innerHTML = "<span id='OriginalTextSpan'>ORIGINAL: </span><span id='OriginalLanguageSpan'></span>"; langMenu.appendChild(origLangDiv); LanguageMenu.Init('LanguageMenu', LanguageMenu_keys, LanguageMenu_values, LanguageMenu_callback, LanguageMenu_popupid); window["LanguageMenu"] = LanguageMenu; clearInterval(intervalId); } }, 1);

Interesting, I also experienced something similar when changing the OBD device. It seems that vLinker MC+ is only active in classic Bluetooth mode by default. Maybe you need to check if there is an option in the firmware or supporting application to explicitly activate Bluetooth LE? Sometimes applications like ABRP also need location permission and restart Bluetooth in order to detect LE devices. I'm also curious if anyone has successfully paired via LE, please share how.

Ah, that actually makes a lot of sense! I ran into the same issue a while back and spent way too much time wondering why the app couldn't find my vLinker MC+. It turned out I had to toggle on location services and also manually restart Bluetooth, just like you mentioned. I haven’t tried forcing it into LE mode yet, but now I’m wondering if that’s why some apps are hit or miss with detection. If anyone’s figured out a reliable way to pair it via Bluetooth LE, especially with apps like ABRP or Torque, I’d love to hear how you did it too! ragdoll hit

(06-21-2024, 11:30 PM)jlneveu Wrote: Hello,

I've bought the vLinker MC+ wich supports automatic wake-up with my electric vehicle to replace iCar pro BLE.
I want to use it with ABRP on my Android smartphone but I can't get the OBD connection for the moment.

The pairing is successful with Android bluetooth (after pushing device button and entering code 1234).

I got a successful upgrade with VgateFwUpdate Tool. The new available version of the vLinker MC+ is 2.2.90 now.

The vLinker MC+ run on Car Scanner App with a Bluetooh connection, no running with Bluetooth LE connection.

With a bluetooth scanner utility, I don't detect any Bluetooth LE device nearby.

In this status, ABRP can't detect this OBD device.

What can I do other ?


Nota : the ref on the box of the device is B088LW211V.

Thank you in advance for your answer.

It sounds like you're encountering a common issue with OBD dongles and ABRP, specifically related to Bluetooth Classic versus Bluetooth Low Energy (BLE). Let's break down the problem and what you can do.  

Understanding the Core Issue: Bluetooth Classic vs. Bluetooth LE

vLinker MC+ is a dual-mode adapter: The vLinker MC+ supports both standard Bluetooth (sometimes called "Bluetooth Classic" or older versions like 2.0, 3.0) and Bluetooth Low Energy (BLE or Bluetooth 4.0+).
ABRP requires Bluetooth LE: A Better Routeplanner (ABRP) specifically states that it requires Bluetooth Low Energy (BLE) for OBD dongle connections. This is crucial. 
Car Scanner and your phone's pairing: When you connect with Car Scanner, it's likely using the standard Bluetooth connection. Your successful pairing with Android Bluetooth (requiring a code like 1234) is also for the standard Bluetooth profile.
No BLE device detected: The fact that a Bluetooth scanner utility doesn't detect a BLE device nearby suggests that either the BLE functionality isn't active in the vLinker MC+ in a way that ABRP can see it, or your phone isn't properly scanning for BLE devices for ABRP's use.

(06-21-2024, 11:30 PM)jlneveu Wrote: Hello,

I've bought the vLinker MC+ wich supports automatic wake-up with my electric vehicle to replace iCar pro BLE.
I want to use it with ABRP on my Android smartphone but I can't get the OBD connection for the moment.

The pairing is successful with Android bluetooth (after pushing device button and entering code 1234).

I got a successful upgrade with VgateFwUpdate Tool. The new available version of the vLinker MC+ is 2.2.90 now.

The vLinker MC+ run on Car Scanner App with a Bluetooh connection, no running with Bluetooth LE connection.   https://unblockedgames-66ez.com

With a bluetooth scanner utility, I don't detect any Bluetooth LE device nearby.

In this status, ABRP can't detect this OBD device.

What can I do other ?


Nota : the ref on the box of the device is B088LW211V.

Thank you in advance for your answer.

The vLinker MC+ you’re using is a Bluetooth Classic device, but ABRP requires a Bluetooth Low Energy (BLE) OBD adapter. That’s why ABRP can’t detect it. To use ABRP directly, you’ll need a BLE-compatible device like the Vgate iCar Pro BLE or OBDLink CX.