Summary: While a computer is not necessary for implementing or using Digital Command Control, there are a number of software packages available which will increase your enjoyment by automating tasks or simplifying decoder programming. With the increasing complexity of multi-function decoders equipped with sound, a tool such as the computer enhances the process by taking the drudgery out of programming multiple CVs while reducing the possibility of mistakes. Other applications include automation, dispatching, control of turnouts, or enhancing operation sessions by planning and scheduling train movements
There are also packages which combine multiple aspects, such as dispatching, scheduling and creating manifest lists for the operators in addition to providing direct control of routes and signals.Please see the Software page for other software relating to trains at a more general level.
The JMRI software is a suite of programs and is a single download. Don't worry about trying to get each part separately - they're all bundled together. Also, you do not need to use each part of the suite to get a specific task done - that is you don't need to setup the automation part if all you want is to quickly program your decoders.
If you need a quick, simple to use, cross-platform software for programming decoders (multifunction and accessory), then this is the choice for you. Many people that have expensive track control software use JMRI for its ability to quickly and simply program a wide range of decoders. The JMRI suite of programs runs on Mac Classic and OS X, Linux, and Windows machines, all under Java. All major manufacturers of DCC equipment (Supported Hardware webpage), systems and decoders, are supported. A very active JMRI users' group is available for user support on Yahoo Groups.
The JMRI suite now includes an Operations function. This requires the input of your motive power, rolling stock, and your "locations". Once all that is done, you can create trains starting and finishing at various locations on your layout, and JMRI will then create the manifest and switch lists. The software can also assign motive power, or the dispatcher can decide what power goes on what trains.
CTI Electronics This software will control DCC trains and accessories such as turnouts, from a screen-based CTC panel and on-screen throttles. Although DCC trains can be controlled "out of the box", most other functions require some programming via the bult-in TCL programming language (TCL = Train Control Language). TCL is similar to BASIC and easy to learn, aided by step-by-step lessons in the supplied manual and on-line "help". CTI does not currently support monitoring of DCC-based input devices such as occupancy detectors, but separate hardware modules are available for sensor inputs, and also for controlling turnouts or signals. Thus, it is possible to create a hybrid system with DCC control of trains and CTI hardware for track occupancy and turnout position sensors, with either DCC or CTI hardware for turnout and signal controls. Here is an example of a layout with CTI-controlled signals and turnouts.
CTI also makes a device called ACELA, for those wishing to write their own model railroad control software. The Acela Network Bridge hardware module is about the size of a credit card. The Acela manages a real-time control and sensing network. You create things like control panel GUI's and signaling logic using software such as JMRI. The Acela module handles the rest.
Train Tools Software has been producing professional model railroad software since 1991. DCC software for the model railroad industry. All software is scale independent, internet enabled and supports all popular command stations.
Software is provided on the DCC under the form of loadable environment modules. The use of a module system means that most software is not accessible by default and has to be loaded using the module command. This mechanism allows us to provide multiple versions of the same software concurrently, and gives users the possibility to easily switch between software versions. The modules system helps setting up the user's shell environment to give access to applications, and make running and compiling software easier.
When you first login, you'll be presented with a default, bare bones environment with minimal software available. The module system is used to manage the user environment and to activate software packages on demand. In order to use software installed, you must first load the corresponding software module.
When you load a module, the system will set or modify your user environment variables to enable access to the software package provided by that module. For instance, the $PATH environment variable might be updated so that appropriate executables for that package can be used.
Lab groups are welcome to install software in their hpc/group/ space if sudo access is not required. This can be helpful for lab specific software or for when a group wants to strongly control software versions and packages.
We are looking for a strong product owner with proven technology experience to lead a team in delivering world class software. We are looking for a detail-oriented individual who will work with product managers and engineering scrum teams. The ideal candidate will have previous experience of building electronic health record software.
VFX and Animation studios typically integrate off the shelf digital content creation (DCC) tools, such as Maya or Houdini, with in-house software and other 3rd party packages to create a connected end-to-end pipeline for their artists. Since the late 90's an increasing number of studios have started running a flavour of Linux as their primary OS for artist workstations for reasons of reliability, flexibility, cost, performance and as a natural progression from SGI's IRIX.
Due to the flexibility of the Linux platform, there are a number of different distributions on varying release schedules and this combines with software providers all having their own schedules to create a situation where DCC software packages are often released with different and incompatible dependencies. This complexity results in VFX studios requiring specialist expertise to integrate a pipeline around these dependencies or often even deciding against supporting Linux altogether.
In previous years Linux platform requirements for DCC packages was mostly led by Autodesk's Maya and other vendors typically followed its lead. In the run up to SIGGRAPH 2013, the Visual Effects Society invited a group of major software vendors to create a working group to better align Linux support between them.
This initiative resulted in the VFX Reference Platform, a collection of major library and tool versions that are updated annually with the objective of being a common platform for all VFX and animation studios and software providers to target. Initially this effort was focused on Linux only but in 2020 support for MacOS and Windows was also introduced. The VFX Reference Platform is driven by a small number of software vendors with a longer term plan to include more software providers earlier in the annual review cycle.
The VFX Reference Platform Working Group is made up of interested parties initially invited by the VES Technology Committee and currently has several members, two representatives from the VES and two each from three major software vendors. If a vendor or other organization would like to join the Working Group, please send a request with details.
All required software to install and run your SPROG device are provided on our web site in the online install pages.You do not need to download or search the web for any software or drivers to use your SPROG.Should you not be able to use the online install you can order distribution media on a USB Flash stick.If you wish to seek newer versions or upgrades, this download page has all the options available.
SPROG IIv4 User Guide (PDF 2.56Mbytes), 43 pages.This guide includes installing the SPROG II and required software, and guidance on getting started to use the SPROG and the JMRI software.
JMRI DecoderPro3 Manual (PDF 3.9Mbytes), 163 pagesThe most recent guides in PDF form date from 2014 (yes, getting to be quite old now and essentially obsolete, but maintaining pdf Guides has not been a priority for the JMRI volunteers!) included more depth on all the features of Decoder Pro, PanelPro and the JMRI software. However many changes have been made since 2014, so see below for the up to date latest available online or in your computer while running the JMRI tools!
With the proliferation and affordability of personal computers, several suppliers have developed software products, which link to a variety of DCC controllers. Hornby developed its RailMaster product and Bachmann Europe did the same with its RailController software. Other software packages are available to suit a variety of budgets and promise a great deal, although they require a learning curve to get the most out of them.
Bachmann married its RailController software with its new Dynamis Ultima controller, both launched at the same time. Since then, enhancements continue to be made to RailController software and Bachmann believes that the future of model railway control will be more computer-based.
On most DCC controllers, there are only a certain number of buttons which can be incorporated because of space limitations. Locomotives and other devices must be addressed by typing in their ID. An example, using the Bachmann Dynamis controller to control a locomotive is: press the locomotive/accessory button to control a locomotive. Press the Loco ID select button. Enter the ID, then use the throttle control or function buttons. It can be long-winded, and this is where computer software becomes useful. On a program like RailController, just select the locomotive to control from the ribbon. This ribbon can be dragged left or right to reveal more locomotives. 041b061a72