Notices
ECU Flash

Coolant Temp and EvoScan

Thread Tools
 
Search this Thread
 
Old Jul 26, 2006 | 12:53 PM
  #1  
ScrappyJack's Avatar
Thread Starter
Newbie
iTrader: (1)
 
Joined: Dec 2005
Posts: 94
Likes: 0
From: Orlando, FL
Question Coolant Temp and EvoScan

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?
Reply
Old Jul 26, 2006 | 01:54 PM
  #2  
MalibuJack's Avatar
EvoM Guru
20 Year Member
iTrader: (5)
 
Joined: Feb 2003
Posts: 10,572
Likes: 14
From: Royse City, TX
Yeah the value is off.. you can fix it in your XML Definition file.. I think the AIT value is off a bit too..
Reply
Old Jul 26, 2006 | 02:06 PM
  #3  
taenaive's Avatar
Evolved Member
iTrader: (20)
 
Joined: Apr 2005
Posts: 920
Likes: 0
From: Chantilly,VA
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.
Reply
Old Aug 14, 2006 | 06:31 AM
  #4  
justchil's Avatar
Evolved Member
iTrader: (44)
 
Joined: Oct 2003
Posts: 4,409
Likes: 0
From: Charleston, WV
Can anyone confirm these changes ^^. I'll keep searching but I'd like to at least get my coolant reading right
Reply
Old Aug 14, 2006 | 06:36 AM
  #5  
evo 8 ya's Avatar
Evolved Member
iTrader: (31)
 
Joined: Jul 2003
Posts: 2,318
Likes: 1
From: 39.800N 76.983W
Originally Posted by justchil
Can anyone confirm these changes ^^. I'll keep searching but I'd like to at least get my coolant reading right
+1
Reply
Old Aug 14, 2006 | 02:14 PM
  #6  
TTP Engineering's Avatar
Account Disabled
iTrader: (465)
 
Joined: May 2005
Posts: 8,824
Likes: 2
From: Central FL
How tough is it to change the XML formulas?
Reply
Old Aug 14, 2006 | 02:23 PM
  #7  
Atlmethevo's Avatar
Evolving Member
 
Joined: Nov 2005
Posts: 313
Likes: 0
From: Atlanta
If you know XML it's easy I already changed it in mine.
Reply
Old Aug 14, 2006 | 03:41 PM
  #8  
AlwaysinBoost's Avatar
Evolved Member
iTrader: (17)
 
Joined: Aug 2004
Posts: 3,275
Likes: 0
From: In da streetz
Originally Posted by TTP Engineering
How tough is it to change the XML formulas?
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???
Reply
Old Aug 14, 2006 | 03:55 PM
  #9  
JohnBradley's Avatar
Evolved Member
Shutterbug
Liked
Loved
Community Favorite
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,406
Likes: 78
From: Northwest
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.
Reply
Old Aug 14, 2006 | 05:58 PM
  #10  
taenaive's Avatar
Evolved Member
iTrader: (20)
 
Joined: Apr 2005
Posts: 920
Likes: 0
From: Chantilly,VA
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"
Reply
Old Aug 14, 2006 | 06:41 PM
  #11  
taenaive's Avatar
Evolved Member
iTrader: (20)
 
Joined: Apr 2005
Posts: 920
Likes: 0
From: Chantilly,VA
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
Reply
Old Aug 15, 2006 | 03:28 AM
  #12  
justchil's Avatar
Evolved Member
iTrader: (44)
 
Joined: Oct 2003
Posts: 4,409
Likes: 0
From: Charleston, WV
I'll try those although I don't have anything other logging device to compare my numbers too :|
Reply
Old Aug 25, 2006 | 07:13 AM
  #13  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Any news on determining the correct conversion forumula?
Reply
Old Dec 1, 2010 | 01:23 AM
  #14  
nonschlont's Avatar
Evolved Member
iTrader: (3)
 
Joined: Mar 2007
Posts: 1,760
Likes: 2
From: Ca
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?

Last edited by nonschlont; Dec 1, 2010 at 02:32 AM.
Reply
Old Dec 1, 2010 | 03:41 AM
  #15  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
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?
Reply



All times are GMT -7. The time now is 05:15 PM.