ScrappyJack

iTrader: (1)

I noticed what seemed like high coolant temp values on a couple of logs. This morning, I started the car and logged as it warmed up. The logged value from EvoScan at "full operating temp" was showing as 206.9024F. The factory gauge reads as normal.

I have logged the car with a PocketLogger before and recall "full operating temp" as being closer to 180 - 190F so it looks like my displayed value is about 20F off.

Is anyone else experiencing the same thing? I know one person mentioned similar results here.

Has anyone compared to a PocketLogger to check the value from EvoScan?

MalibuJack

iTrader: (5)

Yeah the value is off.. you can fix it in your XML Definition file.. I think the AIT value is off a bit too..

taenaive

iTrader: (20)

Yes, they are off. I think you have to subtract -10 from the coolant temp value. and oxygen sensor reading is off too. you have to add +.1 to that. well... it was the result of experimenting with my pocket logger and evoscan.

justchil

iTrader: (44)

Can anyone confirm these changes ^^. I'll keep searching but I'd like to at least get my coolant reading right

evo 8 ya

iTrader: (31)

+1

TTP Engineering

iTrader: (465)

How tough is it to change the XML formulas?

Atlmethevo

If you know XML it's easy I already changed it in mine.

AlwaysinBoost

iTrader: (17)

it is extreamly simple to do. i know nothing about computers and I was able to change the timing value in the .xml file. So if I can do it, anyone can.

now the question is what new value or multiplier is the correct one to use???

JohnBradley

iTrader: (30)

In the .xml there are formulas representing each sensor's output. When you open EVOscan you see them right before the "values". go into .xml and add or subtract as you see fit or have addl scan capability to know is correct.

taenaive

iTrader: (20)

looks like that Eval formula is screwed.
Someone gotta know the right way to translate to Fahrenheit from this register reading.

LogReference="CoolantTemp" RequestID="07" Eval="((-1.468x+139.74)*1.8)+32"

taenaive

iTrader: (20)

Okay, try this formula instead. I think it should be around right range if original formula was the close one.

Find this line LogReference="CoolantTemp" RequestID="07" Eval="((-1.468x+139.74)*1.8)+32"

and replace Eval with

Eval="((-1.468x+134.18)*1.8)+32

or

Eval="((-1.645x+139.74)*1.8)+32

Let me know which one works better

justchil

iTrader: (44)

I'll try those although I don't have anything other logging device to compare my numbers too :|

mrfred

iTrader: (50)

Any news on determining the correct conversion forumula?

nonschlont

iTrader: (3)

had 2 revive this 1 as Im experiencing the same issue. 203*F @ idle...
Just had a turbo and o2 (recirculated) installed today.
Last time I logged coolant temp, (while back) it was ~ 180 ish @ idle and have seen 162*F while cruising/on dyno, but wouldnt go lower than 188*F tonight while cruising. (~50* outside)
temp guage on dash is normal.

MUT 07 (0x6A47), Eval = "x*1.8+32", metric eval = "x", unit = "deg F", metric unit = "deg C", guage/chart min/max = 190

does this look about right?

mrfred

iTrader: (50)

Wow, this is very old history! The correct scaling formulas were determined long ago. You should be logging coolant temp on MUT10 or MUT11 (one is IAT and one is coolant temp, but I forget which is which). What version of EvoScan are you using?