![vcds 12.12 vs 18.4 vcds 12.12 vs 18.4](https://fr.chinaobd2.com/upload/pro/3739-vag-com-12-12-vcds-hex-can-usb-interface-for-vw-audi.jpg)
If by any chance do you (or someone else) has the ability to create a dump of this cable from the Atmega? This could get mine back to its previous state. I guess I am doomed and my only move is to go back to one of the available packages here and flash either 12.12 or 11.xx and live with it. The only thing I can imagine is the Atmega contents. So something else on the cable must have changed. Crap!!! In my case the FTDI232RL still reports the proper VID/PID 0403/FA24 and gets recognized correctly. Now I understand that the real VCDS.exe probably recognized the black-listed serial when launched without the loader and swiftly went ahead and erased the Atmega. In my despair I launched that process directly. My mistake was that I did notice the real VCDS got created in a temp folder.
#Vcds 12.12 vs 18.4 cracked#
My (non-educated guess) is that the EEPROM contents or the complete Atmega (EEPROM and firmware) got deleted and thus when the loader of the cracked Chinese 15.7.0 version queries it the results are wrong and it refuses to launch the real VCDS.exe. I tried a fresh install of WinXP and Win7 both x32 and 圆4 and nothing works. The loader starts and then quits every time. Now the Chinese SW doesn't even come up anymore.
![vcds 12.12 vs 18.4 vcds 12.12 vs 18.4](https://www.njuskalo.hr/image-w920x690/ostala-autooprema/vag-com-12.12-hex-can-vcds-najpovoljniji-slika-33252585.jpg)
K-line based generic OBD-2 created tons of errors. When it did start I got extremely spotty performance. In my case I got the Chinese SW that came with it to start only once or twice. If that is present it's an issue with incompatible or erased firmware in the Atmega. The only advice is to check the 100 Ohm termination resistor on the inputs of the CAN transceiver chip TJA1050 pin 6 and pin 7. Your cable is the exact one I am struggling with. My old 11.3 work perfect! Does anyone have schematic diagram or maybe solution for this problem? I replace MCP2551 and TJA1050 but result was same, CAN not ready. Cable work only with K line CAN is not working. (12-01-2015, 03:40 AM)makadam Wrote: I have a problem with 15.7 clone, with Atmega MCP2551 and TJA1050 STC chip inside.