Sprog Dcc Port Devices Driver

Sprog Dcc Port Devices Driver Download
Sprog Dcc Port Devices Driver Windows 7

Under 'Other Devices', update the drivers for SPROG DECODER PROGRAMMER check under 'Ports (COM & LPT)' for assigned com port number When the SPROG is recognized by the computer, the system will attempt to install the appropriate device drivers automatically. The Decoder Programmer in a ready-to-run package! This complete package includes a powerful 12v 1.25A power adapter (see below), USB cable and all software and installation instructions (Java runtime, DecoderPro, USB drivers) on CD-ROM. Power Adapter: SPROG II runs from a regulated power supply, that powers the SPROG II and the.

A typical complaint is that the computer cannot find the interface to your DCC system. Frequently the culprit is a old device lurking in your operating system that is confusing your new device driver. To clean up old device drivers, search the web for, 'removing old device drivers from ', then follow those directions. Support and Downloads for the SPROG family of DCC devices All required software to install and run your SPROG device are provided on the USB Flash drive supplied with the SPROG Complete Package. You do not need to download or search the web for any software or drivers to use your SPROG. On macOS no USB drivers for SPROG need to be installed to use the SPROG IIv3, SPROG IIv4, SPROG3 or SPROG Nano. They comply to USB CDC (Communications Class Device) and use the default drivers included with macOS.

Hey Guys:

We have a DCC - JMRI with SPROG 3 system, with Kato Unitrack layout operated by a Windows 10 PC & cell phone throttles. There are no physical Command Station or throttles.
We are thinking of a stand-alone LocoNet for integrating LocoNet compatible accessories (we already have 4 DS64's & 2 BD4's working on the layout) & would like to know which products available with you would work with our existing system.
I understand that Digitrax PR4 and RR-CirKits LocoBuffer no more provide the 'termination' needed.
Would RR-CirKits SSB Gateway plus a LocoBuffer-USB do the job? How would the RailSync lines provide the DCC information required by the Digitrax detector devices?
Thanks, Shailesh

Hi Shailesh:

Actually, if you are running trains with the SPROG3, the SPROG3 is acting as the command station and booster for the layout.

Both the SSB Gateway and LocoBuffer USB do essentially the same thing: both units allow you to interface a computer USB port to the LocoNet. The SSB Gateway does provide the required LocoNet termination, the LocoBuffer does not. Of course, the USB port must then be controlled by JMRI (or similar) software. The problem is that you must tell the JMRI software what device to use to control the layout. You will only be able to use either the SPROG3 or the LocoNet. Essentially, the USB port controlled by JMRI is the cab bus and either the SPROG3 or the LocoNet interface is the command station. You are only allowed one command station on a layout, and JMRI follows this rule.

You could have two separate computers running two instances of JMRI (I am not sure JMRI will let you run 2 instances on one computer), one controlling the SPROG3 and one controlling the LocoNet. There would be no cross control. The SPPROG3 would control train movement/control and the LocoNet would control accessories connected to LocoNet. This might be useful if you operate using a dispatcher.

The LocoBuffer is expecting to connect to an existing LocoNet, so the Railsync is provided by the command station, not by LocoBuffer. Thus, if you use the LocoBuffer, you will also need a Digitrax command station if you want the Railsync signal (see below). The SSB gateway DOES NOT provide Railsync signals. It simply provides DC power on the Railsync lines. In a Digitrax system, the command station provides the Railsync signal which is then rectified by LocoNet clients to provide operating power. The SSB Gateway simply provides DC power on the Railsync lines for client power, but there are no data provided.

If you want to use LocoNet to provide control/feedback of accessories while controlling the layout with SPROG3, you probably want to use the SSB Gateway as the LocoNet controller. I think you will need a separate instance (as mentioned above) of JMRI to control this LocoNet, and its commands and data will be separate from the SPROG3 control commands and data. Basically two independent control systems (which could be a dispatcher for one and engineer for the other).

If you want to control both LocoNet and train operation through the same device (i.e. all data are available to all units on the layout), then you will need to replace the SPROG3 with a Digitrax command station (the SPROG3 will still function nicely as a programming interface - its primary design function). In this case, you would use the LocoBuffer to interface the command station LocoNet to JMRI via the LocoBuffer USB port to your computer. My personal feeling is that this is the better choice of the two. Your opinion may vary!

Hope this helps you move forward.

Supported Hardware

Devices, command stations, networks, and protocols:

WiFi Throttles

Applications

By the community of JMRI.org:

Tools

JMRI tools for working with your layout:

Common Tools:
Blocks:
Routing and Control:
Other:

Layout Automation

Use JMRI to automate parts of your layout and operations:

JMRI Help:
Contents/ Index
Glossary/ FAQ

Supported Hardware

Computer Interfaces

JMRI supports the SPROG both as a Decoder Programmer, and as a mini-Command Station. For more information on these capabilities, see the SPROG manual on the SPROG web site.

Note that there are several different versions of the SPROG hardware, and even more versions of the SPROG software.
The following SPROG models operate with the current version of JMRI:

SPROG II
SPROG II USB
SPROG 3 (USB)
SPROG Nano (only as Command Station, using an external Booster)
Pi SPROG One
Pi SPROG Nano

Connecting

Wiring

Original SPROGs were connected via a 9-pin serial cable.
Current SPROGs are available as USB only.
Connect your SPROG using the appropriate cable and power it up.

Settings

USB Drivers
- On Windows 10 USB-connected SPROGs will work using the standard USB drivers installed in the OS. When you plug in the SPROG, it will show up under Hardware like this:
  If you previously installed some special USB driver, uninstall it on Windows 10 before proceeding.
- On Windows 7 and earlier users may need to have a driver installed. For more information on that, see the SPROG manual on the SPROG web site.
  Windows 7 users may also be interested in this video.
- On macOS no USB drivers for SPROG need to be installed to use the SPROG IIv3, SPROG IIv4, SPROG3 or SPROG Nano. They comply to USB CDC (Communications Class Device) and use the default drivers included with macOS.
- For Linux, there are many variations of Linux system installations, and variations in installing the USB support may be encountered, but in general USB CDC devices are supported directly.
Make sure you have the latest version of JMRI. Start one of the JMRI applications.
Go to the Connections tab of the JMRI Preferences pane. This opens automatically the first time a program is run, or you can select it from the 'Edit' menu.
Select 'SPROG DCC' from the list as the System Manufacturer.
Next, select one of the available System Connection options;
SPROG can either function as a stand-alone Decoder Programmer interface, or it can be set to act as a mini-Command Station for running trains.
Once you select and save your choice, JMRI configures the necessary options in the SPROG.
- For Programmer operation, select either 'SPROG' or 'Pi-SPROG One Programmer' as the System Connection, as illustrated:
  In this mode, the Status Bar along the bottom of the DecoderPro Roster pane will show the inactive function in red, like this:
  If both of the left hand fields display in red type, you may have selected the wrong SPROG System Connection.
- For Command Station operation, select one of the '... Command Station' choices.
- To use JMRI without a physical SPROG connected, select 'SPROG Simulator'. The Simulator will mimic basic operation as either a Programmer (default) or a Command Station. You can set the mode under Additional Connection Settings.
Next, under Settings select the appropriate serial port, except for the Simulator. Note that the USB SPROG drivers will appear in the list as a serial port, like cu.usbmodem1411.
Accept the suggested Connection Prefix and Name, or replace it with a more fitting one. Make sure it is unique.
Click 'Save'. You'll be asked if it's OK for the program to restart, click 'Restart' or 'Later'.
After restart of JMRI you should be up and running with the new connection.

Configuring SPROG

SPROG uses a 'Mode Word' to set a number of optional operating modes.

In all recent SPROGs, the default value for the Mode Word is correct for both programmer and command station modes. For older SPROGs you may wish check or modify the Mode Word as follows:

Open the Command Monitor and the Send Command tools from the SPROG menu. Send an 'M' command using the Send Command pane.
You should see a reply in the Command Monitor window, something like:

The h prefix indicates a hexadecimal value. If the value you see is different, then it should be changed by sending the command 'M h800'. Follow this with the command 'W' to save the change in SPROG's EEPROM memory so that it is effective each time you power up the SPROG. Otherwise, the new value will be lost when you power off the SPROG.
Please do not be tempted to experiment with other Mode Word values as this could result in erratic behavior of your SPROG.

Identifying your SPROG Firmware Version

Open the SPROG Console tool pane from the SPROG menu and send a '?' command.
You should see a reply appear in the Command History, something like:

SPROG II USB Ver 2.3 P>

JMRI SPROG Tools

The following tools are available from the SPROG menu when this connection is active: