The VCDS 16.80 interface, often found in the “Windows 7 Vcds 16.80.rar” archive, is a popular tool for diagnosing and modifying Volkswagen and Audi vehicles. However, using it with newer VCDS software and loaders like Kolimer 9.2 often requires an update. This guide outlines the steps involved in updating a HEX-USB interface (HW type 0x46) with firmware version 1.96 for compatibility.
Understanding the Update Process
Updating your VCDS interface involves flashing the ATMEGA162 microcontroller with the correct firmware. This process requires specific hardware and software, along with careful execution to avoid damaging the interface. Before proceeding, it’s crucial to understand the soldering points and the necessary files.
Preparing for the Update
Several key preparations are needed before flashing the ATMEGA162:
-
Disabling the STC Chip: Lifting pin 9 of the STC chip is crucial to prevent interference during the flashing process. While some debate exists on whether to remove it completely, lifting the pin is generally sufficient. Resoldering is typically not necessary if the pin is carefully lifted.
-
Connecting to the ATMEGA162: Soldering a wire to pin 4 (RESET) of the ATMEGA162 is necessary for the programmer to communicate with the chip. Due to the small size of the pins, precise soldering is critical.
-
Connecting to the MCP2515: This chip handles communication with the car. Three wires need to be soldered:
- Pin 13 (MOSI)
- Pin 14 (MISO)
- Pin 15 (SCK)
-
Power Supply: Connecting VCC and GND to a stable 5V power supply, such as a linear voltage regulator (L7805CV), is recommended for programming. Using the car’s 12V supply is generally not advised during this process.
Executing the Flash
With the hardware connections in place, the next step involves using a USBASP programmer and the correct firmware file.
- Firmware Selection: For German language support in VCDS, the “eepromavr_HW_0x46_DRV.bin” file is typically used. The “USBASP_write_0x46.cmd” script might need to be modified to point to this specific file.
- Flashing Process: Running the “USBASP_write_0x46.cmd” script usually initiates the flashing process. Running it as administrator is generally recommended. Consult the USBASP documentation for specific instructions.
Post-Flash Procedures and Considerations
After flashing, several questions often arise:
- Verification: The VAGCOM_HWType.exe tool can be used to verify the success of the flash. The output should reflect the updated firmware and hardware version.
- Bootloader: The bootloader on these interfaces is typically disabled by default. Flashing does not automatically enable it. Manual flashing will likely be required for future updates unless a bootloader-enabled firmware is specifically used.
- STC Chip Functionality: Removing the STC chip entirely might allow the interface to function with newer VCDS versions and loaders without flashing. However, this is not always guaranteed and should be approached with caution.
Conclusion
Updating a VCDS 16.80 interface for compatibility with newer software and loaders can be challenging. This guide provides a comprehensive overview of the process. However, it’s crucial to consult detailed instructions and resources specific to your interface and the chosen programming method. Remember to proceed with caution, as incorrect procedures can permanently damage the interface.
