In the neighborhood of uC and Xtal 8MHz exist another chip, SOIC8 case.
In this chip are emulated more: FTDI, ATMEGA, MPC2515, GAL/ATF.
VCDS 12.12 DEUTSCH CRACK PC
It seems the same issue I was talking about on this page.Ĭable becomes unlicensed or unusable without connecting PC to internet.
VCDS 12.12 DEUTSCH CRACK HOW TO
Then anyone can enlight me to know how to correct this hardware issue or how to improve a clone cable to avoid this issue? Interface can work some minutes, days inclusive weeks without any issue and a day it simple stop working and computer can not recognize it usb port. But still I have a big doubt, why sometimes cables get broken (interface not found port not ready usb port not recognized) sometimes after repair an interface? In fact even usb port is not recognizing FTDI IC in cable, why this happends? I have try changing FTDI IC without luck at all? I am using an isolated WinXP 32bit session without any network connection at all and ICs inside cable have been repaired/reflashed properly, according to info posted here. I have repaired a pair of mine in the past with great sucess. I have been following this thread as much as I can since first post and I have learned to repair a cable. But maybe it's just my unit.įriends I have a big doubt. Overall I would NOT RECOMMEND this cable. I've spent 40 minutes trying to get it to work. The cable was disconnecting all the time, other errors were like this: I've tried ignition of and off, engine on and off. Than I wanted to do 'Auto Scan' I've selected my car, it checked module 01, and that's all it successfully checked. I've connected to the '01 Engine' module, no problem. and status was all 'OK' except of CAN, which is not available in my car. Well I thought this will look different if it was connected to a car. Not good, Atmega cables always showed 'OK' on the Kx lines. No updates, no internet connected, just like it should be. It looks exactly like the original version, the cable is detachable and has to lock screw in it. This will be somewhat of a review of this cable.:
Guys, now on Aliexpress you can find HEX v2 version of VCDS. Wysłane z mojego SM-G900F przy użyciu Tapatalka Yes, I've tested it on Win 10 圆4 Pro, and even on the USB 3.0 port - everything works! Can works, long coding also. If there is no way to write it, would it help to get a new FT232BL an replace it?Īppreciate your answers, thanks in advance!
VCDS 12.12 DEUTSCH CRACK SERIAL
with linux or I read that it is possible to do it with a "real" serial port, but I couldn't find a manual for this)? Is the chip defect or is there a possibility to write the eeprom (e.g. Any other tools also can't write the chip. Mprog reads the device as blank, but when I try to write the Eeprom it says "Error reading device". My problem is that I can't write it anymore, it is recognized either as USB Serial adapter (COM3) (with FTDI drivers) or as RT Cable (with modified rt-usb driver). I ordered it, because I thought I killed my old 10.6.4 cable by desoldering the chip U9 „ST 8S103F2P6“ and parts R50, R51 respectively by erasing the Eeprom (which is probably the case here).Īs you can see in my post the cable identified as VID_0403 & PID_FA20.īut now the FTDI FT232BL identifies as VID_0403 & PID_6001 which is the "standard" PID I think.
Finally I got my new cable of and it's working great!
0 kommentar(er)
