Links to jcsbanks' Speed Density patches
#62
Evolving Member
iTrader: (1)
Join Date: May 2008
Location: Wausau WI
Posts: 128
Likes: 0
Received 0 Likes
on
0 Posts
I would also like to put in a request for the 9653 rom, it is the easiest (most problem free) rom for those of us using evo8 ecus in 2g DSMs to use and I would love to try this out.
#67
Evolving Member
iTrader: (1)
Join Date: May 2008
Location: Wausau WI
Posts: 128
Likes: 0
Received 0 Likes
on
0 Posts
1) Copy the definitions in the xml file in the zipped file to your current 94170015.xml file, launch ECUFlash, open the patched ROM in ECUFlash, and copy all the SD values from the stock patched ROM in the zipped file to a copy of your current ROM. Upload your patched ROM (*not* the one included in the zip file) to your ECU.
It looks like it can be done either way
Also I just wanted to double check a few other things quickly.
Is there a preference for where the MAT sensor output goes? I've seen some discussion saying that it is better to leave the AIT sensor locked and run the MAT through the fuel temp input but which does the 9055 rom assume we are using? Probably the AIT input but I wanted to be sure.
it appears that it goes in the IAT slot if you are just using the SD patches or it can go in the fuel temp input if you are USDM using the MAT patch. More instruction here
Originally Posted by mrfred
Its just for setup convenience. I daily drive my car, and I wasn't ready to swap ECU pins back and forth as I fiddled with SD tuning. To make the patch compatible with reading the GM IAT sensor from the IAT ADC input, leave the "SD Convert IAT to MAT (0x03 -> 0x0E)" entry as 0x03. This sounds counter-intuitive to the table name, but that's because I didn't do such a good job of naming that table.
Do I need to adjust the scaling in ecuflash for my GM map or do I just adjust VE to compensate?
The way I understand it we change the scaling using this
<scaling name="MAP 16bit" units="kPa" toexpr="x*100/82" frexpr="x*82/100" format="%.0f" min="0" max="400" inc="1" storagetype="uint16" endian="big"/>
Copy the MAP 16bit table from ecuflash then change the function in your xml. Fire up ecuflash again and the top row for this table should have changed but the bottom row will be the same. Return the top row to its previous values (before the change in the function) and alter the last cells (top and bottom) to the highest that the sensor can show (311 I believe for a GM map). I was making this part much harder in my mind than it actually is.
I'll start rereading the first success thread tomorrow to see if I can answer my own questions.
Last edited by the_mork; May 15, 2009 at 11:38 AM. Reason: Starting to answer my own questions
#68
Is there any good reason not to use the patched rom? I certainly have fewer tables in my rom that have been altered than in the patched rom. Is there something done to this rom then that would mean that I can't just copy to it instead of the other way around (just like the install for a Tephra rom?). Specifically referring to 9055 if it matters at all.
It looks like it can be done either way
Also I just wanted to double check a few other things quickly.
Is there a preference for where the MAT sensor output goes? I've seen some discussion saying that it is better to leave the AIT sensor locked and run the MAT through the fuel temp input but which does the 9055 rom assume we are using? Probably the AIT input but I wanted to be sure.
it appears that it goes in the IAT slot if you are just using the SD patches or it can go in the fuel temp input if you are USDM using the MAT patch. More instruction here
Do I need to adjust the scaling in ecuflash for my GM map or do I just adjust VE to compensate?
The way I understand it we change the scaling using this
<scaling name="MAP 16bit" units="kPa" toexpr="x*100/82" frexpr="x*82/100" format="%.0f" min="0" max="400" inc="1" storagetype="uint16" endian="big"/>
Copy the MAP 16bit table from ecuflash then change the function in your xml. Fire up ecuflash again and the top row for this table should have changed but the bottom row will be the same. Return the top row to its previous values (before the change in the function) and alter the last cells (top and bottom) to the highest that the sensor can show (311 I believe for a GM map). I was making this part much harder in my mind than it actually is.
I'll start rereading the first success thread tomorrow to see if I can answer my own questions.
It looks like it can be done either way
Also I just wanted to double check a few other things quickly.
Is there a preference for where the MAT sensor output goes? I've seen some discussion saying that it is better to leave the AIT sensor locked and run the MAT through the fuel temp input but which does the 9055 rom assume we are using? Probably the AIT input but I wanted to be sure.
it appears that it goes in the IAT slot if you are just using the SD patches or it can go in the fuel temp input if you are USDM using the MAT patch. More instruction here
Do I need to adjust the scaling in ecuflash for my GM map or do I just adjust VE to compensate?
The way I understand it we change the scaling using this
<scaling name="MAP 16bit" units="kPa" toexpr="x*100/82" frexpr="x*82/100" format="%.0f" min="0" max="400" inc="1" storagetype="uint16" endian="big"/>
Copy the MAP 16bit table from ecuflash then change the function in your xml. Fire up ecuflash again and the top row for this table should have changed but the bottom row will be the same. Return the top row to its previous values (before the change in the function) and alter the last cells (top and bottom) to the highest that the sensor can show (311 I believe for a GM map). I was making this part much harder in my mind than it actually is.
I'll start rereading the first success thread tomorrow to see if I can answer my own questions.
I think the GM MAP scaling is somewhere in the thread. I'll find it and put it in the first post in a day or so.
#70
iTrader: (27)
Hi mrfred!
I am about to give this a try and wanted to clarify something on the IAT. The SD patch will look for the IAT in the Fuel Temp pin as your original post for installing the IAT. Am I right on that assumption?
Also, on the USDM Evo 9 rom, the "SD set baro value", the value comes at "0". Is that right? (See attached pic).
Thanks in advanced!
I am about to give this a try and wanted to clarify something on the IAT. The SD patch will look for the IAT in the Fuel Temp pin as your original post for installing the IAT. Am I right on that assumption?
Also, on the USDM Evo 9 rom, the "SD set baro value", the value comes at "0". Is that right? (See attached pic).
Thanks in advanced!
#71
Hi mrfred!
I am about to give this a try and wanted to clarify something on the IAT. The SD patch will look for the IAT in the Fuel Temp pin as your original post for installing the IAT. Am I right on that assumption?
Also, on the USDM Evo 9 rom, the "SD set baro value", the value comes at "0". Is that right? (See attached pic).
Thanks in advanced!
I am about to give this a try and wanted to clarify something on the IAT. The SD patch will look for the IAT in the Fuel Temp pin as your original post for installing the IAT. Am I right on that assumption?
Also, on the USDM Evo 9 rom, the "SD set baro value", the value comes at "0". Is that right? (See attached pic).
Thanks in advanced!
#74
Evolved Member
iTrader: (2)
ARGH. I didn't get my sensor installed this past weekend (too busy fighting with the wife's scooby), and I won't have the time to do any physical work on my Evo for at least two weeks; otherwise, I'd jump on it.
l2r99gst?
My penance for not being able to help with this will be to work on rolling a patched version of 96530706 with DMA logging, since I've been missing that quite a bit since switching to tephra's latest version.
l2r99gst?
My penance for not being able to help with this will be to work on rolling a patched version of 96530706 with DMA logging, since I've been missing that quite a bit since switching to tephra's latest version.