Notices
Evo X Engine Management / Tuning Forums Discuss the major engine management systems.

EvoScan EvoX Datalogger now supports 2byte Boost/Load/IPW

Thread Tools
 
Search this Thread
 
Old Aug 4, 2009 | 07:01 PM
  #76  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
Originally Posted by Bob_tm
I'm trying to log 5304007 with JDM 2008 xml. All work perfect except
1. Wrong formula for InVVT. It should be the same as for ExVVT Eval="(x-4096)*-0.01953".
2. LoadMIVEC don't work properly. It show something, but real load is 2-3x more. Tested using timing and mivec values.
Yeah, sorry I screwed up on that one. The formula for the InVVT is the same for the ExVVT. Also the correct address for the LoadMivec should be 2380876c. I'll post up a corrected data.xml soon and make sure it gets put into the next release.

Let me know if you have any more problems.
Reply
Old Aug 5, 2009 | 01:34 AM
  #77  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
As promised, here's the latest XML with some corrections to addresses and calculations. The JDM/EDM series should be all fine now.
Attached Files
File Type: zip
Data.zip (22.1 KB, 0 views)

Last edited by SiC; Aug 5, 2009 at 01:42 AM.
Reply
Old Aug 5, 2009 | 02:01 AM
  #78  
Bob_tm's Avatar
Evolving Member
 
Joined: Oct 2008
Posts: 126
Likes: 0
From: Ukraine
It's for AEM UEGO and EDM 53040007 rom

<DataListItem DataLog="Y" Color="" Display="LC-1 AFR" LogReference="LC1AFR" RequestID="23809346" Eval="9.50+(10.00*x/1023)" Unit="afr" MetricEval="" MetricUnit="" ResponseBytes="2" GaugeMin="9" GaugeMax="16" ChartMin="9" ChartMax="16" ScalingFactor="1" Notes="Rear 02 Sensor ecu pin used for LC-1 volts output." Priority="1" Visible="False" />
Reply
Old Aug 5, 2009 | 02:15 AM
  #79  
BigT's Avatar
Evolved Member
iTrader: (8)
 
Joined: Sep 2006
Posts: 1,029
Likes: 2
From: NW NJ
Originally Posted by SiC
As promised, here's the latest XML with some corrections to addresses and calculations. The JDM/EDM series should be all fine now.
For all of the newbies.... where do I put this file? Or where is the one located that I need to change?
Reply
Old Aug 5, 2009 | 02:33 AM
  #80  
Bob_tm's Avatar
Evolving Member
 
Joined: Oct 2008
Posts: 126
Likes: 0
From: Ukraine
"c:\Program Files\EvoScan\EvoScan v2.6 Beta19\DataSettings"
Reply
Old Aug 5, 2009 | 09:57 AM
  #81  
BigT's Avatar
Evolved Member
iTrader: (8)
 
Joined: Sep 2006
Posts: 1,029
Likes: 2
From: NW NJ
Sweet. Thanks.
Reply
Old Aug 5, 2009 | 11:46 AM
  #82  
EVOXSILVER's Avatar
Newbie
 
Joined: Oct 2008
Posts: 52
Likes: 0
From: French Polynesia
Sorry for that but is there anyone who can help me with my AEM UEGO logging problem???
Reply
Old Aug 5, 2009 | 08:21 PM
  #83  
SiC's Avatar
SiC
Evolved Member
iTrader: (1)
 
Joined: Jun 2008
Posts: 1,018
Likes: 0
From: Kanagawa, Japan
Originally Posted by EVOXSILVER
Sorry for that but is there anyone who can help me with my AEM UEGO logging problem???
Most problems with the AEM are related to the USB adapter that everyone is using. The AEM may work in Hyper Terminal or other apps but in Evoscan it does not work. What I did was purchase the Keyspan Serial > USB adapter and all my problems went away.

Hamish just bought an AEM so I'm sure he'll start working out the bugs that everyone is experiencing.
Reply
Old Aug 5, 2009 | 08:52 PM
  #84  
Hiboost's Avatar
Evolved Member
iTrader: (9)
 
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
Question Boost logging capped at 27 psi?

I tried to crank up my boost on 100 octane unleaded tonight and had some issues with the datalogging. My 30 psi boost gauge reads about 1-2 psi high but it was at an estimated 31 psi at torque peak which should be about 29 psi actual, yet the log was still showing up as 26.66074 to 26.70911 psi. It varies slightly but seems to be dependant on how warm the sensor is possibly.

Basically instead of my boost tapering evenly from ~26.6 psi down to 26 psi at 6750 it is holding the 26.6 - 26.7 boost all the way to 6200 and then tapering to 26 psi at 7000. My load cells are also 5% higher on average as well and was faster through the RPM ranges according to VDR and about 30 WTQ extra down low.

Any idea what the max value is for boost? I remember seeing it hit 27.0 psi once but since then I have't seen it climb past 26.7 psi. I thought a 3 bar map sensor should at least log atmospheric plus 2 bar or ~29 psi? Or are we supposed to have a 3.5 bar map sensor in which case it should be good to 36 psi!
Reply
Old Aug 5, 2009 | 09:35 PM
  #85  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
The Evo 10 MAP sensor (same as the JDM Evo 9 MAP sensor) is good to 32 psi at sea level. Are you logging with Mode23, and what boost scaling formula are you using in EvoScan?
Reply
Old Aug 5, 2009 | 10:10 PM
  #86  
Hiboost's Avatar
Evolved Member
iTrader: (9)
 
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
Originally Posted by mrfred
The Evo 10 MAP sensor (same as the JDM Evo 9 MAP sensor) is good to 32 psi at sea level. Are you logging with Mode23, and what boost scaling formula are you using in EvoScan?
Indeed I am using Mode23 with EvoScan 2.6b16. I'll look at upgrading to the latest version but still it was surprising to see it capped that soon. The formula in this version of EvoScan is: (x/4*0.19347)-14.5 with my elevation being between 400-500 ft above sea level.
Reply
Old Aug 5, 2009 | 10:15 PM
  #87  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
well that formula will allow for 34+ psig
Reply
Old Aug 5, 2009 | 10:18 PM
  #88  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
The formula is correct for you elevation, so no problem there. Its not uncommon for boost gauges to read high, but another possible reason for the difference between the MAP sensor and the boost gauge is that EvoScan may not be sampling fast enough to catch the boost spike if its very short in duration. What's the average time between lines of data in your EvoScan logs?
Reply
Old Aug 5, 2009 | 10:23 PM
  #89  
xPRimNT's Avatar
Evolved Member
15 Year Member
Photogenic
iTrader: (4)
 
Joined: Feb 2008
Posts: 610
Likes: 0
From: Edmonton, Alberta
Ok, I seriously can't deal with this anymore.

Why are my third gear logs "skipping"?

My fourth gear pulls are fine, and I get the full RPM range. 1/4 times, my third gear pulls are fine, and I get the full range. However, more often than not, it skips a solid 3+ seconds starting a couple samples after I start WOT. Has ANYONE else seen this?
Reply
Old Aug 5, 2009 | 10:37 PM
  #90  
Hiboost's Avatar
Evolved Member
iTrader: (9)
 
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
Originally Posted by mrfred
The formula is correct for you elevation, so no problem there. Its not uncommon for boost gauges to read high, but another possible reason for the difference between the MAP sensor and the boost gauge is that EvoScan may not be sampling fast enough to catch the boost spike if its very short in duration. What's the average time between lines of data in your EvoScan logs?
I do know my boost gauge reads 1-2 psi high since it sits at 1-2 psi with the car off depending on barometric pressure. I've also compared it to a boost gauge at Buschur's dyno and it was also about 1-2 psi higher than their reading. The sampling rate shouldn't have any problem as my boost gauge shows a solid 31 psi fading to 28 psi by 7000 rpm with almost zero spiking since my signal to the Forge WGA preloaded 7 turns has no restrictor pills in the boost lines. I'm getting about 12 logs per second with 12 items logged.
Reply



All times are GMT -7. The time now is 08:25 AM.