EDIT :: Oh, wait ... EvoScan 2.0 uses the values that JB posted a while back that use the 2-byte load and compressor lb/min for calculation ... those values are fairly accurate.

 

You beat me to it! as Charlie put it to me its like a formula... a+b=c needs to be in that order. you need g/rev, then lb/min, then estimated hp and tq to get your calculation.
thanks charlie

 

Has anyone put the values against a dyno, or are they more for comparison against adding mods?

 

Charlie did some comparisons when JB was first working on the calculations ... I believe they were within like 5 hp of his Mustang numbers.

 

They are within 2-3hp as of the last dyno day I did on a dynojet 424x at Drift Office. It doesnt read like any other dynojet I have seen, but I am assured it is the same.

When I devised it, the 9.15 adjustment to the lbs/min rule (10 is a normal DJ) matched Charlie (Kreionic) within and 5hp and Jason (BigRic09) as well. The problem so far has been figuring out exactly when peak hp has been reached.

The notes in the margin of EvoScan 2.0 explain that but you will probably want to reread the post.

JB

 

Mine were within 2whp of my dynojet results for both HP and TQ.

 

So it seems to be a constant that it matches Dynojets at that correction factor. Jamie what type of DJ? I mean a newer one or an old one with the older software?

 

I forgot last time I was on the dyno. I really only use a mustang now. Next time I go I will log your formulas and send you the graphs to see if you can get the pk numbers at the right rpm. I think you asked me a while back and I completely forgot about it

 

I honestly don't know. It was my first dyno session right after I bought the car and wasn't as 'informed' about the dyno stuff at the time. It was a Turbotrix Racing in NJ though.

 

dumb question... Does it have to be in that order, cause mine looks like this: not exactly in that order, load mute 2byte, rpm mut 2byte, airflow mut 2byte, g/rev,lbs/min, est. hp, tq

<DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="Load MUT 2Byte Mod is a reflashed modification to the ECU via EcuFlash and an EvoScan Reprogramming USB Cable. This is a more accurate value, as the ECULoad value clips at 160 load (5*255/8)" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25*x" Unit="rpm" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes="RPM MUT 2Byte Mod is a reflashed modification to the ECU via EcuFlash and an EvoScan Reprogramming USB Cable. This value will allow display of rpms over 8,000rpm (31.25*255)" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Airflow MUT 2Byte Mod" LogReference="AirFlowMUT2Byte" RequestID="04" RequestID2="05" Eval="6.29*x/64" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="3000" ChartMin="0" ChartMax="3000" ScalingFactor="1" Notes="Airflow MUT 2Byte Mod is a reflashed modification to the ECU via EcuFlash and an EvoScan Reprogramming USB Cable. This value will allow display of AirFlow over 1600hz (6.25*255)" Priority="1" Visible="False" />
<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" 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="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Estimated Torque" LogReference="Lbsft" RequestID="21" Eval="([WHP]*5252/x)" Unit="lbsft"

 

*is blinded by a wall of code*

 

LOL...sorry. I am new to this, and didnt know how much to look @. I wanted to show the differences in my file, I have a question... there is a "y" in the code, but in mine it reads "n" ??? does that even matter?... and my first question about the order. Oh and does that even look right?

 

Wow my eyes hurt now lol. Your posting the formula from the XML. Since evoscan v2.0 you can edit the formula with the edit option instead of going through your XML.

What G20 posted was the the values under eval in the edit screen. Remember Phil thats how I walked you through this?

 

nonschlont,
as long as the loadcalc or load MUT 2Byte, the RPM or 2-bye RPM items are on top before the estimate power items then it is good. Those items need to be eval first in order to use the result for the horse powers calculation.

 

Thank you!
Also thank you charlie for walking me through it, I know we changed it through editing, but I came across that question, opened it up w/ notepad for the first time. ( I even expected it to look just like the quote ) lol I guess what I am trying to say is, now I am trying to understand everything, not just have it. sorta peicing it all together slowly lol
please dont take it like I dont trust you Charlie, definitely not the case!!! just trying to understand whats going on! I noticed that the order was a lil different and wanted to make sure that order would be ok.. It all stems from my lack of knowledge in this field! BUT I am trying to learn...
Big THANKS Charlie. You Da Man!