DCC Help-sort of

My father and I aare going to make the with from DC to DCC. We will be starting afresh on a new layou we are going to make. If anyone could recomend the BESt MIDDLE/UPPER LEVEL DCC equipment that would be great. I mean, decoders and the controller software.

Avenger

Avenger,

Your question, along with “what is the meaning of life?”, is a source of much debate and discussion of this forum. Start by a doing a search and you will find numerous threads debating the ‘best’ dcc system. There is a good tutorial/discussion by Joe Fugate that is worth finding and reading. Also, I would recommend so of the DCC comparisons and articles on Tony’s Tain Exchange’s website. They are very informative and non-biased.

“Best” is a subjective term open to numerous interpretations and will vary depending on the persons needs, abilities and resources. Without going into specifics about any particular system, my first recommendation is to make a list of “gotta haves”, “wanna haves” and “don’t need to haves”. My second recommendation is to go to the various manufacturers’ websites and download and read the system manuals for the ones you are interested in. The manual is what you will have to rely on to get you up and running. DO NOT fall into the trap of thinking you can rely on your local hobby shop, other area modelers or the manufacturers’ help line. At 9pm there’s no one there to answer the phone. You should be able read and understand the manual and what it is telling you to do, at least the basic, without having the complete system in front of you. Read and do your homework now so that you don;t experience buyer’s remorse later.

DCC is a journey. It is a language of numbers that flow as signals to and from your decoder equippted engines. It is sort of like the Scarecrow going to see Oz for a brain and recieving a doctorate without understanding how and why DCC works.

If you want to run one engine, DCC is simple. Enter address 03 and away you go!

Now two engines or more, you just got complicated. Cab numbers, numbers for different settings etc.

DCC is a pleasure, but if you lack grasp of the system you are working it will be Dante’s Hell descending into lower and lower levels of frusteration and stress.

Keep in mind, people are stressed when they learn new things.

Look at the information that is out there about DCC. If you read one of the downloadable PDF’s like a DCC manual from one of the manufactors; it might sound like gibberish. Take time to learn the different terms in the DCC world and understand what they mean.

It still takes two wires to run a whole railroad on DCC. It’s the learning that is the tribulation.

I’m in the process of wrapping my head around DCC too. As was mentioned look closely at available features and decide what you must have. Determine what you can live without and then proceed from there.

I have become interested in the Digitrax system but I hesitate to opt for the entry level system because I feel like I want all the bells and whistles. I’m starting to think that the extra $$ to go to the next level might be worth it.

I was looking at the MRC Prodigy systems, but I have not heard a lot of positive comments on the MRC DCC stuff yet.

Anyway, I’m still researching and looking at products and features. My son and I are just starting his HO 4X8 which will be DC. When it is complete I can start seriously looking at what I want to use on my proposed “around the room” layout in the next room.

Avenger,

As JK already stated, choosing a DCC system is a personal choice. What is “best” for one person may not be the “best” for another person because of preferences and needs.

There are a number of good DCC manufacturers and systems out there. Like buying a car, the best thing to do when picking a DCC system is to be able to test drive one yourself so that YOU get an idea how it feels and what it can and can not do.

However, before you do that, a good thing to do is to write down what your current layout needs and wants are and what you think they might be (future expansion). For example:

  • What size will my current layout be?

  • Do I have room to expand? Will it get bigger?

  • What type of layout will I have? Switching? Continuous running? Both?

  • Do I want the ability to run a DC (non-DCC) locomotive on my DCC layout?

  • How many locomotives will I be running at a given time?

  • How many operators will be using the layout at a given time?

  • Will I want the ability to tweak my locomotives so that they run better?

  • Will my locomotives have special lights or lighting effects (e.g. Mars lighting, ditch, etc.) and do I want the ability to turn them on and off?

  • Do I want to be able to hook up a computer so that I can program decoders more easily?

  • Will I eventually want to add signaling?
    Avenger, these are just a few questions to ask yourself. By answering even some of them, you’ll be able to narrow your choices down.

Decoders are designed to work with any DCC system. Therefore, if you have a Digitrax DCC system, you are not required or obligated to ONLY use Digitrax decoders with it. For me, Digitrax, NCE, Lenz, and TCS are all excellent choices for motion decoders.

Avenger, if you are interested in taking a virtual look at the NCE Power Cab, click on my web link at the bottom of th

There is no “right” DCC system for everyone. If there were, there would be no choices.

How big is your layout, or how big is your planned layout? How many engines do you plan to run at a time? Will you be running multi-engine consists? Will you be running sound engines, or their quiet bretheren?

How big are your fingers? (That’s a real question, and it was the deciding factor for yours “fat-fingered” truly.)

The good news is that all of today’s DCC systems are pretty good. The world has moved away from the “starter” systems of the past, whose biggest disadvantage was that they were not upgradeable. The NMRA standards assure you that any decoder (the part in the engine) will work with any system (the part that generates the commands.) However, the components of the systems are not compatable, so you can’t, for example, use a Lenz throttle with a Digitrax base station.

Also DCC has different function keys. Maybe F2 for a bell. Some manufactors will put in thier OWN system to control the engine.

Even worse, the CV (Configuration Variables) aka switches inside the Decoder’s brain are different from one maker to another. If I was to say configure CV # something to make a bell choice something for a QSI engine… it will NOT be the same value or something for another MANUFACTER of a different engine… like MRC.

Until DCC is truly Common across ALL of the software and the controls UP TO the limits of the hardware used… we will never enjoy peace from the noise of the tower of Babel.

Really??? I thought CV#'s were standardized under NMRA Recommended Practices? I mean, I know some manufaturers do not use all CV’s that are available, but I thought that CV# such-and-such was always that particular variable. Like say CV#1 is always the Loco’s address, and CV#3 is always speed increase momentum, and CV#19 is always Consist Address…No??

Uh, sort of.

I think I bit off more than I can chew here.

Let me try to explain.

My MRC 4-4-0 had CV numbers on their own chart. It was a rather small chart… maybe 20 CV’s each with options. Yes there was the start voltage mid etc.

Now park the QSI engine and look at that manual. Downloaded as a PDF file off the internet for the engine presents ALL of the CV’s PLUS Bit mapping etc etc etc etc etc.

Kinda like being told that this button or number is for the bell on one engine and totally something else with another manufacter’s engine because they felt like writing these values thier own way and not bothering to make sure that a value is the same across the entire hobby range of decoders.

Maybe SOME CV’s are the same because they have to be… but it will be very nice to see ALL CV’s the same across the board.

I’ll shut up now before I confirm my total lack o

I too was under the impression that the CV’s were part of the standard. Now in the case where one loco w/ decoder has CV’s that another loco w/decoder doesn’t I don’t see that as meaning the CV’s are all different depending on the manufacturer. Rather the CV’s that are common between two different products use the same standards. At least I sure hope this is the case. Otherwise I need to go re-learn about DCC because I have come to some incorrect conclusions.

FV is right in a sense that some of the common function button capabilities (F0-F12) are different from one manufacturer to another.

For example, F2 or “2” on my BLI (QSI) and Trix (Loksound) Mikes are exactly the same - i.e. it activates the horn. However, F1 or “1” on my BLI Mike toggles the bell, while F1 or “1” on my Trix Mike turns sound on and off. (Mute is F8 or “8” on QSI decoders.)

Also, the QSI decoder allows you to shut your locomotive down into three levels of “sleep”. The Loksound decoder does NOT have that feature.

Now, even though there are differences between manufacturers as far as functions are concerned, CVs (or configuration variables) are standardized under NMRA rules. The only exceptions would probably be the CVs that operate/manipulate the function button functions.

Tom

It’s my understanding that the basic CV’s associated with moving the engine around the layout were standardized by the NMRA in the original DCC specs.

However, the CV’s for sound were not fully standardized. Sound appears to have evolved faster than the NMRA was able to react to it.

The result is, perhaps, more confusing than it should have been.

Mark Gosdin

Man, oh, man, you have reopened the proverbial can of worms. There is no DCC system that is the best period. Just remember that insofar as up wire from the tracks, there is no compatibility between DCC systems. If you buy Digitrax, for example, you can’t add an NCE throttle later on. I have a Digitrax Zephyr and I considered first how many locos I wanted to run, then expandability and, of course, cost. My guess is that you are probably looking at a 5 amp system, so you may want to start your journey into DCC there.

The CV issue isn’t as bad as it seems, nor as good as you might hope for, but in the end it makes sense.

There is a standard that covers most of the ‘everyday’ CVs. There are addition standard CVs that are optional in any particular decoder, they are for features that do not have to implemented, but if they are, the CVs are defined in the standard. Then there are CVs that are set aside for the decoder manufacturers to use as they choose. This allows for most of the sound programming, and also allows for the addition of features that might be unique for an application.

The easiest way to deal with these is by using a program like Decoder Pro, which can read the ID of the decoder, and then use a database on the computer to know what CVs are avaiable in that decoder, and what they do. Since it is ‘only’ software, it is possible to keep the database at least somewhat up to date as new decoders come out. This makes having a command station with a computer interface a good thing, especially is you plan to go beyond basic decoder programming.

Hi Bearman,

I have looked at the Zephyr too but I am concerned that if I opt for economy I will end up missing features available with the Empire Builder. What are you running with your Zephyr and do you have any feature regrets with it? Thanks in advance.

Thanks for that information! I think I will have to look into this Decoder Pro when I take the DCC plunge. A computer interface to the command station is probably a must have feature for me in the long run.

I also have a Zephyr and it has everything that I need. The Empire Builder can run 22 engines compared to the Zephyr’s 12(the Zephyr is advertised an running 10, but will actually do 12). The Empire Builder is 5 amps and the Zephyr is 2.5 amps. The Empire Builder comes with a DT400 throttle, but you can get a Zephyr and a DT400 throttle for about the same price as an Empire Builder. One thing the Zephyr has that the Empire Builder does not have is a seperate programming track output with read back capability. Because of the lack of a programming track output on the Empier Builder, I would suggest that If you go with Digitrax, either get the Zephyr or go all out and get the Super Chief.

Alright, lets swithch it up. Tell me what DCC system you use and why you like it and why you dont. That’ll give me a better feel.

I started with a friend’s DT400 throttle on a Digitrax Empire builder.

I liked the DT400 very much. The Zephyr didnt have it and the SEB didnt have read CV ability sooo the Chief is it for me. I have yet to run into a system limitation or error. However I do learn that other errors are usually my own errors.

I can still upgrade the Chief into radio when the time is ready and always add onto the loconet. That is something I understand more and more every month.

Everyone has their favorite system - I suggest using what is used most locally (club/hobby shop) if you ever need help. Also, try different systems to see what you like.

Lastly, you can build you own system as well. Both Lenz and Digitrax is well documented and there are some nice systems you can build yourself. For example - the NanoX is a self made Lenz system which is cheap and simple to build and has lots of features (most better than the Zephyr). Best of all, you can build a booster to your power requirements.

Here’s info on the NanoX:

NanoX is a simple DCC command station, without pretensions, that includes XpressNet bus v.3 and can control:

  • 16 locomotives simultaneously in the addresses 1 to 9999
  • 1024 turnouts and signals
  • 31 XpressNet throttles or devices (Lokmaus, SimpleMaus, XbusTCO,…)
  • Programming and reading DCC decoders in Direct, Paged, Register and PoM modes.
  • With a 1,2A Booster including protection against short circuits
  • Supports 14, 28 and 128 speed steps, functions FL and F1 to F12 for every locomotive

It only needs a PIC 16F628, a driver MAX485, six transistors and a few components more.

This site has more info -

http://usuaris.tinet.cat/fmco/home_en.htm

The author also has info on throttles, boosters, and computer interfaces.

You don’t have to be limited to a pre-made system.