Besides the obvious ability to download the sound files to the decoders, is there any functional reason to have a LokProgrammer for programming ESU LokSound Select decoders, over using the latest version of JMRI? The JMRI does a great job of keeping the decoder profiles up-to-date (at least for the more ubiquitous decoders), but not knowing the ins/outs of ESU in particular, want to know if investing in a LokProgrammer is a worthwhile expenditure.
Hi Rick. I find it easier to do certain things with the LokProgrammer, the main one being function key re-assignments. With the LokProgrammer, you have a drop-down box for function keys that let's you reassign them as you please. With JMRI, you have this complicated spreadsheet-like thing that I can never figure out. It is also easier, I think, to change some common behaviors of the ESU LokSound, like changing the "delay start until prime mover throttles up." But I actually use both. I use the LokProgrammer for changing sound files, doing function key reassignments, and some other things, but I use JMRI to do speed tables. I also use JMRI to keep a copy of the entire decoder setup - that is, after I have an engine set up the way I want, I use JMRI to read all the CV's, and then save that to the engine file. Then if I ever need to reprogram an engine from scratch, it's just a matter of setting it on the programming track and writing all the CV's. Plus I like to have every engine in my JMRI database (ESU-equipped or not) for purposes of using Wi-Throttle on my iPhones. So . . . I have both; use both; find both indispensable for certain programming. BTW, I think you can download the LokProgrammer software for free, and play around with it some to decide if you find it useful before investing in a LokProgrammer. John C.
Thanks John -- I took your advice, looked at the download, and then ordered one. Came yesterday and is all installed. So... next question: on the ESU site, there are download files marked by scale for the Select decoders, but it goes on to say you can load the different scale files into any of the decoders. If the driver one is looking for is only available in HO, and you want it in N, can one just go ahead and load the HO sound file?
