You need one of:
Either can read in the current settings in your LokSound decoder and then you can select what you want to happen in function mapping. The Lokprogrammer is much quicker as it can read the decoder using an ESU-proprietary mechanism, the JMRI option is usually much cheaper and will read in the values more slowly (potentially taking the computer an hour to do it, but you can do something else whilst it is reading in the initial values).
JMRI can be much quicker if the decoder has a standard ESU sound project loaded on it (rather than an after market one), as the data for the sound project can be imported from that available on the ESU website. The same is true if someone can provide you with the settings in the decoder you have fitted to the loco.
It is possible manually. You've a lot of reading to do of the ESU manuals, and a lot of notes to keep as you manually read the potentially thousands of CV values associated with ESU function mapping (in practise, with a good plan, you can keep this number well below a hundred, but its still a load of work).
- An ESU LokProgrammer.
- A computer running JMRI connected to your DCC system's programming track
Either can read in the current settings in your LokSound decoder and then you can select what you want to happen in function mapping. The Lokprogrammer is much quicker as it can read the decoder using an ESU-proprietary mechanism, the JMRI option is usually much cheaper and will read in the values more slowly (potentially taking the computer an hour to do it, but you can do something else whilst it is reading in the initial values).
JMRI can be much quicker if the decoder has a standard ESU sound project loaded on it (rather than an after market one), as the data for the sound project can be imported from that available on the ESU website. The same is true if someone can provide you with the settings in the decoder you have fitted to the loco.
It is possible manually. You've a lot of reading to do of the ESU manuals, and a lot of notes to keep as you manually read the potentially thousands of CV values associated with ESU function mapping (in practise, with a good plan, you can keep this number well below a hundred, but its still a load of work).
