EvoScan error, please help!
Feb 27, 2009 | 08:51 PM
#1
Thread Starter
Evolved Member
iTrader: (22)
Joined: Nov 2003
Posts: 2,408
Likes: 6
From: Northern KY near Cincy
EvoScan error, please help!
EvoScan has a wonderful feature of estimating HP and TQ. The problem I have is that the HP to TQ crossover point isn't 5250 RPM like it should be. I have the crossover at 6343 RPM.
In additon the Power @ rpm never gives an RPM value. It always reads "@ 0rpm"
Please let me know what I need to change in EvoScan to get the HP and TQ feature to be more accurate.
I know it is only for reference. The thing is...it is fun to see what my tuning changes effect.
Thank you for any help you all may provide.
Paul
In additon the Power @ rpm never gives an RPM value. It always reads "@ 0rpm"
Please let me know what I need to change in EvoScan to get the HP and TQ feature to be more accurate.
I know it is only for reference. The thing is...it is fun to see what my tuning changes effect.
Thank you for any help you all may provide.
Paul
Feb 27, 2009 | 08:59 PM
#2
Suggestion: upgrade to DataLogLab, it's a better tool and what most of us use to street tune Evo's with. I was never able to get anything reliable from EvoScan's tool. I'm only running EvoScan 2.1 though but I never could get any repeatable results from it. You can try it for 30 days, after the trial you will want to buy the universal version if you like the product. I can send you a definition file if you pm me your email address.
http://www.dataloglab.com/
http://www.dataloglab.com/
Last edited by Mr. Evo IX; Feb 27, 2009 at 09:03 PM.
Feb 28, 2009 | 09:53 PM
#3
Thread Starter
Evolved Member
iTrader: (22)
Joined: Nov 2003
Posts: 2,408
Likes: 6
From: Northern KY near Cincy
Thanks for getting me going with DLL. I would, however, still like to get EvoScan resolved to get simular results. It seems to me that the calculation in EvoScan is wrong some how.
Anyone else experience this???
Anyone else experience this???
Feb 28, 2009 | 09:58 PM
#4
yep! the power/torque @rpm is also 0 for me. I'll try to figure to see if I can change that somehow. If it's ok can you tell me what are your power/torque numbers so I can compare to mine to see how close they are. I have both numbers from EvoScan and dynojet.
Feb 28, 2009 | 10:06 PM
#5
Thread Starter
Evolved Member
iTrader: (22)
Joined: Nov 2003
Posts: 2,408
Likes: 6
From: Northern KY near Cincy
EvoScan says HP = 383 TQ = 355 crossover is at 6343 RPM.
DLL says HP = 385 TQ = 375 crossover is at 5250 RPM
The HP numbers are pretty close. It is the TQ that is way off in EvoScan.
I am tuned with an FP Green at 24 lbs, Revolver cams, all supporting mods.
Yes, I know I should be seeing more. I am still tuning. Learning as I go.
Both were set with correction factors at 1.0
DLL says HP = 385 TQ = 375 crossover is at 5250 RPM
The HP numbers are pretty close. It is the TQ that is way off in EvoScan.
I am tuned with an FP Green at 24 lbs, Revolver cams, all supporting mods.
Yes, I know I should be seeing more. I am still tuning. Learning as I go.
Both were set with correction factors at 1.0
Last edited by Appauldd; Feb 28, 2009 at 10:06 PM. Reason: adding info
Feb 28, 2009 | 11:00 PM
#6
Good number. On my 05 MR, EvoScan says 340 HP and 311 TQ.
I'm on stock turbo, hks 272s, tbe with testpipe, k&n drop-in, fuel pump, 780cc, mbc peak at 24 psi at 4200 rpm gradually drop to 20 psi at 7000-7500 rpm on 91 oct gas. I'm tuning the car myself and been making good progress with it.
I'm using EvoScan dyno feature as a way to measure my tuning progress. When it was stock with only hi-flow cat made 277 hp on dynojet and 282 on evoscan. After put on the mods, with some tuning for straighten out the A/F ratio, it made a little over 310 with about 22 psi boost. After many high way pulls I 'm able to get the current numbers. Off course the EvoScan dyno feature is only for measurement but it's nice to have and even better if it's working more correctly.
I'm on stock turbo, hks 272s, tbe with testpipe, k&n drop-in, fuel pump, 780cc, mbc peak at 24 psi at 4200 rpm gradually drop to 20 psi at 7000-7500 rpm on 91 oct gas. I'm tuning the car myself and been making good progress with it.
I'm using EvoScan dyno feature as a way to measure my tuning progress. When it was stock with only hi-flow cat made 277 hp on dynojet and 282 on evoscan. After put on the mods, with some tuning for straighten out the A/F ratio, it made a little over 310 with about 22 psi boost. After many high way pulls I 'm able to get the current numbers. Off course the EvoScan dyno feature is only for measurement but it's nice to have and even better if it's working more correctly.
Mar 1, 2009 | 12:17 AM
#7
nice #'s! 
<my evoscan reads 350hp/325tq @ 24.5psi, and 360/345 @ 27psi. crossover was 5093 - 5250
@ 27psi on a "Dynojet" translated to 330/340 but Im not even sure if the dyno was calibrated correctly, as "Boost" was off on the dyno. reading almost 2 psi low...
<my evoscan reads 350hp/325tq @ 24.5psi, and 360/345 @ 27psi. crossover was 5093 - 5250
@ 27psi on a "Dynojet" translated to 330/340 but Im not even sure if the dyno was calibrated correctly, as "Boost" was off on the dyno. reading almost 2 psi low...
Trending Topics
Mar 1, 2009 | 09:28 PM
#9
Evolving Member
Joined: Mar 2006
Posts: 228
Likes: 0
Code:
<DataListItem DataLog="N" Color="" Display="Estimated g/rev" LogReference="gRev" RequestID="CALC" Eval="[LoadCalc]/95" Unit="g/Rev" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="12" ChartMin="0" ChartMax="12" ScalingFactor="1" Notes="If you are using the Load MUT 2Byte Mod, you can double click this item, and edit the Function to be: [LoadMUT2Byte]/95

If RequestID contains more than 2 characters, i.e. CALC, then there is a keep alive request sent to the vehicle ecu while this gets calculated." Priority="1" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Estimated Lbs/min" LogReference="LbsMin" RequestID="21" Eval="([gRev]*x)/454" Unit="lbs" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="65" ChartMin="0" ChartMax="65" ScalingFactor="1" Notes="" Priority="1" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Estimated Horsepower" LogReference="WHP" RequestID="CALC" Eval="[LbsMin]*9.15" Unit="Whp" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="1000" ChartMin="0" ChartMax="1000" ScalingFactor="1" Notes="If RequestID contains more than 2 characters, i.e. CALC, then there is a keep alive request sent to the vehicle ecu while this gets calculated." Priority="1" Visible="False" /> <DataListItem DataLog="N" Color="" Display="Estimated Torque" LogReference="Lbsft" RequestID="21" Eval="([WHP]*5252/x)" Unit="lbsft" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="1000" ChartMin="0" ChartMax="1000" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
Mar 1, 2009 | 10:40 PM
#12
Mar 31, 2009 | 01:45 PM
#14
Registered User
Joined: Nov 2007
Posts: 1,507
Likes: 2
From: Trinidad
any progress on this? i log loadcalc, RPM, speed along with the others (Knock, ...).
i am getting some bogus curves i think its because my vehicle settings are off. anyone mind sharing their vehicle settings for an Evo IX?
i am getting some bogus curves i think its because my vehicle settings are off. anyone mind sharing their vehicle settings for an Evo IX?
