How to log load with v7?
just use load calc change the request to 41 and fuction to 1.2*x that way your map tracer will work .
or put this into your xml listed as data in evoscan
or put this into your xml listed as data in evoscan
Code:
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load1B" RequestID="41" Eval="1.2*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="270" ChartMin="0" ChartMax="270" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
What are the advantages of logging 1byte over 2byte in v7?
I have also noticed that while logging 2byte and 1byte simultaneously the values are quite different at times.
For example in the same log where I hit 26psi my 2byte load was around 270-280 whereas my 1byte was showing 300-310.
I have also noticed that while logging 2byte and 1byte simultaneously the values are quite different at times.
For example in the same log where I hit 26psi my 2byte load was around 270-280 whereas my 1byte was showing 300-310.
There are many different loads...uncompensated, baro compensated, and baro+temp compensated. I always forget which tephra made his 1byte load.
Edit: Just looked it up to confirm. Tephra's 1byte is uncompensated load.
For fuel, the baro+temp comp load is used
For timing, baro+temp is used unless IAT is above 77F. Then baro comp load is used.
Edit: Just looked it up to confirm. Tephra's 1byte is uncompensated load.
For fuel, the baro+temp comp load is used
For timing, baro+temp is used unless IAT is above 77F. Then baro comp load is used.
Last edited by l2r99gst; Feb 20, 2010 at 11:28 AM.
What are the advantages of logging 1byte over 2byte in v7?
I have also noticed that while logging 2byte and 1byte simultaneously the values are quite different at times.
For example in the same log where I hit 26psi my 2byte load was around 270-280 whereas my 1byte was showing 300-310.
I have also noticed that while logging 2byte and 1byte simultaneously the values are quite different at times.
For example in the same log where I hit 26psi my 2byte load was around 270-280 whereas my 1byte was showing 300-310.
My mismatch issue was mainly caused by having 1.2 in the "2byte to 1byte load factor" field in my v7 ROM and having 1.3 in the EvoScan eval.
The XML definition for 1-byte load may only have been added in a version of EvoScan released after the v2.4 that you are using.
Try updating your EvoScan to the latest version i.e. v2.7 beta 5, and see if the 1-byte load field then appears in EvoScan:
http://www.limitless.co.nz/evoscan/EvoScanv2.7beta5.zip
EDIT: Hmm, the link for v2.7 Beta 5 doesn't seem to be working at the moment. You'll have to check if the link is back up later, or ask someone else for a copy, or log a support ticket:
http://www.evoscan.org/helpdesk/index.php?a=add
EvoScan v2.6 is available here:
http://www.limitless.co.nz/evoscan/EvoScanv2.6.zip
Try updating your EvoScan to the latest version i.e. v2.7 beta 5, and see if the 1-byte load field then appears in EvoScan:
http://www.limitless.co.nz/evoscan/EvoScanv2.7beta5.zip
EDIT: Hmm, the link for v2.7 Beta 5 doesn't seem to be working at the moment. You'll have to check if the link is back up later, or ask someone else for a copy, or log a support ticket:
http://www.evoscan.org/helpdesk/index.php?a=add
EvoScan v2.6 is available here:
http://www.limitless.co.nz/evoscan/EvoScanv2.6.zip
Last edited by SoCal Rally; Feb 22, 2010 at 10:48 AM.
If you want to log 2byte in v7 you have to modify the MUT table as you would any other ROM.
See https://www.evolutionm.net/forums/ec...te-thread.html for more information.
What to do in Evoscan to coud log 2byte temp+baro comp load ? What to write in the Escan XML ? in the v7 9653 just change the MUT setting for that one ?
2-byte LOAD_Temp_and_Baro_Compensated
MUT00 = 898A
MUT01 = 898B
2-byte LOAD_Temp_and_Baro_Compensated
MUT00 = 898A
MUT01 = 898B
Thread
Thread Starter
Forum
Replies
Last Post





