I thought I saw something about saving coding, but I'm not sure how to do that.
Mbmb: whitemk7 is correct- it's good practice to keep accurate records of ALL your changes just in case the brown stuff and the fan meet and you need to revert your settings to their original values.
There's lots of ways of keeping records: you can make notations yourself, or you can use Ross-Tech's facilities. For example if you are changing adaptation channels, there's a button on the lower RHS of the screen called "Add to log". If you click on this button after you click "Do it!" Tab (and you follow the screen prompts), a .csv file is added to your "logs" sub directory detailing the before and after values you just made.
The other way to use Ross-Tech's facilities is via the "CodingLog. txt " file that resides in the "debug" sub directory. This file lists ALL the changes that you have made with your cable since you first used your laptop. Being a .csv file, it's just straight text with commas separating the data, so it can be a little difficult to read if you have made lots of changes. But you can parse the file though something like MS Excel to make it more readable.
Just a small note of caution about the CodingLog. txt file - the data in this file is recorded just after you press the "Do it!" Tab. This means that the file is blind to what happens after "Do it," is pressed. So if your change request is rejected by the control module, the record in the the CodingLog file won't be accurate (i.e. The record in the file will say that the change was made- when it wasn't). But this idiosyncrasy notwithstanding, it's still a good facility (IMO)
