![ross tech vcds 12.12 espanol ross tech vcds 12.12 espanol](https://www.obdtools.net/images/upload/Image/Ross-Tech-VCDS-v2-20-12-0-1.jpg)
- Ross tech vcds 12.12 espanol drivers#
- Ross tech vcds 12.12 espanol update#
- Ross tech vcds 12.12 espanol driver#
- Ross tech vcds 12.12 espanol software#
- Ross tech vcds 12.12 espanol code#
Ignore the soldering marks on the USB red wire.
Ross tech vcds 12.12 espanol software#
Just follow the directions in the info file in Kolimer's software package.
Ross tech vcds 12.12 espanol update#
Just flashed the cable (failed 2x before 3rd times a charm) following by running vcds via vcdsloader, update to 1.96 and everything works. Was fortunate the cable (friend bought it a couple of years back) had bootloader enabled so no need for any HW mods. Used Kolimer's VCDS Loader v7.1 got it all working perfectly with VCDS 18.9. Vag12.12 cable disabled by newer than 12.12 vcds or networked vcds. Thank you all in advance and have a nicer day,
Ross tech vcds 12.12 espanol code#
21.9 or 22.3 bring me any advantages for my "old" car (Passat B6 09/2005) compared to the version 17.3.1? I actually use the cable only for fault code readout and reset - no coding at this time. Question regarding the mentioned ATmega162 cable: does the newer software (currently I use 17.1.3) e.g.
![ross tech vcds 12.12 espanol ross tech vcds 12.12 espanol](https://www.obdtools.net/images/201806/goods_img/864_P_1529564749392.jpg)
Since that, the cable works again as supposed to. Solution: uninstall/remove everything Ross Tech related and reinstall everything again. With the help of another user (directly by DM, thank you again!) we could solve the problem: the VCDS software have a kind of pirating protection and after a while of usage, the software don't recognize the cable anymore. You can update firmware to 1.96 with this package and use vcds 21.9 or 22.3 It’s a fake Hex-v2, it’s a hex can with ARM chip based, but it’s not the best hex-can ! The best is Atmega162 chip based.
Ross tech vcds 12.12 espanol drivers#
I tried change of version of vcds tried whit difrent drivers loaders but no useĬan sombady help me i dont know what next to do This time he entered module on car but after few secunds give me a messege no response from controller! I start vcds whit interface and he ask me to update offlineĪnd her are pictures of all proceses what i do Then i use vcds usb eeprom write english language selected and finished that
![ross tech vcds 12.12 espanol ross tech vcds 12.12 espanol](https://www.obdtools.net/images/201809/goods_img/907_P_1537368197132.jpg)
Ross tech vcds 12.12 espanol driver#
I tried to reinstall the driver by deleting and the installation failed I deleted the entire program from the laptop reinstalled failed againĪs far as i know this is a clon version not orginal ross techĪfter that i get help from Mario6 to take look on this post and download all i need but after i use vag com hw type to see is bootloader enabled and yes it is The interface blinks green when connected to the car I run vcds I click select and then the modules that have any on the car to click just a little as an attempt to open and nothing happens I can not access any module When the laptop was connected it blocked and since then I can't connect to any module on the car The problem started after a recent connection to the vehicle. I have vcds 21.9 kolimer loader v9.2 hex v2 atmega 162 2117E17 FTDI FT232RQ It needed cutting line to stc chip and soldering icsp programeer. If I have read right, will the HEX-V2 do the job needed straight out the packet? only job needed is the re-flash from VAGCOM_EEWriteLang.exe utility? which is a simple job right?I have a similiar type of cable, just diffrent pcb color. When that said it took me nearly a year of research to figure it out. This protection is irreversible (JTAG fuse), so it is impossible to go back to protection Level1 or 0."ĭespite this I found a way to revert it so I would not say it is impossible. However, booting from SRAM or from system memory bootloader is no longer possible. When booting from Flash, the memory content (single-wire viewer), ETM, and boundary scan are all disabled. The RDP option byte and all other option bytes are frozen and can no longer be modified. "When RDP Level 2 is activated, all protections provided in Level 1 are active and the MCU is fully protected. This will completely disable the debug interface so you wont get any response if you connect a debugger. If I have read right, will the HEX-V2 do the job needed straight out the packet? only job needed is the re-flash from VAGCOM_EEWriteLang.exe utility? which is a simple job right?įrom J2 and right (the one with the small square) you have (The side of the PCB with the STM chip)īoth the bootloader and the firmware will check the RDP level and set RDP2 if not previously set. Start by reading the readme file first, it has detailed explanationĪfter reading the destruction manual, I've decided its better that I don't try and modify my lead, I'd prefer to keep it intact in its current operational state which I can keep as a backup, and purchase another lead which is preferably already good to go, is there a pre-configured lead? which somebody could recommend I buy? and from a recommended seller? (A bit like is recommended in the Autocom thread, in the "Read me" file there is the recommended lead from the recommended seller for that particular software which I purchased last night, in the hope it will be less problematic) Browse several pages back, find link for kolimer's loader v9.2.Īll you need is inside that package, but only if your bootloader is unlocked.