Since installing my first ESU Loksound decoder I've found there are different ways to make use of the various Full Throttle features.
When I first started operating with this new decoder I would put the throttle to notch 3 or 4, and when the train just started to roll I'd press the drive hold button giving the impression of great weight being moved. After that I cycled the drive hold on and off in short bursts gradually increasing the speed of the train. Once I got to the speed I wanted I left the drive hold on and manipulated the prime mover sound as needed, throttling down when I wanted to coast, and throttling up at an uphill grade.
After operating this way for a while found myself running into 2 problems:
1) I would forget what notch the throttle was in when I had first pressed the drive hold, and would forget what actual notch I was currently in, because my NCE hand held wireless throttles have no indicator screens. As a result when releasing drive hold, the train would often speed up or slow down unexpectedly to match the current notch setting.
2) When running through the helices on my layout there were times I wanted to increase or decrease speed for one reason or another, but didn't want to change the notch setting I was in. With drive hold on that wasn't possible.
So I changed the way I used the decoder. I assigned function buttons to the Run 8 and Coast features of the decoder, and started to make use of those much more than in the past. Starting out from a dead stop I still used the drive hold feature as described above. But once I got to speed I turned the drive hold feature off, and then left it off as the train ran as the train made its way around the mainline.
When I came to level sections of track and wanted to throttle back and let the momentum of the train carry itself along, as would happen in the prototype, I simply pressed the coast button and the prime mover dropped to idle. When it came time to reapply power to keep the train moving, I turned the coast button off, and sound came up and automatically matched perfectly whatever the current speed of the train was.
This proved handy, especially when I came to the yard limits on the main. If I was coasting as I entered the yard limit and the speed of the train was too high, since drive hold wasn't on I still had the ability to control the speed separate from the prime mover sound and slow the train down.
I did a similar thing when heading into a grade. Instead of using the drive hold feature and notching the throttle up manually, I pressed the Run 8 button. As the prime mover sound went to notch 8 I could still manipulate the speed as desired, usually slowing the train down to a crawl up the grade. If the grade lessened I had the ability to increase the speed as desired and leave the sound at Run 8, or turn Run 8 off, in which case the sound would drop and once again automatically match the current speed of the train.
There are a lot of other operating scenarios I could have gone through here, such as using dynamic brakes on a downgrade and gradually increasing the speed to simulate the effects of gravity on the train, or leaving the prime mover in notch 8 and increasing the speed as more of the train crests the hill. But I think you get the idea.
Operating the decoder in this way has enabled me to eliminate the problems I listed above, and IMHO really makes the train run in a very prototypical fashion. I no longer have to worry about turning the drive hold off and wondering if the speed will match the sound or not. Using the decoder in this way is also the secret that enables me to make use of the virtual mainline idea I posted in a separate thread here on MRH.
I know many others have recently made the switch to the new ESU Loksound decoders with the Full Throttle feature. So I'm curious to find out if you've thought of any other ways to make use of these excellent decoders as you run your train? I don't want to miss out on any of the possible fun!
Paul Krentz
Free-lancing a portion of the N&W Pocahontas "Pokey" District
Read my blog