Speedo offset fix...

[80stech]

Coding for different wheel size throws everything off. The problem here (I think) is that the speedometer is off, the digital speed,the odometer etc. is accurate.

Interesting that mine with the low cluster is dead on with what the digital values show. Anyone else with low cluster check into this?

[wpoll]

Originally Posted by Ohsoslow

Could you not just code the car with a different wheel size? I seem to remember that there’s options somewhere for setting the car wheel size.. eg 20” wheels are smaller than 19s.. which might give you the 4-5% you’re after..

Yep, as 80stech just said, the car is already dead accurate - it's just the analogue speedo (dial and needle) that is incorrect - deliberately. All other speed measurements in the car agree with the GPS speeds.

Coding the "wheel size" is done via a setting that states the number of ABS sensor impulses per kilometre. In fact there are two - one for the ODO and one for speed measurement. They are also slightly different.

[wpoll]

Originally Posted by 80stech

The low has cluster duplicate sets, so I would for sure look again,(maybe use the search next function) just not the Japan option.

I checked this out - NCS cannot access the "shadow data" - it looks like you can only access it via BMW Scanner, so it looks like this mod would need to be performed using BMW Scanner (aka PASoft).

I also checked out the NETTODAT.TRC file in NCSDummy and reviewed the hex dump and it doesn't show anything more than the FSW_PSW.TRC.

Anyone else keen to try this out?

Repeating Overboost's earlier instructions, the hex data needs to look like this once edited: -

0x00b8 09
0x00b9 3c
0x00ec f6
0x00ed c3

0x0260 09
0x0261 3c
0x0294 f6
0x0295 c3