Loksound 5 Run 8 mode

[Jim Starbuck]

I’m not sure if this is what’s happening but thought I’d ask here. It may have been discussed but the search criteria won’t let me use the number 8.
Is this run 8 mode that’s causing this behavior?
The last three Loksound 5 installs I’ve done (2 58923 Nanos and a 58721 5 Micro DCC Direct) have done this in regards to the sound files. I don’t remember the first one but the last two were S0768 for an SD7 and S0827 for a GP38.

The sound file when started with F1 (default) goes through the startup then sits at idle normally but when I crack the throttle to step one the engine creeps as it should but the sound file notches up to 8 and stays there regardless of throttle position up or down. Even when brought to zero the engine comes to a stop but the sound remains at notch 8 and will only stop when F1 is turned off. If restarted the sound file goes through the startup and idle again normally but goes to 8 at the first hint of throttle.
I have disabled everything below F10 and all the random sounds are disabled as well.
I’ve been able to load a different sound file and the behavior goes away but I’d be interested to know what I’m doing in programming to tell the decoder to do this.
One commonality I’ve observed is the sound files that come up default with the prime mover mapped to F1 act like this and those default mapped to F8 do not.

Thanks,
Jim

[tehachapifan]

Hi, Jim-

I'm yet to see an ESU sound file where F1 is the default startup command, so that has me scratching my head. Isn't F1 always the default bell command?

Otherwise, with the going to notch 8 thing, is it possible that F26 (notch up/run 8 ) is somehow already active when you power up your DCC system?

On my system (MRC Prodigy Express), if I disconnect the throttle with certain commands active or there's a power interruption, those commands will be active every single time I power up my system, until I unplug the throttle again with those commands off.

That said, I've only experienced an unwanted active command upon system startup with a single unit, not several units (although I suppose several units could be affected if that command is assigned to a consist).

...actually, I know this can happen with all units assigned to a consist, as it isn't too uncommon for a consist of mine to not move when I throttle up right after powering up the system, until I activate and then deactivate F9 (drive hold).

[Jim Starbuck]

Thanks Russ,

I never got to where I was using the command station and a throttle.  I was doing all of this through LokProgrammer.
I think something got corrupted in the download or maybe uploading it to the decoder.
This is weird, I went back and downloaded the same sound file again and without making any changes looked at the default function mapping. Everything is normal and assigned to the expected functions.
I have no idea why but at least I know if one like that shows up again all I have to do is reset it and reload.

Hmmm…nothing to see here people… move along.

Jim

[tehachapifan]

Glad that it worked out!

[reinhardtjh]

F1 is the European standard for starting/turn on a sound file (see sound files here: http://projects.esu.eu/projectoverviews/7.  If it was a North American loco sound file then ESU might have goofed when creating it or possibly it downloaded the wrong file.

[Jim Starbuck]

F1 is the European standard for starting/turn on a sound file (see sound files here: http://projects.esu.eu/projectoverviews/7.  If it was a North American loco sound file then ESU might have goofed when creating it or possibly it downloaded the wrong file.

Good call.
That’s a possibility John.