VAG-COM/VCDS EVERYTHING

[KenshinPT]

ok I'll change the resistance by the 150 ohm 1koh I've got you know if it works

Keep trying other lower values than 1Kohm until you reach 100ohm.

I am saying that because the resistor are there to protect your LPT port and not your ATMEGA.

So, beware and keep trying first 820ohm, 680ohm, 560ohm, 470om, 390ohm, 330ohm, 270ohm, 220ohm, 180ohm, 150ohm, 120ohm and finally 100ohm.

[tr3ce13]

......................

[spongemak]

@spongemak yes I have it but for now this dump is not for free. ( please notice that I don't sell this, just I don't share it )
When it will show up a new version dump for sure this one will be for free.

Do u know where I can get/buy it?

[mattydr67]

I have the same problem 1.81+908 & 1.83+908
What version of vdcs have tested ???

10.6.0 version 2010.06.30 realised
flash 1.83.
I will try with 1.81 and I will tell you.
Good luck
@spongemak
"Do u know where I can get/buy it? "
No I don't.

[tomasfilip]

Keep trying other lower values than 1Kohm until you reach 100ohm.

I am saying that because the resistor are there to protect your LPT port and not your ATMEGA.

So, beware and keep trying first 820ohm, 680ohm, 560ohm, 470om, 390ohm, 330ohm, 270ohm, 220ohm, 180ohm, 150ohm, 120ohm and finally 100ohm.

Hey guys,

be aware! This maximal current allowed from LPT is limited, sink is usually only 2.6mA (source 24mA), there is TTL logic, so I=U/R -> 5V/150R ~ 33mA!!

How long is cable from programmer to the VAG-COM? Should be as short as possible..

[tr3ce13]

..................................

[tomasfilip]

I have the same problem 1.81+908 & 1.83+908
What version of vdcs have tested ???

hmm, K-line comunication is working well for 1.81 and 1.83

I put all necesarry files into attachement, here are firmware 1.81,1.83

There is also my program for programming eeprom in FTDI chip, when you run, you will see what is in FTDI eeprom and than is automatically written new contains.. than you unplug a cable and plug again to read new values.

There are also directory with pictures, highresolution of my cable, programmer and VCDS

I used engine controll from old Skoda car (is on table and connected to the rosstech cable +12V, GND and K-line)

VCDS was installed 805 but is patched to the 908 (when I copied files from VDS_908.0_mod.rar I get 908 EN version where cable is fully registered. Program show 20080309)

As programmer I used pony prog for serial port, is the big boards on the picture P1050597, see length of cable, as min. as possible.

[KenshinPT]

I had same issue using 1.83 and 10.6.0
Yesterday os Skoda Octavia I it performe AutoScan but from all controlers from the list it did just 01,02,03,05 even the car has more. If you like to do a scan on each controler no problem.
I will downgrade flash to 1.81 and I will tell you what happend next.
Good luck
@spongemak yes I have it but for now this dump is not for free. ( please notice that I don't sell this, just I don't share it )
When it will show up a new version dump for sure this one will be for free.
I want 908.2 romanian dump for testing but I'm not " in rush"

I have the same problem 1.81+908 & 1.83+908
What version of vdcs have tested ???

Something very wrong is going on...

Getting problems with 1.81+908 is very very very strange...

And everyone is getting the same trouble :O

[tomasfilip]

I am getting this error: Interface Status = -99

I thought that it was because I was using FLASH 1.83 + EEPROM 908.0 in VCDS 908.0.

The cable works good while connected to 12V but not connected to the car.

If I connect to the car I can do the TEST and I get REGISTERED and FULL ACTIVATED but when I try to access any module I get the error.

Sometimes I can acess the module... sometimes I don't.

Anyone have any ideas?

And does anybody know what is changed? because if is fully working before, why not now?

[tomasfilip]

let's talks about FW a little bit...

The version 1.83 show it in 10.6.3 (06.12.2010) where version 1.81 is upto 10.6.0 (30.06.2010) (I have original EN instalation from Rosstech)

In this is instalation are firmware files HCCxxx.bin and HCxxx.bin (don't know differents HCC and HC - guess w and w/o CAN)

So in 805 you will find HCC178.bin, in 9.08 upto 10.6.0 HCC181.bin and as new in 10.6.3 is HCC183.bin

This file is somehow crypted, isn't direct FW to the atmel, but when I used FW 1.62 together with 908eeprom contains, VCDS programs offer update of firmware..

and now will start the funny part of it, of course that normally ATMEGA is locked so you cannot read back, but when you write firmware 1.62 and 'forget' lock uC you can read Firmware back after update..

So I tried get version 1.78 (from 805 - success), 1.81 (from 908 - vcds from my package - by AmineBot - success)

When I tried 10.6.3 - cable is revoked and no comunication, so I tried rename HCC183 to HCC181 to try update in 908.. After update, cable doesn't communicate, when I read back and compare version from vcds with version from this forum I found differences in 5-6bytes.. Unfortunatelly this cable cannot comunicate after update

Hard to say if update process in 908 cannot do 1.83 or firmware 1.83 from Rosstech isn't version 1.83 what we have here..

When I compared 1.81, one bytes in Atmel EEPROM area is changed, what I saw couple times before.. position 401c (29->27), no idea what it is.. But after reset uC replace this string automatically

but cable looks like that is working, or you just replaced eeprom parts to different, if you want

So conclusion, firmware here are OK, 1.78, 1.81 are good (original), I'am not sure about 1.83

In atachement I put all FW from update, where 1.62 is FW for update.. Everybody can 'played' with these..

enjoy

[tr3ce13]

...............................

[tomasfilip]

When eeprom have a revoked/bad serial test give "Interface: Not found!" it?s a fake error

If put this dx in 10.6.3 dir about says "Revoked"

yes, that is true.. Maybe from new version Rosstech show interface not found when see clone cable..

Now me will help some crack for 805,908 Czech version of VCDS..

[tomasfilip]

has somebody tried change small eeprom 93c46 into part 93lc76/93lc86 for avoid writing to the device?

These two eeprom has PE (program enable), pin 7, on 93c46 is here NC.. When this pin will be connected to the gnd, contains will be only read-only

FTDI chip directly doesn't support this kind of memory, but when somebody has in stock, please tried it..

should be interesting, in clone cable PID/VID shouldn't be screwed anymore...

[KenshinPT]

I remember that I read in the erased VCDS thread that the new VCDS 10.6.x as new security.

If you test a device with a black listed serial your doomed. VCDS 10.6.x will something bad to your computer that you'll never be able to use your clone VCDS again unless you format your PC or if you find what VCDS did to your computer...

...Maybe an entry in the register?!

Anyone here can confirm this story?

[tr3ce13]

......................