The Rocrail documentation is kept up to the daily state of development (Daily Build).
This Wiki is maintained against the main line of development. Some features could be not available or are different implemented in your revision of Rocrail, but it is mostly noted with a revision number.
Options and features not documented in the Wiki are for developers only and should not be a trigger to open a Forum thread.
External (Youtube) videos are not part of the Rocrail documentation and are discouraged to use as guide, unless they are linked in the Rocrail Wiki.
New to Rocrail? This guide shows the first basic steps and contexts for a successful start with Rocrail.
Navigation by clicking on the icon
Rocview is the PC-based operator interface for Rocrail
User interface for mobile devices
The Rocrail Server is the central control for the operation of a model railroad
Rocrail objects define the layout and its properties from A (as in Action) to U (as in Utilities)
Command Stations supported by Rocrail
Information on the comprehensive support and integration of various digital Command Stations
Settings and features in automatic mode
Configuration modular layout installations
Rocrail specific DIY (Do-it-Yourself) hardware developments
Functions and relationships
Description of the relationships between settings in different objects
or Report a problem
How to post a well structured problem message in the Forum
User tips & tricks
Examples of solutions to a number of specific tasks (mostly in German)
|User libraries are not officially supported and are not part of Rocrail.|
See for more information: User Library.
By creating a layout with Sensors, Blocks, and Routes, and then assigning your Locomotives to the Blocks, Rocrail can move the Locomotives by itself. You can use Schedules and Critical Sections to create and fine-tune complex movements for each Locomotive.
Tips and help for specific Raspberry Pi topics.
Take the following actions if you encounter problems using Rocrail:
Jump only to the next item in the list if the previous did not solve the problem!