Vag Tacho 2.2-2.5-2.6-3.1 dump files

[Meat-Head]

can not read opel zafiara 2.2 year 2002.can help me.

Wrong car for a start, if immo2 nil poi

[garaje16]

holaaaaaa hay alguien de madrid

[garaje16]

nadieeeeeeeeeeeeeeeeeeeeee

[buljaka]

Don't know if I have the same issue I have a vag tacho 2.5 cable but had to reformat my hard drive and can not find the cd that came with it.
I have not used any newer version software with it. So downloaded the 2.5 software pluged the usb cable in. The computer reconised it when pluged in but when I open vag tacho 2.5 it says interface not found please see attached software and mprog dump.





Will I need to reflash the cable or do I have the wrong drivers?

excatly the same problem, anyone has a solution?

[ryshard]

I've got another problem. I've tried any versions od vag tacho dumps on my china vag tacho 3.01, and I have always, that Usb to K-line interface is connected ID:xxxxx, but when click on Connect Selected ECU got:
Warning: No 12 volts power supply from OBD connector!
Warning: K-Line Fault - Short circuit to Ground!
I even change the L9637D in interface, but still got no connection. Maybe anyone got the cd to this china cable ?

[dadal]

Use mprog 2.8
Program with file VagTahoUsb22.ept

Then run VTU-2XX-UA.exe
Removing and Replacing the usb.
Ready.
Perfect

Hi mate thanks works perfect

[mobilni]

How do you flash cable? is there any instruction on that?

[rui]

Hello. I have some doubts and I wish they could clarify and help at the same time. I have vag-tacho2.2 and can I use a version above?
I have a cable vag can comander 5.1 never got it by running, can you give it back?


thank you

[longgo]

Little old topic but safe my cable. So, here is what happen. I also bought from Ebay clone that claim to be 3.01. One time it start (to test it) and then it went dead..
I try to fix the FTD serial, but the software despite starting began to complain that "12V not present..." , "K-line short to the ground.." or similar..
Well, no connection to any VW - AUDI dash.. Damn.
Then I found that topic and in post #68 was some RAR pack that content FTD file, DATA and EEPROM memory HEX files.. And it bring it back to life...

What where my steps :
1 - open the cable, and found out that the green cable (data line) get broken right away.. So, I cut and re solder all of them

cable1.jpg

2 - cut that line. Have no clue why pin 7 (K-line ) is connected to pin 3 (non universal) but for my range of use do not think will do something good to have K-line tight together with pin 3

cable2.jpg

3 - move the Atmel to programmer

cable3.jpg

That one is cheap , but work great..
As the Atmel was removed, I reflash the FTD chip

4 - select the Ft245RL.ept file using attached MProg

cable4.jpg

select "EDIT" , and wrote the serial number, then using the blue flash logo , flash the cable. Then press READ to confirm I get the number inside:

cable5.jpg

[longgo]

Because only 5 picture per answer, will write second post.. sorry

Next wrote data in the Atmel chip.

- select right chip info:

cable6.jpg

- leave the fuses as is , and all data to be FF FF filled and push write. That manage to erase the chip

cable7.jpg

- next select the proper files, and select the right destination:

cable9.jpg

- set the FUSES and burn.

cap9.jpg

Solder the chip on place and that 12V and K-line errors disappear, and the cable with 2.6 software flawlessly manage to read the pin code from TT N8 dash..

Thanks folks for the great forum and files!

p.s: bought 2 new ATMega 8A chips but manage to use that one what come with the cable. Anyway, perhaps better just to replace it with new and flash the software..

[garnierX]

ive tried quite few times. but un successful.
Many years ago I was using cable ( china vagtacho 3.01 from eBay.co.uk ) and I had a problem with it. I remember that I was messing about with it with mprog and somehow I have fixed it.

Now afer few years I wanted to read PIN from different car and cable is death again.
It might be the fact that I dont have winXP , but win10 x64.
however Ive tried even running XP in virtualbox. still no success.

then Ive found this site and i can hardly remember that I was "fixing" cable somehow like this in the past. ( with mprog ).

I highly appreciate any help that anyone provides. However I guess that there is plenty users like myself that don't know what to do at all and might need a bit more help with that,.


So can someone please sum up what the steps are to make that cable run again?

I'm pretty sure that last time when i did it ive only did something in mprog program and then problably had it running fine./..

some users writes there about some fuses etc... ? wt?? what fuses ? there is no such option in mprog at all or do i missing something?


I have windows 10 x64 and Vag Tacho cable 3.01
how can these two working together?


If it's necessary i can run it under windows xp in virtual box, but i prefer not to.


thank you very much for any help of info that will make it run again.

[Ingwar]

all the best! Does anyone have a cord dump of vag tahoe 5.0?

[CasaEd]

I know this thread is old, but I would just like to thank those people on here who took the time to upload fixes, I've finally managed to get my

VagTacho 3.01 cable working after owning it for 3 years. I don't know which fix brought it back to life and I have no intention of playing with the

cable to find out, it now works as it should, so thank you !

[aabron]

Hello,
Can i replace 93c46 with 93s46 in vag tacho ft245bm, change PID to D99 and serial with mprog and use atmega firmware from version ft245rl vagtacho 3.01?
What i don't understand is that on the schematic of vagtacho 1.0-1.7 on eeprom 93c46 pin 7 DC is pulled low and pin 6 ORG is pulled high.
On 93s47 pin 6 W would be pulled high all the time. Would it work?
Can v1 work up to v3 with 93s46?
Can someone post schematic of vagtacho 2.5 - 3.3?
I am writing about this post:
https://www.digital-kaos.co.uk/forum...l=1#post348698

[pjakub]

Little old topic but safe my cable. So, here is what happen. I also bought from Ebay clone that claim to be 3.01. One time it start (to test it) and then it went dead..
I try to fix the FTD serial, but the software despite starting began to complain that "12V not present..." , "K-line short to the ground.." or similar..
Well, no connection to any VW - AUDI dash.. Damn.
Then I found that topic and in post #68 was some RAR pack that content FTD file, DATA and EEPROM memory HEX files.. And it bring it back to life...

What where my steps :
1 - open the cable, and found out that the green cable (data line) get broken right away.. So, I cut and re solder all of them

cable1.jpg

2 - cut that line. Have no clue why pin 7 (K-line ) is connected to pin 3 (non universal) but for my range of use do not think will do something good to have K-line tight together with pin 3

cable2.jpg

3 - move the Atmel to programmer

cable3.jpg

That one is cheap , but work great..
As the Atmel was removed, I reflash the FTD chip

4 - select the Ft245RL.ept file using attached MProg

cable4.jpg

select "EDIT" , and wrote the serial number, then using the blue flash logo , flash the cable. Then press READ to confirm I get the number inside:

cable5.jpg

Thanks a lot! I just did the procedure as described and revived my VAG TACHO 3.01!!!
Excellent Tutorial!