Help (!) with ESU LokSound V5 (Diesel) decoder function mapping

Bookbear1 Oct 24, 2023

  1. Bookbear1

    Bookbear1 TrainBoard Supporter

    638
    891
    35
    I am attempting to shift some of the default function keys to match the pattern on many of my other locos. (I had no problems doing this with Paragon 3 or 4, or Soundtraxx decoders.) This is my only ESU decoder. I have carefully read the ESU manual and am now more confused than when I started. The manual clearly states that any function can be assigned to any function key. This does not seem straightforward at all. As per the manual, here is what I have now:
    F0, F1, F2 and F8 remain as is. I have set CV31 = 16 and CV32 = 1 to allow access to the CVs above 256.Now, here is what I want to have for the function keys:

    F3 will become the brake set/release sound (was triggered by F17)
    F4 will become the fan sound (was triggered by F11)
    F5 will become the air let off sound (was triggered by F21)
    F6 will become the cab door sound (was triggered by F22)

    Additionally, is there a way to make F9 mute all sounds?

    I am completely lost as to how I move/assign the function keys. I really need step by step directions. As I said, the manual is only confusing me more. I am using a Digitrax Zephyr system, and have a separate programming track set up. I do NOT have access to one of ESU's LokProgrammer devices. Contact me via PM if you prefer, and THANKS for any help!
     
    Last edited: Oct 24, 2023
  2. GGNInNScale

    GGNInNScale TrainBoard Member

    243
    695
    10
    You could download JMRI and use DecoderPro. This might help. I broke down and bought a LokProgrammer...
     
  3. BigJake

    BigJake TrainBoard Member

    3,311
    6,385
    70
    The LokProgrammer is necessary for any work with different sound files, etc. JMRI DP will handle the rest, and can do it rather quickly, even on the mainline if your DCC/programming system supports RailCom.
     
  4. olequa

    olequa TrainBoard Member

    15
    7
    18
    You have to be careful when moving functions around like this. The reason is that certain functions have been assigned by the original project to randomly activate. So for example function 20 might activate the air compressor sound. That function will then be configured in the original project to be randomly activated thus simulating the prototype compressor activity. So if you move some other activity to function 20, say the cab door sound, then you will hear the cab door randomly slam and you will wonder why.
    There is a section in Lokprogrammer software for configuring the random activity. No doubt it exists in DecoderPro as well.

    George
    Edgewood, WA
     
    BigJake likes this.

Share This Page