SD - first test success
John - can you post up a image of your MIVEC map?
Edit - oops already got it. Couldn't see much of a difference which would explain the higher MAPVE on your ROM...
I am assuming my little bit of MIVEC at idle was the cause for the higher RPMVE on mine??
I have a track event this weekend, so the next couple of days I will be back on MAF tuning up the new turbo for my track map
But after that I will do V3 - hopefully we have some other guys testing with 88590015 
Edit - oops already got it. Couldn't see much of a difference which would explain the higher MAPVE on your ROM...
I am assuming my little bit of MIVEC at idle was the cause for the higher RPMVE on mine??
I have a track event this weekend, so the next couple of days I will be back on MAF tuning up the new turbo for my track map
But after that I will do V3 - hopefully we have some other guys testing with 88590015
Last edited by tephra; Feb 11, 2009 at 03:31 AM.
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
I did increase some of my MAPVE numbers from the ones I showed in post #1 (which were calculated from logs) based on the STFT at idle and low loads.
Aaaargh! I'm getting junk from my E02 call. I think the table header must be incorrect. Looking into it.
Aaaargh! I'm getting junk from my E02 call. I think the table header must be incorrect. Looking into it.
Last edited by jcsbanks; Feb 11, 2009 at 03:54 AM.
table header needs to have WORD length adder and table type.
ie 0x00 02 00 00 for 2d table with 0 adder... also no length after the axis memory location for 2d
beat me to it.
just remember to ENSURE the axis memory location is on a LONG boundary...
ie 0x00 02 00 00 for 2d table with 0 adder... also no length after the axis memory location for 2d
beat me to it.
just remember to ENSURE the axis memory location is on a LONG boundary...
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Works on the car. Nice and smooth. Fuel trims at idle and free revving seem even tighter now, within 1% most of the time! Engine doesn't feel any different, but nice to get the best resolution and adjustability.
hehe
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Thanks both for the suggestion.
I also with prolonged idle saw the LTFT move, again about 0.5-1% either way.
STFT are better than when on the MAF sensor.
I also with prolonged idle saw the LTFT move, again about 0.5-1% either way.
STFT are better than when on the MAF sensor.
Last edited by jcsbanks; Feb 11, 2009 at 05:55 AM.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Yes. And I've worked out a new way to patch the ROM that is much more straightforward when it comes to doing the scaling for different MAP sensors. I'll be deploying that in the coming months.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
mrfred, I think you need to load 0x00CD into the baro. You can't do this with an immediate as it is over 0x80 and you end up with a negative. I like the method though and am coding it at present. I think you also have to fix the MAP VE output header as I found in mine.
I've just about finished porting jcsbanks SD v3 over to the 88590015 ROM. Its been a fair bit of work because there are some differences in the USDM ROM code that required me to handle the MAF and baro errors differently. I'm putting what I have up now, so people who have a MAT sensor installed can start preparing a ROM.
*I have one remaining item to finish before it can be used.* I still need to create a scaling for the GM MAT sensor that can be inserted into the IAT sensor scaling table so that I can switch the IAT values over to MAT values.
*NOTE* Once the port is complete (hopefully by Wednesday afternoon), it will only work in conjunction with my MAT logging patch (along with a GM IAT sensor installed somewhere along the intake track).
EDIT #1: Duh, I forgot to mention that the car needs to have my JDM MAP sensor patch + JDM MAP sensor installed.
EDIT #2: jcsb, just in case you are wondering, the NOP1 erases the move #1, r2 that tephra mentioned.
Patched ROM and xml are here (copy the tables from the patched ROM to your ROM):
http://se30.dyndns.org:8080/EVO/8859..._JCSBSD3M1.zip
ECUFlash screen shot:
*I have one remaining item to finish before it can be used.* I still need to create a scaling for the GM MAT sensor that can be inserted into the IAT sensor scaling table so that I can switch the IAT values over to MAT values.
*NOTE* Once the port is complete (hopefully by Wednesday afternoon), it will only work in conjunction with my MAT logging patch (along with a GM IAT sensor installed somewhere along the intake track).
EDIT #1: Duh, I forgot to mention that the car needs to have my JDM MAP sensor patch + JDM MAP sensor installed.
EDIT #2: jcsb, just in case you are wondering, the NOP1 erases the move #1, r2 that tephra mentioned.
Patched ROM and xml are here (copy the tables from the patched ROM to your ROM):
http://se30.dyndns.org:8080/EVO/8859..._JCSBSD3M1.zip
ECUFlash screen shot:
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
mrfred, in 88570008:
ROM:0000B23C mov.w @(h'1AA,pc), r4 ; [0000B3EA] = h'CD
ROM:0000B23E mov.l @(h'1FC,pc), r5 ; [0000B43C] = baroadc1b
ROM:0000B240 mov.w r4, @r5 ; [0000B438] = baroadc2b
ROM:0000B242 shll2 r4 ; [0000B24C]
ROM:0000B244 mov.l @(h'1F0,pc), r6 ; [0000B438] = baroadc2b
ROM:0000B246 mov.w r4, @r6
ROM:0000B23C mov.w @(h'1AA,pc), r4 ; [0000B3EA] = h'CD
ROM:0000B23E mov.l @(h'1FC,pc), r5 ; [0000B43C] = baroadc1b
ROM:0000B240 mov.w r4, @r5 ; [0000B438] = baroadc2b
ROM:0000B242 shll2 r4 ; [0000B24C]
ROM:0000B244 mov.l @(h'1F0,pc), r6 ; [0000B438] = baroadc2b
ROM:0000B246 mov.w r4, @r6
Last edited by jcsbanks; Feb 11, 2009 at 08:45 AM.