2byte to 1byte load mod
Oct 24, 2009, 01:56 PM
#61
Evolving Member
iTrader: (14)
Join Date: Oct 2006
Location: Los Angeles, CA
Posts: 179
Likes: 0
Received 0 Likes
on
0 Posts
log 1byte load on EvoScan, add this on your data.xml for EvoScan, or use EvoScan 2.6.
no - forget 2byte load or load 11bit4.
Code:
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.2*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="0.1" Notes="" Priority="1" Visible="False" />
Nov 4, 2009, 03:56 PM
#62
Okay I gotta question.
If I wanted to log 1 byte load on a 96420008 ROM, how would I got about doing it?
I am already loggin the 2byte corrected that everyone used to log.
I already have 1 byte load ready to log in EVOscan.
Just need to know what to do to the ROM to make this work.
If I wanted to log 1 byte load on a 96420008 ROM, how would I got about doing it?
I am already loggin the 2byte corrected that everyone used to log.
I already have 1 byte load ready to log in EVOscan.
Just need to know what to do to the ROM to make this work.
Nov 20, 2009, 03:30 AM
#69
Evolving Member
Join Date: Dec 2005
Location: South Africa
Posts: 232
Likes: 0
Received 0 Likes
on
0 Posts
Hi all,
Ok, now i am very confused.
i am on the v7 tephra 88850715 rom and found that by 2 byte load is a good 10% above the load the ecu is using (verified from my timing logs) and seanv has the same issue (who posted in the v7 thread)
sean got 1byte load working (raw) and it seems to be correct according to the timing numbers now.
But:
what does the ecu use for 88850715 rom for output of timing and afr. does it use raw load+baro+temp or just raw load?
my MUT table are set at: MUT00 = 6b42 and MUT 01 = 6b43
from what i have read these are logging raw 2byte load. i want to either log corrected (temp+baro) 2byte or 1byte load.
i have changed evoscan to read 1byte, so if i can get the correct mut address for it to read correctly.
also is the mut table purely for logging or does the ecu use it for output . i.e. if we change altitude, will the ecu compesate for it if i am using the raw 1byte mut numbers?
I live at 5500ft, so compensated would be best (I assume)
Mike
if i go 1byte it seems the address needs to be what? 6b4a and 6b4b (assuming that the 898a/b for the 9653 rom
Ok, now i am very confused.
i am on the v7 tephra 88850715 rom and found that by 2 byte load is a good 10% above the load the ecu is using (verified from my timing logs) and seanv has the same issue (who posted in the v7 thread)
sean got 1byte load working (raw) and it seems to be correct according to the timing numbers now.
But:
what does the ecu use for 88850715 rom for output of timing and afr. does it use raw load+baro+temp or just raw load?
my MUT table are set at: MUT00 = 6b42 and MUT 01 = 6b43
from what i have read these are logging raw 2byte load. i want to either log corrected (temp+baro) 2byte or 1byte load.
i have changed evoscan to read 1byte, so if i can get the correct mut address for it to read correctly.
also is the mut table purely for logging or does the ecu use it for output . i.e. if we change altitude, will the ecu compesate for it if i am using the raw 1byte mut numbers?
I live at 5500ft, so compensated would be best (I assume)
Mike
if i go 1byte it seems the address needs to be what? 6b4a and 6b4b (assuming that the 898a/b for the 9653 rom
Nov 20, 2009, 08:52 AM
#71
Evolving Member
Join Date: Dec 2005
Location: South Africa
Posts: 232
Likes: 0
Received 0 Likes
on
0 Posts
will it not give a similar reading to 2byte if uncompensated, hence why i thought of staying with 2byte to get compensation working as our high altitude has an effect.
on the 8859015 rom what mut00/01 numbers do i enter for 1byte load?
thanks
Mike
Thread
Thread Starter
Forum
Replies
Last Post
