Yes 2byte airflow is MUT 02-03.

 

OK. Anybody know the barometer and temperature compensated load MUT addresses?

 

Is there any known issues with fuel trim logging problems using V7 with evoscan. I tried unsucessfully tonight on different laptops to log fuel trims and neither worked using two different versions of evoscan leading me to believe the problem is in V7.

 

what version of V7 you using?

fuel trims should be fine, unless one of the custom roms has somehow disabled closed loop...

 

I used the 88590715

 

so not one of the preconfigured SD rom's? just the ROM straight from my zip?

 

yes pm Kracka he was manning the laptops and can tell you exactly what was going on

 

i'll wait until he chimes in

 

im assuming you had the rear O2 turned off...

 

First off let me just say that I don't have any experience using Tephra V7, I've always been a huge fan of V5.10 so thats what I've stuck with for quite some time. PlanoEvo put V7 on his car and I was merely logging it.

Fuel trims (low, mid, high) were not adjusting and were just staying at the default "zero" of .1008 even though we drove for over an hour trying to get them to adjust. O2 feedback trim was cycling normally and as expected. We tried two different laptops running different versions of EvoScan with the same result.

PlanoEvo - My recommendation is to switch back to V5.10 since it was working perfectly for us last week.

 

well ive seen fuel trims just stop working sometimes... not sure what the problem is...

maybe just reflash the V7 rom again...

 

OK thanks. I'll have him reflash the same ROM back on and if that doesn't work we'll just go back to V5.10 and go from there.

 

if you are using one of phenems / recompile 88590715 rom's it may have the rear O2 delete mod (somehow in addition to Tephra's?) and when I first changed to V7 this did not allow me to log fuel trims. look under the per bit section and disable that mod.




side note: Tephra, any suggestions on why in the 88591715 the gear does not use (or display in evoscan) properly? I get:
logged / used Gear=1 (for 1rst - 2nd)

Then: Gear=2 (for 3rd=5th)

The gear based boost worked 100% correctly in V6.

Thanks!

 

hrmmm.... the only thing i can think of is the MUT addresses have changed... can you let me know what MUTID your logging and what it points to?

 

Evoscan:

<DataListItem DataLog="Y" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.0241*x-3.087" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes="" Priority="1" Visible="false" />

<DataListItem DataLog="Y" Color="" Display="Gear" LogReference="Gear" RequestID="40" Eval="x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="5" Visible="False" />

<DataListItem DataLog="Y" Color="" Display="RPM_SPEED_RATIO_AVERAGE" LogReference="RPM_SPEED_RATIO_AVERAGE" RequestID="42" RequestID2="43" Eval="x/36.37" Unit="rpm/kph" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" />



MUT 40 = 8447

MUT 42 = 8448

MUT 43 = 8449