need help: new xml files for upcoming ECUFlash release
#137
Evolved Member
iTrader: (30)
Join Date: Dec 2003
Location: USA
Posts: 929
Likes: 0
Received 0 Likes
on
0 Posts
^^^Nice job gear head! This xml is setup for load based boost correct? Wondering if a PSI xml was created so people could choose. My other thought is to include tephra mods into the "mod" xml.
Thoughts?
Thoughts?
#138
Evolving Member
iTrader: (3)
The evo7base is modeled after mrfreds evo9base, these are stock boost tables that are re-labled with a few additions. Right now all of my "patched" tables are in a mods xml that is formatted the same way. The ROM specific xml just has stock tables in it.
I left a lot of tables in the base (some could be 9 specific?)so if anybody has any of those tables they can just add the addresses into the ROM specific. There's alot more tables, but at this time I'm not sure as to which are 100% proven. If you or anyone else can add to this with proven tables, please do so.
I left a lot of tables in the base (some could be 9 specific?)so if anybody has any of those tables they can just add the addresses into the ROM specific. There's alot more tables, but at this time I'm not sure as to which are 100% proven. If you or anyone else can add to this with proven tables, please do so.
#141
EvoM Guru
iTrader: (6)
I have taken a look and I still think the Dual BCS vehicles needs to be setup differently.
This is how I have setup 88570008 (which is a dual BCS):
You will see that we have one "main" turbo section, where everything thats common to both (single and dual bcs) setups lives. Then when we are looking at a dual BCS section we hive off another section purely for the Baseline WGDC tables.
The ONLY reason why I havn't just put them all into 1 catagoy is for readability, ie someone might get confused if they see 3 sets of Baseline WGDC's ( in the XML only, the program will only display relevant items)
Thoughts?
If you are happy with that I will post up the new evo9base.xml for you to grab.
Cheers
D.
This is how I have setup 88570008 (which is a dual BCS):
You will see that we have one "main" turbo section, where everything thats common to both (single and dual bcs) setups lives. Then when we are looking at a dual BCS section we hive off another section purely for the Baseline WGDC tables.
The ONLY reason why I havn't just put them all into 1 catagoy is for readability, ie someone might get confused if they see 3 sets of Baseline WGDC's ( in the XML only, the program will only display relevant items)
Thoughts?
If you are happy with that I will post up the new evo9base.xml for you to grab.
Cheers
D.
Last edited by tephra; Nov 23, 2008 at 05:24 PM.
#144
I have taken a look and I still think the Dual BCS vehicles needs to be setup differently.
This is how I have setup 88570008 (which is a dual BCS):
You will see that we have one "main" turbo section, where everything thats common to both (single and dual bcs) setups lives. Then when we are looking at a dual BCS section we hive off another section purely for the Baseline WGDC tables.
The ONLY reason why I havn't just put them all into 1 catagoy is for readability, ie someone might get confused if they see 3 sets of Baseline WGDC's ( in the XML only, the program will only display relevant items)
Thoughts?
If you are happy with that I will post up the new evo9base.xml for you to grab.
Cheers
D.
This is how I have setup 88570008 (which is a dual BCS):
You will see that we have one "main" turbo section, where everything thats common to both (single and dual bcs) setups lives. Then when we are looking at a dual BCS section we hive off another section purely for the Baseline WGDC tables.
The ONLY reason why I havn't just put them all into 1 catagoy is for readability, ie someone might get confused if they see 3 sets of Baseline WGDC's ( in the XML only, the program will only display relevant items)
Thoughts?
If you are happy with that I will post up the new evo9base.xml for you to grab.
Cheers
D.
#146
There are three sets of tables referenced in all the ROMs, but in USDM ROMs, table 2 is a stub table so its a sure thing that it never gets called. However, in JDM ROMs its a full table. No one has spent the time to figure out what logic determines when table 2 is called, so it may be the JDM ROMs can call it.
Last edited by mrfred; Nov 24, 2008 at 05:23 PM.
#150
Yeah, tephra suggested that a while ago, and now that we know the tables are far from correct, it would be a good idea to remove them. Hopefully that section can be repopulated with the correct tables in the near future.
Last edited by mrfred; Nov 24, 2008 at 08:01 PM.