Anyway, thank you very much for your help.
According to Vgate’s website (maybe they upgraded the firmware), the MC model is Bluetooth 3.0 compliant (not BLE), and the MC+ is BT 3.0, 4.0 (BLE) and WiFi compliant: Did you purchase the MC or MC+ model?
Just an strange idea: If you purchased the MC+ model, you may be able to configure it to BT 3.0 (I don’t know how) to check if that improves speed; if so, perhaps this model does not have the reliability issues you have with your LX model.
The OBDlink MX is the best, much much better than the MC. I have both. I use the MX for CAN data and the MC for an OBD2 connection.
Almost four times the price…: as expected, you get what you pay for.
@mmain I think you also use a Meatpi device: Meatpi WiCan OBD vs Vgate vLinker MC, who wins? Maybe I can get a Meatpi Wican OBD at Mouser without paying shipping costs, so the price would be 39,90€ vs 33€ for the MC.
I have VLinker MC+ it works well and is almost wider than obdlink lx ---- obdlink cx. I find it has more parameters and faster connection than others.
Thank you all for your feedback.
@xj8 are you using BT3, BT4 or WiFi connection?
MC+ is more expensive than MC, which is BT3 compliant only. It is also more expensive than Meatpi WiCan OBD (If I finally get it for €40).
@mmain It may be a bit early to have your feedback on the reliability of your MC or MC+ model and its speed in BT3 mode (if possible), right?
I think I will have to decide between the MC model and the WiCan OBD 
@realdashdev Your expert opinion would be greatly appreciated.
That is expected of BLE adapter, they generally have lower data rate. Of course one adapter being faster than other may depend on multiple factors.
This is an age old question; “Which adapter should I use?”. Over the years we have learned that answer is “What ever adapter works best for you”. We always recommend OBDLink adapters and use those for internal testing. Yes, they are more expensive than many others, and yes, on some setups there has been issues with them. But for us, they have been very reliable.
I use OBDLink MX+ on my car for testing daily, and it has been flawless. Even in Finnish weather from -30 to +30 degrees Celsius.
I have read your recommendations on OBDlink devices in several threads, and I am sure you are right, but unfortunately they are are unnafordable for me.
If @mmain purchased a Vgate vLinker MC model (not a MC+), it should be BT3, not BLE (unless it could be updated with a firmware change); OBDLinlk MX+ is also BT3, but as you have said, speed may depend on multiple factors.
So my decision will be between Vgate vLinker MC and Meatpi Wican OBD, and I guess you will rather prefer the Meatpi device, which is BLE (and WiFi). I think @mmain also has a Meatpi device, so his opinion and yours will help me to take a decision.
I am a little bit confused with the information provided at crowdsupply.com regarding to the Meatpi adapter: in the text you can read “The original firmware can use Wi-Fi or BLE to interface directly with RealDash…”, but in the comparision chart you can see:
From the chart it seems to be deduced that the device only interface RD using WiFi, but the truth is that RD lets me choose between BT or WIWI/LAN when I select the MeatPI CAN adapter.
I hope you can help me.
@P_invest_new I only used the Meat Pi in BT (BLE) mode although initially there were some firmware issues with BT reliability, which a beta release mentioned earlier in this thread solved. It was rock solid after this and fast ~1500 fps in can monitor. I see Meat Pi has issued a major firmware upgrade, but as I don’t have the device at hand, I have not upgraded and cannot comment. I should point out I never tried the Meat Pi in OBD2 mode as I always had a separate adapter on the Y cable for mopping up OBD2 parameters I could not find on canbus.
Thank you @mmain I have finally ordered the Meatpi adapter. Anyway I would like to know your feedback on the results of your tests with the vLinker MC/MC+ (reliability, speed, bluetooth version) whenever you finish them.
