I really don't mean to sound like I'm griping or complaining, just wanted to make some observations so as to maybe move some ideas around in the community to help bring about quicker releases and capabilities.
I did notice that yours was the only project that was really 'open' from what I found. I think the site here right now it's more of a dump of "this is what I learned today" type posts rather than actual organized progress toward a centralized store of information and applications... finding posts on here is a pain through searching. I notice that the ecuFlash is really focused on mitsu which is fine, but there could be a concerted effort to have it ship with support for all vehicles stated on this site. Enginuity is getting there, but there are some GUI concerns with that application. I pretty much had to write my own application last night to get a GUI/capability I've been waiting on for a while now from any of the editors. It just seems like there's not much open-ness in the openecu group... release of the colb's logging code was good, but lack of good comments and structure make it pretty long read. To add to the disorganization, there's no consistant standard documentation, mapping (xml) formats, and programming language.
I do this stuff for a living during the day, run a auto parts business part time, and to me the projects here are lacking some structure in regards to timelines, milestones, and feature releases. Obviously you guys are probably doing this in your spare time, but some organization still wont hurt and may help others provide input into your project knowing a given timeline for release.
Again, more 2 cents.
-Rob
p.s. DTCedit is here
http://marylandturbo.com/misc/DTCEditInstall.msi and only works on LegacyGT DBW files for now (I own a LGT
)
qoncept wrote:Standardized definition files and/or consolidating the programs isn't going to happen. I posted a thread before adding user-definable maps in Enginuity, Colby posted what he had come up with. I used it, addressed some of it's issues, and released Enginuity that way. A few months later, Colby released ECUFlash with the same problems fixed in a different way, and now they aren't compatible. ECU Edit's XML structure isn't even close to the same as ours.
The problem is the whole community honestly isn't very open, despite the name. No one is making an effort to make the tools "play nice," and to date only Enginuity's source has actually been released. There is nothing I can do to help on the others, and many users prefer Enginuity and want more features, so I keep working on it. There are actually a few more developers working on Enginuity now as well, which is already helping with the quality and quantity of new features. I really wish there was more teamwork going on in the scene, but what can you do?
Posted: Tue Jul 25, 2006 10:07 pm
I dunno, so much todo so little time.