With the support (particularly in letting me have some documentation of file structures and operating concepts) of the TED folks, without which this would, of course, be next to impossible, I am working on a data editor for the Ted Pro. The project is progressing well, and I hope to have the initial version working by the end of next week (November 11), and the user documentation mostly written by the end of the following week. The initial version of the application will allow certain known forms of logical data corruption in the device's memory to be fixed, and missing or incorrect stored Power and Cost data (by hour, day, or billing period) to be added or corrected.
The application does not, for a whole host of reasons, operate directly on the data in the ECC's memory, but it will be capable of extracting the saved data from History (.tbk) files and/or of downloading it directly from a working ECC, across the network. After editing, via an interface that looks like the Footprints 'History' view. but with editable data fields, the modified data is written to disk as a .tbk file, and the ECC's memory is updated by using Footprints to 'restore' this. I will be releasing the application as 'donationware' and will be continuing to support it myself. The TED folks (not unreasonably) have asked me to make it clear that this is not and will not (for the foreseeable future) be an 'official' TED utility, so they cannot guarantee or support it. Users will necessarily be using it at their own risk, though the actual risk of anything bad happening that cannot be fixed by restoring an original History backup file would, in my judgement, be very small indeed, even if I were being much less careful with the coding than I am.
If anyone is interested in beta-testing the initial version of the application, I would ask him/her to contact me by email or Private Message here, and I will respond by email. I would particularly be interested in communicating with testers with a more maxed-out hardware installation, since my installation only has two MTUs and two Spyders - the application is written to deal with a full complement of both (respectively 4 and 32).
