Vgate vLinker MS for Monitoring & FORScan (and connection issues)

[Firn]

For anyone considering the Vgate vLinker MS, it's proving to be a solid device for both general OBD-II monitoring (using Torque/Car Scanner) and for use with FORScan. Its also less than half the price of the Obdlink MX.

Mobile App Use (Torque/Car Scanner)

Connects easily via Bluetooth.

Fast response—PID retrieval speed in Torque is higher than the average listed for the OBDLink MX.

It can remain plugged in and so far has not caused battery drain.

So far, no connection with ABRP (A Better Route Planner)—still troubleshooting that.


Windows Setup Caveats

Getting it to connect in Windows was trickier:

It didn’t appear in the standard Bluetooth device list.

Internet advice pointed to an “Advanced” Bluetooth settings screen, but my version of Windows lacked this.

I was finally able to get it added through "more devices and printer settings", "add device".


FORScan Performance

Once connected, FORScan recognized the device right away.

Successfully scanned modules and viewed live data and DTCs.

I didn’t attempt writing changes, resetting modules, or flashing firmware—just basic diagnostic functions for now.

Sponsored

 

[Firn]

Getting the Vgate vLinker MS setup in Windows 11


Open Bluetooth Settings and go to "View more devices"

In "View more devices" scroll to the bottom and select "More devices and printer settings"

In the devices and Printers select "Add Device"

The vLinker should show up here by name (not shown in this screenshot). Make sure you have enabled pairing on the vLinker.

The vLinker MS will now show up as a Bluetooth device in the device list and you can also select it from the dropdown in FORScan.

 

[bmwhitetx]

Thanks for this. I have the OBDLink MX+ and had issues with my Win11 laptop as well. Will try this out.

 

[Firn]

Thanks for this. I have the OBD link MX+ and had issues with my Win11 laptop as well. Will try this out.

In the Bluetooth and Devices > Devices window (second screenshot) if you select "More Bluetooth Settings" you can go to the Comms Ports tab and see which comms ports your device is connected on (or remove them). My former MX+ was on comm 3 and 4 and I did remove it before connecting the vLinker but I do not believe that made a difference in my case.

Also, Windows is dumb...
To add the device you are in a screen under the control panel (Control Panel > Hardware and Sound > Devices and Printers). If however you go to the control panel, select hardware and sound, and then select Devices and Printers (or add device), it will not open that display, it opens the Settings window (and closes the Control Panel). You then need to follow the instructions above to get to the "devices and Printers" screen in the control panel.

 

[watts/up]

Man, making changes using FORScan is already stressful enough for me. Can’t imagine adding Bluetooth to the mix. You’re braver than I am.

 

[Firn]

Man, making changes using FORScan is already stressful enough for me. Can’t imagine adding Bluetooth to the mix. You’re braver than I am.

I was using the MX+ previously, which many on here like. The big difference was I wanted to find a single device that would work for Carscanner/Torque, ABRP, and FORScan, which the MX+ does not do (plus mine broke).

Unfortunately I have not been able to get ABRP to work with this device (that is also a BT port/access/control issue in Android). I have not spent much time on it however.

 

[Yellow Buddy]

For anyone considering the Vgate vLinker MS, it's proving to be a solid device for both general OBD-II monitoring (using Torque/Car Scanner) and for use with FORScan. Its also less than half the price of the Obdlink MX.

Mobile App Use (Torque/Car Scanner)

Connects easily via Bluetooth.

Fast response—PID retrieval speed in Torque is higher than the average listed for the OBDLink MX.

It can remain plugged in and so far has not caused battery drain.

So far, no connection with ABRP (A Better Route Planner)—still troubleshooting that.


Windows Setup Caveats

Getting it to connect in Windows was trickier:

It didn’t appear in the standard Bluetooth device list.

Internet advice pointed to an “Advanced” Bluetooth settings screen, but my version of Windows lacked this.

I was finally able to get it added through "more devices and printer settings", "add device".


FORScan Performance

Once connected, FORScan recognized the device right away.

Successfully scanned modules and viewed live data and DTCs.

I didn’t attempt writing changes, resetting modules, or flashing firmware—just basic diagnostic functions for now.

You’re able to program with yours? My blinker works for monitoring, and but it doesn’t allow programming. I had to buy a dedicated wired cable to program.

 

[rugedraw]

You’re able to program with yours? My blinker works for monitoring, and but it doesn’t allow programming. I had to buy a dedicated wired cable to program.

The Vlinker does work for programming.

Sponsored