View Single Post
  #57  
Old 01-03-2019, 10:48 PM
wpoll's Avatar
wpoll wpoll is offline
Member
 
Join Date: Sep 2015
Location: South Island, New Zealand
Posts: 5,029
wpoll will become famous soon enough
Quote:
Originally Posted by Overboost View Post
Great work Wayne! We are not defeated yet. Since we have the high cluster maybe we have the code in 2 separate lines in the EEPROM much like our temp gauge buffer modification.

It looks like you have found out the NCS method is only for those lines (00B8, 00B9 and 00EC, 00ED)

We may have a second line at 0260, 0261 and 0294, 0295 and will take BMW Scanner to modify the EEPROM.


This is an excerpt from another post with some additions.
I take no responsibility for anyone messing around with his/her software without knowing exactly what they are doing!

Open PASoft and go to IKE, read eprom and backup. Do a search for consecutive values 11, 33 and values EE, CC

The two bytes for speedo calibration and scale length should be at addresses 00B8, 00B9 are 11, 33. Changed to 09, 3C to select Japanese (accurate) speedometer.

The complemented data that should be at addresses 00EC, 00ED are EE, CC. Changed to F6, C3.

Some E39's have two copies of its data and the second set, which also must be changed, they should be at addresses 0260, 0261 and the complement data at 0294, 0295.
Ah crap - I forgot about the second set of data values. I did read about them and assumed that NCSDummy would modify those too. I guess this lack of "backup data values" is used for data verification (rather than a checksum) and since it's missing, the data reverts to the original value.

Might be time to fire up BMW Scanner and set the hex manually!

But this doesn't answer the question about what is CURRENTLY causing the speedo offset? In the e38/39 it's easy to see what is causing it - the data for the TACHO_ parameters - but in the case of the e53 this data is missing (and you confirmed it's was missing in yours too, so it's not just my 3.0d). So what is creating the offset?

If I start changing hex values with BMW Scanner, I might as well re-code the temp gauge too. Heck, I told myself I would never code anything that wasn't a "must have", due to the risk of screwing stuff up. Rather past that point now!

Good luck with the weekend! Last time I was in the pits (on a team) was for Rally Otago (Mitsi Evo) and before that the engines had pushrods (Formula Ford)! A little less electronics in those days...

Gad - didn't mean to sound so OLD!
__________________
Wayne
2005 BMW X5 3.0d (b 02/05)
2001 BMW F650GS Dakar (b 06/01)
Reply With Quote

Sponsored Links