My club uses JMRI to program engines on a programming track. You cannot program on the main at our club. (We use Easy DCC) It appears, for example, that some members have programmed an engine at home using Digitrax. When they bring that engine to the club and we use JMRI to modify the decoder, sometimes, not always, the engine has other parameters that will change. BLI is one of the engine types that seems particularly susceptible to this but others will sometimes do it, too. Anyone else had a similar experience? In other words, perhaps would it be a good idea to put any engine to be operated on the layout through the programming track and check the important parameters?
Flash, One of the keys to programming with JMRI is to read all sheets / CVs before modifying. Then you can save just the changed values. The decoder files in JMRI start out with what the developer believes are the defaults as it comes from the manufacturer (and in most cases they are accurate). So if someone modifies various CVs (via Digitrax) and then goes to another system (say JMRI) they have to be careful as to how they write the changes to the decoder as it may write the default values in addition to the changes they are attempting to make. This is especially troublesome if they pick the wrong decoder file in JMRI.
