rns 510 coding vcds usb interface not found

I think I could encounter the same problem. I could be in the same position as a local garage ran a diagnostic check for me and informed me that #19 gateway settings were all zero and that a code from VW would be required to change this. After obtaining the new module, the person found out a code was required and VW refused to provide this. Whilst reading through the retrofit forum I came across an article regarding a Polish Golf that required a new CAN Gateway. However, as I also own an Audi Q5 I would probably need a Hex Can.

I was about to pull the trigger on purchasing a microcan. Grateful for a 'steer' in the right direction. Or maybe there is something we need to do with the VCDS to wake the module to establish communications to the PC. But it could also be the type of CANbus I am told. I think I have a faulty module but I can't get a refund as seller isn't convinced it is faulty. Grateful for some help as my problem has been going on for weeks. But it does work on my car with the new module. Does anyone know how this can be done with the RT tool? The PCI cable connects by the serial port on the PCI and not USB so it could be the RossTech serial interface cable is too out of date.

Someone from VW who is not familiar with the Ross Tech says the module needs to be woken up and he does this with a VW tool. The VCDS will not sync with the new module installed. if I swapped back to my F version, all ok again.Ī friend helped me with his VCDS to try and configure the new module. The car would not start, no ignition lights. When I installed my new module 5k0953569T my ignition was dead. I am in the process of retrofitting a Mk6 MFD steering wheel to my 2012 Tiguan 2.0 S My name is Neil, a Brit in Houston with a 2012 Tiguan.

Rns 510 coding vcds usb interface not found