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).

• Enables layout schematics to be created with signals, points, track sections and block instruments.
• Supports most types of UK colour light signals, semaphore signals, and ground signals.
• Interfaces with the Pi-SPROG DCC command station to drive the signals and points out on the layout.
• Uses the Raspberry Pi GPIO inputs to provide train detection in support of signalling automation.
• Incorporates MQTT networking to allow multiple signalling applications to be linked for larger layouts.
• 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

BREAKING CHANGE - Single Slip and Double Slip points have been shortened to improve route highlighting but this does mean you will need to edit your schematic (extend track lines) to take account of this change. Also, Double Slip points have been changed to give a straight route through the point for their default state.

• New feature to scroll canvas via mouse (drag and drop) in Run Mode - useful for larger layouts
• Changed default GPIO sensor timeout to 20ms (the optimum value I have arrived at by testing)
• Improvement - Item IDs (signals, points, lines etc) can now be in the range 1-999
• Improvement - Route selection buttons are now always displayed on top of route lines
• Improvement - Text Boxes are now always displayed on top of route lines
• Improvement - Improved representation of Trap Points and single slip points
• Improvement - Improved Route highlighting through points (for most point types)
• Improvement - Improved readability for theatre route indications and track occupancy
• Bugfix to GPIO sensors - to prevent the occasional spurious segmentation errors on settings apply
• Bugfix to timed signals (triggered by another signal) - to prevent spurious SPAD warnings
• Bugfix to handle update of Route ID (if changed by user in the route configuration dialog)
• Bugfix to schematic route highlighting for 'Y' points (route now correctly highlighted)

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: enquiries@model-railway-signalling.co.uk (if reporting bugs then please attach the sig file, application logs and any relevant screenshots)

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
$ python -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

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.11/README.venv for more information.

To overcome this, remove the 'EXTERNALLY-MANAGED' file from the default python installation and then re-attempt the install (as above). Note that this is the file location for the Raspberry Pi python 3.11 installation. Other platforms may use a different location for this file:

$ sudo mv /usr/lib/python3.11/EXTERNALLY-MANAGED /usr/lib/python3.11/EXTERNALLY-MANAGED.old

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
$ python -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
$ python -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
$ python -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

If you want to use Block Instruments with full sound enabled (bell rings and telegraph key sounds) then you will also need to install the 'simpleaudio' package. If 'simpleaudio' is not installed then the application will still function correctly (just without sound).

$ pip install simpleaudio

If you are running on a later version of Python you may need to install libasound2 before the simpleaudio pip install will work.

$ sudo apt-get install libasound2-dev

Note that for Windows, the 'simpleaudio' it has a dependency on Microsoft Visual C++ 14.0 or greater (so you will need to ensure Visual Studio 2015 is installed first).

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

Application documentation, can be found in the 'user_guide' folder: https://github.com/johnrm174/model-railway-signalling/tree/main/user_guide

Some example layout configuration files can be found in the 'configuration_examples' folder: https://github.com/johnrm174/model-railway-signalling/tree/main/configuration_examples

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.