Pages: 1 ... 10 11 [12] 13 14 ... 16
Author Topic: Tuning instrument cluster gauges for Audi/VW/Seat/Skoda  (Read 125991 times)
stuydub
Full Member
***

Karma: +24/-12
Offline Offline

Posts: 227


« Reply #165 on: March 16, 2021, 02:10:00 AM »


All u need is here :

https://mega.nz/file/iq5XBSZT#rx7sXb5z8ML7iTm61n_WYSZLcgDXOOIQSkB6VC8M2Q8
Logged
vt86
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #166 on: March 17, 2021, 02:08:06 AM »

Found solution for my problem. I'm feeling bit stupid right now. Some reason Vag-k+can was skip neg.response mode. With out that it read only few lines. After cluster reset everything worked fine. So if someone else will do same noob mistake. Reset your cluster and try again.  Grin


edit:
Also for info genuine RossTech VCDS cable can be used with VAG eeprom 1.19g (set to dumb mode). But because problematic old laptop I ended using another laptop with vag-k+can 3.6
« Last Edit: March 17, 2021, 06:44:06 AM by vt86 » Logged
MiroCro
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #167 on: March 31, 2021, 04:32:04 PM »

Hello,dash in my '98 octavia 1.6sr(1u1919034j) reads about 20 km/h lower than before(about 10km/h lower than gps) after upgrading from rod-operated to cable-operated gearbox out of the '03 1.8t.
also,if it's possible i would like to adjust speedometer scale so i can fit background foil out of the 240km/h octavia dash 1u0920811b.
can someone give me some guidelines how to do this,as i have no experience at this field?i have vag eeprom programer v1.19g and vag k+can commander full v2.5
both dumps are in attachment,i can also attach dumps from two mk4 golf clusters(1j0919660x-220km/h out of 1.4 16v and 1j0920820a out of vr5)  if it'll be easier to transfer speedomeret scales in my cluster's eeprom.
thanks in advance!
« Last Edit: March 31, 2021, 04:35:17 PM by MiroCro » Logged
MiroCro
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #168 on: April 13, 2021, 03:29:35 AM »

Anyone? Undecided
Logged
stuydub
Full Member
***

Karma: +24/-12
Offline Offline

Posts: 227


« Reply #169 on: April 15, 2021, 05:41:25 AM »

Anyone? Undecided

Transfer a dump over from a 1.8t cluster remember to transfer IMMO DATA over if needed
Logged
MiroCro
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #170 on: April 15, 2021, 12:35:14 PM »

Dumps aren't same...
Logged
stuydub
Full Member
***

Karma: +24/-12
Offline Offline

Posts: 227


« Reply #171 on: April 16, 2021, 04:54:16 AM »

Dumps aren't same...

AND ? i running Octy cluster in a mk4 with mk4 dump on it..Code the clocks in as normal the re read dump and edit
Logged
Nasenbastl
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #172 on: April 16, 2021, 06:32:04 AM »

Checksumme Huh??
Logged
stuydub
Full Member
***

Karma: +24/-12
Offline Offline

Posts: 227


« Reply #173 on: April 16, 2021, 07:46:24 AM »

Checksums aint a really big issue with these clusters
Logged
Steven97i1
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 86


« Reply #174 on: July 03, 2021, 03:15:07 PM »


it says eeprom not supported with my 8l0 920 931 E

eeprom attached!

Read with VAGTacho, eeprom programmer v19 not Working (unkown hardware number)
wanted something like needle swap and my kmh is not working correctly (+5KMH gps)
Logged

Searching for All XDF for an Free XDF database ONLY for nefariousmotorsports.com
Elder2000
Newbie
*

Karma: +2/-0
Offline Offline

Posts: 3


« Reply #175 on: July 21, 2021, 07:28:50 PM »

Hello
Auto after SWAP Skoda Octavia 1.8T plus DSG.
On the dashboard of the Golf R32 it shows the gear numbers.
On the dashboard  of the Octavia it does not show.


Hi
I recently swapped the exchange to dsg dq250 here in Brazil
and I have the same problem of not showing the current gear
managed to solve?
Logged
stuydub
Full Member
***

Karma: +24/-12
Offline Offline

Posts: 227


« Reply #176 on: July 22, 2021, 10:27:30 AM »

Reflash with r32 dump or change software coding
Logged
EuroXs4
Full Member
***

Karma: +15/-31
Offline Offline

Posts: 209


« Reply #177 on: October 26, 2021, 07:56:36 AM »

A few dash dump in vageepromer and don't red VIN and other?

VAG EEprom will show you all the data but needs to be decrypted. FIRST SAVE ENCRYPTED  AS BACKUP!! Then set to new mode it will then decrypt all the information and show you vin,immo id, and pin. Note sometimes when changing things checksum will not calculate correctly resulting in deF. on the lcd. ALWAYS MAKE ENCRYPTED BACKUP FIRST! Prosta sprawa.
Logged
pedropp93
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 15


« Reply #178 on: February 13, 2022, 08:16:15 AM »

Hello guys,

Based on what tjwasiak said on post no #21 and some other findings, I have finally figured out how to properly rescale my cluster.

Long story short: I had 1/2 FIS on my octavia mk1 with bad LCD so I decided to swap from Superb 1 with full FIS. After some immo issues i got it right. But I found out that I had speedometer too low - from 0-60 it showed about 5km/h lower, and from 60-end 10km/h lower. On the other side, old octavia cluster was showing a bit too high (5 more 0-80, 10 more 80-end). And we can all agree, that lowered values are far more dangerous than higher values right? Cheesy So I needed to tune it.

So I read my "new" superb cluster again. I copied my speedo scale (tacho was already done) and k-value from old cluster and it resulted as predicted - I had the same, bit higher valueas as old octavia cluster Cheesy But, as an engineer, It wasn't enough for me - as I have learned how to properly modify dump Cheesy.

I took a protractor, measured angles between single 5km/h indicators on both ranges (0-120, 120-240), calculated proper values for speedo stepper motor for specified (my custom) speed values (as tjwasiak said, you have to determine your k-value right in order to have good speed readings), and put it into dump.

As the result, I have only 3km/h higher than GPS on whole 0-240 speed range, which is great because I still have that small "overspeed" error margin, which helps me mentally Cheesy This error can be caused by some k-value uncertainty (resulted from wheel diameter uncertainty), angle measuring error (because photo of speedo was took a bit off proper front angle) and other like dividing reminders in calculations.

My setup is as follows:
Old Octavia cluster (seems type VWK501): 1J0 920 9(xx B) - not sure which it was but I will check and edit.
New, swapped Superb cluster (seems type VWK503): 3U0 920 941 A

In [] brackets I will put addresses in octavia cluster. Remember, I'm giving here my actual, custom values. Addresses from octavia's cluster are just in case someone would want to copy from octavia's cluster. You won't find values I show here in octavia's cluster (except k-value) Smiley.

k-value: 3480 (this value is copied from octavia's cluster), Originally it was 4182 (as far as I remember). Address 0x192 [0x150]

speedo x-axis: 0050 00A0 01E0 0500 0780 07D0 0B40 0F00 (for 3, 10, 30, 80, 120, 125, 180, 240 km/h). From address 0x258 [0x220]

speedo y-axis: 0065 00CA 0260 0655 0980 09C7 0CD8 1030. From 0x268 [0x230]

BUT THERE ARE TWO THINGS YOU NEED TO BE AWARE OF!!!

First. After switch ignition ON, speedo shows 5km/h (even with engine off). This could be (probably) because speedo stepper starts not from 0, but from first value in x-axis. That's why (I guess) original x-axis starts from about 1,5km/h. You know, it will be set about 1 degree up, so it is unnoticable. I will do the same, and set first value of x-axis to 1km/h (and proper first value of y-axix accordingly) and check this out. Nevertheless, all remainding speed readings are ok. Checked with GPS.

Second. Unfortunately, as tjwasiak said, there will be def error on cluster. And that's probably because of checksum error, caused by modyfing k-value. I deduced (correct me if I'm wrong) that speedo (and tacho) scales are not checksum protected. And k-value is. To get rid of def error, you can recode your cluster with the same value, but unfortunately it will force returning your k-value to previous, and that will crash this whole idea, because everything here is based on assumpion that k-value is correct Smiley. And the reason why this will happen, is that cluster coding last digit sets k-value Smiley You are lucky, if for some reason you can choose from some values during coding (on ovtavia's cluster I was able to choose four as I remember), unfortunately I wasn't on superb's cluster. I am able only to set XXXX5 as my last coding digit, which results in going back to 4182 k-value Sad. To fix this properly, you would need to know how checksums are calculated in VDO clusters (probably some kind of CRC) and also where to put it in eeprom. And unfortunately I have no idea for both Sad

BUT!!!. If you don't need to change k-value, you are home. I had to change it, because I swapped cluster from different car and beside that, it was diesel, and I have 1.8t Smiley If your k-value stays the same, I guess there won't be a checksum error and even if it will appear, you can recode with the same coding, because it won't change your k-value Smiley


Does anyone know how to calculate checksums and where to put them? Smiley
« Last Edit: February 13, 2022, 08:18:17 AM by pedropp93 » Logged
macxxx
Sr. Member
****

Karma: +29/-1
Offline Offline

Posts: 498


« Reply #179 on: February 13, 2022, 05:03:27 PM »

I know how the checksum works on VDO Audi clusters ( a4 B5 , A6 c5 , A3 8L ) - but it's hard to explain because I dont't know everything. I will try to prepare a dump screen with selected bytes for two types of checksum.

For sure it works different beacause in Audi K value is fixed , and recoding doesn't fix def error.
Logged
Pages: 1 ... 10 11 [12] 13 14 ... 16
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.094 seconds with 16 queries. (Pretty URLs adds 0.008s, 0q)