96940011 05 EVOVIII ROM: Known Patches
Jul 28, 2007, 10:52 AM
#47
Evolving Member
iTrader: (8)
Join Date: Nov 2005
Location: Seattle, Washington
Posts: 155
Likes: 0
Received 0 Likes
on
0 Posts
PHP Code:
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
Jul 31, 2007, 03:38 AM
#48
Evolved Member
iTrader: (6)
Join Date: Jul 2005
Location: Charleston, SC
Posts: 1,228
Likes: 0
Received 0 Likes
on
0 Posts
It is. Those are actually the ids that v.99 comes "pre setup" pointing at.
PHP Code:
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
So does that data string actually work in EvoScan?
Aug 2, 2007, 07:52 AM
#51
L2r99gst,
Thank you for your help today! however, it does not apear FFFF8976 is correct or there is something I did incorrectly. I put 8976 in 02 and 8977 in 03 and selected RPM 2 byte in evoscan. 2 byte RPM was logging in incorrect values. The wierd thing is, the log followed engine RPMs basic curves but, it was really exagerated. The spikes and dips happened at the same time but there was not the same difference between the two. I do not have access to the log right now but as an example, when engine RPM was at 906.25, 2byte RPM was at 7093.75. Then when Engine RPM is at 1312.5, 2 byte RPM is at 10593.75.
Anyway, if anybody has any advice on this I would appreciate it.
Thanks!
-Scott
Thank you for your help today! however, it does not apear FFFF8976 is correct or there is something I did incorrectly. I put 8976 in 02 and 8977 in 03 and selected RPM 2 byte in evoscan. 2 byte RPM was logging in incorrect values. The wierd thing is, the log followed engine RPMs basic curves but, it was really exagerated. The spikes and dips happened at the same time but there was not the same difference between the two. I do not have access to the log right now but as an example, when engine RPM was at 906.25, 2byte RPM was at 7093.75. Then when Engine RPM is at 1312.5, 2 byte RPM is at 10593.75.
Anyway, if anybody has any advice on this I would appreciate it.
Thanks!
-Scott
Aug 2, 2007, 10:22 AM
#52
Newbie
iTrader: (5)
Join Date: Jul 2007
Location: Charlotte
Posts: 58
Likes: 0
Received 0 Likes
on
0 Posts
Ok, this is my first post on the evom forum. I like what I see so far in the ecuflash sub forums.
My question is how do I know which are unused request spots in my MUT table so I can add in 2byte RPM? I know which columns and rows I modified for 2byte Load, how do I know which columns and rows I can modify for future use?
I also noticed in my evoscan data.xml file that 2byte airflow references requestid 02 & 03 and 2byte RPM does as well, is this a problem?
Thanks!
My question is how do I know which are unused request spots in my MUT table so I can add in 2byte RPM? I know which columns and rows I modified for 2byte Load, how do I know which columns and rows I can modify for future use?
I also noticed in my evoscan data.xml file that 2byte airflow references requestid 02 & 03 and 2byte RPM does as well, is this a problem?
Thanks!
Aug 2, 2007, 11:23 AM
#53
Ok, this is my first post on the evom forum. I like what I see so far in the ecuflash sub forums.
My question is how do I know which are unused request spots in my MUT table so I can add in 2byte RPM? I know which columns and rows I modified for 2byte Load, how do I know which columns and rows I can modify for future use?
I also noticed in my evoscan data.xml file that 2byte airflow references requestid 02 & 03 and 2byte RPM does as well, is this a problem?
Thanks!
My question is how do I know which are unused request spots in my MUT table so I can add in 2byte RPM? I know which columns and rows I modified for 2byte Load, how do I know which columns and rows I can modify for future use?
I also noticed in my evoscan data.xml file that 2byte airflow references requestid 02 & 03 and 2byte RPM does as well, is this a problem?
Thanks!
Aug 18, 2007, 09:05 AM
#54
Evolved Member
iTrader: (12)
Join Date: Jun 2005
Location: Sleepy Hollow
Posts: 821
Likes: 0
Received 0 Likes
on
0 Posts
The MUT addresses that handle the commonly logged parameters can be deduced from the EvoScan "Data.xml" file. As you suspect, both 2-byte airflow and 2-byte rpm can't use the same MUT addresses. If you want to log 2-byte load, 2-byte airflow, and 2-byte rpm, then a few more unlogged MUT addresses are needed. I've been using MUT address 8A through 94 to probe various RAM addresses as part of my effort to understand the Evo programming. That block is not currently used to host any parameters that people are interested in logging. Any unused MUT address can be used though. Doesn't need to be consecutive, although for accuracy, it helps.
So if for some reason I did want to log all three, could I put 8976 in 04 and 8977 in 05 of the MUTT table, then go in to the data.xml for EVOScan and change the requestid to 04 and requestid2 to 05? Just skimming the request ID's in data.xml of EVOScan, I don't see anything requesting from those two...
Also with 2 byte load configured, you can not log calculated load, correct? Since it is requesting from 00 and that has been now been "re-allocated" for 2 byte load along with 01?
Aug 18, 2007, 10:28 AM
#55
Sorry to be the dumb kid in the class...I hope the lightbulb will go on one of these days.
So if for some reason I did want to log all three, could I put 8976 in 04 and 8977 in 05 of the MUTT table, then go in to the data.xml for EVOScan and change the requestid to 04 and requestid2 to 05? Just skimming the request ID's in data.xml of EVOScan, I don't see anything requesting from those two...
Also with 2 byte load configured, you can not log calculated load, correct? Since it is requesting from 00 and that has been now been "re-allocated" for 2 byte load along with 01?
So if for some reason I did want to log all three, could I put 8976 in 04 and 8977 in 05 of the MUTT table, then go in to the data.xml for EVOScan and change the requestid to 04 and requestid2 to 05? Just skimming the request ID's in data.xml of EVOScan, I don't see anything requesting from those two...
Also with 2 byte load configured, you can not log calculated load, correct? Since it is requesting from 00 and that has been now been "re-allocated" for 2 byte load along with 01?
- Calc load and 2-byte load together: it should be possible in concept because calc load has nothing to do with the real MUT 00, but have not tried it. Not sure what evo4mad is doing with the "00" for calculations.
Aug 18, 2007, 10:34 AM
#57
What I've found in EvoScan is that completely calculated values, such as LoadCalc or IDC%, can be set to any Request ID since they never actually make a call to the ECU. My IDC% calculation and a fuel trim calculation I've set up are both calling request ID's used by the 2-byte air flow mod and all 3 are working perfectly.
Aug 28, 2007, 11:37 PM
#58
Can someone please explain to me exactly what I need to do to the MUT table and evoscan data file to get 2 byte rpm working if I already have 2byte load and airflow..Thanks in advance for any help, it is greatly appriciated..
Last edited by PeteyTurbo; Aug 28, 2007 at 11:41 PM.
Aug 29, 2007, 08:24 PM
#60
PHP Code:
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
Then, in your MUT table, go to where requests 04 and 05 are and put in 8976 and 8977, respectively. Also, change the Eval from 31.25x to 3.906x as mrfred mentioned above.
Eric
Last edited by l2r99gst; Aug 29, 2007 at 08:28 PM.