Here's what I got . . .

The ProtoThrottle will work with any DCC system, but the first thing you need to realize is that you can't just get the throttle by itself - you need also to get a receiver to allow the throttle to communicate with your particular system. In my case, I got the NCE-compatible receiver. I also got a fascia-mount holder, just because.

You probably already know that the ProtoThrottle is a wireless DCC throttle that mimics an EMD diesel control stand, and you've probably heard that it's complicated to set up and there's a steep learning curve. I can attest to the fact that it's pretty intimidating at first, but once I got the throttle and receiver to communicate, I was running trains with it in under 5 minutes.

However, getting it to communicate with the receiver was a little bit of a challenge - and getting it to work exactly the way I wanted with my decoders took a bit more time. I'll cover setting up the receiver in this post and will cover optimization later.

There are 3 steps to setting up the receiver (as outlined in the manual, which can be found  here):

1. Configure the DIP switches
2. Connect to the command station
3. Configure the ProtoThrottle (hereinafter referred to a "PT")

I have an NCE system and the PT receiver connects to the NCE cab bus using the supplied phone-like cable. The "Base Address" of the receiver and the "Base Address" configured in the PT need to be the same in order for them to communicate. You change the receiver's address using the DIP switches.

This is where I got a bit mixed up. Read on to avoid my mistake.

According to the manual, you add the value(s) of the "BASE ADDR" DIP switches that are in the ON position to get the receiver's base address number. These switches were all off on my receiver when I, um, received it. So I figured the "BASE ADR" of the receiver was 0 (zero).

Next, you go into the "COMM CFG" menu on your PT to make sure the Base Address is the same as that on your receiver. On mine, it was "00" (the default) so I figured I was all set.

I wasn't.

After some minor frustration, I finally decided to try and just change BOTH addresses. First, I changed the DIP switches on the receiver thusly:

Note that the switch above "1" in the "BASE ADDR" section of the receiver is now pushed up, set to ON.

Then I went into the COMM CFG menu and changed the BASE ADR to "01"

And just like magic, it WORKED!

The manual says that both "the throttle and receiver ship with a default base address of zero" and that "any address will work as long as both the throttle and receiver are configured to the same value." I'm certainly in no position to dispute the guys at ISE, so I'm just sharing my experience. YMMV.

The only other thing you have to consider when configuring the receiver is to be sure it doesn't have the same "CAB NUMBER" as any of your other throttles. 

< begin sidebar>

You do have a list of the cab addresses of your throttles handy, right? Here's mine:

Don't worry if you don't have this info, yet. I finally got around to compiling my list after an ops session where things went crazy sideways when somebody brought a throttle with the same cab address as one of mine. Unbeknownst to me. I quickly figured out all my addresses and have maintained a list ever since. I strongly suggest you do too!

< end sidebar>

Like with the BASE ADDR, the receiver's cab number is determined by adding up the values of the DIP switches that are pushed up/set to "on" As long as that number is different than all your other cab numbers, you're all set.

And that's IT! for setting up the receiver. It actually took you longer (probably much longer) to read this post than it will take to actually do it. But hopefully you found the process easy to follow and realize it's easier than you might have thought. I do strongly recommend you read over the receiver setup manual though - especially if you have a DCC system other than NCE.

Once the receiver and throttle are communicating, you just use this throttle like you would any other. Assuming you haven't remapped the horn or bell functions in your decoder(s), it'll work just as you expect. But to get the MOST FUN out of the ProtoThrottle, you're going to want to change some CVs  and make sure the PT brake is using the brake on the decoder.

But those details are for another post. In the meantime, you can just enjoy using a throttle that actually has a THROTTLE lever as well as a reverser lever and a brake lever. No more pushing buttons!

And if you don't have a PT yet - and especially if you do - be sure to check out  ISE's website and the super helpful folks over at the  PT group to learn more.

Now, if you'll excuse me, I have some switching to do . . .

So far…

the hardest part for me was to find the “missing in box” handles!  Hahahahahaha!  Thanks for this post.  When I get back home I’ll use it to get mine programmed!  I’m excited to get it running locomotives!

Thanks again Chris!

Decoder config for Proto

I'd like to try a ProtoThrottle out some day.  I've heard the hardest thing is to configure the decoder in a loco to work properly with the ProtoThrottle so it works ideally.

Configuring the decoder for the ProtoThrottle

There are really only three things I can think of that need configuring on a decoder to optimize it for use with a ProtoThrottle:

1. Momentum. You want some. 'nuff said. (well, not really 'nuff said, because figuring out how much you want can be a very interesting exercise. See also Brakes)

2. Brakes. It's entirely a personal choice how strong you want the brakes to be. And on a SoundTraxx T2 this expands out to Independent, Train, and Dynamic brakes. Quite honestly, getting the brakes dialed in can be the biggest headache - but it's not exclusive to the PT by any means, since you need to do it to get the feature to work with any throttle.

3. Lights. You want to get rid of directional lighting and set up the rear light on it's own function so they can be controlled independently.

The big trick is getting this all set up the same for all decoders. And is a major reason I decided to standardize on one decoder as much as I can (Tsunami2 for me, although I have a few oddballs like the RDC and P42 with LokSound). Which decoder you standardize on is your choice, all have positives and negatives. Fortunately for the oddballs, the PT can hold multiple configurations, you just have to remember which is which that you set up.

Configuring PT & Decoders

I'm working on this myself and am interested in how others are dialing theirs in... Thanks Jeff for the summary of your process!

yes, good to know.  I've seen

yes, good to know.  I've seen some discussions here about the trails and tribulations of setting up decoders for PT use to optimize it.

Programming decoders for a Proto Throttle

I've heard the hardest thing is to configure the decoder in a loco to work properly with the ProtoThrottle so it works ideally.

Decoders can be programmed normally.  The main programming difference is that the PT does not have as many function combined buttons/knobs/levers as many controllers have buttons.  Choosing which functions to be controlled takes some thought.

For example, take braking.  TSU2's come with braking set to F11.  My choice is to set braking for F5 so visitors can see the brake status on a NCE ProCab screen.  Lights, on the other hand, can be seen by looking at the engine.  They can be assigned to any available function, including those above F9 that would otherwise require an additional button press on a ProCab.  The engine can then be operated with either the PC or PT.

To repeat, programming the decoder is the same as always.  Programming the PT requires more thought because there are less buttons, and some of those buttons can be programmed as either latching on not latching.

Don M.

Decoder Programming

The programming isn't hard, but unless you're already using brakes, it'll take some adjustments.  Also, you need to have consistent behavior between decoders in a consist of locomotives to ensure the locos respond as expected.  Personally, I implemented braking before the PT was introduced, and bringing the PTs on line was very simple.

The most reliable method of implementation is to standardize on one brand of decoder, and program the functions the same on all locos.  In my case, I selected SoundTraxx (Tsunmai, Tsu2, and Motor Control -- earlier versions didn't have brakes) because they were the only manufacturer (at the time) who had a working brake function.  Many of today's decoders provide braking capability, and will work well with the PT.

When programming, the first -- and most important -- step is to get the locomotive running as well and as smoothly as possible.  Without any momentum programmed in, it should start and stop very smoothly, and run well at very low speeds.  This way, when stopping with the brake, the prime mover can drop back to idle while coasting and stop smoothly with the brake.  I use the decoder's BEMF to get the loco to crawl at speed step 1 and start without jerking.  If you're not familiar with tuning using BEMF, there are lots of "how to" tutorials on the web.

If you're setting up a consist, I recommend matching the loco performance (usually using BEMF and speed tables) before setting up the momentum and braking, and checking again after making the consist to ensure the locos play well together.

Once the locomotive is running well, set up the momentum and braking.  Braking in ST decoders is implemented by reducing the stopping momentum (CV4) by a value stored in a CV (116 for Dynamics, 117 for Independent, or 118 for Train Brake).  Because the maximum braking value allowed is 127, I typically set CV4 to about 137, which becomes 10 when the brakes are on -- which I find to be a nice, gradual braking rate with a moderate stopping distance.  You can set it for whatever you like; often, switchers are set up with a shorter stopping distance than rad engines.

Starting momentum I usually set to about 25 or so for road locomotives and 20 or so for switchers.

Setting up the lights is a little trickier, because decoders often have different function settings, even within a manufacturer's line, for lighting functions.  For ST I generally map the forward and rear lights to FX5 and FX6, respectively, so they can be controlled independently.  Before the PT, I had the lights set up so the "headlight" button, or F0, controlled the forward light, F3 controlled the rear light, and F4 controlled the dimmer.  Your decoder may require different assignments.

Setting the PT up for light control requires going into the "Func" menu, and assigning F0 and F4 to the front light dim, and just F0 to the front light bright, and (in my case) F3 and F0 to rear dim, and just F3 to rear bright.  Your setting may (probably will) vary.

A side note:  For the most satisfying sound response to the throttle, you may want to adjust the sound notching in the decoder.  In ST decoders, one can adjust the number of throttle speed steps between sound notches on the decoder (ie, the number of steps to be advanced before the prime mover increases in speed).  To get a reasonable correlation between the eight throttle notches and the sound, I set mine at 15 speed steps (128/8 = 16, but 15 is the max setting).

Once you've done it a couple of times, it'll take longer to read this than it will to do the programming.  Using DecoderPro helps immensely. It's free, and puts programming into plain English -- no worries about CV numbers, etc.

Hope this helps!

Tim Garland's "How to Operate Like a Pro" Article

Way back in August of 2018 Tim Garland wrote a great article in Model Railroad Hobbyist.  He details both setting up and operating the PT.  That was followed up by a lot of good discussion on the forum.

This is a link to the forum discussion.  It includes the link to the original article.

I think it's a great article.  If you're configuring a PT, especially if you've never done it before, it would be well worth the time spent reading.

GS

Great stuff Chris!

Lots of excellent advice in this thread. 

In case it helps, here's a quick video of PT basics with LS5 DCC decoders . There's no right or wrong way, this is just my approach. There's so much flexibility with PT and moderns DCC decoders so experiment and see what works best for your roster and for how you and your crews prefer to operate.

As Jeff said, standards are a Good Thing.   If you need to mix and match decoder brands there's an element of Lowest Common Denominator but I think you'll find PT's a game-changer compared to conventional throttles in any case.

Pete

A little more background on the Proto Throttle.

This is an early interview with the three principals of Iowa Scale Engineering and three beta testers.  Tim Garland is a part of the group of beta testers and responds.  I found this interview very interesting.

http://modelerslife.libsyn.com/proto-throttle-is-born

Tim is a regular on his YouTube channel.