|
RomRaider
Documentation
Community
Developers
|
|
It is currently Tue May 21, 2013 1:59 pm
|
| Author |
Message |
|
Nuke209
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Wed Oct 12, 2011 10:17 pm |
|
 |
| Experienced |
Joined: Sun Oct 15, 2006 9:10 pm Posts: 191
|
NSFW wrote: Nuke209 wrote: What year/make/model is that ROM? 2005 STI USDM, I see that you have it for A2JZB10J, B11J is the latest revision for that same ecu
|
|
| Top |
|
 |
|
NSFW
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Thu Oct 13, 2011 2:48 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2273
|
|
There's a very good chance that the definitions I posted for WolfPlayer's car will work with that ROM. Try it... It will probably be pretty obvious if the definition isn't compatible - the tables will be filled with random numbers. If you post a screenshot of the tables I'll give them a sanity check.
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, LC, FFS, OMG Please don't send me tuning questions via PM - use the forums instead. Thanks!
|
|
| Top |
|
 |
|
Nuke209
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Thu Oct 13, 2011 11:13 pm |
|
 |
| Experienced |
Joined: Sun Oct 15, 2006 9:10 pm Posts: 191
|
Gave it a shot on the B11J and tables looks just like the B10J 
|
|
| Top |
|
 |
|
NSFW
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Thu Oct 13, 2011 11:55 pm |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2273
|
You're in business, then. 
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, LC, FFS, OMG Please don't send me tuning questions via PM - use the forums instead. Thanks!
|
|
| Top |
|
 |
|
Merp
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sat Nov 05, 2011 6:58 am |
|
 |
| Experienced |
 |
Joined: Thu Jul 23, 2009 1:46 pm Posts: 480 Location: Pennsyltucky
|
|
| Top |
|
 |
|
NSFW
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sat Nov 05, 2011 2:37 pm |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2273
|
Great! I am pretty sure that Freon's "dyn_def" table (I think that was the term he used) was trying to do the same thing, and the two were probably fighting each other at times. What I'd really like to do is make a 3D table with MAF on the X axis, and delta-MAF on the Y axis. The code that computes delta-load could probably be hijacked to compute delta-MAF for us instead. Gotta run, time for lunch. 
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, LC, FFS, OMG Please don't send me tuning questions via PM - use the forums instead. Thanks!
|
|
| Top |
|
 |
|
Merp
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sat Nov 05, 2011 6:27 pm |
|
 |
| Experienced |
 |
Joined: Thu Jul 23, 2009 1:46 pm Posts: 480 Location: Pennsyltucky
|
|
| Top |
|
 |
|
Merp
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sun Nov 06, 2011 1:47 pm |
|
 |
| Experienced |
 |
Joined: Thu Jul 23, 2009 1:46 pm Posts: 480 Location: Pennsyltucky
|
Just made some tweaks, zeroed the high load row (increased the row header as well) of the 3d table (Tau A Rising [ect x load]), and reduced the high load (1.4g/rev+) region of Tau B Rising - load. So far good results SPECIAL THANKS TO SUBARU DIESEL CREWScoobyrom is AWESOME! XMLwrite made things easier, but scoobyrom is in a league of its own. Thanks! A8DH200X - A8DH202X Code: <table type="2D" name="Tau B Rising - RPM" category="" storagetype="uint8" endian="big" sizey="10" storageaddress="0xC8AF0"> <!-- min: 0.9765625 max: 1.953125 average: 1.757813 --> <scaling units="RPM" expression="x*0.1953125" to_byte="x/0.1953125" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Engine Speed" storagetype="float" storageaddress="0xC8AC8"> <!-- 3600 to 7200 --> <scaling units="RPM" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau B Falling - RPM" category="" storagetype="uint8" endian="big" sizey="10" storageaddress="0xC8B24"> <!-- min: 0.9765625 max: 9.960938 average: 7.070313 --> <scaling units="RPM" expression="x*0.1953125" to_byte="x/0.1953125" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Engine Speed" storagetype="float" storageaddress="0xC8AFC"> <!-- 3600 to 7200 --> <scaling units="RPM" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau A Rising - ECT" category="" storagetype="uint16" endian="big" sizey="16" storageaddress="0xC9122"> <!-- min: 1 max: 6.905762 average: 3.807892 --> <scaling units="degC" expression="x*0.0004882813" to_byte="x/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Coolant Temp" storagetype="float" storageaddress="0xC8974"> <!-- -40 to 110 --> <scaling units="degC" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau A Falling 2 -ECT" category="" storagetype="uint16" endian="big" sizey="16" storageaddress="0xC9142"> <!-- min: 1 max: 1.899902 average: 1.432495 --> <scaling units="degC" expression="x*0.0004882813" to_byte="x/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Coolant Temp" storagetype="float" storageaddress="0xC8974"> <!-- -40 to 110 --> <scaling units="degC" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau A Falling 1 - ECT" category="" storagetype="uint16" endian="big" sizey="16" storageaddress="0xC9162"> <!-- min: 1 max: 14 average: 9.337524 --> <scaling units="degC" expression="x*0.0004882813" to_byte="x/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Coolant Temp" storagetype="float" storageaddress="0xC8974"> <!-- -40 to 110 --> <scaling units="degC" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau B Sigmoid" category="" storagetype="uint16" endian="big" sizey="13" storageaddress="0xC91B8"> <!-- min: -1 max: 1 average: -0.1097506 --> <scaling units="d(g/s)/dt" expression="x*0.0004882813-16" to_byte="(x+16)/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="delta Load" storagetype="float" storageaddress="0xC9184"> <!-- -0.3 to 0.3184 --> <scaling units="d(g/s)/dt" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau B Rising - Load" category="" storagetype="uint16" endian="big" sizey="11" storageaddress="0xC9200"> <!-- min: 0.125 max: 1.700195 average: 0.6045809 --> <scaling units="g/rev" expression="x*0.0004882813" to_byte="x/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Engine Load" storagetype="float" storageaddress="0xC91D4"> <!-- 0 to 3 --> <scaling units="g/rev" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="2D" name="Tau B Falling - Load" category="" storagetype="uint16" endian="big" sizey="11" storageaddress="0xC9244"> <!-- min: 0.5 max: 2 average: 0.7954546 --> <scaling units="g/rev" expression="x*0.0004882813" to_byte="x/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="Y Axis" name="Engine Load" storagetype="float" storageaddress="0xC9218"> <!-- 0 to 3 --> <scaling units="g/rev" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description> </description> </table> <table type="3D" name="Tau A Rising - ECT x Load" category="" storagetype="uint16" endian="big" sizex="16" sizey="3" storageaddress="0xCAAE4"> <!-- min: 1 max: 12.10938 average: 4.185404 --> <scaling units="" expression="x*0.0004882813" to_byte="x/0.0004882813" format="0.000" fineincrement="0.01" coarseincrement="0.1" /> <table type="X Axis" name="ECT" storagetype="float" storageaddress="0xC8974"> <!-- -40 to 110 --> <scaling units="DegC" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <table type="Y Axis" name="Load" storagetype="float" storageaddress="0xCAAD8"> <!-- 0.7 to 1.2 --> <scaling units="g/s" expression="x" to_byte="x" format="0.00" fineincrement="1" coarseincrement="5" /> </table> <description>Transient fueling (Tau) input A compensation applied during rising load values</description> </table>
_________________ RomRaider IRC Chat: http://webchat.freenode.net/?channels=romraider Subaru Alpha Definition Git Repo & Instructions: viewtopic.php?f=34&t=8635&p=82450#p82450
|
|
| Top |
|
 |
|
td-d
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Fri Nov 11, 2011 11:42 am |
|
 |
| RomRaider Donator |
Joined: Thu May 20, 2010 4:01 am Posts: 1422 Location: Johannesburg, South Africa
|
What's interesting in the '08 code (well, assuming I've found the right locations  ) is that all of these tables are doubled - which makes me think cruise / non-cruise. E.g. for the AZ1G202G : Code: loc_2BBFC: ; CODE XREF: Fun_Transient_Fueling_TauB_?+28j ROM:0002BBFC extu.b r14, r0 ROM:0002BBFE cmp/eq #1, r0 ROM:0002BC00 mov.l off_2BD48, r4 ; Sigmoid?Map2_C9478 ROM:0002BC02 bf loc_2BC06 ROM:0002BC04 mov.l off_2BD4C, r4 ; Sigmoid?Map2_C9428
_________________ ___________________________________ He who dies with the most gadgets wins.
|
|
| Top |
|
 |
|
NSFW
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Fri Nov 11, 2011 9:24 pm |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2273
|
The 05 LGT ROMs don't have the same cruise/non-cruise logic as the STI ROMs. There are some tables in my ROM that exist in pairs (target boost comes to mind), but even for those, the switch ratio is hard-coded to 1.0 so only one table ever gets used. It's like they started thinking about cruise/non-cruise while they were working on LGT ECUs, but didn't really use it until they did the STIs. 
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, LC, FFS, OMG Please don't send me tuning questions via PM - use the forums instead. Thanks!
|
|
| Top |
|
 |
|
dschultz
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sat Nov 12, 2011 11:26 am |
|
 |
| RomRaider Developer |
Joined: Wed May 20, 2009 9:49 pm Posts: 3662 Location: Canada eh!
|
|
Or, the tables are for use with another transmission type and they just left them and hardcoded the table select variable for the type of tranny the ECU would be used with.
|
|
| Top |
|
 |
|
dschultz
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sat Nov 12, 2011 11:44 am |
|
 |
| RomRaider Developer |
Joined: Wed May 20, 2009 9:49 pm Posts: 3662 Location: Canada eh!
|
td-d wrote: Code: ROM:0002BC00 mov.l off_2BD48, r4 ; Sigmoid?Map2_C9478 It's been like 30 years since I had to do math functions. I had to look that up to figure out what a sigmoid is 
|
|
| Top |
|
 |
|
dschultz
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sat Nov 12, 2011 11:55 am |
|
 |
| RomRaider Developer |
Joined: Wed May 20, 2009 9:49 pm Posts: 3662 Location: Canada eh!
|
|
How much of an affect would running TGV deletes have on the Tau? Do you think it would be enough to cause engine surge at low load (<1) engine acceleration through the 2000 - 2500 RPM range?
|
|
| Top |
|
 |
|
NSFW
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Sun Nov 13, 2011 1:26 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2273
|
dschultz wrote: How much of an affect would running TGV deletes have on the Tau? Do you think it would be enough to cause engine surge at low load (<1) engine acceleration through the 2000 - 2500 RPM range? I could see it having some effect.... my understanding is that they're primarily intended to improve atomization of the fuel on its way into the chamber, so the tau model probably should change depending on whether the TGVs are open. I wonder if that's one of the flags that gets checked in the code that calculates the delta-load enrichment, I haven't investigated any of them but that seems like a good candidate. However, my TGVs would open up as soon as I touched the throttle, so they were never in effect by the time I reached the end of my driveway. I've heard they were more active in more recent years, but I don't know any details. I get a bit of stumbling in that RPM range, mostly just when the motor is cold, but occasionally even when warm. I don't think AFR is a factor though, because my wideband stays pretty stable even when the stumble happens. But now you've got me wondering... if the TGVs stayed closed, maybe better atomization would be helpful.
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, LC, FFS, OMG Please don't send me tuning questions via PM - use the forums instead. Thanks!
|
|
| Top |
|
 |
|
dschultz
|
Post subject: Re: "FMIC Rich Dip" partially caused by the ECU Posted: Tue Nov 15, 2011 12:16 am |
|
 |
| RomRaider Developer |
Joined: Wed May 20, 2009 9:49 pm Posts: 3662 Location: Canada eh!
|
NSFW wrote: However, my TGVs would open up as soon as I touched the throttle, so they were never in effect by the time I reached the end of my driveway. I've heard they were more active in more recent years, but I don't know any details. Being deleted there's possibly less air turbulence which to me would suggest a larger puddle and a rich condition compared to just TGV's that are open all the time. So as not to clutter up this thread and take it off topic, I posted my problem over here.
|
|
| Top |
|
 |
Who is online |
Users browsing this forum: No registered users and 0 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|