WOWSound Mute On Startup Feature

Mute On Startup is a feature available in WOWSound decoders starting in Version 4. this feature has evolved over time, and the behavior may be slightly different between sound decoder types and Versions. This page provides information on the feature itself, and will direct you to the resources you need for your specific Decoder Type and Version.

How Mute On Startup Works

Fundamentally, Mute on Startup works by delaying the WOWSound decoder's audio startup sequence. This delay will begin when the decoder receives power, and will end when the decoder receives a DCC packet addressed to itself. This can be a change in speed, turning the headlight on, blowing the horn/whistle, etc. ANY packet that addresses the decoder will "wake it up."

Version 4.5 WOWDiesel decoders will start up with the prime mover off, but will still respond to inputs for sounds and lights. In order to start the prime mover, the operator must use the Prime Mover Ignition function (default F12) to start the engine sound. This change prevents some of the undesirable behaviors reported by uses as a result of the issues described below in the troubleshooting section.

Troubleshooting Mute On Startup

"I enabled Mute on Startup but my decoder is not muted!"

Mute on Startup is dependent upon whether or not the decoder receives a packet addressed to it, particularly those which reflect a change in state from what is stored in memory.

With some command stations, One or more "refresh packets" will be sent out to the currently addressed engine(s) on the throttle(s). As a result, you may have a situation where one or more of your locomotives continues to power up when the system starts if it is actively being addressed. You can prevent this from happening by releasing that decoder from your throttle, or selecting a bogus address prior to powering down your system.

If you do NOT have the decoder in question selected and either reboot your system OR remove it from the track (let it power down all the way) and place it back on the track, it should remain quiet. The exception to this is if your system uses "refresh packets" to periodically communicate to the decoder the status. Note also that if the function for the startup sequence (idling sounds, prime mover ignition, etc.) is ON, the decoder may receive this command when the system powers up, and will start. If the function state is different from what was in memory when the decoder powered down, this can also force the decoder to power up since it saw a change in the function status. Many command stations flush the function status when they power down, meaning all functions are OFF on power-up. This will often cause the decoder to react since one or more functions may have been ON (the headlight for example).

Mute on Startup also does not go into effect until the decoder powers down after enabling the setting. You must program the CV's to enable MoS, then power the decoder down completely (include Keep Alive® if connected). On the next power up, the decoder should be muted.

Programming (Enable/Disable) Mute On Startup

Version 4 decoders use TCS' Indexed CV's to enable or disable the feature. The indexed CV used is "User Options" whose options and defaults vary between each decoder type. For more information on Version 4 Indexed CV's click HERE.

The User Options indexed CV is 4:19 and the Mute on Startup option is controlled by Bit 2 of CV204.

Program a value of 4 into CV 201, then Program a value of 19 into CV 202. Use the values listed below for CV 203 and CV 204.

!!!WARNING!!! IF you have already made previous modifications to the User Options, it is recommended that you first READ the User Options index - Refer to instructions in our Version 4 Indexed CV documentation. Use the links below to the Guided Programmers if you would like to configure the other users options. These tools will generate the values to program based on your choices.