Programming decoders including
Sound.
A
lot has been asked and said about programming loco decoders, especially since
the first RTR Broadway Limited sound locos with QSI chips appeared on our
layouts. Prior to these RTR locos, sound in our locos could only be added by
installing a Soundtraxx after market decoder, that was beyond the skills of a
lot of modellers and these only operated with DCC. Since the introduction of
the RTR BLIs and others, that run on DC as well as DCC, sound has become
popular. At the moment it has been reported that most of the RTR sound locos
with the QSI chips are being sold to owners of DC layouts. This is probably
because layouts controlled with DC are still the majority of total layouts.
With the advances in DCC and the decoders becoming smaller, more features and
cheaper and along with systems with more features becoming cheaper, DCC layouts
will become more popular.
These
BLIs etc with QSI chips and some of the Soundtraxx especially the new Tsunami,
have caused some angst amongst DCC users. These users are used to reading the
value of the CVs, prior to programming and some Command Stations, when reading
a CV value, comes back with a message “Cannot read CV” or similar depending on the
DCC system.
The
reason the Command Station gives this result, is because the C/S thinks there
is a short on the Program Track due to the sound decoder’s higher Inrush
Current exceeding the C/S’s threshold for current limiting on the Program Track,
to protect the decoder and system, if there was a short on a new decoder installation.
Most
of all the newer decoders including the sound units, support Programming on the
Main, POM, type of programming and commonly called “Operations” mode, that
allows the decoder to be programmed while the loco is on the mainline (layout).
POM allows you to adjust CVs while you are using the loco, but in most cases,
you have to have the loco stationary. This reduces the inconvenience of
returning the loco to the dedicated Program Track and if only one DCC system, a
break in operations that most people would not tolerate if on a club layout or
a few operators on a home layout. Programming would have to be “after hours”. Using
POM makes “matching motor speed characteristics” etc much easier. All CV values
can be changed using POM and this includes the short and long addresses (CV1 –
short and CVs 17 &18 - long) depending on the DCC system. My NCE system
allows this.
POM
programming has one slight (depending on the user) disadvantage. It cannot read
the CV values that some users are used to, while programming.
To
program a loco, it is not a requirement to read the CV values, it is just that
users are used to it and this has created some sort of “security blanket” for
those users. I don’t understand why seeing the value of something you are going
to change is necessary, except maybe a stating point to change a CV. No value
displayed in POM, just insert a value and you can see the results as soon as
you return to running the loco, by operating the throttle. Some decoders allow
CVs to be changed while the loco is moving eg. DSD100-LCs allows volume changes
while running.
POM
programming is a command to change a CV value with an address attached to it,
and this command action is just like sending a command to a loco, for example,
increase the speed of the current loco, change direction, turn on the headlight
etc. These commands have an address attached to them and only the decoder with
the exact same address, responds. It is for this reason that all the locos on
the layout, don’t move, when the ”speed knob is turned up” when addressing, say
loco 4512. This is basic DCC, independent control of all locos on the layout.
Some
have reported that they have programmed all the locos on the layout. Unless
there is “operator error” in trying to do this POM, it is impossible to program
all the locos on the layout. Operator error cannot be guarded against by the
manufacturer. Some basic understanding of what happens on your layout, will
confirm this. It has all to do with addresses. The only way you can program all
locos is do a Global Command and this is possible by using address 0. Why
someone would use “0” for an address while trying to address say loco 4512, is
certainly beyond me. In fact a global command is exactly what happens when the
Emergency Stop button is pressed to stop all the locos on the layout for what
may be an emergency for whatever reason.
Reading
the decoder CV values in these sound decoders required some form of program
track booster. A Power Pax from Tony’s fitted to the Program Track allowed
reading CV values of the early Soundtraxx and QSI decoders. Along comes the
Soundtraxx Tsunami (latest sound decoder) and the CV values cannot be read even
with a Power Pax, depending on the DCC system. Soundtraxx recommends a Program
Track Booster PTB-100 to enable reading CV values. Another unit that has to be
purchased to replace the Power Pax, what next?
Since
all programming can be done on the
When
a decoder comes from the factory, whether it is installed in the loco or is an
after market version, it comes with all the CVs at the default value. When this
loco or decoder (in a loco) is placed on the track some form of programming
must be carried out. This will depend on the user, and will start from just
changing the 2 digit address or allocating a 4 digit address just to run the
loco on the layout with other locos present. Users that tinker with CVs to get
optimum performance and special effects etc will change from between a few CVs
eg. CV2, 3,4, and CVs for lights (decoder specified), to many CVs eg user
downloaded speed tables multiple CVs for sound etc, but many of the CVs that
are in the decoder will not be change and hence these will be still at their
default values.
Bye
the way a loco run quite ok just using the default values and I am sure many
DCC user are operating this way. They have only given the loca a new address.
So in a lot of cases CVs don’t get changed.
Decoder
Pro a free decoder programming utility that can downloaded from the
Internet is a great way of storing your loco roster complete with CV
values and provides an easy way to set up you specific loco’s features eg.
headlights, speed tables etc. If you use the procedure outlined below, you
don’t have to read any CVs in Decoder Pro either, so these extra
boosters are not necessary. Just look and try before you start saying not
possible. This is because of the great people who are producing Decoder Pro,
load in all the default values for all the decoders that are available, baring
the latest, latest releases and probably some really early ones.
So
if you have a Tsunami or QSI decoder, you can successfully program the decoder
including changing the address and loading a user defined speed table without a
Program Track Booster.
If
you still find you need a P/T booster then just go ahead and purchase one. The
problem is not going to go away, if we continue to use our existing DCC
equipment. DCC manufacturers are always improving their products. Look at the
new NCE Power Cab an entry
level DCC system that does read CVs on the program track of all the sound
locos. A great full feature, complete DCC starter kit.
So
for my mind, and as my mate Erik has done, our Program Tracks are gathering
dust under the layout because reading CV values is for the “birds”
Using Decoder Pro without reading
the CV values
Using
Decoder Pro without reading the CV values of the decoder using a Soundtraxx
Tsunami that requires a Program Track Booster from Soundtraxx. My NCE DCC
system could not read the CV values. I have since modified my NCE Command
Station to enable reading Tsunami and any other sound loco.
My
mate Erik told me this is what he does and he exclusively uses Decoder Pro to
set up his locos and makes all of the adjustments using Decoder Pro. So I have
tried this and written the steps below how to do it.
To
make this work, one has to get out of your head, the necessity of reading CV
values to program a decoder. This is some sort of “security blanket” that just
is an old mother’s tale that some DCC users have got used to, and just won’t
let go off. Since DCC system and decoders that are capable of programming on
the Main (POM) type of programming, the Program track is not necessary and can
be located under the layout to gather dust.
The
only reason that I can see to use a program track is when a decoder has been
corrupted and that it has lost its address. It has not necessarily reset. It
just wont respond to any address. POM requires an address, so if there is no
address, then the decoder will not respond to the command when using POM. This
troublesome decoder may be reset on the Program Track because here there is no
requirement of an address. You will not have to read any CVs just, in most
cases write “2” to CV 30. Check decoder manual about reset procedures.
I
assume all have Decoder Pro installed in their computers and the computer
connected to their DCC system. If not all this can be done from instructions at
http://jmri.sourceforge.net/download/
Anyway
enough of the preamble, lets get into it.
It
looks complicated but if you have used Decoder Pro you will be able to just
whiz through it. This is nothing new and probably a lot of people are doing it
this way anyway, like Erik.
Programming without reading CVs
using Decoder Pro.
Simply
put, you are assigning, by giving your loco ID number (eg 3618), to an already
made up Decoder Pro decoder specifications sheet, complete with default values,
by selecting the relevant decoder from the decoder list that opens up when you
use the Use Programming Track selection.
Now
that the correct pane with all the CVs and default values has been filed and
saved against the Loco ID, address, you open up Decoder Pro using the “Program
on the main track” selection and change only the CVs that need changing to give
the decoder the features you want eg. Volts start, med and max, momentum, light
and sound selections etc. These are easily changed using Decoder Pro’s plain
English prompts for each of the available options against each feature. All the
other CVs are left at their default value for correct decoder operation. All
this, without reading a CV value. Easy hey.
Step by Step Instructions to achieve
this:
Note: I noticed with the QSI,
I had to exit Decoder Pro after I set the decoder to respond to the 2 byte
extended address, to change the volume of my Eureka 620/720 diesel rail motor
and to use Decoder Pro in Operations mode, POM, you have to disable the verbal
acknowledgement, CV 62. Go to the “QSI Misc” panel and disable this
CV.
As
the decoder in the loco comes from the factory with all the default settings or
the loco has had a reset done on it, all the CVs except CVs 17, 18 and 29 will be
the same in Decoder Pro as they are in the Loco. This all done without reading
a CV even in Decoder Pro.
Now
I can change any of features of the decoder using Decoder Pro and their plain
English statements for each decoder feature. No need to work out the CV value.
Just select the option you want. This is especially useful with the Tsunami,
with all of its 200 or so CVs. A lot of these will stay at their default
values.
For
example, under the “Speed Control” pane you can manufacture a speed table or adjust
Volts Start, med and max to modify the way the PIC in the decoder controls the
motor. Under the “Lights” pane you just select the option of how your
headlights operate eg Rule 17 dimmable etc you want . Under the “Sound/Volume
control” pane, you can adjust the sound levels of sound locos. This method of
adjusting sound volume is really great in Decoder Pro especially for QSI
decoder that need two CV values to do this.
All
of this is accomplished without the inconvenience of going back to the Program Track
just staying “on the main track”..
See
how you go, especially you fellas that don’t have a program track booster.