So I had the idea of rolling a website with the sole purpose of aggregating information for the different ME7.x ECUs.  There are original BINs, tuned BINs, DAMOS files, random spreadsheets with code word locations (and more) scattered all over these forums, and over the internet for that matter.  Wouldn't it be nice if you could simply look up an ECU either by number (06A906032NK, for example) or filter by year/make/model and get a page with an apt description of the ECU, quick facts, code locations and files?  Enter OpenMotronic.

OpenMotronic is my idea of a minimalist approach to combining all the knowledge out there on *specific* ME7.x ECUs.  This website is not for stuff like how to tune your S4 ECU, etc.

Right now, it's mostly a skeleton - I'm trying to nail the design down before I even try to make it into a working site.  I'm looking for your thoughts on how I've laid out the ECU info, and what info I've decided to included.

Keep in mind: this is not supposed to be the end-all-be-all for ME7.x information - it is supposed to be a relatively comprehensive, although not 100%, source of information.

With that in mind, I give you OpenMotronic (beta ): http://www.openmotronic.com/ecuinfo.html


Also, here's a look at how straight-forward I plan to have the search page be:  http://www.openmotronic.com/search.html



Thoughts?

EDIT:  I should also mention that this is only the first planned version.  In the future, there is nothing to stop me from being to add more sections for other info.  The main priority/first goal is to aggregate all basic ECU information/files together, though.

Here's my initial thoughts on the UI portion or code locations: the "code locations" section is for ECUs without DAMOS files or any other resources to accurately pull out all the code locations. 

For instance, the example ECU (06A906032NK, my car's ECU, heh) doesn't seem to have a DAMOS file out there for it... atleast publically available.  Thus, it might only show a small table of verified code locations based on testing or whatever.

Now, given one of the numerous S4 ECUs like an Mbox or C box, etc etc - you could omit the code locations section and simply provide the XDf or DAMOS, etc.

Of course, this doesn't mean I couldn't ever design a code location UI specifically for searching from the thousands of codes.  This was just my initial thought process to how I went about that particular section.  (My example page violates the either code locations OR
DAMOS files thing... but it's only for display purposes anyways)

As time permits I will start populating topics to the wiki... anybody else with me?

I think what would be great, is if people could just outline the information they want to see on the wiki. The people on this site have tons of info in there heads, so if there was specific info missing on the wiki, I think it would be easier for the experts to contribute.