Address change

From Jmri

This is usually one of the first tasks performed on a 'new' decoder equipped Loco. Hopefully, details of the decoder and the Loco have already been saved, as illustrated on the DecoderPro page. Clicking on the 'Basic' tab should open this window:

All that is needed is to decide if you want 2 or 4 digit addressing, and to enter the correct address in the correct box! - No need to worry about which CV's are involved!

  [[NOTE:]] Systems are not consistent in the handling of 2 digit addressing.
 For example Digitrax considers addresses up to 127 to be 2 digit, whereas Lenz
considers addresses up to 99 to be 2 digit.
Check your owners manual to see how this is handled on your system.
   Most systems will not recognize a leading 0(zero) as a digit.

Note that JMRI makes extensive use of colors to try and give you information:

1. White Is used when the program is sure that the data it is displaying is the same as that contained in the decoder.
2. Yellow is used when the program isn't sure - ie, if it has been read from a roster entry and not compared with the data actually in the decoder. This is the reason the input boxes will be yellow until you do a 'read full sheet' for example.
3. Red is used for data that the program 'knows' to be different from that stored in the Decoder. Hence, when you change data in JMRI you will see it turn red when you do a 'write', and then back to white after a successful write.

The other options on this screen should be fairly self explanatory and should be set in accordance with whatever you want! For example, if you want to reverse the direction your loco moves when you select 'forward' or 'reverse' on your throttle, simply change the 'NDOT' box and write the sheet.

That's it! - As long as the input boxes display the address (etc) that you're expecting, and are white in color, you're done and can continue with changes to the other sheets. Sheets available vary depending on the Decoder detected, so go ahead and select 'em and see what you can find!

As with all things computer based, it's a really good idea to 'save' the data just before the computer and/or software crashes :-) Assuming you can't do that, save it at whatever point you will be upset if you lose the changes you've made and/or you want to be able to back up to a previous known 'sane' state.