2-Byte Load Issue
2-Byte Load Issue
I just did my first 2-Byte load log today. This was just a simple test to make sure that my 2-byte load and LC-1 were logging correctly. I noticed that the 2-byte seems way off and doesn't update often at all.
I set up the 2-byte load exactly as described in the "for dummies" thread, found here. I'm using the 2-byte load logging function just as it comes with EvoScan .99, as seen below:
Any thoughts on why I'm getting this odd response?
I set up the 2-byte load exactly as described in the "for dummies" thread, found here. I'm using the 2-byte load logging function just as it comes with EvoScan .99, as seen below:
Code:
<DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="" />
hmm... deffinatly something off. I'm my experience, it should log a little higher than calculated load. At least on my set-up. I noticed calculated load is usually off more as the load increases. For me, at 260 load range(2 byte), calcload is down in the 240-245 range. For you, it seems the reverse. It also seems to not be populating as often as it should.
CJ
CJ
I see one thing that might be wrong ...
The setup tutorial says to set up the tables like this:
EvoScan is calling RequestIDs of "00" and "01." Is the request ID the table name? Meaning that EvoScan is looking for "00" and my table is named "2 byte load high bit."
The setup tutorial says to set up the tables like this:
Code:
<table name="2 byte load high bit" address="3EE86" category="Misc" type="1D" level="1" scaling="uint16" /> <table name="2 byte load low bit" address="3EE6A" category="Misc" type="1D" level="1" scaling="uint16" />
I'm having a similar issue. I hit 261 2-byte load around 3,000rpms and it stays that wall all the way to 6,800 rpms. I copied the .xlm code from this tutorial
https://www.evolutionm.net/forums/sh...d.php?t=261465
https://www.evolutionm.net/forums/sh...d.php?t=261465
hmm... deffinatly something off. I'm my experience, it should log a little higher than calculated load. At least on my set-up. I noticed calculated load is usually off more as the load increases. For me, at 260 load range(2 byte), calcload is down in the 240-245 range. For you, it seems the reverse. It also seems to not be populating as often as it should.
CJ
CJ
Evolved Member
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
Hi
What is your ROM ID? I belive the thread you quote is for the 008 and 011 ROMs. Odd that others are getting higher loads with 2byteload, mine is quite a bit lower, but then I have a JDM car.
MB
What is your ROM ID? I belive the thread you quote is for the 008 and 011 ROMs. Odd that others are getting higher loads with 2byteload, mine is quite a bit lower, but then I have a JDM car.
MB
I just did my first 2-Byte load log today. This was just a simple test to make sure that my 2-byte load and LC-1 were logging correctly. I noticed that the 2-byte seems way off and doesn't update often at all.
I set up the 2-byte load exactly as described in the "for dummies" thread, found here. I'm using the 2-byte load logging function just as it comes with EvoScan .99, as seen below:
Any thoughts on why I'm getting this odd response?
I set up the 2-byte load exactly as described in the "for dummies" thread, found here. I'm using the 2-byte load logging function just as it comes with EvoScan .99, as seen below:
Code:
<DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="" />
My ROM is 88590015, just like the tutorial states. You can see the ROM ID reference here ...
I also double checked the values in another thread.
I tried changing the table names in my ROM but I saw no difference.
3.) Open ECUFlash v1.3 and a version 15 ROM image.
I tried changing the table names in my ROM but I saw no difference.
Trending Topics
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I see one thing that might be wrong ...
The setup tutorial says to set up the tables like this:
EvoScan is calling RequestIDs of "00" and "01." Is the request ID the table name? Meaning that EvoScan is looking for "00" and my table is named "2 byte load high bit."
The setup tutorial says to set up the tables like this:
Code:
<table name="2 byte load high bit" address="3EE86" category="Misc" type="1D" level="1" scaling="uint16" /> <table name="2 byte load low bit" address="3EE6A" category="Misc" type="1D" level="1" scaling="uint16" />
I modified my ROM per Fred's recommendation and the 2-byte load works great now. The values update quickly and are just slightly lower than calculated load in most cases. Thanks for the help everyone.
Thread
Thread Starter
Forum
Replies
Last Post