Stock ECU Tuning Wiki is up and running
So I'm going to be installing Tephra's Rom soon and wanted to use this as a chance to provide for the Wiki ...
I've already uploaded a stock ROM. My plan is to upload packages with:
94710015:
Stock tables + v5.10 + XML
Stock tables + v5.10 + JDMMAP + XML + mod specific table changes
Stock tables + v5.10 + JDMMAP + Direct Boost + XML + mod specific table changes
I know there is another ROM that has done this. Here is my question:
As far asn I'm concerned there is no reason to have limited XML definitions for each of the packages. There is no harm with including all the tables for JDMMAP and Direct boost and even Tephra Mods, so long as the values themselves aren't changed in the package, and there is a note in the readme saying that changing those values can either prevent the car from running, damage it, or do nothing at all unless the appropriate modifications are included.
Agree? Disagree?
PS, in fact along with this I think it is worthwile to have a download section of complete XML's with all known definitions, and CORRECTIONS. It might even be time to rethink how we use the "User Level" such that beginner shows everything an unmodded ROM would need (to include stock MAP and solonoid). The next level would be all the stuff you need to see when dealing with modified parts (JDMMAP and Solonoid / changed pill). The level after that would be for an actual modified ROM (aka Tephra) and everything after that is all the stuff that I don't hear about people changing anyway (like the knock tables). That way we can stop looking at tables we don't need to see to save space.
I've already uploaded a stock ROM. My plan is to upload packages with:
94710015:
Stock tables + v5.10 + XML
Stock tables + v5.10 + JDMMAP + XML + mod specific table changes
Stock tables + v5.10 + JDMMAP + Direct Boost + XML + mod specific table changes
I know there is another ROM that has done this. Here is my question:
As far asn I'm concerned there is no reason to have limited XML definitions for each of the packages. There is no harm with including all the tables for JDMMAP and Direct boost and even Tephra Mods, so long as the values themselves aren't changed in the package, and there is a note in the readme saying that changing those values can either prevent the car from running, damage it, or do nothing at all unless the appropriate modifications are included.
Agree? Disagree?
PS, in fact along with this I think it is worthwile to have a download section of complete XML's with all known definitions, and CORRECTIONS. It might even be time to rethink how we use the "User Level" such that beginner shows everything an unmodded ROM would need (to include stock MAP and solonoid). The next level would be all the stuff you need to see when dealing with modified parts (JDMMAP and Solonoid / changed pill). The level after that would be for an actual modified ROM (aka Tephra) and everything after that is all the stuff that I don't hear about people changing anyway (like the knock tables). That way we can stop looking at tables we don't need to see to save space.
Last edited by Jumperalex; Aug 26, 2008 at 07:23 AM.
So I'm going to be installing Tephra's Rom soon and wanted to use this as a chance to provide for the Wiki ...
I've already uploaded a stock ROM. My plan is to upload packages with:
94710015:
Stock tables + v5.10 + XML
Stock tables + v5.10 + JDMMAP + XML + mod specific table changes
Stock tables + v5.10 + JDMMAP + Direct Boost + XML + mod specific table changes
I know there is another ROM that has done this. Here is my question:
As far asn I'm concerned there is no reason to have limited XML definitions for each of the packages. There is no harm with including all the tables for JDMMAP and Direct boost and even Tephra Mods, so long as the values themselves aren't changed in the package, and there is a note in the readme saying that changing those values can either prevent the car from running, damage it, or do nothing at all unless the appropriate modifications are included.
Agree? Disagree?
PS, in fact along with this I think it is worthwile to have a download section of complete XML's with all known definitions, and CORRECTIONS. It might even be time to rethink how we use the "User Level" such that beginner shows everything an unmodded ROM would need (to include stock MAP and solonoid). The next level would be all the stuff you need to see when dealing with modified parts (JDMMAP and Solonoid / changed pill). The level after that would be for an actual modified ROM (aka Tephra) and everything after that is all the stuff that I don't hear about people changing anyway (like the knock tables). That way we can stop looking at tables we don't need to see to save space.
I've already uploaded a stock ROM. My plan is to upload packages with:
94710015:
Stock tables + v5.10 + XML
Stock tables + v5.10 + JDMMAP + XML + mod specific table changes
Stock tables + v5.10 + JDMMAP + Direct Boost + XML + mod specific table changes
I know there is another ROM that has done this. Here is my question:
As far asn I'm concerned there is no reason to have limited XML definitions for each of the packages. There is no harm with including all the tables for JDMMAP and Direct boost and even Tephra Mods, so long as the values themselves aren't changed in the package, and there is a note in the readme saying that changing those values can either prevent the car from running, damage it, or do nothing at all unless the appropriate modifications are included.
Agree? Disagree?
PS, in fact along with this I think it is worthwile to have a download section of complete XML's with all known definitions, and CORRECTIONS. It might even be time to rethink how we use the "User Level" such that beginner shows everything an unmodded ROM would need (to include stock MAP and solonoid). The next level would be all the stuff you need to see when dealing with modified parts (JDMMAP and Solonoid / changed pill). The level after that would be for an actual modified ROM (aka Tephra) and everything after that is all the stuff that I don't hear about people changing anyway (like the knock tables). That way we can stop looking at tables we don't need to see to save space.
The other thing I was personally thinking was writing a .bat script to backup the appropriate files and place the new ones there. What do you guys think about THAT?!
While I agree from a l33t perspective, I think the point of the packages is to dumb things down. I think that may or may not be more confusing than anything.
The other thing I was personally thinking was writing a .bat script to backup the appropriate files and place the new ones there. What do you guys think about THAT?!
The other thing I was personally thinking was writing a .bat script to backup the appropriate files and place the new ones there. What do you guys think about THAT?!

fostyou- bat script seems pretty cool but a little over the top. If the user can't figure out where the files go then we are in trouble. Although I think it will make things easier for the average user and that is the goal of the wiki.
Last edited by dudical26; Aug 26, 2008 at 09:56 AM.
fostytou I have thought about a .bat too but worry that too many people might be installing things in different places. Also thought about a backup bat with the same problem though.
As for the ecuflash xml definition confusion ... you have a point, but that is why I think we need to play with the user levels. And possibly do a little clean-up on the name convention / grouping to make it easier to know exactly what a table / group of tables are for.
duducal26 I agree it would be good to have colby on board, but we can do whatever we want with an xml we want to post, even with different user levels. But again, having his support/help is always good.
Frankly, I'm hoping that what we do gets incorporated into either his next revision, or just into his current download. I just feel like the xmls have like frankenstein and are in need of a cleanup/reorg. Given all the work colby does, it seems like something we can help with at the minimum. Of course he is welcome to ignore it
As for the ecuflash xml definition confusion ... you have a point, but that is why I think we need to play with the user levels. And possibly do a little clean-up on the name convention / grouping to make it easier to know exactly what a table / group of tables are for.
duducal26 I agree it would be good to have colby on board, but we can do whatever we want with an xml we want to post, even with different user levels. But again, having his support/help is always good.
Frankly, I'm hoping that what we do gets incorporated into either his next revision, or just into his current download. I just feel like the xmls have like frankenstein and are in need of a cleanup/reorg. Given all the work colby does, it seems like something we can help with at the minimum. Of course he is welcome to ignore it
I didn't realise that we could alter the groupings with the XML thats a good point.
To some degree I think, or at least hope, that whatever we do with the wiki will become the standard. If we change the user groupings I think we can make that change widespread.
The most important thing is to make sure that all of the downloads we distribute are consistant accross the range.....in every way.
Even down to the structure of text files in the the download and what we include or don't include in the XML.
If we make standards now and keep everything consistant we can really allow room for growth without creating tons more work for everyone.
jumperalex- can you make an xml with your suggested changes so that we can finalize what we think all XML's should include. Again I think this XML should support all rom modifications possible.
To some degree I think, or at least hope, that whatever we do with the wiki will become the standard. If we change the user groupings I think we can make that change widespread.
The most important thing is to make sure that all of the downloads we distribute are consistant accross the range.....in every way.
Even down to the structure of text files in the the download and what we include or don't include in the XML.
If we make standards now and keep everything consistant we can really allow room for growth without creating tons more work for everyone.
jumperalex- can you make an xml with your suggested changes so that we can finalize what we think all XML's should include. Again I think this XML should support all rom modifications possible.



