Another Golf 5 Visteon Dash

[testarossa]

Hello guys,

I have read this forum and a lot about this thema, and I know that it seems very difficult to recalibrate Visteon Dashs on Volkswagen.
Now I have one here and I wanted to get the kms changed on this 1K0 820 963B (from 116722 to 68600). Is someone able to solve this?

[tachonow]

Hello guys,

I have read this forum and a lot about this thema, and I know that it seems very difficult to recalibrate Visteon Dashs on Volkswagen.
Now I have one here and I wanted to get the kms changed on this 1K0 820 963B (from 116722 to 68600). Is someone able to solve this?
Post more details. Eep type.
Year of car.

[testarossa]

Hi, car is a Golf V from 2007 with 95160 E? inside.

[testarossa]

Hi, anyone can help me please?

[testarossa]

Hi, now i figured out how to calculate kms (01 C7 F2) and checksum (BA). That was very easy :proud:

But the real problem on this cluster seems to be the string from 000002308 to 000002407 (16 91 68 AA 1B 23 7B 93 14 D9 7B 9D 1B 1B 78 19).
And it repeats at 000006204 to 000006303.
How to calculate that fu**ing string??
I have already tried to copy and paste it from another cluster but no way, it shows "Error" on the display:motz:

[kavan]

does anybody know where the login pin is in the dump?

[autofan1965]

Login is really strong encrypted at this point only few peopel in the word know algo. When You need PIN just post dump my friend can calc it for You.

[drpeter]

Hi, now i figured out how to calculate kms (01 C7 F2) and checksum (BA). That was very easy :proud:

But the real problem on this cluster seems to be the string from 000002308 to 000002407 (16 91 68 AA 1B 23 7B 93 14 D9 7B 9D 1B 1B 78 19).
And it repeats at 000006204 to 000006303.
How to calculate that fu**ing string??
I have already tried to copy and paste it from another cluster but no way, it shows "Error" on the display:motz:

Checksum changes every 128 km so you must devide some bytes through 128 (Hex 80) and add some to get the checksum. It is very complicated that's why some company's still have problems with this type (like smelecom).

[testarossa]

So DrPeter, you think it is quite impossible to solve it via dump?
I am not a fan of this OBD solutions, i'd rather use my brain. But if there is no other way, which progs do you recommend?

[cokolo]

[ QUOTE=testarossa;1214739]So DrPeter, you think it is quite impossible to solve it via dump?
I am not a fan of this OBD solutions, i'd rather use my brain. But if there is no other way, which progs do you recommend?[/QUOTE]

DP3 works these dashboard perfect and fast (20sec) :-) :celticscarf:

[testarossa]

Yes, DP3 seems to be very interesting, but it is a complete programming device for a lot of cars and by far too expensive for me to adjust only this piece of Visteon sh*t.
Other pc based programs like AVDI, TU, that can do it?

[vageric]

no, TU can not do this one.

[cokolo]

Avdi
Yes, DP3 seems to be very interesting, but it is a complete programming device for a lot of cars and by far too expensive for me to adjust only this piece of Visteon sh*t.
Other pc based programs like AVDI, TU, that can do it?

I have Avdi and he can do only pin read from Visteon dasboard and I have Diga orginal and diga can do older Visteon dash with eeprom 95160 :-) :wink:

[autofan1965]

Best price / possibilietes solution for KM in Visteon is XCAN work with 4 diffrent version this dashes really good.