[dustwhyn]

The slow update rate of our speedometers has always irked me. I know you can change it from the default 2 updates per second to 5 with BimmerCode, but it still wasn’t enough for me- I wanted a speedometer that had a smoother and more fluid update rate.

I did some digging around and found out that the actual name that the value is stored under is “DIGIT_GESCHW_UPDATERATE” in KOMBI.

After some experimentation, I can confirm that setting the value to 0x01 instead of 0x02 (5 updates per second), does indeed result in smoother updates at 10 per second according to the math (1000ms divided by set value times 100).

Out of mere curiosity I also set the value to 0x00 to see if it would either break or uncap the update rate, and it works without errors, but in all honesty I can’t tell if it’s any different than setting it to 0x01.

[G22b58]

So you didn't notice any effect on other cluster update rates (like rev counter or map)?
Perhaps the formula you found out could be described as updateRate=10Hz/value (or updatePeriod= 100ms*value)?

[dustwhyn]

Originally Posted by G22b58

So you didn't notice any effect on other cluster update rates (like rev counter or map)?
Perhaps the formula you found out could be described as updateRate=10Hz/value (or updatePeriod= 100ms*value)?

Nothing out of the ordinary as far as I can tell. It only seems to affect the speedometer digits.

The second formula is actually the correct one. I was just trying to explain it in a way easier for others to understand. I’m just curious as to why it still works when set to 0x00 lol.

[dustwhyn]

Update: I’m not noticing any difference at all between 0x00 and 0x01.