VAG-COM/VCDS EVERYTHING

[peetr]

alexm1, I've used version 17.8. Maybe I'm gonna try a newer version, but as long as everything works I'll stick to 17.8

[liviudiaconu]

17.8.1 en-ro: No adaptations, no bits on Long coding helper" The same as in 17.8.0 from august and 17.10 beta.

[magadan]

17.8.1 en-ro: No adaptations, no bits on Long coding helper" The same as in 17.8.0 from august and 17.10 beta.

I wrote about this problem earlier.

....You will wait for the fact that substitution of public key, will become impossible, by means of a simple loader, it is necessary to do still something.

[kolimer]

I can confirm that long coding is not working as expected in 17.8.1 (No correct items are shown for bytes). It's working in 17.1.3 and 17.8.0.

[alexm1]

About 17.1.3 - will work with v2 loader +dumps? Or you can help with new loader /dumps?

[H2Deetoo]

I can confirm: 17.1.3 - will work with v2 loader +dumps.

[alexm1]

Can you share download link for 17.1.3 software? Thanks

[magadan]

I can confirm that long coding is not working as expected in 17.8.0 and 17.8.1 (No correct items are shown for bytes). It's working in 17.1.3.

If created the correct public key, and then calculated the new digital signature for atmega EEPOM, then long coding will work.
But there is also other way until it was forbidden by Ross.

[hid3]

One question. Currently I have and use 17.1.0, I want to try out 17.1.3 and see if Long coding and UDS Adaptation work fine.
Should I reflash the atmega with the dumps freshly or can I just reinstall the software to 17.1.3?

Thank you

[Mario6]

Can you share download link for 17.1.3 software? Thanks

Hi. Here you have a link to VCDS 17.1.3 En. (Slow download)

https://ulozto.net/!Jd4UHbfBjzIA/vcd...178.1513870186


I fixed my broken VCDS 16.8.3En. Thanks to KOLIMER.
I have three types of activators. One is Kolimers (V2) and 2 Chinese. And they all work correctly. I use VCDS 17.1.3 PL and everything works. I tried VCDS 17.8.0 PL (Kolimer activator) but I did not notice if everything works. (long coding).

[hid3]

I tried VCDS 17.8.0 PL (Kolimer activator) but I did not notice if everything works. (long coding).

In order to verify that the cable is fully working and safe, you need to try UDS adaptation channel, which is known to have a certain value.

E.g. I test on Instruments cluster on 6 Golf, check Staging if it's Activve or Not Active. If you see some nonsense in such channel, means it doesn't work correctly and such interface is DANGEROUS.

Meanwhile, Long Codings may work (or at least you won't notice that it works incorrectly, so relying only on that is not a guarantee

[Mario6]

Probably you are right. I checked the cable only on VW Passat B6 2006 and B5 2004(runs slower on K lines). In my old VW I do not have UDS so I will not check it out.

[vaicekas]

In order to verify that the cable is fully working and safe, you need to try UDS adaptation channel, which is known to have a certain value.

E.g. I test on Instruments cluster on 6 Golf, check Staging if it's Activve or Not Active. If you see some nonsense in such channel, means it doesn't work correctly and such interface is DANGEROUS.

Meanwhile, Long Codings may work (or at least you won't notice that it works incorrectly, so relying only on that is not a guarantee

Stagging is a bad example for checking the interface. Because only in some of the dashes these options are allowed. In order to activate Stagging it is necessary to adjust the EEPROM dump of the speedometer. There is no way to do this with vcds.
My Passat B7 Speedometer did not have the ability to turn on Stagging with VCDS. I removed the speedometer, dumped the eeprom, corrected several bits, wrote back, and now I can activate or deactivate Stagging with VCDS

[hid3]

Stagging is a bad example for checking the interface. Because only in some of the dashes these options are allowed. In order to activate Stagging it is necessary to adjust the EEPROM dump of the speedometer. There is no way to do this with vcds.
My Passat B7 Speedometer did not have the ability to turn on Stagging with VCDS. I removed the speedometer, dumped the eeprom, corrected several bits, wrote back, and now I can activate or deactivate Stagging with VCDS

Yeah, I know Staging is not available on all of them, but I gave it as an example of a thing, where you know expected values: Active / Not Active. if you see something else there, you know it's wrong. On your cluster, you can pick up *any* adaptation, which value you approx. know. It might be time till service, mileage since service, etc.. - it's your car and you know it.

It looks like you really wanted to boast that you activated Staging on your car. On my car (Golf 6) it alsoo was not available, as it's only available on GTI/GTD/R versions. But instead of taking out the cluster, I had the EEPROM dumped via OBD port, amended the necessary bytes and pushed it back. In addition to that, I also enabled Volume To Be Replenished in menu and true coolant temperature indication

[hid3]

If created the correct public key, and then calculated the new digital signature for atmega EEPOM, then long coding will work.
But there is also other way until it was forbidden by Ross.

So you mean that R0$$ made some amendments in versions later than 17.1.3 so that it stopped working correctly?

Do we have a list of known-good working versions? Or should we make one? I can confirm that 17.1.0 and 17.1.3 are working absolutely correctly on 0x44 HW. Others feel free to add