VAG-COM/VCDS EVERYTHING

[34260551]

ok downloaded 17.1.3v2 and have hooked up my 0x46 via the pin header to usbasp, and extreme burner sees the chip. how do I go about flashing it? sorry need a step by step.

1.File->Open Flash-> select Flash1.96_HW_0x46.hex
2.File->Open EEPROM-> select eepromavr.hex
3.Fuse Bits/Settings
avr(1).JPG
4.Press 'Write All'

[liviudiaconu]

I open my cabel and inside is FT232B.

So what i need to repair my vcds? with file is good ? I need reprog atmega one more time ?

See attach. After ask kolimer if her solution work with B chips.

[cypher007]

1.File->Open Flash-> select Flash1.96_HW_0x46.hex
2.File->Open EEPROM-> select eepromavr.hex
3.Fuse Bits/Settings
avr(1).JPG
4.Press 'Write All'

any ideas if this will work on a 0x46 17.1 cable? if it does flash do I then use the original rosstech soft or do I need a cracked one?

p.s. I know not to update using the rosstech software.

[liviudiaconu]

If you want use oem soft, is better to buy a oem cable, too.

[cypher007]

1.File->Open Flash-> select Flash1.96_HW_0x46.hex
2.File->Open EEPROM-> select eepromavr.hex
3.Fuse Bits/Settings
avr(1).JPG
4.Press 'Write All'

that worked great. I can read codes out of my old 2003 car. Ill try a newer car later.

[obd2cartool]

most vag cable version hw with ATMEGA + FTDI chips support reprogramming like vag 11.11.3, vag 16.8.4, one kind need active 16.8.3 only support english version ,vag 17.1.0 . other like use original software (not office cable) it is used NEC project, we test different FT232 chips, there is no obvious difference. and Thanks kolimer and other friends!!

[deluss]

The correct order to repair cabel is:
1. Write VCDS BL by USB and Mprog.
2. Next: File->Open Flash-> select Flash1.96_HW_0x44.hex
3.File->Open EEPROM-> select eepromavr.hex
4.Fuse Bits/Settings

This is correct order ?

[bibkare]

The correct order to repair cabel is:
1. Write VCDS BL by USB and Mprog.
2. Next: File->Open Flash-> select Flash1.96_HW_0x44.hex
3.File->Open EEPROM-> select eepromavr.hex
4.Fuse Bits/Settings

This is correct order ?

It doesn't matter which operation's done first, ftdi or atmega, i have a habit to do atmega first.

[bibkare]

Tested new dump on BL interface and used .ept from liviudiaconu few posts above, works excellent, just be sure to use proper fuses (in my case it was v44) also tested on cheap RL version - the one without GAL and 7805, was able to do long coding, autoscan and everything. Excellent work Kolimer.

best regards

[pepeEL]

Can you write full manual for this...?with link for files share

[ni88l3r]

Hi guys,

finally I got my new cable of obd2cartool.com and it's working great!

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).

As you can see in my post http://www.digital-kaos.co.uk/forums...=1#post2927162 the cable identified as VID_0403 & PID_FA20.

But now the FTDI FT232BL identifies as VID_0403 & PID_6001 which is the "standard" PID I think.

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).
Mprog reads the device as blank, but when I try to write the Eeprom it says "Error reading device". Any other tools also can't write the chip.

Is the chip defect or is there a possibility to write the eeprom (e.g. 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)?
If there is no way to write it, would it help to get a new FT232BL an replace it?

Appreciate your answers, thanks in advance!

ni88l3r

[alexm1]

I had this problem a few months ago....I soldered back R50 and problem solved, actually I desoldered only STC(U9).

[ni88l3r]

Soldered R50 back in, still no luck, but thanks anyway.
Any possibility to program the ftdi directly?

Or should I just throw the cable in the bin, I finally jave a working cable

[uragan1987]

can somebody make full hd photos of an working device, that was flashed with kolimer files,
(long coding, no errors)
wanna try to build one from 2 bad clones.
thx

[deluss]

Tested new dump on BL interface and used .ept from liviudiaconu few posts above, works excellent, just be sure to use proper fuses (in my case it was v44) also tested on cheap RL version - the one without GAL and 7805, was able to do long coding, autoscan and everything. Excellent work Kolimer.

best regards

Need to desolder something like R50 ?