What are the options for programming sound into LokSound decoders? Is this something that can be done in JMRI Decoder Pro or some other software for example, or do you have to purchase an ESU LokSound Programmer in order to perform this function? Sent from my SM-G973U1 using Tapatalk
As far as I know adding sound requires the 'programmer'. About anything else can be done with DecoderPro. You can even run the program that comes with the 'programmer' to set CV's if you want and then copy the results into DecoderPro. If you haven't bought the sound decoder some of the sellers will put the sound file you want on it before sending it to you for no additional charge. SSB who advertises on here does that and maybe others also. That is what I've done but also bought a 'programmer' but haven't used it yet. Sumner
The brand-specific programmers use proprietary protocols to load large sound files MUCH faster, and more reliably, than would be possible through the NMRA standard programming protocols. Most of the delay in programming decoders on a programming track comes from the original method NMRA uses to read back and/or acknowledge programmed info, involving drawing more/less current by pulsing the motor, which is very slow. Decoders and command stations that implement the NMRA RailCom standard can read back decoder data much faster (but still not as quickly as proprietary decoder readback methods that are not DCC compatible). RailCom, when supported and enabled, is operable on both the mainline and programming track. You can use JMRI with normal programming methods to select between multiple sounds for specific functions contained in a sound file already loaded via the proprietary loader.
Thanks for the input guys. I really appreciate it. And since I have already purchased the decoders, I guess that means I need to purchase an ESU LokSound Programmer to go along with them. I was hoping there was a less expensive way to do this, but since their isn't, I guess ESU is going to be getting a little bit more of my money. And much more of my money in the long run, now that they will have me locked into their ecosystem. Oh well, at least it's the best sound decoder ecosystem. Ha! Sent from my SM-G973U1 using Tapatalk
Possibly who you bought them from might still load the sound files but that would probably be freight both ways. Buying the programmer is probably a good idea in the long run though. Further down the road you might want to change the sound file with a newer/better option they might release. I bought one sound decoder without a sound file on purpose as I wasn't totally sure where I'd use it so will have to use the programmer at some point. Also it is probably faster than dealing with DecoderPro programming the non-sound options so will be nice to have. Sumner
If you don't own a LokProgrammer, and only occasionally need to upload sound into your decoders, try to find a local hobby shop with a LokProgrammer that can do it (either for free or a decent fee) or look for a local club or modeler who has one that you can use. I use JMRI Decoder Pro for programming my decoders. I don't have LokProgrammer. Some hobby shops will pre-load a sound file of your specification into a blank decoder free of charge when you purchase it. That's what I usually do.
Another alternative is to go over to the Loksound group on groups.io and see if you can scare up somebody local to you that has the hardware. I, for instance, would be happy to program some locos for you if you were in my area. George Edgewood, WA
I have the lokprogramer and I prefer programming my locos with it over decoder pro. Most of my locos are loksound though.
Do you not use Panel Pro when running your locomotives? That would make a difference to me. I have a Pi SPROG 3, so using JMRI for running as well as programming is pretty much the only option for me. Having the roster be the same for programming and running keeps thing simpler, and JMRI serves the connection to my phone throttle app. But if you use another DCC system, with its own wireless/WiFi throttles, etc., then I can see where it's not a big deal to run trains without JMRI.
Right! I don't use jmri to run trains, I use dccex with engine driver on my mobile as my throttle. I added all my locos directly on the dccex station with labels for all functions. It's an extra step, but I have less than a dozen locos any rarely buy anymore than that. So once done it's done.
Thanks for the replies everyone. I really appreciate all the information. I went ahead and purchased a LokSound Programmer since I plan to have quite a few sound locos in the long run, so I figured it would be the easiest way to go. Right now I am just in the process of rebuilding a layout I picked up used last summer, and as it came with a Digitrax DCC system, my plan is to run the layout with it in the beginning. Not sure if that will change in the long run. We'll just have to wait and see where my interests in the hobby take me. Sent from my SM-G973U1 using Tapatalk
I use the LokProgrammer to, initially, program my sound decoders. I then use decoder pro to make all of my sound adjustments, on the main and on the fly. I print out the sound file "bulletins" which show each function, the sound slots associated with the function and the default volume value. I also do all my speed matching within decoder pro, using the speed tables. I find that I have to adjust quite a few settings to get the sound just right. I then put the finished loco back on the lokProgrammer track and read the decoder back to the file to update my settings. In essence I have 2 roster lists; one in ESU and one in JMRI. Regards, Brian P.S. for anybody that has installed the ESU sound decoder in the KATO Charger; The default setting for the sound drove me NUT!! The Prime mover, literally, sounded like a large electrical hum that took about 10 seconds to work on your nerves. I will have to confirm but I think that I had to turn down slot 25 (like from 80 to 15) to fix the issue. I also used a 9x16 speaker with small baffle that would be better than the 8x15, IMHO. I can get the DigiKey item# if anybody is interested.
The only downside of ESU decoders with Decoder Pro is the necessity to use Read All Sheets on the Roster Entry tab to read the "setup" of the decoder into Decoder Pro before beginning to make changes to any of the settings. This is because the ESU decoder begins life as a blank slate and the locations (slots) of sound files and configuration is determined by the individual that loaded it rather than having a standard setup.
That's why I always start my programming using the lokprogrammer. I then export the lokprogrammer cv list. Then I go into decoder pro and create a new loco. I then import the ESU lokprogrammer cv list that I created. It will then populate everything into decoder pro. You MUST, then, save the entry and CLOSE out of the loco that you just created. (It's going to prompt you that you haven't written the configuration to the decoder - disregard this as the cv list that you just imported IS from the decoder. After closing the entry, then go back into the entry. You can then program on the main and individually change any slot entry. Then save any changes. You don't want to read all sheets as it will take forever outside of the lokprogrammer. I like making changes within DecoderPro as I can do it on the fly and live on the main. If needed, I can go and take a look at the specific steps to create the cv list, in ESU, and then import that file within decoderpro. Regards, Brian
Has anyone tried reading out the entire decoder using RailCom? I know it's supposed to be much faster than vai the programming track, and still likely much slower than using the LOK Programmer, but how much slower?
