The SPROG family of DCC devices
Problem?
If you have a problem in using your SPROG II then please check the list
of Frequently Asked Questions to see if you can resolve the problem.
If you are still experiencing difficulties then please e-mail us using the
Contact link on the left. Note the computer (Windows, Mac, Linux and versions; loco and decoder types).
If you are using DecoderPro then it is usually helpful to include a log of what you are trying to do.
Open a DecoderPro command monitor (from the SPROG menu), log to a file and then
try repeating the operation you were attempting; send the log file to
us.
If you are a new user then please ensure you have read the Getting Started Guide on the Download page.
Frequently Asked Questions
General Questions
Where can I buy SPROG II?
What are the differences between SPROG II and other DCC interface devices?
What software do I need to use SPROG II?
How do I know what firmware version my SPROG II has?
Can SPROG II be used as a computer controlled command station/booster?
Where can I buy SPROG DCC devices?
SPROG DCC is available direct from SPROG USA,
and from the UK SPROG shop.
SPROG DCC products are also available from selected retailers in the UK, Europe, USA, Canada and Australia.
Buy online.
What are the differences between a SPROG and other DCC interface devices?
SPROG II - and SPROG3 - are a stand-alone DCC decoder programmer and DCC controller.
The SPROG II or SPROG3 is not an interface to a DCC system, but does the things a typical Command Station does,
in an easy to use, computer-controlled manner.
There are other DCC devices, such as Locobuffer, that are designed to link the computer to an existing DCC system,
and the DCC system then provides the response to computer-sourced commands.
For stand-alone programming, SPROG II and now SPROG3 provide a comprehensive programming solution that can be used in the layout room,
or anywhere else, for NMRA-compliant decoders of any scale, including sound.
Also, for small layouts needing under 1A total current, SPROG II can be used to control the layout directly, acting as the DCC Command Station,
without needing any additional DCC system hardware. SPROG3 increases that current capability to 2.5A, more than enough for many layouts, and te SBOOST booster allows the addition of further power sections, up to 2.5A each.
What software do I need to use SPROG II?
We recommend and supply DecoderPro.
There are also other railroad control programs available that now provide support for SPROG devices.
It is possible, but tedious, to use SPROG II with a terminal emulator.
DecoderPro requires that you have Java installed on your system from
Oracle; also included on the installation CD.
Look at the online install pages to run an immediate install of the current production software and drivers.
How do I know what firmware version my SPROG II has?
In DecoderPro 2.2 and later, select the SPROG menu, and then Console;
You should see the firmware version reported in the command monitor, e.g., "SPROG II Ver 2.7".
If you are using an older version of DecoderPro, please upgrade (see above).
Can SPROG II be used as a computer controlled command station/booster?
Yes, for smaller layouts, within the 1 Amp power capacity of SPROG II and the power supply, 1.25 Amp as supplied.
SPROG II's current firmware gives full computer controlled command station functionality,
either for small layouts or larger layouts when used with an external booster.
The new SPROG3 offers all the same SPROG II coapbilities, with a 2.5A maximum current capacity.
Additionally, the new SBOOST booster can be used with SPROG II, or SPROG3, to add another 2.5A capability.
Connecting SPROG II or SPROG3 To Your Computer
What cable do I need to connect to SPROG II or SPROG3?
SPROG II and SPROG3 are supplied with the appropriate USB cable.
Should your cable have been lost or damaged, you need a USB A to USB B cable.
This is the same cable as used for most USB printers, and can be purchased from any electronics store, or from us.
My SPROG II does not respond to the computer. What do I do?
This is probably the most common question.
SPROG waits for the computer to tell it what to do.
Assuming all the installation process works well, plugging in the SPROG to the USB port will enable access.
The Red light on SPROG will be steady, showing you have power to SPROG, but not yet to the track.
So, after all that, you would really like to know: -
which PORT has SPROG connected to it.
USB SPROGs use Virtual COMport drivers. These present the SPROG device as a "Port" on the computer.
On Windows machines, right click on
"My Computer" ("Computer" in the Start Menu for Windows 7) and Select "Manage", then select Device Manager. Click + next to
"Ports (COM & LPT)" and note the COM port number assigned to SPROG.
Check to see that the Port has no warning showing, as this will indicate the Driver is not correctly installed.
On a Mac, from System Preferences, select Network and note the "usbserial-feedcode" entry is present.
Using DecoderPro, ensure this port name is selected in the DecoderPro preferences.
More DecoderPro FAQs are below.
If you are still not connecting, it can be possible to use the default Windows
HyperTerminal or similar serial communication program
In Windows prior to Windows7, select Start Menu>All Programs>Accessories>Communications>HyperTerminal.
Connect to COMn (The one indicated in Device Manager) (if asked, 9600 baud, other settings should be at defaults
of 8 bit, No Parity, one stop, hardware flow control)
press Enter, and you should get "P>"
press ? then Enter and you should see "SPROG II Ver 2.7" or similar.
If not, then take a look in the Device Manager just in case the COM port
got re-assigned. On some computers, plugging the same SPROG into a different
physical socket comes up with a different COM assignment.
Using DecoderPro With SPROG II
How do I use DecoderPro with SPROG II?What can I do if my decoder is not supported by DecoderPro?
Does SPROG II support the DecoderPro Throttle?
What does "Error timeout talking to Command Station" mean?
What does "Stopping due to Error: no locomotive detected" mean?
How do I use DecoderPro with SPROG II?
To configure DecoderPro to work with your SPROG you must start DecoderPro
and select "SPROG DCC", and "SPROG" from the File>Preferences menu. Be sure to select "SPROG" mode for programming.
"SPROG Command Station" mode is also offered, and can be used to control a layout.
See the SPROG User Guide (PDF 1.49Mbytes), 54 pages. for more details.
JMRI DecoderPro will look for a port to connect to. It will find from the system a
list of actual and apparent ports, and will show that list in Preferences.
You select the one that has SPROG connected to it, and save the Preferences; you will exit DecoderPro
when prompted to save the preferences.
Start DecoderPro again and you will see the main menu screen.
Once Decoder Pro is running and the main menu screen appears, select Use Programming Track, and in the
Service Mode Programmer window that appears, click "Read Type from Decoder".
Now the Red power light on SPROG will flash, indicating Track Power, and will try to read the decoder on the track.
"Error talking to Command Station" messages mean the USB cable does
not connect, or your serial or USB port is still not set right.
We strongly recommend you upgrade to the latest production version of DecoderPro; look at the online install pages to run an immediate install.
What does "Error timeout talking to Command Station" mean?
"Error talking to Command Station (306)" messages mean the computer and the SPROG are not communicating.
This could be that the USB cable does not connect, or your USB port is still not set right.
This is often caused by a mismatch between the COM port selected in DecoderPro preferences
(edit menu) and the COM port to which the SPROG is actually connected.
USB SPROGs use Virtual COMport drivers.
A first check to make is to turn off the SPROG (disconnect power by pulling out the green plug,
and disconnect the USB) and then reconnect.
Then check the COM port number.
On Windows machines, right click on
"My Computer" then click Properties -> Hardware -> Device Manager.
On Windows 7, from the Start menu select Control Panel, then System, then Device Manager.
Click + next to
"Ports (COM & LPT)" and note the COM port number assigned to SPROG. Ensure this is selected
in the DecoderPro preferences.
If this is showing the right PORT, but not getting DecoderPro to run,
then we can look at the Config file and go from there.
On a MAC, run the application System Preferences and select Network (Go to > Applications > System Preferences > Network). For SPROG II you should see a port named tty.usbserial-xxxxxxxx (the xxxxxx often reads "feedcode"). For SPROG IIv3 or SPROG3, you will not always see the device in the Network view any longer; this is not a problem, as we will find the device through the DecoderPro Preferences anyway, where it will appear as a "usbmodem" device identifier.
Config File
DecoderPro stores the Preference settings in a file named DecoderProConfig2.xml, located
on Windows in C:\Documents and Settings\your-name-here\JMRI (unless you have deliberately moved it).
On a MAC it is at your-name-here -> Library -> Preferences ->JMRI.
This file sometimes gets confused, and it is totally safe to remove it; it will be recreated next time you open DecoderPro and you select preferences again.
If you are not connecting DecoderPro to the SPROG successfully, close DecoderPro, delete the DecoderProConfig2.xml file, and then start DecoderPro again.
You should now be prompted to select Preferences again. If not, the file you deleted is not the one DecoderPro is trying to use; search for any other files with this name and delete all of them!
Similarly named files exist for PanelPro, or other JMRI tools, if you have used them.
What does "Stopping due to Error: no locomotive detected" mean?
The next most common message is "Stopping due to Error: no locomotive
detected (301)" which is most often due to dirty track, or some other reason why the
decoder in the loco does not respond to the signals from the track.
This message means that SPROG is working, but is not seeing the decoder in the loco for some reason.
If you see this message, look at the SPROG device itself.
The red Power light on the SPROG will be steadily lit while the SPROG is on, but inactive,
and the Power light will wink on and of about one per second when the Track Power is turned on.
Try the operation, such as "Read Type From Decoder" that you were using once more, and observe the Power light.
If it is flashing, but the loco is not responding, then check wiring, etc.
Note: SPROG detects the presence of the decoder by measuring track current (as do other programmers also),
and looking for specific current pulses as the decoder reacts to instructions.
If you have a decoder which does not have a motor connected (e.g. a "Function only" decoder),
those current pulses may not exist, and so SPROG will not see the response.
Some other decoders also do not return good motor current pulses,
and so do not seem to be detected by the programming sequence.
In these cases, it is not unusual for an operation to be executed successfully, such as writing to the decoder a new value for a CV,
but the SPROG cannot tell, and so DecoderPro flags the problem.
Try seeing if the effect you were programming has been successful, by running the loco and seeing if it responds as desired.
Does SPROG II support the DecoderPro throttle?
Yes (note: you require SPROG II version 1.3 or later firmware for the function buttons to operate correctly).
You turn the track power on and off using the Power Control under the tools menu,
or by clicking the colored light in the top of the Throttle window.
Any programming operation will always leave the track power turned off, but the Throttle panel can sometimes indicate incorrectly.
Look at the power light on the SPROG to be sure. This light is flashing when the track power is on.
There had been a known issue with the JMRI throttle function controls and SPROG, with earlier versions. All recent SPROG II deliveries have corrected this, but if you see an issue, please do the following:
Open the DecoderPro SPROG Console window.
Send a "M" command - you should see a reply something like =h80C. (If it is h800, no further acton is required).
Send the command "M h800"
Send the command "W"
Function control should now work, explanation follows...
Back in the early days of SPROG there was a mismatch between the JMRI
code for sending function control packets and what SPROG expects. The
JMRI code sends the packet including the error check byte. SPROG then
tries to add the error check byte resulting in the packet going to
the track having one extra byte. Some decoders happily ignore the
extra byte and just work, some decoders check the byte count and
ignore the whole packet, some accept the packet and do strange
things. Hence the confusion with some people saying it works, some
seeing problems, it just depends which decoders you are using.
The command sequence given above disables the error check byte in
SPROG and then writes the new mode to EEPROM so it will persist next
time you turn on your SPROG.
Using SPROG II with sound decoders
- Can I use SPROG II to program new sounds into my sound decoder?
- Will SPROG II work with Broadway Ltd sound equipped locos?
- Will SPROG II work with BLI Blueline decoders?
- Will SPROG II work with QSI decoders?
- Will SPROG II work with MRC decoders?
- What about other sound decoders?
Can I use SPROG II to program new sounds into my sound decoder?
No. There is (as yet) no standard way of programming new sounds into sound decoders. There are some vendors offering the ability to add or change sounds, and if you want to replace the sounds supplied, you must use the decoder manufacturers proprietary sound programming device.SPROG II can set all the sound options in the sound decoders by setting CVs, but not replace the sounds themselves.
Will SPROG II work with Broadway Ltd sound equipped locos?
The short answer is yes, but the full answer can be a little longer. These locos are notorious for the inrush current when they are powered up. SPROG II firmware has been updated to cope with this, so long as the power supply is of sufficient capacity. Our standard 1.25A supply has been successfully used on most locomotives. If you see problems, you may see improvement if you include a low value current limit resistor fitted in one of the programming track leads. Also see below for more news in the new firmware versions.Will SPROG II work with BLI Blueline decoders?
Firmware version 2.2 and later now supports Blueline decoders by enabling a special mode. Select the menu item SPROG>Console, and set the BlueLine checkbox. Click Save and close the Console window, and program your Blueline decoder!Clear the checkbox for other decoders, as Blueline mode may be slower on other types.
Will SPROG II work with QSI decoders?
Firmware 2.5 now fully supports CV programming and readback for both v6 and v7 QSI decoders, including steam. There is one occasional problem, due to a characteristic of the decoder; CV1 in v6 decoders does not always read.Will SPROG II work with MRC decoders?
Yes, SPROG II supports CV programming and readback for MRC decoders. Some MRC decoders seem to indicate that programming does not work, showing "no loco detected (301)" errors; check this by reading back the values - it usually did work correctly, but the acknowledgement was not clear, and so not recognized by the SPROG.What about other sound decoders?
No problems reported! We have tested many makes and have been successful in programming all necessary CV values with SPROG II. If you are having trouble using your SPROG II with a sound decoder, contact us with the SPROG firmware version (SPROG>Console menu item, and read the large window for "SPROG II USB Ver x.x" text), and DecoderPro version (on the opening screen - current version is 2.14 or later), and we will help you to solve the problems.So how do I get the latest firmware?
The current firmware is version 2.7, or 1.8 if your SPROG II is "series 1" and has 1.x versions.If your SPROG is doing all that you need without issues, upgrading is not needed, but if you have problems and need support for some of the latest sound decoders, or if you use SPROG as a Command Station to run your layout, the newest versions may have some improvements for you.
Contact us directly to arrange an upgrade.
Specific Decoder Problems
Which decoders has SPROG II been tested with?What can I do if my decoder is not supported by DecoderPro?
Problems with ZTC decoders
Problems with Digitrax decoders in direct mode
Will SPROG II work with Broadway Ltd sound equipped locos?
Which decoders has SPROG II been tested with?
We regularly test SPROG II with decoders from as many different families as possible, to ensure support for the maximum
range of types and vendors. We will adjust the programming if we find new capabilities or differences that need to be supported.
Please consult the compatibility list for a partial selection.
What can I do if my decoder is not supported by DecoderPro?
More decoders are being added all the time. If you are familiar with
XML (or wish to learn) then you could write your own definition file.
More details on this procedure can be found on the JMRI webpages.
Another tack is to ask on JMRIUSERS
if anyone has already written the appropriate definition file, or Contact us; we create definitions too!
To use new or updated decoder files:
Updated decoder files can be found in the Yahoo Groups files area, or in the a The installation process was simplified in JMRI 2.3.6, where "Import Decoder File" and "Import Decoder URL" menu items were added to the Debug menu.
The definition is stored in your preferences directory, instead of the JMRI distribution directory,
so that installing a new version of JMRI doesn't delete it.
Note, however, that if a newer version of JMRI comes along with a copy of this decoder definition installed,
the program will give priority to the specific version that you imported.
The manual process is as follows:
It is an xml file, and so will not read easily if you double-click it. To read
it (which I recommend in general to see the author's comments), open WordPad or a similar plain text editor, and
then find and open this file.
Having found the right file, and read the comments, it has to go into the right
place (C:\Program Files\JMRI\xml\decoders is the JMRI distribution directory, unless you moved it) and then open DecoderPro,
pick from the menu on the first screen Debug>Recreate Decoder Index
then quit DecoderPro, restart and check the decoder list for the new type to be present.
ZTC decoders should now program correctly. Other makes of decoder will probably still
respond but if you have problems, you can turn off ZTC compatibility mode using "Z 0".
Unfortunately, it has been found that, even with this fix, ZTC202 decoders do
not work with SPROG II.
Problems with Digitrax decoders in direct mode
Download the file to your JMRI installation; default Windows installation will be at C:\Program Files\JMRI\xml\decoders.
On a MAC OS X system the JMRI installations is under Applications.
Download by right-click (Control-Click on Mac) on the file and selecting "Save As"; you do NOT want to read it in Explorer!
Open a send command window from the SPROG menu
Send the command "Z 1" (without the quotes)
Send the command "W"
DecoderPro originally defaulted to paged mode programming when using SPROG. When this
was changed to direct mode, a bug was uncovered in the early SPROG II firmware which prevented
Digitrax decoders being programmed in direct mode. To work around this bug, select paged
mode programming in DecoderPro when programming digitrax decoders. This is fixed in
version 1.4 firmware and later; contact us for an upgrade.
Power Supply
What sort of power supply do I need for SPROG II?Can I use my old DC throttle/transformer/controller as a power supply for SPROG II?
Can I use a booster with SPROG II?
What sort of power supply do I need for SPROG II?
A regulated power supply is required giving 12 - 15V DC for SPROG II, or 12-20V for SPROG3. No NMRA
conforming decoder should require more than 250mA during programming.
Some decoders will draw more than this momentarily during power up and
the ACK pulse generated by pulsing the motor could be more than this,
depending upon the motor. We recommend a supply of at least 1.25A, as available from this site.
We supply as standard a 1.25A supply that supports even those higher power (especially sound) systems that take a higher inrush current.
Can I use my old DC throttle/transformer/controller as a power supply for SPROG II?
Probably not; in fact, please don't!. Many old DC powerpacks/throttles/transformers/controllers
do not provide smooth DC and are unsuitable for use as a power supply
for SPROG II, SPROG3 or SBOOST. You may find that operation is erratic using such a unit
as a power supply for SPROG devices.
Can I use a booster with SPROG II?
Yes, SPROG II can be used with track power boosters, but does not need or benefit from programming boosters.
SPROG II can power up to the available current of the power supply that you are using,
or a maximum of 1 amp, for programming or for running a small layout.
For programming, the NMRA specification says that any comforming locomotive will need no more than 250mA to program,
and SPROG II is fully able to support this.
Some of the sound-equipped locomotives draw higher currents starting up,
and so have had issues when programming on conventional DCC programming tracks, but again,
we have developed SPROG II to support these needs.
If you do want to run your layour from the SPROG II and your computer,
then a booster that increases available track current can be used with SPROG II very effectively.
See the details of our new SBOOST 2.5A Booster for more information.