Using JMRI 4.8 to program function keys and lighting on a LokSound Select

jdcolombo Jul 31, 2017

  1. jdcolombo

    jdcolombo TrainBoard Member

    1,183
    269
    31
    Hi everyone.

    Although I use a LokProgrammer to program my LokSound Select decoders, I realize that not too many people want to spend another $160 on hardware and learn new software in order to do some common programming tasks on their LokSound decoders.

    Since many of us in the DCC world have adopted JMRI's Decoder Pro as a tool for programming decoders, I thought it would be helpful to write a document that describes how to use Decoder Pro to change function key programming and add lighting effects on their LokSound Select decoders. While Decoder Pro is a fabulous tool, it has a few quirks when it comes to programming LokSound decoders. One of those quirks is that JMRI doesn't actually have updated default CV's for the Select Sound files (it doesn't even have a complete current list of those files). As a result, you MUST do a "read all sheets" or read all the CVs from the CV sheet before you begin any programming to make sure that JMRI loads the correct CV values for your decoder.

    The attached document covers this and other quirks, and introduces the "theory" behind programming LokSound's function keys - that theory differs considerably from any other decoder made today. The document then uses some common examples to walk you through the process of combining the theory with JMRI's programming tools to do some common things - like making the headlight stay on in both directions; changing what a function key does; adding lighting effects and assigning those to a function key; programming alternating ditch lights, and so forth.

    While I have tried out these examples myself, and tried to double- triple-check the text, there is always the possibility that I missed something as I was writing all this down, or that I still have a typo in the document. Suggested changes are welcome; PM me here at Trainboard if you find that something doesn't work or find a typo that needs correction.

    Also, please let me know if you find this document useful; if enough people think it is worthwhile, I'll try to find a way to distribute it more widely.

    John C.

    [edit - removed older file version]
     
    Last edited by a moderator: Aug 1, 2017
    Sumner and papahnash like this.
  2. papahnash

    papahnash TrainBoard Member

    337
    69
    17
    Hi John,
    I only read the first few pages but that was all it took to impress me.
    Thank you for a great article.
     
  3. jdcolombo

    jdcolombo TrainBoard Member

    1,183
    269
    31
    UPDATE:
    After some discussions with Dave Heap, who programmed much of the code for Decoder Pro's support of the LokSound, I've revised the discussion of the automatic ID process - this does in fact work well; the problem is that if you ask JMRI to identify a LokSound Select Micro or a Select Direct, it is likely to highlight both and tell you to pick which one you have before proceeding. The reason for this is that the Select Direct is in fact just a Micro plugged into a larger board; they are in fact the same decoder, just a different physical format. Dave also pointed out that there is an easier way to "swap" function key assignments for Drive Hold and Dynamic Brake, which is what I describe in one of the examples, so I also updated that discussion. Finally, I made clear at the end of the flashing ditch lights example that each increment of the "grade crossing hold time" slider represents .065 seconds. The new file is attached; I'm not entirely sure how to remove the old file; if one of the Forum Moderators could do that, it would be much appreciated.

    John C
     

    Attached Files:

    Sumner and hoyden like this.
  4. RBrodzinsky

    RBrodzinsky November 18, 2022 Staff Member TrainBoard Supporter In Memoriam

    5,685
    2,780
    98
    John, one way to maintain a file like this, with version control, is to use the Resources section.
     
  5. jdcolombo

    jdcolombo TrainBoard Member

    1,183
    269
    31
    Ah. Good to know. Is there a manual for using Trainboard? :) I'm not going to write that one . . .

    John
     
  6. RBrodzinsky

    RBrodzinsky November 18, 2022 Staff Member TrainBoard Supporter In Memoriam

    5,685
    2,780
    98
    Would sure make being staff easier!
     
  7. JohnForsythe

    JohnForsythe TrainBoard Member

    25
    3
    4
    I wanted to touch on this thread a bit. I know it is old but it is still relevant.

    I've been out of the hobby for about 2 decades. Back in the day, I built Rail Power Products locos and bashed blue box Athearns. New locos are really nice, but I saw no reason to get rid of my existing power if I could get decoders to fit and function. I explored JRMI and bought a basic Digitrax decoder to fiddle around with. I liked the results and wanted to get a more fully featured decoder. After listening to files, watching reviews, etc, I decided that LOKSound was the decoder for me. Little did I know... :)

    I ordered up a blank decoder, had it programmed for a my loco and anxiously waited its arrival. A quick wiring up to test and I was blown away by basic sound functions. However, I couldn't really get it to do anything else. I began to think perhaps I was in over my head, having never really programmed ANY DCC decoder. Searching the webs brought me to this post. After reading your excellent PDF and reading the LOKSound manual, and reading the spec sheet for the sound file, I was able to start in with a rudimentary knowledge. After some trial and error, the lights began to go on and I'm confidently modifying and combining functions. The loco is fully wired up for lights and sound and buttoned up and I'm ready to retrofit my next diesel. All thanks to folks like you and the very generous folks who program JRMI for free.

    Keep up the good work,

    John
     
  8. ARV57

    ARV57 New Member

    1
    0
    1
    John,

    I realize this is an old thread but WOW did it help me.

    During the past couple of years I have been getting back into model railroading after a five-decade absence. How things have changed!

    I recently joined TrainBoard because I found a link to your thread through a Google search. It was the only thread I could find that helped me to program my ESU decoders in a straightforward manner.

    I can’t thank you enough for providing this tutorial. It was exactly what I needed to program a couple of my locomotives that have ESU LokSound decoders.

    I wanted to change the ditch lights to alternating flashing at a grade crossing and Example 12 was the answer. It took me a couple of tries but I got the lights working the way I want. It may not be prototypical for my locomotives but people love to see flashing lights along with bells and whistles!

    I have other locos with Soundtraxx decoders and I haven’t had too much difficulty programming them using either the NCE Power Cab or JMRI Decoder Pro. The ESU decoders really had me stumped. Not sure why they make it so difficult.

    Thanks again for providing the tutorial. It is just what I needed.

    Best,

    Alan
     
  9. jdcolombo

    jdcolombo TrainBoard Member

    1,183
    269
    31
    I'm glad you found it useful. Programming the ESU decoders is complicated and I hoped that my tutorial would make it a bit less so.

    John C.
     

Share This Page