Friend of mine has a Tsunami decoder for a galloping goose. It has a nice startup sequence which initiates when the goose is put on the rails. However, the instructions which come with the decoder don’t tell you how to shut down the engine so that you can do a manual restart. I’m not talking about the mute function key.
Looking at the on-line Tsunami manual, I found that they tell you to use the DCC handset’s emergency stop button to initiate the engine shutdown (press the emergency stop button once). This seems problematical (read “stupid”) to me, especially since we have an NCE system where if the stuttering finger hits emergency stop 3 times the railroad grinds to a halt.
So, my question is: Is there a way to reprogram the decoder so that the shutdown feature gets moved from emergency stop to one of the unused function keys?
I would say no because you would effectively be mapping ES to another button…not changing its digital signature, which is what the decoder uses for the effect you want. It’s the decoder, not the button that elicits the response you want. The decoder is programmed to behave to a coded message. It doesn’t care from which button you send it.
So, if you remap, you replace. The button normally used for ES would not be ES any longer.
I’ve got a Tsunami in a GP-9. One day, I accidentally got the engine to “shut down,” but I’d done it by fat-fingering and couldn’t figure out what I had done. The manual, as you’ve pointed out, is particularly unhelpful.
I’ve got a Lenz System 100 “Dispatcher” throttle. When the manual says the “Emergency Stop” button, it does NOT mean the system stop button, but rather the engine stop button. On the Lenz system, I’ve got a button which will either set the engine speed to zero if it’s running, or reverse direction if the speed is already at zero.
So, to bring the engine to a stop and then go through shut-down, I bring the speed down to zero and wait for the engine to come to a stop. Then, I’ve found it works best if I increment the speed by 1, and then press that Engine Stop button twice.
The Tsunami shutdown, by the way, does not work the same as a QSI decoder shutdown. On my QSI engines, once I go through shutdown the engine stays shut down until I press the key for startup. On the Tsunami, the engine will come back to life after a system power down, either for a short or when I shut things down for the night.
Mr. B: To the best of my knowledge the NCE system does not have an engine stop button. There is only an emergency stop button that gets pushed 3 times to bring everything to a halt. To quote from the Tsunami Diesel Users Guide:
"Start the Prime Mover
To start the diesel engine, simply increase the throttle to speed step 1. The engine will crank over several times and settle into a nice idle. On a few command stations, such as the NCE Power Cab, the Tsunami decoder may skip the startup sequence and immediately play the idle sound. If this happens, press emergency stop first, then increase the throttle and youshould hear the engine start."
Although this references the Power Cab, the Pro Cab handset is identical. I would think that there should be some way to task one of the function keys to have the engine motor shut down. Especially so since the Goose decoder has several unutilized function keys. Otherwise I consider this a design flaw of the “what was that person thinking when he came up with that idea” variety. With the QSI decoder, you can have the shutdown sequence initiated by double pressing one of the function keys. Even my almost universally disliked and hated MRC decoder doesn’t use the emergency stop nonsense.
I just picked up my first Tsunami with Baldwin sound and I am wondering the same thing. Still looking through the manual. All I can do right now is the quiet function.
I have two LokSound decoders with Baldwin sound and those are configured to hit funtion 8 for engine start up or shut down.
Hopefully, the Tsunami can do the same. I am going to look around the Yahoo SoundTraxx Group and see what I can find.
My Atlas and proto locos with sound, double clicking 9 puts the loco in idle mode, Double click 9 again puts it in disconnect mode, and finally double clicking 9 again shuts it down. To initiate the start up sequence double click 6. Pressing 8 once is to mute the sound. I only have one Tsunami loco and it is a steamer and I haven’t tried a shut down sequence with it.
Steam engines cannot be shut down like a diesel – the only shut down for a steam engine was to let the fire go out. Not the same thing as shutting down a motor at all.
The following information is quoted from the Tsunami Diesel User’s Guide:
Diesel Engine Control
Tsunami provides two CVs for setting up the diesel engine sound effect:
CV116 Engine Control
CV 131 Exhaust Volume
Setting CV 116 between 1 and 15 enablesAutomatic Engine Notching Mode. Automatic notching causes the engine RPMs to change in proportion to the throttle setting. Pressing Emergency Stop will cause the engine to shut down.
This sounds like you have CV 2, start voltage, set too high.
I think the OP was asking if the Tsunami has a startup and shutdown sequence like a QSI decoder – no, it is not like a QSI at all. Turning the throttle to speed step 1 is the startup for a Tsunami, and pressing Emergency Stop is the shutdown.
A little brain dead in this respect, but maybe QSI has the startup and shutdown sequence patented.
Right now I am basing this on the LokSound Baldwin decoders that can easily be configured for prime mover start up and shut down with the loco not moving.
Yes, I know, the LokSound is not made in the USA but this day and age, I do not consider that an issue.
Right now my Baldwin LokSound locos can start moving at 1 mph at speed step one, 128 mode with a max speed of 40 mph. The prime mover rpm picks up some before the loco moves.
I LOVE the simple and re-mappable startup/shutdown of Loksound decoders. I wish QSI could be configured the same. I have 2 Tsunami’s on the way, and hope this doesn’t taint all the good things I’ve heard about them. I had a horrible experience with soundtraxx customer support on a couple of LC series in the past that has kept me away from the Tsunami’s for this long.
I also LOVE the RPM “ramp up” that the LokSound does prior to starting the motor moving- as described above. It took QSI a bit to get this down, but the Proto SW9 is decent and the H10-44 is great. The Paragon in my new Q2 has this and it is adjustable. Probably not an issue for steam, but nice for diesel.
Again, I hope this is not the case for the Tsunami. All the good quality sound in the world would not make up (IMO) for unrealistic motor to sound synchronization, and poor startup/shutdown sequence control.
No, not exactly. I’m the OP. As the Tsunami came installed, the loco would go through the start up sequence as it was being put on the rails. I’m sort of assuming that it would also go through the start up sequence on system power up. The information I couldn’t find initially was how to make the motor sound shut down so that I could make it re-start. No sense having some great start up sounds if you can’t show them off.
Looking at the on-line users manual, I found that you can make the motor go through the shut down sequence by pressing the emergency stop botton on the CE handset one time. People being what they are, some impatient individual will push the E-stop three times and cause a system shutdown. I find this unacceptable.
What I wanted to know was if there was a way to program one of the otherwise unused function keys to have it initiate the shutdown rather than the E-stop.
Some of the Tsunamis that come in locos factory installed (Bachmann etc) are not the same design as the separately sold versions that usually have lots more features. You might want to check with Soundtraxx to see what features are included in this version.
I do know that the steam Tsunami’s (full featured versions) functions can be re-mapped within limits. There is a chart in the manual. Not sure about start up sequence because I generally don’t bother with such being steam and all. I have to say that the galloping goose is one cool decoder with the engine revs and shifting sounds. The goose is my favorite guilty pleasure at my friend’s narrow gauge layout. I can see why you want to show it off…
I think I mislead you when I said “as it came installed”. This Tsunami was an after-purchase installation. When I said “as installed”, I meant as installed by the guy at the hobby shop.
I don’t know what “quiet mode” is. The Tsunami instructions are pretty clear on how to make the engine go through the shutdown sequence, once you find it:
"Start the Prime Mover
To start the diesel engine, simply increase the throttle to speed step 1. The engine will crank over several times and settle into a nice idle. On a few command stations, such as the NCE Power Cab, the Tsunami decoder may skip the startup sequence and immediately play the idle sound. If this happens, press emergency stop first, then increase the throttle and you should hear the engine start."
They don’t mention changing any CVs.
Again, all I want to do is use a function key to make this happen instead of the emergency stop button, just like with a QSI or an MRC.
Using the Quiet Mode
Tsunami’s Quiet Mode is used to turn the sound on only after the decoder is placed into service. It will also automatically turn the sound effects off when the decoder is not being used. This is particularly useful when you have a large number of sound equipped engines on your layout and don’t wish to have them turn all at once!
To activate the Quiet Mode, simply program CV 113 to any non-zero value between 1 and 255. This value sets the amount of time in tenth second increments, that the decoder will wait before it turns the audio off. Thus, a setting of 120 corresponds to 12.0 seconds.
When the Quiet Mode is active, the decoder will remain quiet when it is first powered up and then automaticall
Maybe this is worth trying, thanks. But if I read what it says, my impression is that it is turning the audio off and on automatically, sort of like using the mute function except without user input. It does not say that it makes the engine sound go through the shut down sequence.
Again, what I’m looking for is a method for the operator to shut down the engine, just like with the other decoder brands, without having to use the E-stop button.
Below is a link to a video of a Spectrum 70 ton with LokSound Micro decoder. I can press Function 8 and the prime mover starts. Get up to speed, then stop and press Function 8. The prime mover shuts down.
Hit Function 8 again, the prime mover starts up again. No EStop used. I use the NCE Power Cab.
With the Tsunami, after hitting the EStop the prime mover shuts down.
I go to speed step 1, the loco begins to move and the prime mover starts up after about one second. Not prototypical.
My LokSound decoders are configured to start moving the locos at one mile per hour at speed step one.
This what I would like with the Tsunami decoders. Not sure I can achieve this right now. If not, I will probably sell the Tsunami on ebay and go to strictly LokSound decoders.
Well, I just got back from the LHS where the Tsunami was installed. I spoke to the installer, and the short answer regarding getting a function key tasked to get the motor to shut down was “it can’t be done”. The longer answer was that the Tsunami folks designed the decoder the way they thought it should be, and were not going to give anyone access to the decoder’s “brains” to do otherwise.
I did bring up the issue about having to be at speed step 1 to initiate the motor startup and how normally the CVs were set up to have the looco start moving at that point, and that it wouldn’t be prototypical to have the loco start moving before the motor started. The answer there was to quickly move the handset speed controller from a zero setting to speed step 1 and then back to zero, allowing the startup sequence to be completed before the loco moves. Doesn’t sound ideal to me.
I suppose that the way out of that issue would be to re-program the CVs so that the loco starts to move at speed step 2 instead of one.
Still doesn’t make me happy as I can’t get my original issue solved, but since it is not my loco and not my decoder, such is life.