Okay so I started messing around with this tonight but ran into a couple of snags. I altered the lines at 3ee6e & 3ee72 just as I did for 2 byte load (for whatever their values were) way back and altered the lines to 27550 and 27551. I entered the scaling presumably as the eval line in EvoScan but it kept shutting down as long as I tried to log it. If I turned it off it was okay so I am sure I have the scaling request wrong. Any ideas?

This is how I understood the line should look in the data.xml from what I read:

<DataListItem DataLog="Y" Color="" Display="2 Byte Airflow" LogReference="2Byte Hz" RequestID="02" RequestID2="03" Eval="6.29/64*([256*requestID02]+requestID03)" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="2800" ChartMin="0" ChartMax="2800" ScalingFactor="0.1" Notes=""/>

or something like that anyway...I just threw in the max Hz values since I didnt have anything to go by.


JB

 

I think its your Eval thats throwing it off....from looking through EvoScan I don't think Eval ever explicitly uses the requestID in calculations. Its always "x" where x is the response from the ECU or LogReference for the particular item (e.g InjPulseWidth).

 

What version of EvoScan are you using? My 2-byte load entry in EvoScan 0.99 is:

<DataListItem DataLog="Y" Color="" Display="2-Byte Load" LogReference="Load2Byte" RequestID="00" RequestID2="01" Eval="0.3125x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes=""/>

If you had set up 2-byte air flow to be reported at MUT 02 and 03, then it would look like:

<DataListItem DataLog="Y" Color="" Display="2-Byte Air Flow" LogReference="AirFlow2Byte" RequestID="02" RequestID2="03" Eval="6.29x/64" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="3000" ChartMin="0" ChartMax="3000" ScalingFactor="1" Notes=""/>

The Eval formula may not have the correct constants. I haven't looked to see what the constants are for 2-byte airflow.

 

Thanks M thats what I was doing wrong. I knew the Eval had to be the cause but I just didnt know where I need to change it or what I needed to change it too. I am using V99 as well. The 2 byte load works great (I did it months ago) I just couldnt get the 2 byte airflow to work to save my life.

On another note I tried using the formula that Eric posted in this thread to have a Air Mass Calculation (like g/s or lbs/min) in Evoscan and while it didnt work yet I think its a matter of getting my eval written correctly for it as well. I might have the formulae off and thats the problem I am not sure. I am kinda weak on code and seeing how things need to be, its been a LONG time since I have messed around with anything and then it was just hex hacking GT1 to make better cars

JB

 

Okay after testing the changes that M suggested today I was able to momentarily log the hz as recorded as a direct image of "normal" hz. BUT, it would as soon as V99 linked, disconnect and give me the error message that "2 byte hz does not have reference in logtable". I have no idea why or what its referring to yet however.

JB

 

Let's make sure that this is correct. What were the factory values at 0x3ee6e and 0x3ee72?

 

I use the same equation MRFRED posted in post 33 of this thread for 2byte airflow and logged it for 45 minutes. Works great.

 

Using the Type 13 for the base, the values were 27177 and 27176 respectively.

 

ok. You got the right addresses. Seems that the hiccup is in your EvoScan Data.xml file. Did you add an entry to convert the 2-byte airflow reading into a g/s value (or some other value)?

 

No, but I did just notice that scaling factor is 0.1 and I am not sure how I arrived at that. Could that be it? I dont have my lappy with me to log (still at work) but it seems somewhat plausible I spose? It looks exactly like the entry in #31 except I changed the request id part to what you had: 6.29x/64 and left everything else the same.

JB

 

Ah ha. The LogReference name cannot have any spaces in it. "2Byte Hz" -> "2ByteHz".

 

D'OH...figures it was something stupid. Thanks for the troubleshooting, I owe you now...next time you are over this way or I am that way the beer is definitely on me.

 

Adding 2 byte airflow to USDM Evo IX type 13 and 14 (NOT 15) condensed. Thanks to JCSBanks, l2r99gst, MrFred, and Everyone else that contributed

Add 2 new tables to the xml

Open Ecuflash and change these values to 27550 and 27551 respectively.

Add this to EvoScan:

Works perfect

 

On thing I want to mention is that when you first look at the new 1D tables in ECUFlash, the values should be 27177 and 27176. If they are not, then the addresses are not correct for your ROM, and don't make the change to 27550 and 27551.

 

Thanks for those numbers. I'll be sure to check mine before heading out to log. I just did this mod last night.