Mitsulogger 1.6 beta 4 - SNEAK PEEK
Mitsulogger 1.6 beta 4 - SNEAK PEEK
While in the process of debugging a few issues with some of the new features I added, not all of them are actual bugs, just issues with some users, but thats neither here nor there, I still have to fix it so they don't have these problems. I caught some work that John was doing with a very early release of Mitsulogger that he's been using to test his live tuning protocol. In any case, I migrated some of his code, and enhanced it, over to this beta so it can evolve a bit more.
I was very careful early on to write code that could handle this inevitability.. THe major things I'm working on at the moment are keeping data integrity, and reading the ECUID properly, and matching it to Axis and data/Table locations so the maps can be imported into the Map tracing window, altered, and written back into ram for testing. Eventually you'll be able to move the tables back to a rom file and save it for further editing. (I want to discus a patch/merge file format with Colby, this way Maps, data and rom patches can be merged with roms more easily)
I was very careful early on to write code that could handle this inevitability.. THe major things I'm working on at the moment are keeping data integrity, and reading the ECUID properly, and matching it to Axis and data/Table locations so the maps can be imported into the Map tracing window, altered, and written back into ram for testing. Eventually you'll be able to move the tables back to a rom file and save it for further editing. (I want to discus a patch/merge file format with Colby, this way Maps, data and rom patches can be merged with roms more easily)
It'll probably be disabled if I get all the bugfixes done in Beta 4, and don't finish the map tracing features and its quite complex programming for all of the possible romID's
I'm actually planning on converting the requestID.XML file to some sort of database, which will allow adding/removing/editing and persistent enabling/disabling of requests.. This will also allow me to add the features for different roms.
I also am adding a "Diagnostic Tools" window so you can do one-time tests such as ACD service, ISCV Park (for setting BISS), and other MUT related diagnostics.
I'm still in the process of figuring all of this information out, especially the diagnostic flag data (that appears as weird data when logged)
If I can get far enough along in the Live tuning features, when I've gotten all the bug reports addressed and fixed, then it will make it into beta 4, otherwise it will be disabled until its complete.
The good news is that it works, and is real close to being fully functional at a low level (reading a map from rom to ram, copying the map from ram to the PC, modifying, and writing it back to Ram) But for now, I'm trying to give John Banks the tools he needs to finish his R&D for the live data protocol.
I'm actually planning on converting the requestID.XML file to some sort of database, which will allow adding/removing/editing and persistent enabling/disabling of requests.. This will also allow me to add the features for different roms.
I also am adding a "Diagnostic Tools" window so you can do one-time tests such as ACD service, ISCV Park (for setting BISS), and other MUT related diagnostics.
I'm still in the process of figuring all of this information out, especially the diagnostic flag data (that appears as weird data when logged)
If I can get far enough along in the Live tuning features, when I've gotten all the bug reports addressed and fixed, then it will make it into beta 4, otherwise it will be disabled until its complete.
The good news is that it works, and is real close to being fully functional at a low level (reading a map from rom to ram, copying the map from ram to the PC, modifying, and writing it back to Ram) But for now, I'm trying to give John Banks the tools he needs to finish his R&D for the live data protocol.
