JRSCCivic98 wrote:Why don't they already just have all the tables available from xmlwrite? Just wondering?
I've been creating the defs for Enginuity as of late (screen name Merchgod on the Enginuity site). I don't add any tables to the definitions (regardless of the source) unless their exact function is known and the resulting values make sense and are known to be correct or have been tested as in the case of Spec C Wannabe. I also try to come up with a conversion formula that makes the most sense from a tuning perspective (that is, easiest to visualize) and as much as I can one that has the greatest accuracy based on how the ecu uses the underlying value. I'm not saying that my definitions are 100% tested, verified and bug-free, but I try to represent at the very least "a best guess" due to the large number of revisions in every market that are supported.
Xmlwrite is a very good resouce. I've yet to find an error in regards to table size and the offsets are nearly always spot on as far as I can tell. The majority of the differences would be in the conversion formula as I don't always agree with them or I think they should be represented in a different way (ex. percent change verses multiplier). I've found a few storage size errors (such as 32bit injector latency), but this is probably something corrected in a later version of the "reference" xmlwrite was created from. I also have support for tables and revisions that are not included in xmlwrite. In addition, I try to present it in a way that will give as much information as possible to a user through the use of detailed help descriptions and different ways of presenting the values, such as label descriptors indicating the function of each individual value in a 1d table.