Tea cups wrote:The reason to use Enginuity, besides the fact that I'm a little biased, is the ability to use standard ("American") or metric definitions (each are available for download), have everything categorized nicely, plus a few extras like check box cel disabling and checksum fixes and I've found a few tables that aren't supported in xmlwrite. Also, there are newer revisions that are supported by Enginuity but not xmlwrite. Xmlwrite is good, though, and always something to consider, especially if you are looking for an obscure table. You can always modify the xml to support different categories and units in ecuedit, but a lot of people want something that works right out of the box.
Using Enginuity or not - it's your right. Metric system in xmlwrite? so, it's not a big deal. Logger in ecuEdit simple converting values from one metric to another. It's too simple include this support for maps.
And, ecuEdit also support checksums (much early than Enginuity).
Tea cups wrote:Plus, if a revision is not supported by Enginuity you can post up your rom to the Enginuity site and if I can, I'll add support for it in the next revision.
What prevent to you (someone else) do it on ecuedit site?
Tea cups wrote:Don't get me wrong, Ecuedit has more features than Enginuity right now, but you will see additional features added in later Enginuity releases, such as logging, definition editing from the interface, reading/flashing and a few features such as multiple units where you could choose what type of units you want - such as engine load in grams, grams/rev, or grams/sec.
I'm many times from many peoples, including that community, heard about their plans to adding some features, etc. But that not comes true, yet. May be I'm wrong. So, goodluck