I can calculate ABS module codings for:
* Continental/Teves MK60EC1 and MK60;
* TRW systems in Passat B6 / B7 / CC /Tiguan;
* MK100;
* Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
* EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
* ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.
Oh, I can see it is going to be very interesting.
First of all, I do not know who is this obdcarsale, but if someone is going to call me a cheater then he needs to give a prove, because public defamation is subject to a judicial punishment. It is not China but UK forum and UK is still in the European Union.
Secondly I have bought this cable from aliexpress like everybody, nothing is for free there.
I do not see any reason for giving an explanation here but I am doing it on my own will.
I have found this cable not working correctly, however as I am new in VAG (I have this car for a month now) I have wasted a lot of time struggling to find out what am I doing wrong. Moreover due to this broken cable I have disabled some functionality in my car as long coding was not working. Thanks God it wasn't so important for normal functioning of the car, so I didn't have to go to authorized service to fix it. I didn't get any solution from the seller so I got the refund. When I was looking for another cable, even original one, I have found information that there is an option to fix this. Then I wasted another few days till I found this forum and those useful information.
So in summary I didn't get this cable for free, I have paid for it as everybody, but finally I had to spent dozens of hours and break my car to make this cable working as seller does not give a sh*t what he is selling. This is also the reason this threat is over 500 pages long.
And finally, I do not want to point a cheater here, but I would like to see a permission from Ross-Tech LLC. for obdcarsale or any other aliexpress seller, to offer their products (hardware based on their design and software that is signed Ross-Tech name). Also permission from the developer of the Loader application they offer, to offer this product.
hid3 (1st May, 2019)
Good morning guys.
I need your precious help.
In 4 days I practically read almost all the 500 and more pages of this 3D, but I can't solve my problem which I now expose to you (as precisely as possible).
A couple of weeks ago I bought a VAG cable and it arrived with minidisk (VCDS 18.9 EN-ITT with loader 7.0).
As per the instructions attached to the minidisk, I deactivated the internet connection and stopped AV and Defense (WIN7).
I launched the ITT installer. I also installed the driver correctly. At the end of the installation, I moved the Loader to the VCDS folder and launched it. Vcds has correctly opened with the 7.0 loader popup.
I connected the cable via USB to the PC and recognized it, recording and saving it.
It was already late and I disconnected everything and turned off the PC.
Back home, I turned the PC back on and, when I connected the cable to the PC via USB, it no longer recognized the cable (unrecognized USB device).
Contacted the seller, 'he washes his hands' saying that I blocked the cable.
Let's move on to the technical part.
thanks to this 3D, I'm trying to figure out how to fix this problem.
The cable, whatever I do is not recognized, neither from my PC nor from other PCs on which I put the driver.
The type of interface is visible in photos and, from the file info.pdf I discovered that it is the most recommended (it was just luck).
No program inserted in the loader (HWType, EEWriteLang, ProgIsp, etc etc) manages to detect it. The interface, when powered at 12v, but also at 5V via the programmer, lights up first in red then regularly switches to green.
I tried via USBISP to communicate via serial (MOSI / MISO / SCK / RST / VCC and GND) without success.
Where am I doing wrong ?
With the ATMEGAs I have a little bit of experience, but this time seems to be kidding me.
Thanks to anyone who can help me.
Those disputes are managed by Aliexpress and there was no decision to return broken cable. Cost for the return is too big and no one wants to pay for it.
And don't be a hipocrite. Usage of hacked software is called theft.
Ouh, that is embarasing...
Sinapsi,
Check what VID&PID are detected in windows devices manager, probably those are erased, so you need to fix that with MProg application.
You should not need to flash ATMega if FTDI will be working again.
But regarding ATMega connection make sure all signals are connected correctly, because for me it looks invalid. Also make sure the power is supplied correctly (from programmer of from ATMega PCB). However if you connected ISP wires incorrect and reversed power supply, you could damage ATMega.
bg17aw (10th May, 2019)
Thanks for the quick reply.
it is completely unknown.
The ISP connection is correct (checked several times) but Mprog does not communicate with the ISP. Unless the pinout written in the info.pdf file is incorrect, or this card has a different pinout (after dinner check the tracks and connections with the ATMega)
It is not the first time that I use these programmers via ISP, but something like this has never happened to me.
Assuming I can get them to talk, what file should I upload from those available? There is more than one file for RT interfaces.
SinapsiAgain check in "M.D" "Details" and "device instance ID" vid and pid. Then try this from post 1 or 2 (translate). I had a similar situation with OP-COM but I could not fix it. I bought the next one.
(But earlier, I've fixed the vcd$ and op-com several times (FTDI)
https://www.digital-kaos.co.uk/forum...YTHING/page542
Last edited by Mario6; 1st May, 2019 at 07:49 PM.
I had already tried to force the device with the RT driver. As soon as you apply the change, it warns you that the device is not working anyway.
keeping the forcing, I also tried MProg (it doesn't see anything connected) and even vidpidfix can't do anything.
it's incredible. How can an FT232R (original FTDI) lose data and, above all, no more input?
It seen that you have a clone ftdi chip. Its now dead. Desold it put a new one and it will works again.
Is this a clone for you ?
Did you connected like this?
pinout.jpg
SinapsiI have three cables so damaged. VID and PID alone 0000 tried everything, could not do it.
I created a booth for checking and repairing scanners yesterday, it turned out great, I bought a CAN from the Passat B6 ($ 9), picked up an old battery from a laptop for three 18650 batteries (lay just like that for me) soldered crocodiles, I recommend it to anyone who needs offline testing (on the table)
Gateway power network connector:
food + 12v - 1.14
food - (weight) - 11
Tire for diagnostics H - 19 - for 6 pin diagnostic connector
L-9 Diagnostic Tire for 14 pin diagnostic connector
OBDII diagnostic connector:
food + 12v - 16
food - (weight) - 4
The tire for diagnostics of N - 6 - on 19 pin Gateway
The tire for diagnostics of L - 14 - on 9 pin Gateway
Last edited by Roma77; 2nd May, 2019 at 09:01 AM.
bmw318isblack (28th September, 2019), da78n (3rd May, 2019), rak183 (2nd May, 2019)
the problem is clear the FTDI Chip is broken. If y can not fix it with the tool from #8220, dann y have to change it.
Bookmarks