@NCE

Hi Eric,

My NCE system works well.  I've got a cement basement floor and fortunately the Pro radios haven't met it yet.  I like the size and feel of the throttle.  NCE's control and programming is very good and their support is superb.  AND they're still around!!! 

Recently I've started to wish that I could see more of the functions that were turned on when running my LokSound  decoders.  6 is not enough any more.  I've started to wonder if I could build a throttle in the old case.  Maybe Jim will read this and start to formulate the next gen... Or even better an update for the current body.

It will be interesting to see where this thread goes.

Thanks for the post.

Nick

P.S. Is the VRS for Vermont Rail Systems?

I use Digitrax to run my

I use Digitrax to run my Loksound equipped units (and everything else).  My DT400 only goes up to F12, but the newer throttles can get to the higher functions, or my throttle can be sent back and upgraded to the latest specs. 

I do feel that a computer hooked up to the system with JMRI is almost a necessity with sound decoders of any make.  Using WiThrottle or Engine Driver all the functions up to F28 are available.  And programming is much easier with the computer. 

MRC Prodigy for my N scale . . .

. . . Atlas S-2 with LokSound. Gets me up to F14, but that's not really applicable for the Slate Fork -- there are no trackside warning detectors, and a TWD readout is what F14 activates on the S-2. 

The only drawback is F2: I can't really get a short horn with it. But I'm thinking this might be the decoder programming, not the Prodigy's design.

I've not tried the S-2 with my Digitrax system, which is currently boxed up.

You are

going to get people who run and like all the systems out there.  You have to figure out what you really want and if you really don't like NCE for some reason, why?  Do the others have something better that you'd prefer?

I went from Digitrax to NCE just because it was simpler.  I still may opt for the ESU ECoS system as it is really simple, but quite pricey (the reason I'm holding back).  

With all things being equal, depending on what all you have with your NCE system, I would just stick with them and perhaps upgrade your throttle and perhaps save yourself some money.  

Lenz

I run Lenz with CVP wireless throttles, and I prefer to avoid any functions that require multiple keypresses to reach, so I'm limited to F0-F8.  Still, I've not found that to be a problem at all, and my roster is entirely Loksound with Full Throttle sound files.  

For my own operations, I've never been a big fan of functions that don't have a prototype corollary, e.g. pressing a button to make a coupler crash sound, so I've never had a need for more function buttons. Those kinds of things sound great as a spectator, but when I'm the one doing the operating, I've found that they take my head out of the prototype illusion I'm trying to create. Loksound's Drive Hold function falls in that category, since a prototype engineer doesn't perform a similar task, but I've found it to be so intuitive that it becomes second nature. As a result, and because it adds so much realism, it actually takes me deeper into that prototype illusion. 

For my needs, Lenz is outstanding. I've had my system for 20 years without a single component failure. The only gripe I've had has been that only one unit per consist recognizes some commands, like independent brake.  I easily got around that by programming all units in each consist to the same unit number, which works great for me, but doesn't allow me to easily add or remove units during operations, e.g. when using helpers or setting out power for a local at an outlying yard.

Lenz

I use a Lenz system with a Lenz 100 Throttle and a Lenz 90 Throttle. They work fine but functions are limited. If or when I replace it I would opt for NCE unless something better presents itself between now and then. It seems that throttles are behind what decoders are capable of and need to catch up!

Tim

Reassigning Function Buttons

I think the re-assignment of function buttons is one of the things that is often overlooked.  I've been playing with a couple of re-arrangements and getting to a point where I'm relatively satisfied.  The Lokprogrammer makes this easy.

I'm moving toward a strategy that moves seldom used functions to the "shifted" keys. (I use NCE) For instance, the startup/shutdown sequence, as delivered, is on F8.  Even though most people know this, I'm moving it to either F18 or F28. You only use it a couple of times, so it doesn't need to take up the space on a more easily accessed key.

F28, for instance would be Option-Option-F8 on the ProCab/Powercab or shift-shift-f8 on the smaller throttles.

Something like the independent brake can move into the vacated F8 slot.  That's used much more often than the startup/shutdown sequence.

Another candidate is the "switching mode." Fundamentally that cuts the power setting for each speed step in half, giving you finer speed control for switching. I'm not sure I need that at all. I run in the 128 step mode and have plenty of fine control as it is. If it's too fine, I can just switch back to 28 step mode.  That frees up another un-shifted button for something like "coast" or "run-8" that are currently unassigned.

I'm fairly certain that anyone operating on my layout could pickup changes like that fairly easily. At any rate the F-key definitions are on the back of the locomotive card for reference.

After you start playing with this a while, you can see why this is another reason that contributes to the desire to convert your entire fleet to Loksound. Many other decoders significantly limit the assignment of function keys.

Since I run several of my locomotives on my home layout and at shows I've mapped the "Volume" control to a function key. This steps through 7 (or maybe eight) volume settings. So I can easily set an appropriate volume for the environment. 

gs

JMRI

I use Digitrax, but wouldn't think about using anything but JMRI to program locomotives.

Perhaps Jim could figure out

Perhaps Jim could figure out a rotary encoder (thumb wheel on the side of the throttle?) to select the function and a button to activate the function, press the activate button again to deactivate the selected function, or the button could be built into the rotary sector, if such a thing exists.

John

@gs

Hi,

Nce and LokSound...  How do you program volume as you mentioned above.  I was on the verge of your reprogramming the functions thought and I think you pushed me over the edge!!!

Thanks!

Nick

ESU

I'll be going with the ESU command station for my layout.

what he said- JMRI to program, any sys to run

I use JMRI to program and 3 systems to run - NCE, JMRI (also has a throttle), and phone app

The user interface is the main decision for any DCC system. You choice will be the correct one.

Roco Z21

I've ditched my NCE Procab and I'm now using Roco's z21 with my iPhone or iPad as a wi-fi throttle and it's great.  Easy to set up and use. All locos are instantly recognizable by photo, cab number and description with 24 functions available for each.  Very easy to program.

http://www.z21.eu/en