Connect the car end of your Interface to your vehicles Diagnostic Port. G
H If your vehicle has a 2x2 port (some pre-1996 vehicles), then use a 2x2 Adapter between the Interface and the ports in the car.
Start the VAG-COM program on your PC through either the Start Menu or the icon on your Desktop. G
Turn the vehicles ignition switch to the ON position. Make sure the key is turned far enough that the dash lights are fully illuminated. The engine may either be running or stopped. From the Main Screen in VAG-COM (shown on Page 6 of this Manual) click the [Options] button to go into the Options screen (shown on Page 31 of this Manual).
H Select the correct port for your PCs Serial Port (typically COM1 or COM2) or USB Port (USB) and click the [Test] button. Ensure that VAG-COM finds your interface. You should see a message like this. If the Adapter Status is not Found!, check the connections at the car and PC. Make sure both are plugged in securely. If K1 or K2 status is not OK, you may have a short or an open circuit in the cars diagnostic port (most likely caused by the Aftermarket Radio Problem, as shown in the FAQ in Appendix B of this manual).
Once you have tested successfully, click [OK] and click [Save] to apply this configuration, you will be returned to the Main Screen. Click on [Select Control Modules] to view the Select Control Module Screen (as shown on page 7 of this manual). Select one of your car's Control Modules such as Engine After VAG-COM has connected, click on [Fault Codes] to check for Fault Codes (DTCs). Repeat the process for each of your car's Control Modules. If you encounter problems, see the FAQ in Appendix B of this Manual first. If you still have problems, feel free to contact us with full details about your PC and vehicle, preferably while you are in front of both. Note: Your car will not have all the Control Modules listed in VAG-COM, only the ones on the Applications Page for your car. See our Website for more info: www.Ross-Tech.com/vag-com/cars/applications/

Main Screen

This screen appears when you start VAG-COM by clicking the shortcut on your Desktop or by selecting VAG-COM from the Start Menu. On this screen, you have 7 buttons that you can click with your mouse: [Select] [Auto-Scan] [Control Module Finder] [OBD-II] [Options] [About] [Exit] (This closes the VAG-COM program) See our Website for an Interactive Online version of this manual: http://www.ross-tech.com/vag-com/tour/

Basic Functions This grouping of "Safe" functions are used to read data from the Control Module. Grayed out buttons are functions that have not yet been implemented or are not applicable for this specific controller. Each of these functions is detailed on the following pages. Advanced Functions These functions are capable of making various "programming" changes to the Control Module. You should refer to the Factory Repair Manual for your particular car (or to other documented procedures) before "playing" with these functions. It is completely possible to render your vehicle inoperable or damage components if you make changes in this section without the correct information and training. Each of these functions is detailed on the following pages. Use [Close Controller, Go Back - 06] to properly close the communications session and return to the Select Control Module screen.

Fault Code Screen

On this screen, VAG-COM shows you any DTC's (Diagnostic Trouble Codes or Fault Codes). VAG-COM shows the DTC numbers and also decodes each DTC into meaningful text. G [Print Codes] will print a Fault Code Report. If your PC is not connected to a printer when this button is pressed, be sure to use Windows to set the printer to "Work Off-Line" first! Later, when you connect the PC to a printer, un-check "Work Off-Line" to print the report. [Copy Codes] will copy your fault codes to Windows Clipboard. Once you have pressed the Copy Codes button, you may paste the results into the application of your choice, such as MS Word or Notepad.
H [Freeze Frame] adds Freeze Frame data for Fault Codes on control modules using the KWP-2000 protocols. Note: Not all control modules fully support this; very few cars can currently handle freezeframe data using the VAG proprietary protocols. Self-explanatory messages will appear in place of data when this function is not supported.
[Clear Codes - 05] will erase the DTC's from the Control Module's memory. Be aware, this is does not fix the problem that caused the fault! DTC's should only be erased after correcting the condition(s) that caused them in the first place. Note: There is no way to erase individual DTC's while leaving others alone. This is not a limitation in VAG-COM it's just the way the VAG protocols work. [Go Back] takes you back to the main Control Module screen where you can select other functions.
Measuring Blocks (VAG 1551/1552 function 08)

On this screen, you can read all sorts of data from the Control Module in real-time. Use [Up] and [Dn] to scroll through the available groups (000 - 255 on most Control Modules). Don't become discouraged when you find some that say "ERROR: Group xxx Not Available" or if you find some groups where the fields are all blank. Most 1996 and newer ECU's have Groups in the 200 range, but there are often "gaps" in the numbers. You can also type a Group number into the Group box and click [Go!] You can also [Log] the data from the measuring blocks. For more information see page 13 Data Logging. [Switch to Basic Settings] can be used to go to Basic Settings for the Group that is currently being displayed. This should be done only under guidance from the Service Manual or when following some other documented procedure. For more information see page 19 Basic Settings. NOTE: Multiple Groups are not permitted in Basic Settings. The [Switch To Basic Settings] button is intentionally disabled if you have groups "running" in the second and third rows. To stop a running group, click on the box that displays the group number (as though you wanted to enter a new number). This button is also disabled on controllers using KWP-2000. On those, you need to go directly to the Basic Settings screen. The data presented in each Measuring Block Group varies greatly from Control Module to Control Module and between different models and years. Some groups are documented in the Factory Repair Manuals, but many are not. Feel free to explore the Control Modules in your car by scrolling through all the Groups. You can't hurt anything with the Measuring Blocks function!

Measuring Blocks cont.

In each case, VAG-COM will attempt to "scale" the raw data coming from the Control Module into real-world units like degrees C, km/h, etc. At the present time, all scaling conversions are to metric units. Note: Group 000 and any other group that displays 10 fields instead of 4 is an exception. No scaling is possible because the Control Module provides no "Data Type" information with the data for these. Groups of this type can only be displayed in the top row of the screen. VAG-COM also tries to elaborate as much as possible what the data means. Unfortunately, the "Data Type" information coming from the Control Module is not that precise. For example: VAG-COM can tell that a particular field contains a Temperature, but the data from the Controller doesn't tell us whether this is the Coolant Temperature or the Intake Air Temperature. To reduce the confusion, VAG-COM supports Label Files and will display the name of the Label File. When a Label file for the Control Module you are looking at does not exist, VAG-COM will come up with an "educated guess" for what a particular Data Type means. The dealers' VAG-1551 and 1552 scan-tools do not provide any elaboration; they only show whats in the display fields! Sample Rate: We can get just over 4.0 samples per second from our '97 VR6 ECU (single group) with the most aggressive protocol-timing settings. This ECU runs at 9600 baud. Most newer ECU's run at 10400 and should give proportionately more. Naturally, if two groups are being displayed simultaneously, the sample rate drops to around 2.0, and 3 groups simultaneously runs at around 1.3. Sample Rate will vary from controller to controller and the PC used will also have some effect. Some controllers (particularly AG4 transmissions and Digifant-III ECU's) use a "hybrid" datatype that requires reading a long header when changing group numbers. Viewing multiple groups still works with these data types, but the sample rate becomes extremely slow. If you see "Reading Header" all the time under the Sample Rate display, you'll know you've got one of these. In Engine controllers using KWP-2000, there is a [Turbo] button in Measuring Blocks screen of the latest version of VAG-COM. Pressing this button can significantly speed up sampling, in some cases to over 30 samples per second when logging a single group. Once you have pressed [Turbo] you will remain in this High-Speed mode until you exit the Measuring Blocks screen. [VAG-Scope] is a plug-in for VAG-COM that allows you to graph Measuring Group Information. See Appendix C for information on VAG-Scope. Use [Done, Go Back] to return to the Controller Info / Select Function screen. Warning! If you wish to observe real-time data while driving the car, use a second person who is not in front of an active airbag!

Single Reading (VAG 1551/1552 function 09)
This function allows you to look at real-time data from control modules that support it. However, the data stream coming from the control module gives NO CLUE what the data means or how to scale it into real-world values. The only way to know what the values mean is to find a reference to this function in the Factory Repair Manual for your car. This function is rare, but it is used, for example, with some OBD-I 2.8L 12V V6 engines. The very name of this function annoyed us, so we added a twist. You can look at two channels of "Single Readings" at once! Use [Done, Go Back] to return to the Controller Info / Select Function screen.
View Readiness (VAG 1551/1552 function 15)
The Readiness Code is a set of 8 bits, each of which corresponds to one monitored emissions "system" in an OBD-II car. When all readiness bits show "pass", it means that all systems have been checked and pass the on-board tests. Whenever you clear DTC's or remove power from the ECU, all readiness bits will be set to "fail". Most cars do not have all 8 systems, so as soon as you apply power again, the bits corresponding to systems that are not actually in the car will come up "pass" again. The above screen-shot was taken immediately after clearing the DTC's in a 1997 VR6. You can see that this car does not support "monitors" for the EGR, Catalyst Heating, or Air Conditioning because this specific car does not have EGR or Catalyst Heating. It does have Air Conditioning, but a "monitor" is only required if the system uses ozone-depleting refrigerant (R12). It takes a variety of specific driving conditions to "test" all the systems. It can be done in a short time using a very specific and complicated procedure found in the On Board Diagnostic section of the Factory Repair Manual for your engine. The alternative is just to drive the car for 2-3 days. Make sure you include at least one short highway trip and your Readiness Bits should all read "Pass" again. Use [Go Back] to return to the Controller Info / Select Function screen. Note: This function is only available on Engine Controllers that are OBD-II compliant (all 1996 and newer US-Model gasoline engines). Non-US models and TDI's may not support this function even though they are otherwise OBD-II compliant. OBD-I did not require any "monitors". 12V 2.8L V6 engines may have readiness bits stored in or near Measuring Block Group 029.

Basic Settings cont.

VAG-COM also tries to elaborate as much as possible what the data means. Unfortunately, the "Data Type" information coming from the Control Module is not that precise. For example: VAG-COM can tell that a particular field contains a Temperature, but the data from the Controller doesn't tell us whether this is the Coolant Temperature or the Intake Air Temperature. To reduce the confusion, VAG-COM supports Label Files and will display the name of the Label File. When a Label file for the Control Module you are looking at does not exist, VAG-COM will come up with an "educated guess" for what a particular Data Type means. The dealers' VAG-1551 and 1552 scan-tools do not provide any elaboration; they only show whats in the display fields! Use [Done, Go Back] to return to the Controller Info / Select Function screen. The most common use for the Basic Settings function is to recalibrate the Throttle Body (sort of like having a Chiropractor do an adjustment on the engine). Another common use for Basic Settings is to bleed the ABS Hydraulic Unit on newer cars. Please refer to a Factory Repair Manual for your car before attempting to do any of these procedures! You can begin and end a Data [Log] while in Basic Settings. See page 13 for information on Data Logging. Basic Settings in KWP-2000:
On Controllers using KWP-2000, there is an [ON/OFF] button that allows you to initiate and exit Basic Settings while still being able to see the values in the measuring groups.
Output Tests (VAG 1551/1552 function 03)
The Output Tests function is used to test a Control Module's Electrical Outputs (and the wiring that connects it to the various devices). Output Test under KWP-2000 includes simultaneous measuring data To begin Output Tests, and to progress through each step, click [Start/Next]. Notes: The Outputs that can be tested and the sequence in which they become active is controlled strictly by the Control Module; this is not a function of the Diagnostic Tester. To find out which Outputs can be tested and the sequence in which they will become active, please refer to the Factory Repair Manual for your car. Once the Test Sequence once it has been started, clicking [Done, Go Back] will take you back to the Open Controller Function Screen. THE TEST SEQUENCE WILL STILL BE ACTIVE! Most Control Modules will permit the Output Test Sequence to be run only one time per session. If you run the Test Sequence to completion, VAG-COM will allow you to return to the previous screen without closing the session, but you may not be able to run the Output Test Sequence again. If you need to run the Sequence again, manually Close the Controller and re-start the session. On some cars, you must cycle the key OFF and ON or even start the engine (to clear the cylinders of fuel). Some Outputs require additional action before they become active. Fuel Injectors are a common example. To activate a Fuel Injector, you must press (and in some cases release) the gas pedal. Exact details can be found in your Factory Repair Manual. On most systems, the Output Test function is only available when the Engine is not running. Warning: Do not use the Output Tests function on any system while the car is in motion! Running Output Tests on the ABS brake system can temporarily disable the brakes entirely and cause individual wheels to lock and unlock. We strongly suggest you refer to the Factory Repair Manual for your specific car before running Output Tests on any Control Module so you will know what to expect! Use [Done, Go Back] to return to the Controller Info / Select Function screen.

Options Screen

On this screen you can set a number of Options. Select Com Port Set the COM Port to which you have connected the Interface Adapter. You can then click [Test] to see if VAG-COM can find the adapter. See the Getting Started section on page 2 for more information. The [LEDs] button is useful for testing a port's outputs with the Interfaces that have LED's. Debug Output Level A zero in this field (the default) means NO debug output will be generated whatsoever. This should decrease VAG-COM's susceptibility to interference by things like virus scanners (except when logging data). To generate Debug Output, put a number in this field. The number should of a reasonable size, such as 100. Small numbers will generate very little information. Left Margin Printing This is the number of spaces that printed pages are shifted to the right. Color Scheme This display mode changes the background color from blue to white, and looks better on some older monitors. The change will take effect after you close and restart VAG-COM.

Options Screen cont.

Protocol Options Start Baud is the first baud rate that VAG-COM will try when connecting to a controller. The current default value is 0. This means VAG-COM will determine the correct start baud on its own. With the HEX-COM or HEX-USB Interface, this field is unavailable since they figure out the Start Baud automatically. KW2 Delay has to do with the amount of time used during the initialization of a session between the PC and the car. The current default value is 30. Do not change this value from the default unless you are having difficulties communicating with a particular controller. Contact us for advice if you are. TST Addr. has to do with the packet addresses used by KWP-2000. The current default value is -1. Do not change this value from the default unless you are having difficulties communicating with a particular controller. Contact us for advice if you are. Blk Int affects the protocol timing. The current default value is 55. To get the highest sample rate possible in the Measuring Blocks screen, set this to 25. Note, however, that this may cause unreliable communications with some controllers. Char lnt also affects the protocol timing. The current default value is 1. To get the highest sample rate possible in the Measuring Blocks screen, set this to 0. Note, however, that this may cause unreliable communications with some controllers. The KP2 Time parameter only applies to controllers using the KWP-2000 protocol. The current default value is 25. Decreasing it increases the sample rate in Measuring Blocks on control modules that use the KWP-2000 protocols. The default value should be safe for all applications, but if it's not, you can always increase it again (to a maximum of 99). Using the Reduce CPU Usage checkboxes will greatly increase responsiveness of other apps running at the same time as VAG-COM. The disadvantage is somewhat reduced sample rate. o KWP-1281: The default value is unchecked. This reduces CPU usage when connected to controllers using KWP-1281. Using this feature *may* make the session with some control modules unreliable. o KWP-2000: The default value is unchecked. This reduces CPU usage when connected to controllers using KWP-2000. Force HEX Dumb causes the HEX-COM or HEX-USB Interface to function like a dumb Interface, so the PC handles all protocol timing, rather than letting the Interface take care of timing. This should not be necessary with any known controllers.

2000-2001 VW Golf/GTI/Jetta/Beetle Airbag System (important!) We have had a number of reports of Air Bag Warning Lights staying on permanently after scanning with VAG-COM. The Air Bag Controller shows DTC number 65535, indicating an internal error which cannot be cleared. This problem seems to be limited to airbag controllers with the part number: 6Q0-909-605-A. There are a number of different "Index" or "color-code" variations of this controller and not all of them are affected, but we haven't got a definitive list of which ones are which. If you have a 2000-2001 Golf, Jetta/Bora, Beetle, or a similar SEAT or Skoda model, you should physically inspect the airbag controller and look at the part number. If it is not 6Q0-909-605-A, then it should be safe to scan. If it is 6Q0-909-605-A, then it is at risk of this problem -please avoid scanning the airbag controller in these cars, unless you are prepared to buy a new one!
Appendix A: VAG-COM Problems & Issues cont.
2000-2001 VW Golf/GTI/Jetta/Beetle Airbag System cont. So, can you unintentionally connect to the Airbag controller? When you try to access the Airbag controller, you need to click on Airbags in the Select Control Module screen. Then, you are confronted with a disclaimer screen asking if you really want to proceed, the default answer is "No". We have no reports of people scanning their airbags by mistake with these safeguards in place. Also, please note the disclaimer on the Download Page. If you have a vehicle with the affected part number and are concerned, simply do not scan the airbag controller. Accessing the other control modules in the car should not affect the airbag controller in any way. Comment: There is no way that scanning a controller should cause it to become dysfunctional in this manner, even if the scan-tool fouls up in some way. We believe there is a bug in the firmware in these controllers. We also believe VW knows this, but isn't admitting it. The affected controllers are no longer available as replacement parts, they have been superceded by a new part number: 1C0-909-605-A which appears not to have this problem. On the previous page is the location of the airbag Controller in the Golf/GTI/Jetta: (Thanks to Drew Weirshousky for the excellent photos!) 1997 VW Passat B5 Central Convenience System These controllers seem to have a bug that causes them to drop the communications session when VAG-COM requests the door-slave controller "Extra" info. A work-around is available in Version 0.70e which simply does not request any "Extra" info. If you have a 1997 B5 Passat (non-US models only), use 0.70e on the Central Convenience system. 1998 and newer Passats do not have this problem. 1990-1992 VW 2.0L 16V Engines Works fine with the HEX-COM and HEX-USB. If you're using a "dumb" interface, you must set the Start Baud on the Options Screen to 4800 to get these to work. If you have anything else in Starting Baud Rate, the ECU will "choke" and you'll need to turn the ignition OFF and back ON again before you can communicate. 1990-1993 VW Cabrio/Cabriolet Airbags These controllers do not communicate with VAG-COM. In fact, they do not communicate with Volkswagen's VAG-1552 scan tool either, unless the 1552 has an old, outdated program card installed. 1994-1997 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 VAG-COM's low-level protocol drivers as of version 0.70 seems to take care of this in a majority of cases, but I 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 PC's try a higher value. On very slow PC's, try something less. 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.

1995-2000 VW Sharan Electrical Controller (address 09) These controllers have some strange bugs in the protocols which prevent them from working with VAG-COM. We hope to have a fix for this in the near future. Concert 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. Some Concerts 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 the radio for at least 10-15 seconds. This can be done by:
Removing the radio from the car. Disconnecting the car's battery Pulling the fuse for the radio.
Note: Some radios will require you to enter the "security code" using the radio's front panel after loosing power. See the owner's manual for the radio for instructions. It appears 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). 1992-1994 2.6L V6 Engine (non-US only) VAG-COM cannot 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 the HEX-COM or HEX-USB Interface, which work great. 1996-1997 Audi A6 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.
Appendix B: VAG-COM Frequently Asked Questions (FAQ)
Q: Will VAG-COM work with my car? A: VAG-COM will work with most Volkswagen and Audi models sold World-Wide 1994 through 2004. It will work with some cars all the way back to model year 1990. It will also work with most late-model SEAT, and Skoda models sold in markets other than North America. If your VW or Audi has a 16-pin "OBD-II style" Data Link Connector, VAG-COM will definitely work. If your car has the old "2x2" Data Link Connection, check if there is a wire going to each pin, as shown in the picture. If there are four wires, VAG-COM should work. If there are only three, it won't. Please see these Application Charts where you can select your model and see which modules can communicate with VAG-COM. Also see the Issues page for a few things that may not work as expected. If in doubt, e-mail us. Please see these Application Charts at: www.Ross-Tech.com/vag-com/cars/applications/ where you can select your model and see which modules can communicate with VAG-COM. Also see the Issues page for a few things that may not work as expected. If in doubt, e-mail us. Q: Will VAG-COM work even if my car is "chipped"? A: Yes. If it doesn't work in a "chipped" car, the chip-vendor did something seriously wrong! Chips from reputable vendors are fully VAG-1551 (and VAG-COM) compliant. Q: What functions are included in the current release? A: VAG-COM is a software program that turns your PC into sophisticated VW/Audi diagnostic tool, which performs the functions of a factory VAG-1551 or VAG-1552 scan tool. Please see the Function Chart in Appendix E for the current feature set. Q: What are the computer requirements? A: A PC running Windows: We recommend at least a Pentium-100 (or AMD equivalent) with 16MB of RAM and Windows 95 or newer. VAG-COM may work on some lesser PC's, but anything less than the above recommendation is unsupported. Windows 95, 98, ME, NT4, 2000, and XP are all fine. Available disk-space is a total non-issue, VAG-COM requires less than 1 MB. To use one of our Serial Interfaces, the PC must have an available RS-232 Serial port! Otherwise, you'll need to choose one of our USB Interfaces.

Observe the port we surrounded with the GREEN oval. Notice the 9 MALE pins? That is a SERIAL port and WILL work! Observe the port circled and crossed in RED. Notice the 15 FEMALE pins? That is a MONITOR port and will NOT work!
Appendix B: VAG-COM FAQ cont.
Q: What if my Laptop doesn't have a Serial Port? A: We now offer our own USB Interfaces which use the USB port on your PC, rather than the Serial Port. We even offer USB Interface Upgrades for existing Ross-Tech customers. These interfaces work best with Windows XP. If you have a PC that doesn't have a Serial port and it has a version of Windows prior to XP, we strongly urge you to update to Windows XP before installing VAG-COM. Realistic hardware requirements for Windows XP and VAG-COM are a 500 MHZ CPU with at least 128 MB or RAM. If you want to use one of our RS-232 Serial interfaces (especially the HEX-COM) on a PC that doesn't have a serial port, we recommend you buy this Quatech SSP-100 PCMCIA-Card. We don't sell them, but we've had excellent results with them. See our website for installation and configuration notes. USB<->RS-232 converters are often unable to handle the baud rate and timing requirements that are demanded by many control modules using the VAG protocol. We have had very poor results with most available USB<->RS-232 converters, therefore USB<->RS232 converters are "Not Supported." Please do not ask us for technical assistance if you are using one of these converters. Q: Can I use VAG-COM on a desk-top computer? A: Yes, but you will probably need an extension cord for your interface. We usually stock serial extension cables in 15' (3m), 25' (7.5m) and 50' (15m) lengths. Note: We do not support the use of extension cords with our USB interfaces. The USB standards specifically exclude the use of extension cords. Q: What if the PC I wish to use with VAG-COM doesn't have Internet access? A: Because our software is provided to you via our download page, rather than on floppy disks or CD's, you will need a way to transfer the Self-Installing EXE file to the PC that you will be using with VAG-COM. The file fits easily on a floppy disk and can also be burned onto a CD-R or CD-RW. Make sure that you do not run the EXE file until you have copied it onto the PC where you would like VAGCOM to be installed. Additionally, in order to activate VAG-COM, you will need to copy and paste the Serial Number from the PC that you will be using with VAG-COM into our Registration Form. Likewise, when we return your Activation Code, you will need to copy and paste that into the PC that you will be using with VAG-COM as per the instructions on our Activation Page. Q: Will there be a Mac or Linux version? A: There will be no "native" Mac or Linux versions. The time and effort required to "port" VAG-COM to these platforms would never pay. One person has gotten VAG-COM running under Linux using WINE -- click here for details. Several people have tried various PC/Windows emulators for the MAC, but we have no reports of success on that platform. If you get VAG-COM working on a Mac, we'd be happy to give you credit here, just don't expect to receive any support from Ross-Tech for that platform.

Q: Why has VAG-COM become De-Activated on its own? There are a few conditions that can cause previously-registered installations of VAG-COM to become De-Activated:
Performing major systems maintenance like upgrading your operating system, swapping hardware or reformatting your hard drive will "kill" an activation. If you're going to do maintenance of this type, manually de-activate first -- see the previous question. A problem with your system clock such as a dead CMOS battery, or manually setting the system clock backwards in an attempt to defeat the time limit on other shareware products. VAG-COM's Serial Number may change if it perceives that is has gone "back in time". A PC without a properly functioning system clock is considered defective. The use of some "System Cleaning" utilities that root around in the Windows Registry can kill the activation. "Machine Gun Clicking". We have not been able to reproduce this here, but have enough reports from users to believe that it happens: If the user is impatient and "machine-gun" clicks on the VAG-COM icon and causes a second instance of VAG-COM to begin loading before the first instance has finished loading, it can "kill" the activation. This appears to be most common on older, slower PC's, and PC's which have a marginal amount of RAM for the version of Windows that is installed. Current release versions (208.X and newer) contain code to prevent multiple instances of VAG-COM from loading. If you're still running any older version, we'd like to suggest you download an update. If you're an existing registered user with a "dumb" interface, Beta 310.0 or newer will remain shareware until you request a new activation code. Legitimate activations for previous versions won't be affected. Existing registered users with dumb interfaces must complete the short form to request a new activation code for Beta 310.0 or newer. Requests submitted via e-mail or forms with incomplete information will be rejected and will delay your activation. Intelligent Interfaces (HEX-COM and HEX-USB) are not affected by this.

Q: What is the purpose of the "OBD-II" button? Why would I want to press it? A: See the OBD-II section of this manual for more information. You can use this test to determine whether a car is ISO/OBD-II compatible, i.e. whether it "speaks" the OBD-II protocols, if the car uses the ISO-9141 hardware layer for OBD-II. This has nothing to do with the VAG protocol that VW uses, and the results of this test have nothing to do with VAG-COM working with any VW/Audi/SEAT/Skoda vehicle. No VW or Audi products prior to model year 1996 are OBD-II compliant! Please note that most vehicles sold outside of the US are NOT OBD-II compatible, and even US-market TDI's are not OBD-II compatible. Additionally, the newest vehicles using KWP-2000 are not scannable with generic OBD-II scanners. Q: How do I print screens or data in VAG-COM? A: Currently, the only printing feature built into VAG-COM is the Print Codes button on the Fault Codes screen. You can save data to a Log file and print using a spreadsheet program. Also, you can use a Print Screen utility to capture a current screen and print it. Q: What are Label Files? A: Please read The Label Files Page on the Ross-Tech website: www.ross-tech.com/vag-com/labels.html Q: How can I speed up my sample rate in VAG-COM? A: The sample rate at which you can view and log data is largely determined by each controller in the car. There are a few things you can do to speed up the rate for a given controller. First, logging one group at a time, rather than two or three, will help greatly. In order to get the highest sample rate possible go to the Options screen and set Blk Int to 25 and Char Int to 0. Note, however, that this may cause unreliable communications with some controllers. The KP2 Time parameter only applies to controllers using the KWP-2000 protocol. Decreasing it speeds up the sample rate in Measuring Blocks on control modules that use the KWP-2000 protocols. Try setting it to 0. If any of these adjustments cause unreliable communications, change them back closer to the defaults. If in doubt, use the Restore Defaults button! In Engine controllers using KWP-2000, there is a [Turbo] button in the latest version of VAG-COM. This can significantly speed up sampling, in some cases to over 30 samples per second. See the Measuring Blocks page for more information. Q: What kinds of cool stuff can I do with VAG-COM? A: See our Car Info & Procedures Page on the Ross-Tech website: http://www.ross-tech.com/vag-com/cars/index.html You can look up Vehicle Specific Application Charts for your car to see which control modules exist and can communicate with VAG-COM. Additionally, there are some very useful links to pages about Key Matching, Immobilizers, as well as some excellent spreadsheets submitted by our customers. Q: How do I set up my HEX-USB or TWIN-USB Interface? A: To use one of our USB Interfaces, you'll need to download and install the latest version VAG-COM with USB Support. After you have installed VAG-COM, you will need to follow the instructions on the USB driver installation page on the Ross-Tech website: http://www.ross-tech.com/vag-com/hex-usb/usb-config.html

* KWP-1281: The original VAG Diagnostic Protocol. Used on all diagnostic-capable systems from 1990 through model-year 2000. ** KWP-2000: The "new" VAG Diagnostic Protocol. Used on a few 2001+ ABS systems and some 2002+ Engines, Transmissions, and Airbags.

Diagnostic Software

For VW/Audi/Seat/Skoda/Bentley
Ross-Tech-Tip - VW/AUDI Control Module Coding
People often struggle to determine the coding when replacing a control module in a VW or Audi vehicle. Since there can be many choices based on the equipment installed in the car, how does one know which codes to use? VW/Audi anticipated this problem. Each vehicle comes with two copies of the build sticker. The first is in the maintenance booklet. A sample is shown in the label above. This sticker shows all of the installed equipment in the vehicle. If the maintenance booklet is not in the vehicle, a second copy of the sticker should be located near the spare tire well in the trunk as shown in the photo above right on an 8P chassis Audi A3. Understanding the information on the sticker is key. All of the installed options are listed in the form of 3-digit production codes called PR codes as shown on the label above (taken from an 06 Audi A3). As an example of the use of these codes, assume that an ABS module failed on this A3. The old module is dead and wont communicate with a scan tool so the original coding cannot be retrieved. Using the PR codes and a reference such as a repair manual or the information found on the Ross-Tech Wiki (wiki. Ross-Tech.com), we can still figure out the coding needed. For our example we are using this specific Ross-Tech Wiki reference: http://wiki.ross-tech.com/index.php/Audi_A3_ (8P)_Brake_Electronics_(MK60)#Coding
We have to assemble the module coding by relating the PR code for the options that are present to the actual code value needed by the module. Once these are found, we then sum all of the code values into one code number.

DESCRIPTION

Vehicle Model Code Front Brake Option Scan PR codes on the sticker for a match of possibilities found in the reference. Match = 1LJ new sensor cluster for FNIII 54 15/16 Suspension Type Scan PR codes on sticker Match = UA1 Standard/Sport Suspension Engine Code- Engines is 2.0l FSI Tire Pressure Monitoring System (TPMS) - Match=7K0 - Without TPMS Sum of all codes = new coding

CODING

+0000000

+0000002

+0000640
+0004096 +0016384 +0021122
Use your diagnostic tool to enter 0021122 as the coding for the replacement module.
First appeared in Motor Age Magazine, June 2009 , Copyright 2000-2010 by Ross-Tech LLC

www.Ross-Tech.com

For more information visit:
Ross-Tech, LLC 881 Sumneytown Pike Lansdale PA 19446, USA Tel: +1 267-638-2300