View Single Post
  #176  
Old 11-21-2020, 01:43 PM
oldskewel oldskewel is online now
Member
 
Join Date: Nov 2014
Location: SF Bay Area
Posts: 1,423
oldskewel is on a distinguished road
Great info. I have not seen this before. I expect it will be easier and safer for people to make this change vs. finding and editing the hex code values in both places, etc.

More info for others in this useful thread:
https://xoutpost.com/bmw-sav-forums/...rmostat-6.html

One question I had when doing it manually there, that I never got an answer for, is what are the in-between values between those breakpoint settings?

As reported by overboost, crowz, and me, these are the original arrays:
0F 62 32 CB 4B CB 73 38 78 6A 7D FF overboost
0F 65 32 D0 4B D0 73 38 78 69 7D FF crowz
0F 5E 32 C9 4B C9 73 36 78 6A 7D FF oldskewel
15 -- 50 -- 75 -- 115 -- 120 -- 125 -- hex to Decimal (*C) conversions. meaningful values shown, others left as "--"

So my question is what do those in-between values do / mean? They are different, but not random or zero, for the three of us. I left mine unchanged, not wanting to risk anything. And I see from your post here that they are shown as "00" in the pre-designed array choice.

Mostly just curious, but I would have felt better about the whole process if I understood everything, like this mystery. I was fairly paranoid about bricking the car while doing that.

BTW, the breakpoints I programmed, and am still happy with, are
15 - 60 - 94 - 96 - 110 - 115

with a few more details in:
https://xoutpost.com/1163393-post54.html

With 94 and 96 as the middle two, it pretty much does away with the deadband region. It operates with the gauge straight up (at 95, I guess) most of the time, but will now clearly move a little hotter or a little cooler when things are a little cool or a little hot.
__________________
2001 X5 3.0i, 203k miles, AT, owned since 2014
Reply With Quote

Sponsored Links