Recall of vLinker FS USB from the list of recommended adapters

[boosted_diesel]

An easy solution for this would be to buy the Vlinker Fs bluetooth.
It’s better without cables in the way anyway.

[pswiatki]

An easy solution for this would be to buy the Vlinker Fs bluetooth.
It’s better without cables in the way anyway.

Well.... Better if it works reliably. If the BT link fails during a capture session (say: while driving), then it is very, very bad.

[pswiatki]

Team!

Found confusing message in What's New setion:

What's new in FORScan

February 05, 2024 - Recall of vLinker FS USB from the list of recommended adapters

The adapter has removed from the list of recommended ones due to found problems and the fact that the manufacturer is unable to resolve it for several months already.

Year should be 2025.

[pswiatki]

I have received my "replacement", vLinker FS USB from Amazon and spent a bit of time with it this afternoon. Seems to work great on my surface laptop. So no complaints from me either!

What do you mean when you say "replacement"?

By the way: haven't checked and already ordered vLinker FS USB. I will check the condition of the product when it arrives on Thursday. Same source, Amazon.

[boosted_diesel]

An easy solution for this would be to buy the Vlinker Fs bluetooth.
It’s better without cables in the way anyway.

Well.... Better if it works reliably. If the BT link fails during a capture session (say: while driving), then it is very, very bad.

Ive never had a bluetooth vci loose connection while doing anything. You would have to walk away over 15ft from the vehicle with the device for the connection to be lost.

[pswiatki]

An easy solution for this would be to buy the Vlinker Fs bluetooth.
It’s better without cables in the way anyway.

Well.... Better if it works reliably. If the BT link fails during a capture session (say: while driving), then it is very, very bad.

Ive never had a bluetooth vci loose connection while doing anything. You would have to walk away over 15ft from the vehicle with the device for the connection to be lost.

Aha, aha. Good for you! But I was not talking about walking away until RF unlock occurs on the BT radio, but rather that I would trust physical connection way more than a wireless link (there could be interference, SW fook-up in a no-so-obvious use case during - say - a link re-negotiation, sudden link speed changes, etc.). Those things do not happen in wired connections.

[boosted_diesel]

Well.... Better if it works reliably. If the BT link fails during a capture session (say: while driving), then it is very, very bad.

Ive never had a bluetooth vci loose connection while doing anything. You would have to walk away over 15ft from the vehicle with the device for the connection to be lost.

Aha, aha. Good for you! But I was not talking about walking away until RF unlock occurs on the BT radio, but rather that I would trust physical connection way more than a wireless link (there could be interference, SW fook-up in a no-so-obvious use case during - say - a link re-negotiation, sudden link speed changes, etc.). Those things do not happen in wired connections.

Your obviously not very familiar with scantools. The vast majority of modern and the most expensive scantools that do full programming use Bluetooth these days. There is no problem with them at all. You'll have to dream up another scenario im afraid.
Even a £3000 autel with j2534 pass thru is bluetooth.

[pswiatki]

I doubt the BT chips used in professional equipment are the same as those found in inexpensive (or plain CHEAP) devices. I need more research to make sure. For now, my experience with BT-equipped interfaces for OBD is not so good. Exactly the reason why I opted for USB.
Just a quick question so I can understand it better: when you say "scantools" - do you mean merely comm bridges between OBD and PC equipment (+ appropriate software), or standalone devices designed from the ground up?

EDIT: even if not for the hardware differences - I bet the software is much more carefully crafted and it would make a huge difference.

[boosted_diesel]

I doubt the BT chips used in professional equipment are the same as those found in inexpensive (or plain CHEAP) devices. I need more research to make sure. For now, my experience with BT-equipped interfaces for OBD is not so good. Exactly the reason why I opted for USB.
Just a quick question so I can understand it better: when you say "scantools" - do you mean merely comm bridges between OBD and PC equipment (+ appropriate software), or standalone devices designed from the ground up?

EDIT: even if not for the hardware differences - I bet the software is much more carefully crafted and it would make a huge difference.

That may well be becuase you've tried some cheap online options?
There is plenty junk out there, even stuff that can damage your car. Ive never had any issue with forscan, I started with the elm327, then moved to the vcm2 when I realised it was compatible. I later added the Vlinker fs Bluetooth just over a year ago and it's performed flawlessly. Personally given the Vlinker fa Bluetooth in only £56 uk, I would say it is cheap, but it has the same capabilities as my vcm2 which costs a lot more.

There are over 10 million Bluetooth scantools (usually tablet based systems) and laptops in use around the world daily. Even fords IDS system at the dealership which I also have can use cable or Bluetooth. Again, ive never had a connection issue ever at all when using it. I use Vlinker Bluetooth, autel Bluetooth, Ford VCM2 with Bluetooth and more, never had an issue with the cheap or more expensive stuff. You seem awfully worried for nothing. I do this for a living and I'm not worried. Although I do agree with you on one thing, if I was gonna fully program an ecu or other modules I would probably use my vcm2 with its cable for obvious reasons.

Tbh your probably as well to have both the cable and Bluetooth type as they both have their own ups/downs/merits. The cable type is a nightmare when your doing underbonnet diagnosis and need to simultaneously see live data. At that point bluetooth is golden. But when programming a cable is preferred due to the tiny risk of any errors then potentially bricking a module.

[Mr_Kostas]

What about the Vgate vLinker FD+ OBD2 Bluetooth?
Is that also affected?
Thanks