|
RomRaider
Documentation
Community
Developers
|
| Author |
Message |
|
nsfw
|
Post subject: Experimental A2WC522N / 521N / 522S tables and parameters. Posted: Thu Dec 01, 2011 4:21 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
|
I'm creating this thread to share highly experimental tables and parameters for my ROM, which is A2WC522N.
I have confirmed that A2WC521N and A2WC522S are similar enough that everything here will work - the differences are posted below, byte-for-byte.
If you have a USDM 05 Legacy GT or Outback XT, and you are not running one of these ROMs, it will be safe to flash one. I switched my own ECU from A2WC510N to 522N by copying the tables I had modified to a stock 522N ROM, and that worked just fine. It takes much less time for you to do that switch, than for me to define new tables and parameters in other ROMs, so these are the only ROMs that I will be working on for the USDM 05 LGT/OXT.
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Thu Dec 01, 2011 4:21 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
These tables in the Fueling - Load Change Compensation section are related to the "Enrichment Compensation 2" logger parameter below. Also see this thread: viewtopic.php?f=25&t=7442The code that uses this tables is pretty complex. I don't think there is an easy way to explain this stuff, especially considering that I don't fully understand it yet. I've done my best to describe what I've figured out so far. When I disabled this completely, I found the my engine would stumble whenever I tried to raise RPM from idle. For example, when a traffic light turns green. So there is definitely a good reason for these tables's existency. The best theory we have so far is that these tables model the coating of fuel that accumulates on the walls of the intake ports. The model seems to work well at idle and low airflow. However it's very wrong for turbo spool-up - it was pushing my AFR about 0.7 richer than the fuel table was calling for (for details see the thread linked above). It also cause a very brief lean blip when you lift the throttle, which I suspect contributes to shift knock. Currently I have altered these tables as follows: A3) Input A Falling Load Activation is 0 at ECT of 176 F and higher. (applicable at low load as well as a high) A3) Input A Rising Load Activation, for loads of 1.2 g/rev and higher, is 0 at ECT of 158F and higher. B3) Input B Load Scaler is 0 at loads of 0.8 g/rev and higher. Click here for a screenshot of the modified tables.All other tables retain their stock values. I mostly just tried to disable this at high load while leaving it intact for low load, however the Input A Falling Load Activation table affects falling load at low load as well. However this doesn't seem to have any big drawbacks. The Fuel Pump Duty table lets you adjust the low and medium duty cycles for the fuel pump. I stumbled on these almost by accident, and didn't see anything useful about them at first, but I have heard that some fuel pumps run better if they don't get modulated power. In other words, if the Low and Medium values are raised from 33% and 66% to 100% and 100%, so the fuel pump controller acts like an on-off switch. No, I do not have tables that will alter when the ECU switches between the Low, Medium, and High levels.  I might figure it out eventually, but it's not as simple as I was hoping it would be. Code: <scaling toexpr="x" frexpr="x" format="%.2f" min="0" max="0" inc="5" storagetype="float"/> <scaling name="AVCS" toexpr="x*0.005493164" frexpr="x/0.005493164" format="%.3f" min="0" max="0" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="B1) Input B Deadband Threshold" toexpr="x*6.103516E-05" frexpr="x/6.103516E-05" format="%.3f" min="0" max="3.99994" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="B2) Input B Sigmoid" toexpr="x*0.0004882813-16" frexpr="(x+16)/0.0004882813" format="%.3f" min="-16" max="15.9995" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="B4) Input A/B Shared ECT Compensation" toexpr="x*0.0625" frexpr="x/0.0625" format="%.3f" min="0" max="15.9375" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="B6) Input B Rising Load Activation (ECT)" toexpr="x*0.0004882813" frexpr="x/0.0004882813" format="%.3f" min="0" max="31.9995" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="CL target? RPM*Load?" toexpr="x*1.525879E-05-0.5" frexpr="(x+0.5)/1.525879E-05" format="%.3f" min="0" max="0" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="Cruise?" toexpr="x*0.007813692-256" frexpr="(x+256)/0.007813692" format="%.3f" min="0" max="0" inc="0.1" storagetype="uint16" endian="big"/> <scaling name="Delta-Load InputC RPM Scaler" toexpr="x*0.1953125" frexpr="x/0.1953125" format="%.3f" min="0" max="49.8047" inc="0.1" storagetype="uint8" endian="big"/> <scaling name="Raw Short Float" units="units" toexpr="x" frexpr="x" format="%.2f" min="0" max="10000" inc="1" storagetype="float" endian="big"/> <scaling name="Raw Uint 16" units="raw" toexpr="x" frexpr="x" format="%.0f" min="0" max="255" inc="1" storagetype="uint16" endian="big"/>
<table name="Fuel Pump Duty" category="NSFW Beta" address="3ad04" type="2D" level="1" scaling="rawecuvalue"> <description>The ECU will set fuel pump duty cycle to 0%, 100%, or one of these two values.</description> <table name="Fuel Pump Duty" type="Static Y Axis" elements="2"> <data>Medium</data> <data>Low</data> </table> </table>
<table name="A2) Input A Falling Load RPM Scaler" category="Fueling - Load Change Compensation" address="c7630" type="2D" scaling="Delta-Load InputC RPM Scaler"> <description>If load is falling, and Flags027 has the 2 bit set, Input A is scaled by the value from this table, which is based on RPM. If load is falling, and Flags027 does not have the 2 bit set, the Input A Falling Load Scaler is used.</description> <table name="Engine Speed" address="c7608" type="Y Axis" elements="10" scaling="RPM"/> </table>
<table name="A3) Input A Falling Load Activation (ECT)" category="Fueling - Load Change Compensation" address="c7bde" type="2D" scaling="B6) Input B Rising Load Activation (ECT)"> <table name="ECT" address="c7470" type="Y Axis" elements="16" scaling="CoolantTemp(DegreesF)"/> </table>
<table name="A3) Input A Rising Load Activation (ECT)" category="Fueling - Load Change Compensation" address="c9110" type="3D" scaling="B6) Input B Rising Load Activation (ECT)"> <table name="ECT" address="c7470" type="X Axis" elements="16" scaling="CoolantTemp(DegreesF)"/> <table name="Load" address="c9104" type="Y Axis" elements="3" scaling="EngineLoad(g/rev)1"/> </table>
<table name="B1) Input B Deadband Threshold" category="Fueling - Load Change Compensation" address="c7cf8" type="2D" scaling="B1) Input B Deadband Threshold"> <description>If the rate of load change over time is less than the value in this table, Input B will be set to zero. If the rate of load change is greater, Input B will be set to the rate of load change (limited between -0.2 and +0.2).</description> <table name="Engine Speed" address="c7cd8" type="Y Axis" elements="8" scaling="RPM"/> </table>
<table name="B2) Input B Sigmoid" category="Fueling - Load Change Compensation" address="c7c34" type="2D" scaling="B2) Input B Sigmoid"> <description>Input B is transformed by this table, then the Input B scalers are applied.</description> <table name="Delta Load" address="c7c00" type="Y Axis" elements="13" scaling="Raw Short Float"/> </table>
<table name="B3) Input B Load Scaler" category="Fueling - Load Change Compensation" address="c7cc0" type="2D" scaling="B6) Input B Rising Load Activation (ECT)"> <description>Input B is then multiplied by this value, which is a function of Load.</description> <table name="Load" address="c7c94" type="Y Axis" elements="11" scaling="EngineLoad(g/rev)1"/> </table>
<table name="B4) Input A/B Shared ECT Compensation" category="Fueling - Load Change Compensation" address="c763a" type="2D" scaling="B4) Input A/B Shared ECT Compensation"> <description>This table is referenced when Flags030 is equal to 1 and Flags027 has the 2 bit set. Otherwise, the shared ECT compensation is 1.0. This is always applied to Input B, but is only applied to A when load is rising.</description> <table name="ECT" address="c7470" type="Y Axis" elements="16" scaling="CoolantTemp(DegreesF)"/> </table>
<table name="B5a) Input B Rising Load Scaler (Load)" category="Fueling - Load Change Compensation" address="c7c7c" type="2D" scaling="B6) Input B Rising Load Activation (ECT)"> <description>If load is rising, Input B is multiplied by this value, which is based on load.</description> <table name="Load" address="c7c50" type="Y Axis" elements="11" scaling="EngineLoad(g/rev)1"/> </table>
<table name="B5b) Input B Falling Load RPM Scaler (RPM)" category="Fueling - Load Change Compensation" address="c75fc" type="2D" scaling="Delta-Load InputC RPM Scaler"> <description>If load is falling, Input B is scaled by a value from this table, which is based on RPM.</description> <table name="Engine Speed" address="c75d4" type="Y Axis" elements="10" scaling="RPM"/> </table>
<table name="B6) Input B Rising Load Activation (ECT)" category="Fueling - Load Change Compensation" address="c7b9e" type="2D" scaling="B6) Input B Rising Load Activation (ECT)"> <description>If load is rising, input B is scaled by this value.</description> <table name="ECT" address="c7470" type="Y Axis" elements="16" scaling="CoolantTemp(DegreesF)"/> </table>
<table name="B6) Input B Falling Load Activation (ECT)" category="Fueling - Load Change Compensation" address="c7bbe" type="2D" scaling="B6) Input B Rising Load Activation (ECT)"> <description>If load is falling, input B is scaled by this value.</description> <table name="ECT" address="c7470" type="Y Axis" elements="16" scaling="CoolantTemp(DegreesF)"/> </table>
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Thu Dec 01, 2011 4:21 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
These logger parameters are handy for tuning tip-in: Code: <ecuparam id="E815" name="NSFW Tip-In Applied Counter" desc="This increases while tip-in is being applied. Tip-in enrichment will be terminated if/when this counter exceeds the value in the Tip-In Enrichment Disable Applied Counter Threshold table."> <ecu id="2F12785606"> <address length="1">0xFF59F0</address> </ecu> <conversions> <conversion units="Iterations" expr="x" format="0" /> </conversions> </ecuparam>
<ecuparam id="E817" name="NSFW Tip-In Cumulative" desc="This is proportional to the total amount of additional fuel delivered for tip-in (exact units are unknown). Tip-in enrichment will be terminated if/when this exceeds the value in the Tip-In Throttle Cumulative Reset table."> <ecu id="2F12785606"> <address length="4">0xFF59EC</address> </ecu> <conversions> <conversion units="Units" storagetype="float" expr="x" format="0.0000" /> </conversions> </ecuparam>
These are compensations that are added to the closed-loop fueling target. I still have no idea what most of them are for. Code: <ecuparam id="E890" name="NSFW Closed Loop Compensation 1" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF56A8</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E891" name="NSFW Closed Loop Compensation 2" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF56B8</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E892" name="NSFW Closed Loop Compensation 3" desc="Also known as AF Correction #3, this parameter oscillates during steady-state cruise. There are two chemical processes happening the catalytic converter, one of which requires additional oxygen, and periodically going slightly lean facilitates both processes. This is why your AFR gauge bounces steadily while you're cruising at a steady speed."> <ecu id="2F12785606"> <address length="1">0xFF57DC</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E893" name="NSFW Closed Loop Compensation 4" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF56D4</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E894" name="NSFW Closed Loop Compensation 5" desc="No idea. Always zero so far."> <ecu id="2F12785606"> <address length="1">0xFF56D8</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E895" name="NSFW Closed Loop Compensation 6" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF56E0</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E896" name="NSFW Closed Loop Compensation 7" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF56E4</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E897" name="NSFW Closed Loop Compensation 8" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF56E8</address> </ecu> <conversions> <conversion units="Delta Lambda" expr="x" format="0.00" /> </conversions> </ecuparam>
These are compensations that are added to the Final Fueling Base. I still have no idea what most of them are for. Compensation #2 is very interesting - see the "Load Change Compensation" tables above, and this thread: viewtopic.php?f=25&t=7442Code: <ecuparam id="E905" name="NSFW Enrichment Comp 1" desc="TBD."> <ecu id="2F12785606"> <address length="4">0xFF5D80</address> </ecu> <conversions> <conversion units="Lambda enrichment" storagetype="float" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E906" name="NSFW Enrichment Comp 2" desc="Acts like tip-in and tip-out, and causes half of the rich dip that FMIC owners have been complaining about for years."> <ecu id="2F12785606"> <address length="4">0xFF5614</address> </ecu> <conversions> <conversion units="Lambda enrichment" storagetype="float" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E907" name="NSFW Enrichment Comp 3" desc="No idea."> <ecu id="2F12785606"> <address length="4">0xFF58FC</address> </ecu> <conversions> <conversion units="Lambda enrichment" storagetype="float" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E908" name="NSFW Enrichment Comp 4" desc="No idea."> <ecu id="2F12785606"> <address length="4">0xFF59AC</address> </ecu> <conversions> <conversion units="Lambda enrichment" storagetype="float" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E909" name="NSFW Enrichment Comp 5" desc="No idea."> <ecu id="2F12785606"> <address length="4">0xFF59B4</address> </ecu> <conversions> <conversion units="Lambda enrichment" storagetype="float" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E910" name="NSFW Enrichment Comp 6" desc="No idea."> <ecu id="2F12785606"> <address length="4">0xFF594C</address> </ecu> <conversions> <conversion units="Lambda enrichment" storagetype="float" expr="x" format="0.00" /> </conversions> </ecuparam>
These are timing compensation. Again I have no idea what most of them are for. Most of them have been zero whenever I have logged them. One of them was active only when the engine was idling (used for idle RPM control, no doubt). You'll notice that 004 is missing from this list - that one was simply FBKC + FLKC. Code: <ecuparam id="E861" name="NSFW Test Timing Comp 001" desc="Used at startup time only?"> <ecu id="2F12785606"> <address length="1">0xFF5C84</address> </ecu> <conversions> <conversion units="RPM" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E862" name="NSFW Test Timing Comp 002" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF5c9c</address> </ecu> <conversions> <conversion units="RPM" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E863" name="NSFW Test Timing Comp 003" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF5cc0</address> </ecu> <conversions> <conversion units="RPM" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E865" name="NSFW Test Timing Comp 005" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF5c38</address> </ecu> <conversions> <conversion units="RPM" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E866" name="NSFW Test Timing Comp 006" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF5c74</address> </ecu> <conversions> <conversion units="RPM" expr="x" format="0.00" /> </conversions> </ecuparam>
<ecuparam id="E867" name="NSFW Test Timing Comp 007" desc="No idea."> <ecu id="2F12785606"> <address length="1">0xFF5cbc</address> </ecu> <conversions> <conversion units="RPM" expr="x" format="0.00" /> </conversions> </ecuparam>
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Thu Dec 01, 2011 4:24 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
Stuff I'm still looking for: - How to get the stock O2 sensor to report AFRs richer than 11.1. If you move the sensor to the downpipe it's almost as good as a wideband, except for that 11.1 limit.
- Fuel pump duty control. As noted above, this seems like it should be a simple thing but it's still a mystery to me.
- What does the ECU do with the 'gear position' parameter? I don't know, but I'm curious.
- Why does my AFR dip to 12:1 when I'm descending a mild hill with the cruise control on?
- Where's the table that governs how quickly the ECU shuts off the fuel injectors for engine-braking?
- Why are there three idle tables?
- I'd like to be able to control how much the AF Correction #3 parameter oscillates. I've heard from a couple of people would like to turn it off.
- I'd like to be able to adjust the min/max limits of AD Correction #1. This is the value that flutters around a lot in real-time to try to make your real AFR match the closed loop target AFR.
It's possible that the two parameters above might contribute to the surging / stuttering that so many people complain about - I don't think that's highly likely, but I'd still like to try disabling them just to see if it helps. By default, AFC #1 ranges between -25% and +25%, but maybe +/- 5% or 10% would help. Or not. Never know until you try. It boggles my mind that Subaru hasn't been able to fix the stumbling problem, especially in light of the number of people who have been complaining about over the last several years. I know a lot of people would be delighted if there was an easy fix. The MP Load compensation approach has worked very well for some people, but not all, so I think there's more than one thing contributing to the problem. Also note that if we had control over the AF sensor limit, and AF Corrections 1 and 3, that would pave the way toward running in closed loop all the time, targeting whatever AFR you want. How cool would that be?
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Thu Dec 01, 2011 4:31 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
Differences between A2WC522N (my 05 Legacy GT's stock ROM) and 522S (Outback XT) are: Code: c:\temp>fc /b A2WC522N-stock.hex A2WC522S.hex Comparing files A2WC522N-stock.hex and A2WC522S.HEX 00000FFC: 12 13 00000FFD: 33 32 00002007: 4E 53 00002014: 20 5F 00002015: 20 4F 00002016: 20 42 00002017: 20 4B 000C0007: 4E 53 000C0014: 20 5F 000C0015: 20 4F 000C0016: 20 42 000C0017: 20 4B 000CC9E1: 4E 53 000CD87E: 78 79 000FFAF8: 81 90 000FFB00: 00 FF 000FFB01: 01 FF 000FFB03: FE FF 000FFB88: 5E DF 000FFB89: 37 D3 000FFB8A: 00 BA 000FFB8B: 5D FD At 0xFFC, my ROM has 0x1233, the Outback has 0x1332. There's a function that copies "A2WC522N" from ROM into RAM, followed by the value at FFC. There's some I/O code that later overwrites that RAM location with 0 or 1 but I don't see any reads of that RAM. 0x2007, 0xC0007, 0xCC9E1 - these are all addresses of an N in A2WC522N. The Outback ROM of course has an "S" instead. At 0x2009, my ROM has the string "21ZH4TUS_MT " and the Outback version has "21ZH4TUS_MT_OBK " 0xC0007 is the "N" in A2WC522N. The Outback ROM of course has an "S" there. 0xC0014-17 is the same as 0x2009 - appending _OBK to 1ZH4TUS_MT (but there's no leading "2" on that string in this location, just a leading space instead). 0xCD87E is the ECU ID. Mine is 2F127 856, Outback is 2F127 956 0xFFAF8 gets copied to 0xFFFFBFE2, and there are no other XREFs to 0xFFFFBFE2. 0xFFB00-03, there are no other XREFs to this range. The values are all curiously close to zero, which is interesting but I'm not sure why.  0xFFB88-9B are used by methods at 0xF706 and 0xF87C, but I haven't got a clue what that code is doing. The differences between 522N and 521N are similarly trivial, but there is one additional interesting thing... 521N on left, 522N on right: 000C187A: 00 FF 000C187B: 06 FF These values are used by some code that is doing something related to cruise control. There was a reflash recall around this time which was related to LGTs and OXTs dropping out of cruise unexpectedly. The root cause was later determined to by the neutral position switch, though.
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
Guy on the corner
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Thu Dec 01, 2011 11:47 pm |
|
 |
| RomRaider Donator |
 |
Joined: Thu Aug 09, 2007 10:40 am Posts: 211 Location: Colorado
|
Subscribed. Didn't want you to think nobody was paying attention, NSFW. 
_________________ '05 LGT, BNR68+E85
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 02, 2011 12:04 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
Much appreciated. 
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
seabass
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Thu Dec 22, 2011 3:12 pm |
|
 |
| Newbie |
Joined: Tue Dec 07, 2010 6:01 pm Posts: 14
|
|
Any idea if this will work for A2WC510R? I'm hoping this will help me figure out some tip in knock I'm getting taking off from a stand still.
BTW, I owe you a few beers for everything I've learned from reading your posts.
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 12:15 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
|
I doubt they will be compatible. Is that an 05 LGT ROM? What market? You might be able to upgrade to A2WC522N, but I don't know how to find out for sure.
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
seabass
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 12:27 am |
|
 |
| Newbie |
Joined: Tue Dec 07, 2010 6:01 pm Posts: 14
|
|
| Top |
|
 |
|
dschultz
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 12:39 am |
|
 |
| RomRaider Developer |
Joined: Wed May 20, 2009 9:49 pm Posts: 7314 Location: Canada eh!
|
|
What trim level is it (7th digit in the VIN)? It looks like A2WC510R was updated to A2WC511R then to A2WC521R.
|
|
| Top |
|
 |
|
seabass
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 2:19 am |
|
 |
| Newbie |
Joined: Tue Dec 07, 2010 6:01 pm Posts: 14
|
|
7th number is 7. It's an xt limited. Any idea if there's a benefit of updating it?
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 3:01 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
I don't what the differences are, but I didn't notice any change when I upgraded from 510N to 522N. The only thing I noticed in the definitions is that per-cylinder timing comps went from 2D tables based on RPM to 3D based RPM and load, but the shape was basically the same: +2 degrees in cylinders B and D above 3600 RPM at any load, except that the 522N ROM also adds 1.78 degress at 2000 RPM and > 1.8 load. Big deal.  Anyway, I just did a binary comparison of 521N and 521R and they're quite different, I don't think these defs will work. I was hoping that since only the last letter is different, perhaps the ROMs would only be subtly different, but no... I think it's an AT vs MT thing - the 'R' versions are for the AT Outback XTs, and the 'N' versions are MT Legacy GTs. (The MT Outback and MT Legacy ROMs are almost identical.) I'm only going to be doing definitions like these for the most-recent ROM for a given make/model/year, to cut down on the amount of work. So if you want to tweak these tables you'll have to upgrade to 521R. If you want it bad enough to do the upgrade, I'll find them for you. 
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
|
seabass
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 3:16 am |
|
 |
| Newbie |
Joined: Tue Dec 07, 2010 6:01 pm Posts: 14
|
|
If it's as simple as copying my modded tables over to the A2WC522R rom, then I'll do it. Thanks again!
|
|
| Top |
|
 |
|
nsfw
|
Post subject: Re: Experimental A2WC522N / 521N / 522S tables and parameter Posted: Fri Dec 23, 2011 4:31 am |
|
 |
| Moderator |
Joined: Wed Nov 22, 2006 10:23 pm Posts: 2565
|
seabass wrote: If it's as simple as copying my modded tables over to the A2WC522R rom, then I'll do it. Thanks again! A2WC52 1R. download/file.php?id=964
_________________ 2005 Legacy GT w/ ATP 3076, IWG, MBC, BCS, BC 272, LC, FFS, OMG Please don't send questions via PM. Post a thread and send me a link to it instead. Thanks!
|
|
| Top |
|
 |
Who is online |
Users browsing this forum: No registered users and 2 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
|
|