Ok, so I had this great Idea for after a few hours of searching I have several items or tables in my rom that i am curious as to what they control, with no deffinition or reference as to what they do.

Like the "Wastegate Solenoid Activation RPM" table for instance.... What and how do we set that fine little nugget of code?

Or the "Limp Home Table"... I get the idea but what actually is it doing?

So why the Data Base, you might ask, well I have been to the wiki and seen that there are maps there, etc. What if we take it a step further, and make a 3d table or array that a user could essently pick the rom id, pick from a list of deffinitions in that rom, and blammo, you have the rom snippet of code, and the deffinition of what it controls, and a little lamen english on what it does...

I thought about attempting this Jewel myself, but realize I only have about 3 different actual roms, and I don't know how many .xml files. I don't think that my .xmls with strings of modified code are all complete. I would put it all together, if I had all the code or possible tables that have been discovered so far.

I thought this would give anyone a way to add snippets of code if they need it, and build themselves the custom xml. of their choice. It makes the beginner or do it your selfer a little safer. Code is not in the .xml if the user shouldn't or doesnt need to adjust it. After they get going, and read through, they can add those snippets of code they need.

Example. First thing in my rom I modified was MFRED's boost control for the ECU. I had to read through that dig, figure out how to add the code, and then adjust. Yes the code is in their nice and neat, and looks great. When I wish to go back and refference it though, what happins if I forget wich thread I need to find code from, where do i get it? I have to search, check for a name, remember the actual title of the thread, and then remember which page it is on...you get my point. What about those of us who lose the files all together, or have a corupt file and/or virus. I have seen a few of you digging around for all the code again...

For those of us who could have a little spot to go find that snippet of code, would seek it as the fountain of youth.

Yes I do see draw backs to this, and do see the critisizm that may come from suggesting such a Data Base, but look at the possibilities. There are roughly a handful of guys on here so far that I see day in and day out, write out lengthy threads about the new table and code they have found. This gives a way to orginize and librarize(yah I know...lol) the code. We can add years and models to this Data Base as well, It should not take that much actual sotrage space. The hex files and .xml's are very small. And your talking currently, approx 10 different EVo8/9 roms, you will probably have just as many EVo X Roms... Either way, were talking MB's of space, not gigs.

I am sure it exists on the Dark Side of the galaxy(some where burried deep inside Death Star , but as for the Rebellion, we must build it!

Just my suggestion and would be helpful donation to the forum.

 

I can't beleive I missed this thread. Maybe we can add some of my thoughts into that wiki. It looks like several of you share the same thought and idea I have in some regards. I guess I will start adding over there....

Thought still stands though on getting some deffinitions included with those roms that explain some of those weird tables and what they do...

Thanks for all your time. Please post any suggestions in the above listed forum that everyone else seem to find but me...lol.

 

I think it would be a great upgrade to ECUFlash if we had a little notes section/window for each table where we can put comments in...that would save to the XML.

Maybe whomever is in communication with Colby can run it by him and ask if it's possible.