Greetings;
First post. Vagcom/VCDS user since 2004.
(Backstory)
Long story short, ive owned a Micro-Can since 2007 (and also another older version since 2004) and since the i used it for many VW i owned throughout the years with mostly no issues. Then, on 2019 i purchased a new MK7.5 Golf R that forced me to get a Hex-V2, which came with 3 Vin licenses.
Natutally, 1 of the licenses got used with the Golf R which was expected. Other than that; i was planning to save the other 2 vins for future cars i would potentially own later on, saving the Micro Can for my other car, which is a 3.6 swapped VW Corrado.
Unfortunately, and i cant remember exactly why, i needed to use VCDS for some troubleshooting on my 3.6 and the Micro Can wouldnt work so i decided to bite the bullet and use one of my remaining vins on the Hex-V2 which then only left me with one vin available. Even more unfortunate was the fact that i had to swap ECUs on that car during some engine trouble , which meant that the VCDS saw it as a new vehicle, and hence it consumed my last vin #. I contacted VCDS support explaining my ECU replacement situation but unfortunately nothing was done in my favor. So at this point i have 3 cables (whatever the classic pre Micro can cable was / Micro Can / Hex-V2) and somehow i managed to use 3 vins with just 2 cars. Unfortunate for sure but i decided to just suck it up and move on.
(Current situation)
Last weekend I updated my Software to the lastest version and also did a cable firmware update because it was forced by the software in order to make the cable connect to the car. To my suprise, the cable is now registering this Corrado vin once again as a new vin, when in fact it should have just recognized it as pre existing, since i havent swapped ecu’s since i last used my 3rd vin. Obviously this bothers me since there was no hardware change on my end to provoque this, and once again ive been forced to get yet another vin when i had already depleted my previous ones under circunstances that shouldnt had happen (in theory), based on the hardware i have purchased for personal use.
Any insights on this would be greatly appreciated.
PS: also for some reason, the Micro-Can cable stopped recognizing the Can on the 3.6 Corrado even when the Hex-V2 sees it perfectly when doing the test routines…out of nowhere. But thats a separate issue im trying to understand…
PS2: Cant post an autoscan because neither cable allows me to; Micro can doesnt connect and Hex-V2 connects and works but somehow doesnt do the autoscan per ce.
First post. Vagcom/VCDS user since 2004.
(Backstory)
Long story short, ive owned a Micro-Can since 2007 (and also another older version since 2004) and since the i used it for many VW i owned throughout the years with mostly no issues. Then, on 2019 i purchased a new MK7.5 Golf R that forced me to get a Hex-V2, which came with 3 Vin licenses.
Natutally, 1 of the licenses got used with the Golf R which was expected. Other than that; i was planning to save the other 2 vins for future cars i would potentially own later on, saving the Micro Can for my other car, which is a 3.6 swapped VW Corrado.
Unfortunately, and i cant remember exactly why, i needed to use VCDS for some troubleshooting on my 3.6 and the Micro Can wouldnt work so i decided to bite the bullet and use one of my remaining vins on the Hex-V2 which then only left me with one vin available. Even more unfortunate was the fact that i had to swap ECUs on that car during some engine trouble , which meant that the VCDS saw it as a new vehicle, and hence it consumed my last vin #. I contacted VCDS support explaining my ECU replacement situation but unfortunately nothing was done in my favor. So at this point i have 3 cables (whatever the classic pre Micro can cable was / Micro Can / Hex-V2) and somehow i managed to use 3 vins with just 2 cars. Unfortunate for sure but i decided to just suck it up and move on.
(Current situation)
Last weekend I updated my Software to the lastest version and also did a cable firmware update because it was forced by the software in order to make the cable connect to the car. To my suprise, the cable is now registering this Corrado vin once again as a new vin, when in fact it should have just recognized it as pre existing, since i havent swapped ecu’s since i last used my 3rd vin. Obviously this bothers me since there was no hardware change on my end to provoque this, and once again ive been forced to get yet another vin when i had already depleted my previous ones under circunstances that shouldnt had happen (in theory), based on the hardware i have purchased for personal use.
Any insights on this would be greatly appreciated.
PS: also for some reason, the Micro-Can cable stopped recognizing the Can on the 3.6 Corrado even when the Hex-V2 sees it perfectly when doing the test routines…out of nowhere. But thats a separate issue im trying to understand…
PS2: Cant post an autoscan because neither cable allows me to; Micro can doesnt connect and Hex-V2 connects and works but somehow doesnt do the autoscan per ce.
