Sprog Dcc Port Devices Driver
Supported Hardware
- WiFi Throttles
Applications
Tools
Connect your Lenz LI100, LI100F or LI101F to your DCC Command station via their XpressNet connections. Then connect the LI100/LI100F/LI101F to the computer's serial port using a 9-pin serial cable. Then go to the preferences panel of a JMRI-based program.
- To interface to the DCC decoders on the trains we're using the Sprog 3 Command Station. Sprog 3 The Sprog 3 is a simple USB based DCC controller that allows for both programming and running of devices on a DCC rail network.
- The Pi Sprog is a complete system, but you need a smartphone running Engine Driver (android) or Withrottle (IOS) to use as a throttle. Or the new ESU throttle, which is basically an Android device with a big knob added. Unless you will run from on-screen throttles in JMRI.
- Install SPROG II USB drivers Use the supplied USB cable to connect SPROG II to the host computer. The power LED should be lit. The first time you do this you will see the “Found new Hardware Wizard”. Follow the steps below to install the SPROG II drivers and then the USB Serial port drivers.
- Common Tools:
- Blocks:
- Routing and Control:
- Other:
Layout Automation
JMRI Help:
Contents/ Index
Glossary/ FAQ
JMRI supports a wide range of DCC 'command station'-style products from various model railroad automation vendors. We also support non-DCC layout accessories and devices that connect via a variety of networks and protocols. This page lists hardware and networks that JMRI is known to work with, and provides links to information on how to configure JMRI to work with each particular type.
- Hardware Supported:
- Additional Topics:
If there is a way to make a computer communicate with a given piece of model railroad equipment, it is possible to connect it to JMRI. If you don't see your particular system here, please ask about it on the JMRI users.
For developers adding new hardware integration: see here for information about Creating Help and Web Pages for New Hardware.
Category/Alphabetic Index
This index cross-references hardware and products by the categories under which they appear on this page. Click on a category to go to that category on this page. Click on a hardware item to go to the JMRI Help page for that product or family. The sidebar provides an alphabetic list.
Networks and Protocols:
- WiFi Throttles
Programmers:
Multi-purpose Hardware
Configure: See the JMRI arduino help page for information on configuring for accessory control. See also DCC++ for use as a DCC command station.
Configure: CTI Electronics boards via Acela adapter.
General information on connecting JMRI to a Digitrax LocoNet
Configure: Connections to a LocoNet via
- The older LocoBuffer-II, LocoBuffer and MS100 interfaces
Configure: LocoNet Simulator for use when disconnected from a layout.
Configure: Remote connection to a LocoNet via JMRI LocoNet Server.
Configure: Remote connection to a LocoNet via LbServer. More information on connecting multiple computers to a single LocoNet
Configure: Programming and testing decoders without a command station via a Digitrax PR2 interface, PR3 interface, or PR4 interface.
Configure: Directly connecting to an Intellibox.
Configure: Connecting to a Standalone LocoNet.
Configure: Connecting to a IPOCSMR system.
Configure: Lenz LI100, LI101F, LIUSB or GenLi XPressNet interfaces, ZTC Controls ZTC640 interface, or an XPA and Hayes compatible modem.
Please check the notes above for system specific restrictions on what JMRI can do.
General information on connecting JMRI to a SPROG programmer/command station
General information on connecting JMRI to a SPROG Generation 5 programmer/command station
Command Stations
Configure: Atlas Commander via Lenz LI100, LI101F, LIUSB or GenLi XPressNet interfaces, ZTC Controls ZTC640 interface, or an XPA and Hayes compatible modem
Note: you can not program decoders with this configuration.
Configure: EasyDCC command station via Serial or Terminal Server
Configure: DCC++ Open Source Arduino Command Station.
Configure: DR5000
General information on connecting JMRI to a Digitrax LocoNet
Configure: Connections to a LocoNet via
- The older LocoBuffer-II, LocoBuffer and MS100 interfaces
Configure: LocoNet Simulator for use when disconnected from a layout.
Configure: Remote connection to a LocoNet via JMRI LocoNet Server.
Configure: Remote connection to a LocoNet via LbServer. More information on connecting multiple computers to a single LocoNet
Configure: Programming and testing decoders without a command station via a Digitrax PR2 interface, PR3 interface, or PR4 interface.
Configure: Directly connecting to an Intellibox.
Configure: Connecting to a Standalone LocoNet.
Configure connection to ECoS command station.
Configure: Twin Centre communications (LocoNet)
Configure: Fleischmann Z21 and z21 via Ethernet.
Configure: Hornby Elite via built in USB Port
Configure: Hornby Elite or Hornby Select via Lenz LI100, LI101F, LIUSB or GenLi XPressNet interfaces, ZTC Controls ZTC640 interface, or an XPA and Hayes compatible modem.
Please check the notes above for system specific restrictions on what JMRI can do.
Connection: Serial cable
Configure: TMCC Command Base
Configure connection to CS2 Command Station 2.
CS Command Station - see ESU ECoSMRC decoders can be configured via DecoderPro using any supported DCC system.
For more information on connecting JMRI to the MRC command station, see the MRC system page.
Configure connection to a Powerhouse Pro via serial link or Terminal Server.
Configure connection to a PowerCab via NCE USB adapter.
Configure: Roco LocoMaus 2 (Roco Part number 10760), Roco MultiMaus (Roco Part number 10810), or Roco multiZENTRAL-Pro (Roco Part number 10830) via Lenz LI100, LI101F, LIUSB or GenLi XPressNet interfaces, ZTC Controls ZTC640 interface, or an XPA and Hayes compatible modem.
Please check the notes above for system specific restrictions on what JMRI can do.
Configure: Roco Z21 and z21 via Ethernet.
Configure: SPROG as either a stand-alone DCC programmer or DCC command station
Configure: SPROG Generation 5 as a DCC command station and programmer
Configure connection to TAMS Master Control command station.
Configure: Uhlenbrock Intellibox-I or -II via LocoNet interface
Configure: Uhlenbrock Intellibox-I via built-in serial port
Configure: Uhlenbrock Intellibox-II via built-in USB connection
Configure: Viessmann Commander via Lenz LI100, LI101F, LIUSB or GenLi XPressNet interfaces, ZTC Controls ZTC640 interface, or an XPA and Hayes compatible modem.
Please check the notes above for system specific restrictions on what JMRI can do.
Connection: Wangrow Serial Port
Configure: System One
Configure: ZIMO MX-1
Configure: ZTC Controls ZTC511, ZTC Controls ZTC521 via Lenz LI100, LI101F, LIUSB or GenLi XPressNet interfaces, ZTC Controls ZTC640 interface, or an XPA and Hayes compatible modem (requires XPressNet V3.0 software).
Please check the notes above for system specific restrictions on what JMRI can and cannot do.
Networks and Protocols
Configure: Bruce Chubb's C/MRI control system for a connection via direct serial, USB-serial adapter, or network connection.
General information on connecting to a Digi XBee network
Configure: Used for IPOCSMR.
General information on connecting JMRI to a Digitrax LocoNet
Configure: Connections to a LocoNet via
- The older LocoBuffer-II, LocoBuffer and MS100 interfaces
Configure: LocoNet Simulator for use when disconnected from a layout.
Configure: Remote connection to a LocoNet via JMRI LocoNet Server.
Configure: Remote connection to a LocoNet via LbServer. More information on connecting multiple computers to a single LocoNet
Configure: Programming and testing decoders without a command station via a Digitrax PR2 interface, PR3 interface, or PR4 interface.
Configure: Directly connecting to an Intellibox.
Configure: Connecting to a Standalone LocoNet.
Configure: CBUS networks
Configure: Modbus networks
Configure: MQTT networks
Configure connection to an RPS (Railroad Position System) position detection system.
Configure: OpenLCB networks
Configure: Connection to SRCP server
Sprog Dcc Port Devices Driver Updater
Connection: X10, Insteon power-line controllers
Configure: CM11, 2412S and compatible controllers.
Programmers
General information on connecting JMRI to a Digitrax LocoNet
Configure: Programming and testing decoders without a command station via a Digitrax PR2 interface, PR3 interface, or PR4 interface.
Connection: Quantum Programmer
Configure: USB connection
QSI decoders can be programmed with DecoderPro through any DCC system. JMRI can't load sounds into QSI decoders.
Configure: SPROG as either a stand-alone DCC programmer or DCC command station
Configure: SPROG as DCC command station and programmer
Sprog Dcc Port Devices Driver Download
Accessories and Other Devices
Configure: See the JMRI arduino help page for information on configuring for accessory control. See also DCC++ for use as a DCC command station.
Configure: Bachrus MTS-DCC Model Train Speedometer
Configure: DCC4PC detection boards Infrared receiver driver download for windows 10.
Configure: Hare, Wabbit, Block Watcher or PSX family products.
Maple Systems touch panel
Configure: connection via serial link
Configure connection to Oak Tree's Railroad Control Interface (RCI), including the IO-24, IO-48 and O-48 interface cards and HH-2 handheld throttle.
(Note: RCI is to be replaced by Layout Control System (LCS))
Configure: RailDriver cab simulator
Configure: Grapevine nodes
Configure: TracTronics SECSI connections
Hardware Manufacturer Index
This section cross-references hardware manufacturers and products that are known to work with JMRI. See above for links to specific help pages.
[TBA]
Connecting to Command Stations
- Macintosh
- PC
- Terminal Server
- Raspberry Pi
General hardware info
If your layout uses some feedback mechanism to sense the actual positions of Turnouts, for example a microswitch connected to the throw bars or a decoder that returns a confirmation message, JMRI can use that to keep track of what's actually happening on the layout. We call this 'Feedback', and how to configure and use it is described on the Turnout Feedback page.
A way to use a PDA to access JMRI.
CBUS® is a registered trade mark of Dr Michael Bolton
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.