model-railway-signals 6.2.0

Create your own DCC model railway signalling scheme

model-railway-signalling

A DCC model railway signalling application written in Python, enabling automated and interlocked layout signalling schemes to be designed and configured via the UI without the need to write any code. The application is primarily intended for the Raspberry Pi, but will also run on other platforms (albeit without some of the Raspberry-Pi specific interfacing functions).

• Provides a full DCC Command station for your model railway layout:
  • Control your locos via on-screen throttles or via your smartphone.
  • Control all your DCC accessories intuitively via the on-screen schematic.
• Enables signalling schematics to be easily created with route lines, points and signals:
  • Supports most types of UK colour light signals, semaphore signals, and ground signals.
  • Supports complex trackwork formations such as crossovers, slips and 3-way points.
  • Get the schematic looking how you want by changing the styles of objects as required.
• Interfaces with the Pi-SPROG DCC command station to drive all of your DCC Accessories:
  • Uses a DCC Accessory bus (seperate from the track bus) to control your layout.
  • Supports all standard DCC signals, point motors and other DCC accessory decoders.
  • Signals and points are simply operated via their control buttons on the schematic.
  • Add virtual 'DCC Switches' to the schematic to control other DCC accessories.
  • Includes a DCC programming utility for both 'one touch' and CV Programming.
• Enables full signalbox simulations to be realised for your layout:
  • Add virtual 'Signal box Levers' to the schematic to control your signals/points.
  • Supports integration with external switches (Such as the DCC Concepts Cobalt S Levers).
  • Add virtual 'Block Instruments' for communication and coordination between signal boxes.
• Uses the RPi GPIO inputs (connected to external track sensors) to detect train movements:
  • Add 'Track Sections' to the schematic to provide a mimic diagram of train location.
  • Train designators then 'move' through the schematic based on 'signal passed' events.
  • Alternatively, use 'track circuits' for an absolute indication of block occupancy
  • Track occupancy can then be used to support signal automation (see below).
• Provides full prototypical operation of your layout - just like the real thing.
  • Signals can be interlocked with points, other signals and Track Sections ahead.
  • Points are interlocked with the signals that control movements across them.
  • Points can also be interlocked with Track Sections representing 'track circuits'.
  • Multiple aspect signals will always reflect the state of the signal ahead.
  • Signals can be automated based on the 'occupancy' of Track Sections ahead.
• Provides "one click" set-up and clear-down routes through your layout:
  • Interlocking is preserved - Routes are disabled if conflicting movements are set.
  • Routes are highlighted on the schematic to show they have been successfully set.
  • Supports automated set-up and clear-down of routes based on GPIO sensor events.
• Incorporates MQTT networking to allow multiple signalling applications to be linked.
  • Allows multiple signalling areas or signal boxes to be created for larger layouts
  • Multiple applications use the same DCC command station for control of your layout.
  • Provides easy expansion of the number of external Track Sensors that can be used.
• Full documentation and several example layout files are packaged with the application.

The application also provides a Public API to support custom layout control interfaces.

Configured / pre-installed systems are now available to purchase from: https://www.model-railway-signalling.co.uk/ The website also included a number of user guides that can be downloaded (in PDF format).

My youTube channel also has a number of videos demonstrating the use of the application: https://www.youtube.com/@DCCModelRailwaySignalling

What's new for Release 6.2.0:

[!IMPORTANT] Release 6.2.0 will only support the loading of layout files created by Release 6.0.0 or later. If you have layout files created by an earlier version of the application then you should first upgrade to Release 6.0.0 and then load/re-save your files before upgrading to Release 6.2.0. You have been warned!

• DCC Loco control - Now the DCC Signalling system can be used as a full DCC Command Station:
  • Ideal for smaller layouts if you don't want the to use a seperate command station.
  • Add your DCC locos to the Roster, defining DCC address and DCC functions.
  • Control your Locos via on-screen throttles (fully compatible with touchscreens).
  • Start the built-in Throttle server and control your locos from your smartphone.
  • Tested and fully supported for Android (third party 'Engine Driver' App).
• Scripting interface improved and extended to include locomotive control:
  • Entire layouts can now be fully automated via python scripting.
• Extended Hide/Unhide ('h' and 'u' keys) to Signal, point and lever buttons).
• Improved initial synchronisation of layout state following DCC connect.
• Added ability to inhibit flashing aspects for signal approach control.
• Added ability to click on signals subject to approach control to 'release' them.
• Added ability to specify the same GPIO sensor for signal passed and signal approach events.
• New functionality to allow copying of route definitions and route buttons:
  • NX route definitions can now be copied within the Route Button configuration.
  • Copying of Route Buttons will now bring across all individual route definitions.
  • Makes it easier to define laddered routes with minor differences between them.
• Performance improvements when editing or initialising very large schematics.
• Improved logging - logs are now also written to disk to aid subsequent diagnostics:
  • If you encounter problems you can now easily email us the logs for diagnosis.
• Minor Improvements to the DCC Programming utility.

Bug reports and feedback is welcome and appreciated:

• What aspects are intuitive? What aspects aren't?
• What aspects do you particularly like?
• What aspects particularly irritate you?
• What new features would you like to see?

email: [e-mail] (if reporting bugs then please attach the sig file, application logs and any relevant screenshots)

Installing the application

For a first time installation use:

$ pip install model-railway-signals             <== This should work for most python installations
or
$ python -m pip install model-railway-signals   <== If the command line version of pip is not installed/enabled
or
$ python3 -m pip install model-railway-signals  <== If you have multiple major versions of python installed

When installing the application on later versions of python you may get the following error:

error: externally-managed-environment

To overcome this, add the '--break-system-packages' argument to the command - e.g.

$ pip install --break-system-packages model-railway-signals 

To upgrade to the latest version use:

$ pip install --upgrade model-railway-signals            <== This should work for most python installations
or
$ python -m pip install --upgrade model-railway-signals  <== If the command line version of pip is not installed/enabled
or
$ python3 -m pip install --upgrade model-railway-signals <== If you have multiple major versions of python installed

To remove the application:

$ pip uninstall model-railway-signals                    <== This should work for most python installations
or
$ python -m pip uninstall model-railway-signals          <== If the command line version of pip is not installed/enabled
or
$ python3 -m pip uninstall model-railway-signals         <== If you have multiple major versions of python installed

To install a specific version of the application the application:

$ pip install model-railway-signals==4.5.0               <== This should work for most python installations
or
$ python -m pip install model-railway-signals==4.5.0     <== If the command line version of pip is not installed/enabled
or
$ python3 -m pip install model-railway-signals==4.5.0    <== If you have multiple major versions of python installed

The application has minimum external dependencies (over and above the 'standard' python installation), 'pyserial' and 'paho-mqtt', both of which should automatically get installed with the application. If for some reason this doesn't happen (I've been made aware of one instance on a Windows platform) then these packages can be installed seperately (prior to installing the model-railway-signals package):

$ pip install paho-mqtt
$ pip install pyserial

Running the application

The python package should be run as a module (note underscores):

$ python -m model_railway_signals  <== This should work for most python installations
or
$ python3 -m model_railway_signals <== If you have multiple major versions of python installed

If required, a layout schematic can be loaded at startup:

$ python -m model_railway_signals -f layout_file.sig

If required, the logging level can be specified at startup (ERROR, WARNING, INFO or DEBUG)

$ python -m model_railway_signals -f layout_file.sig -l DEBUG

Full documentation is packaged with the application (access by selecting Help => Docs from the main menubar).

A number of example layout configuration files are also packaged with the application (access by selecting File => Examples from the main menubar)

My youTube channel also has a number of videos demonstrating the use of the application: https://www.youtube.com/@DCCModelRailwaySignalling

And finally, a top tip for running the application on the latest Debian Bookworm release which uses Wayland as the GUI backend rather than X11 (which was the backend for previous Debian releases). I found that with Wayland, the Tkinter GUI performance was terrible for some reason (not just my application - python/Tkinter performance in general) - and that was running on a Raspberry Pi 5 which I would have expected to improve overall performance. Anyway, I found that the fix is to switch the GUI backend of the Raspberry Pi back to X11 - performance of the user interface is now lightning quick!

To change the backend - Run "sudo raspi-config", select 'Advanced Options' then 'Wayland' and select X11.

An additional benifit was that some of the other applications I use (such as the kazam video capture software) will now work as normal on the Raspberry Pi 5.