PROBLEM Vgate vLinker FS USB obd2 remote start encoding!
Posted: Fri Dec 23, 2022 9:25 am
Nice day.
At the beginning I wanted to say that the Vgate vLinker FS USB obd2 cable is a great cable and any updates with this cable are a pleasure. Forscan 2.4.5 beta3 + Vgate.
The cable has the latest firmware from your site.
What should I do, today I had a strange situation that after learning the remote start key (standard 2 keys + new for remote start) in the mondeo mk5 2015, the cable would not connect to the car. It only read a few modules and the rest was red (I had already saved the vehicle profile so it should be blinking). I've tried reconnecting and restarting my laptop a few times but nothing helps.
I tried another Obdlink-ex cable and this cable read all the modules as it should. With this cable I have completed the coding of the key. Then, out of curiosity, I reconnected Vgate vLinker FS and then it read all the modules.
I have to admit that I was helpless and happy that I had another cable.
Could it be that there are some bugs in cable or forscan software? It's not the first time I'm doing this and with obdlink-ex I've never had such a problem.
I would like some feedback if there is a way to fix this error (e.g. with a new forscan software? ). I used Forscan 2.4.5 beta3. I also wrote cable manufacturer (Vgate) and they said that it is not the cable but the Forscan and that I am the first with such errors.
I hope that this problem can be solved somehow.
Regards
At the beginning I wanted to say that the Vgate vLinker FS USB obd2 cable is a great cable and any updates with this cable are a pleasure. Forscan 2.4.5 beta3 + Vgate.
The cable has the latest firmware from your site.
What should I do, today I had a strange situation that after learning the remote start key (standard 2 keys + new for remote start) in the mondeo mk5 2015, the cable would not connect to the car. It only read a few modules and the rest was red (I had already saved the vehicle profile so it should be blinking). I've tried reconnecting and restarting my laptop a few times but nothing helps.
I tried another Obdlink-ex cable and this cable read all the modules as it should. With this cable I have completed the coding of the key. Then, out of curiosity, I reconnected Vgate vLinker FS and then it read all the modules.
I have to admit that I was helpless and happy that I had another cable.
Could it be that there are some bugs in cable or forscan software? It's not the first time I'm doing this and with obdlink-ex I've never had such a problem.
I would like some feedback if there is a way to fix this error (e.g. with a new forscan software? ). I used Forscan 2.4.5 beta3. I also wrote cable manufacturer (Vgate) and they said that it is not the cable but the Forscan and that I am the first with such errors.
I hope that this problem can be solved somehow.
Regards