Vcds

The confusing part is an initial full scan WAS done using the setup. Only when trying to access modules did the communication error of controller not responding occur.
Have suggested starting a fresh session then just try to access the controller, also suggested trying with the engine running.....

I assume the port settings were saved during the initial setup?
 
The confusing part is an initial full scan WAS done using the setup. Only when trying to access modules did the communication error of controller not responding occur.
Have suggested starting a fresh session then just try to access the controller, also suggested trying with the engine running.....

I assume the port settings were saved during the initial setup?
When I did the full scan the baud rate was set on zero
 
The cable is
VAG-K+CAN
Commander full
The correct cable for vcds-lite is a KKL Serial to USB (serial at the car end, USB at the laptop).
Your cable description includes "+can" might imply it's for the later version of VCDS. Lite does not support canbus diagnostics.
Probably nothing, but doesn't sound right to me.
Mac.
 
Agree with Mac. Although confused as how cable worked once with those settings.

Either get an ebay KKL cable or the Gendan cable.
 
I asked Ross-Tech, some time back, about setting Baud Rates to improve comms, this was their reply.

The baud rate differs for each control module and even then, a different year or control module supplier may use a different baud rate.
That is why VCDS needs to detect the baud rate each time a control module is accessed.
With 3rd party hardware, we rely on a software solution to do that, which is reliable enough to work in most cases. With our older HEX and HEX
+CAN hardware, the baud rate detection is entirely happening on the hardware side, which makes it far more reliable. So there is no specific baud rate you should set a port to.

From this, there is no advantage setting the baud rate, indeed it may cause comms failures.

Mac.
 
Last edited:
Back
Top