How do you keep track of functions and CV's for different decoders?

For almost 2 years I have been running BLI Locomotives and have gotten used to default and re-programmed Function Keys, Volume CV’s and even momentum programming.

Recently I got a Proto 2000 0-6-0 which has an early QSI decoder. Everything is different. You even reset it with a magnetic wand and it has very few CV’s you can adjust and Function keys do different things.

I have a Bachman I’m replacing the decoder on and an athearn that is DCC Ready that I want to add a TCS KA sound decoder to.

I assume they will all be different related to programming functions and capabilities.

How do you guys keep track of your different decoder capabilities and functions? Is there an easy way or do I just need to remember?

I use JMRI/Decoder Pro on my laptop. It is hooked up via a USB interface to my Digitrax DCC system. Most DCC systems have a similar interface product.

You can adjust CV’s and ‘save’ them to the roster. Very nice, and the software is a free download.

Jim

Hello all,

There are a couple of different options.

The first would be to record your CV’s in Excel. For some folks not proficient in Excel this is more trouble than it’s worth.

On the other hand you will become extremely proficient with this program- -uh, software- -yeah I’m old.

The other option, and the one I use, is JMRI Decoder Pro.

With this software you can not only keep track of the CV’s but also reset and reprogram decoders; if you setup a programming track.

This software also makes programming CV’s simple because it asks, in simple language, what you want to do. You do not have to calculate CV’s.

It is freeware and available for Billy-Windows and Mac machines.

Because it is Java based software you will need to have the appropriate Java software.

To read or program decoders you will need an interface device; Digitrax PR3 or similar.

Hope this helps.

Thanks for the replies, I can read and program through my NCE system. That is not a problem for what I do. I could use Excel but I was hoping for some panacea that is not likely to exist.

Maybe I’ll create an info card for each loco ( you know a 3x5 or smaller that I can keep by the layout and refresh my memory when I place a loco in service witch a decoder I’m not familiar with.

Gary,

Although it will do a number of other things, as well, Decoder Pro is your friend for quickly and conveniently copying, storing, and retrieving ALL the CV values for each of your locomotives. Generally you can copy all CVs for a single locomotive in <1 min. It would be a lot quicker than trying to record it individually with your Power Cab and Excel.

Tom

There’s not much you can do with different locos using different numbers for the same function, except where possible remap them. I generally don;t have any issues with this because I usually only use a couple of functions - the lights (F0 on every decoder), bell (F1 on all) and the horn/whistle (F2 on all). Most of the other things, I never even touch. The ones over F12? Those I’ve only used to just see what they do. I can do without radio chatter (out of era for me), station annoucements (why does a freight loco call “All Aboard”?), and ambient sounds - those things should come from sound modules placed under the layout, not from the locos. MTH even has train wrecks - sorry, I am not Gomez Addams.

Those dedicated functions for grade crossing signals, or the different buttons for short horn blasts and long horn blasts - why?

Doubling down, I use only one sound decoder in all my locos (except 1). So even those functions I never or rarely use are on the same F key for all my locos.

–Randy

i don’t have a PC And from what I can see it doesn’t work with an iPad

Randy, I too don’t care much for talking and only use basic sounds so I think I’ll try to keep to one or 2 decoder types.

Maybe I’m reading between the lines or I’m being influnced by my own issues. Decoder Pro is hard to bit when it comes to keeping track of Cv values programens into the decoders for each locomotive. My experience is that once I’m done programing I only go back to Decoder Pro to program a new loco or not often to tweek some values. I think a toll I needed is to quickly access the specific functions applicable to a locomotive. Not all my locomotives respond to the function keys in the same manner, except fo the basic ones like bell, horn and lights. Maybe this is just me that I have not mapped to the same key for the same function on every single engine. I think an index card file, organized by road number is useful (my memory is not as good as it used to be).

Moe

Go to the Goodwill store (or wherever), pick up an old PC, load Linux on it, and install JMRI.

For less than the price of a new plastic loco, you’ll have software that’ll make programming even the most difficult decoders as easy as point and click.

It’ll also give you the tools to (if you so choose) control signals and so forth on your layout, create dispatcher panels, control room lighting, and even create and print manifests and switch lists for your operating sessions.

I’ve been a JMRI user for 14+ years and wouldn’t be without it.

When it comes to programming my decoders - I rarely bother loading up JMRI. All o fmy motor only decoders are the same, and all my sound decoders are the same. After you do a dozen, you memorize the CVs. Address ralted CVs - well, every DCC system handles that automatically. The only thing I set on motor decoders is basic lighting which involves changing 2 CVs. And since I use all decoders that support CV2-6-5 for simple 3 step speed tables, I use those to do any speed matching and limiting.

Another aborted project of mine - I was going to add a JMRI compatible list of CVs to the database I use to store my locos and rolling stock, and actually have a button to shell out to JMRI with that loco loaded in the roster. However, the number of times I’ve needed to refer to the old settings on any of my locos - worst case, i can read a CV on the program track if I really need to knwo what it currently is, but in most cases, the reason I am changing a CV is because I don’t want what’s there now - so what’s there now is a completely meaningless value. Maybe I’m just strange, but it takes me longer to set up a loco using JMRI than just using my DCC throttle - BECAUSE I don;t use any of that complex stuff where JMRI really helps you out. I don’t need to pick complex lighting options from a nice dropdown menu because I don’t use complex lighting options, it doesn’t fit my era and prototype. And since I have standardized on decoders - I’m not going to wait 15+ minutes for JMRI to read all the function mapping CVs in a Loksound decoder when my Lokprogrammer does it in 15 seconds.

–Randy

I have JMRI on my computer and all the neccessary hardware to hook it up but I just haven’t bothered. I use LokSound decoders and they require very few adjustments out of the box. The few CV adjustments that I have made so far fit quite nicely on a 3 x 5 recipe card. Perhaps when I get to a point where I can match locomotive speeds I might figure out how to use JMRI.

Dave

Tops on my list of “DCC Must Do Someday” is to come up with a standardized schedule of function button assignments for most of my roster.

It can be very frustrating because there are SO many functions offered by the various manufacturers.

A few weeks ago I installed identical WOW Diesel decoders in a pair of Genesis F-3s. I thought I had them programmed to act as one unit, i.e. same road number and operating characteristics, using Decoder Pro.

After making several trial runs I was stumped because the second unit, a B unit, kept stalling and dragging the lead unit to a stop but with the wheels still turning but the sound was still on so it wasn’t a pick-up issue.

Then, after turning the throttle down and back up again, they took off just fine, only to stall somewhere else three or four minutes later!

Finally, I got a clue! I heard a chirping sound coming from the B unit. Somehow, the alerter function was activated and by me not responding to it, the engine went into a penalty service stop.

So that’s one example of trying to figure out A) what functions to keep disabled and B) I had NO clue as to what button to push to acknowledge the alerter!

It gets even worse since I have LOTS of odd-ball DCC locos from several manufacturers that each require oddball function presses even to get them to run.

For instance, Rapido alone I have the RDCs, the FL-9, The U-A Turbotrain, Amtrak F-40s and maybe a few others. Each one of these require different start-up sequences, various options such as HEP, strobe lights, diesel or electric mode, “Straight to 8” mode, switching mode, etc.

I have Walthers Metroliners, again all different functions for mars light, number boards, brakes…

Now, WOW sound has so many functions for lights and sound that there is a “shift” key to toggle between the two! It can be a real pain and the kind lady is always telling me &qu

I try to keep my model railroad simple and like many people I cannot remember which function does what on my locos - especially when modern locos can have up to Function 28 and especially when a loco has not been used for a few months.

My short term solution at the moment is to print out an A5 laminated card for each loco I have.

The card has the loco number and photo printed at the top followed underneath by a printed list of the function numbers and what each function does

eg. F0 Lights on, F1 Bell on, F5 ditch lights on

The card is placed where I can see it, hooked on to the fascia with a bulldog clip or I hold it in my hand with the controller.

My longer term solution is to use the Roco Z21 DCC system which uses a mobile phone or tablet to run the trains. The phone “app” is programmed with a photo of the loco and the functions which can be programmed to any number. The system then uses visual images to select a loco and an on screen icon for each function.

eg. a horn symbol for F2, a bell symbol for F1

The system has been purchased and has been trialled with a model railway club layout during a weekend exhibition. It worked well and even 7/8 year old children could run trains, blow the horn, sound the bell and switch lights on and off using a mobile phone or tablet without any complex instructions.

Pen and paper. Unless simplicity has been made illegal.

Thanks for all the replies [8-|]

If you use car cards to operate - there are locomotive cards as well, and this would be a great place to record that information.

–Randy

As some have already mentioned, choosing and sticking to the same decoder and functions for all for motive power is the easiest way. With JMRI, you can simply upload the configuration, change the loco address and your ready.