Official 2 byte thread!
I was recently tuning an Ev08, with 94170015, at some considerable altitude and discovered that the 2-byte load address (895C,895D) was incorrect.
Or more likley, an un-compensated 2-byte load address.
The Load_IAT_BARO_16 address is at 8960, 8961.
Perhaps someone in Colorado might like to test this also and confirm/refute the result.
This got me wondering if any other addresses as listed in Jacks first post may in fact be un-compensated 2-byte.
Or more likley, an un-compensated 2-byte load address.
The Load_IAT_BARO_16 address is at 8960, 8961.
Perhaps someone in Colorado might like to test this also and confirm/refute the result.
This got me wondering if any other addresses as listed in Jacks first post may in fact be un-compensated 2-byte.
George
(x*0.3125)*([baro]/[AirTemp]) this produces a compensated 2-byte load for the 94170015 Rom, I would believe that it would also work correctly on your ROM ID
Remember, you are not changing anything in EcuFlash, only the formula in Evoscan, this means that by default you will also have to datalog your barometer, and air temperature.
But as you can see from my last post I have verified Merlin's mut table addresses to be compensated....
George
Sorry I posted an old formula from Evoscan the correct formula to compensate for barometer and air temp is.....
(x*0.3125)*([baro]/[AirTemp]) this produces a compensated 2-byte load for the 94170015 Rom, I would believe that it would also work correctly on your ROM ID
Remember, you are not changing anything in EcuFlash, only the formula in Evoscan, this means that by default you will also have to datalog your barometer, and air temperature.
But as you can see from my last post I have verified Merlin's mut table addresses to be compensated....
George
(x*0.3125)*([baro]/[AirTemp]) this produces a compensated 2-byte load for the 94170015 Rom, I would believe that it would also work correctly on your ROM ID
Remember, you are not changing anything in EcuFlash, only the formula in Evoscan, this means that by default you will also have to datalog your barometer, and air temperature.
But as you can see from my last post I have verified Merlin's mut table addresses to be compensated....
George
You shouldn't need to change anything in evoscan relating to the formula, all you need to do is make sure whatever request ID's you're using in evoscan you use in the MUT table in ecuflash.
<DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="04" RequestID2="05" Eval="0.3125*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="Measured voltage from the car battery. May be as low as 10 Volts when ignition is off. Should rise to around 14-15 Volts when the engine is running." Priority="1" Visible="False" />
This is the line that is suppose to be in evoscan, and for me I'm using ID"s 04 and 05.
Then in ecuflash I make sure that at these locations I have: 0x899A and 0x899B respectively.
<DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="04" RequestID2="05" Eval="0.3125*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="Measured voltage from the car battery. May be as low as 10 Volts when ignition is off. Should rise to around 14-15 Volts when the engine is running." Priority="1" Visible="False" />
This is the line that is suppose to be in evoscan, and for me I'm using ID"s 04 and 05.
Then in ecuflash I make sure that at these locations I have: 0x899A and 0x899B respectively.
I have the latest version of ECU Flash and this is all I did.
Go into the MUT Table and enter the information on the first page. Keep in mind all new version of ECU Flash have 3D MUT. I need to thank JohhBradley for his support. Here is why I entered for my IX.
88590015
2byte load
MUT 00 = 6B42
MUT 01 =6B43
2byte RPM
MUT 02 = 6B1E
MUT 03 = 6B1F
2byte AirFlow
MUT 04 = 6B9E
MUT 05 = 6B9F
I also used the latest version of EVO SCAN and it is setup for all the 2Byte monitoring. Therefore, with the latest version you only need to enter the 6 values shown above into the MUT Table.
When I logged 2byte RPM vs 1byte RPM it was perfect. I hope this helps as some of these threads are old and don't reflect software updates.
Hi
I'm a little lost on the air flow. For 96532706
I was logging grams/sec when on 1 byte load to gauge how hard i was pushing the turbo but can't seem to do that any more. I don't know how to convert the 2byte air flow in to grams/sec of lb/min
One other thing is my tuner is asking where the 2byte load is coming from as apposed to 1 byte and how much more accurate than 1 byte it is as we are seeing up in the 360's load with my FP Green HTA at 32psi. *a little more than he is used to seeing with similar sized turbos. (granted he has not done a Green HTA with my set up before)
Kind regards
Andy
I'm a little lost on the air flow. For 96532706
I was logging grams/sec when on 1 byte load to gauge how hard i was pushing the turbo but can't seem to do that any more. I don't know how to convert the 2byte air flow in to grams/sec of lb/min
One other thing is my tuner is asking where the 2byte load is coming from as apposed to 1 byte and how much more accurate than 1 byte it is as we are seeing up in the 360's load with my FP Green HTA at 32psi. *a little more than he is used to seeing with similar sized turbos. (granted he has not done a Green HTA with my set up before)
Kind regards
Andy
Would anybody care to send me the link with the necessary XML code on the first page? or post the code necessary for a 94170015 rom?
I am gathering it would be:
<table name="2 byte load high bit" address="8960" category="Misc" type="1D" level="1" scaling="uint16" />
<table name="2 byte load low bit" address="8961" category="Misc" type="1D" level="1" scaling="uint16" />
</rom>
Do I open ecuflash and alter the values to 27458 and 27459, respecitively?
Can anyone confirm this?
I am gathering it would be:
<table name="2 byte load high bit" address="8960" category="Misc" type="1D" level="1" scaling="uint16" />
<table name="2 byte load low bit" address="8961" category="Misc" type="1D" level="1" scaling="uint16" />
</rom>
Do I open ecuflash and alter the values to 27458 and 27459, respecitively?
Can anyone confirm this?
Last edited by prowakeskater; May 31, 2011 at 05:46 AM.






