EvoScan EvoX Datalogger now supports 2byte Boost/Load/IPW
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.
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.
Let me know if you have any more problems.
As promised, here's the latest XML with some corrections to addresses and calculations. The JDM/EDM series should be all fine now.
Last edited by SiC; Aug 5, 2009 at 01:42 AM.
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" />
<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" />
Hamish just bought an AEM so I'm sure he'll start working out the bugs that everyone is experiencing.
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!
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!
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?
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.
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?
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?
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?
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?




