Maybe I'm just missing something and should be doing it differently. I tried running the program in XP compatibility mode - same result. If I open the hex editor and manually change a value there and save the bin - the change is saved properly. Thinking that maybe the beta was causing my problem, I downloaded 4.14. The definition basically says, in plain English, 'the byte at location X in the bin file should be multiplied/divided/offset by W, Y, Z to come up with a real world number. TunerPros native definition format is 'XDF'. I have tried making changes to both scalars and Tables. The bin defition file (XDF) tells the editing software how to interpret each byte in the bin file. I can make a change, save it, then restart Tunerpro, and the difference tool still shows no differences. But, if I do a compare with the base bin, no changes are registered. So - at this point I'm thinking that my change has been saved. The filename at the top of the screen then shows a star beside it. Load Last BIN at startup - If checked, the last opened bin will open next. Load Last XDF at Startup - If checked, the XDF file that you specify as default will open automatically when you load TunerPro. Below is a short description of each option. I then click save and the editing window closes for that scalar. Preferences editor can be found in the tools menu, or by right-clicking in the workspace window. A star appears in the editing window for that particular scalar. I change a scalar value by some amount. I have made an XDF which is fairly compreshensive, but am having some difficulties with actually editing the bin file. I'm going to be using this purely for static bin editing - no RT required. In any case, I am game with using Tunerpro, as it looks to be pretty powerful.
The behind the scenes changes made by these bin editors (namely crome) create unwanted/unknown changes. TunerPro software allow you to interpret and modify the files of the control unit easily and with accuracy. I'm tired of using someone elses Honda bin editor which dumbs down the calibration process to the point where it is difficult to tell what items are actually being changed in the bin. I am working on an XDF file for a Honda OBDI P72 bin. I'm pretty familiar with hex and bins, etc.