Engine), VCDS will ask if you wish to store the VIN, but selecting No will still allow the connection to continue.
If you directly connect to a control module (e.g.
VCDS AUDI CODE
Ross-Tech VCDS Wiki - How-to guides, fault code information, coding info and much moreĪ VIN-Limited interface can do Auto-Scans, Clear DTCs, and look at Measuring Values on an unlimited number of cars. VCDS (VAG-COM) - Useful procedures and car information (e.g. Please visit the Ross-Tech Website for more information:
VCDS AUDI SOFTWARE
This lead and software will work with the following: The HEX-NET (WiFi) is available in 2 versions:
VCDS AUDI LICENSE KEY
The license key is held within the lead so the software is useless without the genuine lead Latest version of software can be downloaded directly from Ross-Tech website (You will not recieve a CD).
VCDS AUDI FULL VERSION
Genuine FULL VERSION (not Lite) Ross Tech VAGCOM Lead with Free Downloadable Software SPozderĬhassis Type: 4B (4B - Audi A6 C5 (1998 > 2006))Īddress 03: ABS Brakes Labels: 8D0-907-389.lblĪddress 17: Instruments Labels: 4B0-920-xxx-17.lblĪddress 56: Radio Labels: 8D0-035-1xx-56.Genuine VAG-Com VCDS Software VW, Audi, Seat, Skoda Diagnostic Tool This feature would have given me the information I needed for the bad coil.ĭo you still recommend trying old school wired interface. Nevertheless I have never been able to get the OBDII to work (ignition off, ignition on and car running). This time I turned ignition on before starting the scan with USB to VCDS 14.7.2 and did get the rest of the groups.īut somewhere I thought I read in the instructions the car should be in the off condition for the autoscan. Locks Labels: 4B0-962-258.lblĮnd-(Elapsed Time: 09:43)-Ġ1370 - Alarm triggered by Interior MonitoringĠ1368 - Alarm triggered by Luggage Compartment SwitchĪddress 55: Headlight Range Labels: 4Z7-907-357.lblĮnd-(Elapsed Time: 09:29).
I compared it to AUTOSCAN done on June 15 and they are nearly identical.Ĭhassis Type: 4B - Audi A6 C5 (1998 > 2006) Below is the text document from AUTOSCAN I did today. Used HEX-NET and VCDS on tablet on 2014 Honda CRV and got message "NOT OBDII Compatible" same as when I tried OBDII on the Allroad. What am I missing? Can it be fixed with an iPhone, windows7 table and public only web access. After selecting on the OBDII the system initiated and then returned a window stating my 2001 Audi Allroad was not OBDII compliant? (news to me) I tried this with the ignition on and again with the engine running with the same error. Using VCDS I tried the autoscan and again no engine or transmission functions were displayed. I did the OPTIONs-TEST-USB and the TEST showed all items to be OK (At least the "firmware needs to be updated" was removed by the VCDS-Mobile update). So I closed out the VCDS-mobile and started with a freshly downloaded version of VCDS 17.4.2. After it completed the autoscan I checked for software updates again using VCDS-mobile OPTIONs and it said the unit was current. I noticed when I did the auto scan no engine or emissions items were being displayed. After a month of trying this was great progress and things were looking good.
VCDS AUDI UPDATE
Once on I did one firmware update and created the cloud account. Once connected I was able to use the Safari browser to locate the address for the VCDS-moble. By connecting with the USB and using my IBM Tablet (windows7) I set the unit to infrastructure mode tethered to my Iphone access point (it took a few parking lots before I found a very strong and stable signal). Note that the Chassis Type '4F is listed under that model. See the Model information Column for Audi to find the A6 Model. The 7th and 8th digits are 4F for Audi A6 (4F), the 10th digit is 6 which stands for Model Year (MY) 2006. I have figured out with the help of the forum that public hotel wi-fi is not the way to connect the device to get the firmware updates. Example (Audi A6): VIN: WAUZZZ4F36N111022. To increase the complexity of setting up the VCDS-mobile as soon as it arrived in Austin TX I moved to Malta NY.