Audi Issues &
01J (CVT) Transmissions
have rather unusual timing requirements. When used with a HEX
Interface, increase Char Int on the Options
Screen to approximately 4 or 5.
As of VCDS version 805, the appropriate value
is automatically determined. A user intervention should not be necessary
and Symphony Radios
These are made by
Matsushita. The Concerts have blatant bugs in the diagnostic
protocols. We've added one work-around to the low
level protocol drivers that works in some, but not all Concerts, and
it is not 100% reliable in any case.
occasionally get "stuck" in an undesirable mode after attempting
communications. If your Concert gets "stuck", the way to
reset it is to remove all power from from the radio for at least 10-15
seconds. This can be done by:
the radio from the car.
the car's battery
the fuse for the radio.
radios will require you to enter the "security code" using the
radio's front panel after losing power. See the owner's manual
for the radio for instructions.
that I suspect there is something not quite up to snuff in the Symphony's
ability to drive the K-line. We've had some reports that they work better with
non-optically isolated interfaces, and they may work better with the engine running (which means
there is a higher voltage on the VBatt lines in the car).
2.8L 12V V6 Engine
There is a bug
in the Hitachi ECU that does not allow reliable monitoring or logging of
multiple measuring groups. For these vehicles, we recommend only viewing
or logging one group at a time.
C4 (A6/S6) Instrument Clusters
These have a
high bit-error rate. We suspect they use a software-UART and
"stretch" bits sometimes. The error-detection/correction
logic built into VCDS's low-level protocol drivers as of version 0.70
seems to take care of this in a majority of cases, but we still
had few reports of customers not being able to communicate with these
clusters. In version 0.75 or or newer, please
ensure that Char Int on the Options
Screen is set to approximately 3 (which is the default).
On some PC's, it may be necessary to adjust this value to something other
than 3. On very
fast PCs try a higher value than 3. On very slow PCs, try a value lower
We have received reports from users who cleaned the terminals on the
wiring connections at the back of their instrument cluster with
electronics cleaner. This appeared to fix the problem with communicating
with these clusters.
2.6L V6 Engine (non-US only)
communicate with some of these ECU's while using a "dumb" Interface. These ECUs (made by Hella)
are so incredibly fussy about the protocol timing that there is no way to
get them to work with a "dumb" interface and an application running in
user-mode under Windows. For vehicles with these engines, we recommend a
HEX Interface, which work great.
Note, if you use a USB Interface, we HIGHLY recommend the use of Windows
XP or newer. Use of other versions of Windows may prevent VCDS from successfully
working with these ECU's.