Release Notes for JMRI 5.11.7 release

Date: June 13, 2025

From: Bob Jacobsen

Subject: Test Release 5.11.7 of JMRI/DecoderPro is available for download.

Notes:

This is a test release. Please post a note if you encounter any new or old bugs! And please back up your JMRI files before installing this, in case you want to go back to an earlier version.

This is the next in a series of 5.11.* test releases. It requires at least Java 11 to work. We recommend that you use Java 17. (See our page on downloading Java) We expect this series to end in the next JMRI production release in June 2025. (See the tentative release schedule)

We are getting close to the next production release, so we would particularly appreciate your testing of this release to make sure it works for you. That way, if you find new problems, we can try to fix them before the production release.

JMRI is now only available under the GNU General Public License. For more information, please see our copyright and licensing page.

Update From Older JMRI Versions

If you are currently using a version older than JMRI 5.0, please follow these instructions carefully:

1. Is your current version older than JMRI 4.12? If so, then update to JMRI 4.12 first, and ensure everything works correctly: check start-up, check things you need to be working, and check the JMRI log as well) before doing anything else. Store your configuration and panel files under a new name and use those from now on. Then continue with step 2.

   If you are currently using JMRI 4.7.3 or earlier on Linux or macOS (Windows doesn't need this), then it's very important that you update to JMRI 4.12 and carrying out the migration process described in the JMRI 4.12 release note before updating to any later release.

2. Is your current version older than JMRI 4.20? Then update to JMRI 4.20 first, and ensure that works correctly (check start-up, check things you need to be working, and check the JMRI log as well) before doing anything else. Save your preferences again. Store your configuration and panel files under a new name, use those from now on, and go on to step 3.
3. Is your current version older than JMRI 4.24? Then update to JMRI 4.24 first, and ensure that works correctly (check start-up, check things you need to be working, and check the JMRI log as well) before doing anything else. Save your preferences again. Store your configuration and panel files under a new name and use those from now on.
4. Is your current version older than JMRI 5.0? Then update to JMRI 5.0 first, and ensure that works correctly (check start-up, check things you need to be working, and check the JMRI log as well) before doing anything else. Save your preferences again. Store your configuration and panel files under a new name and use those from now on.
5. You can then install this release.

Following this multi-step order of updating via stable major releases safeguards you against possible migration issues that can arise from skipping these versions.

New problems with this release

• None yet

New warnings for this release:

• None yet

Older warnings

See the JMRI 5.10 release note for more warnings predating the 5.11 development series, including pointers to various migration issues. These may be relevant to you if you're updating from an earlier version; we strongly recommend you update to at least JMRI 5.0 before installing this test release. See instructions above.

• Since JMRI 4.99.1 This test release, and all subsequent ones, require the use of Java 11 or later. We recommend that you use Java 17. Java 8 is explicitly not supported. There's more information on this migration on the JMRI Tech Road Map and JVM Capabilities pages.
• If you're using a Firefox web browser and opening JMRI help files locally (not over the web), a Firefox bug can sometimes cause it to enter a loop. There's a workaround in this JMRIusers post.
• Since JMRI 5.11.3 There's been a change to how OpenLCB turnouts are addressed when using the MTT addressing short cut. Turnouts 253,254,255, 510, 511, 512, 765, 766 and 767 will be addressed differently. If you're using any of these via e.g. MTT253, you will need to change the address. If you've been having trouble getting those addresses to work, this change should fix that.
• Since JMRI 5.11.5 OperationsPro program file locations were changed in JMRI 5.11.5. Start up actions involving operations windows from previous releases no longer work. You'll need to remove them and add them back if needed.

Download links:

These files are located in the JMRI 5.11.5 GitHub release. A Docker container can also be obtained from https://hub.docker.com/r/jsa1987/jmri-docker.

Changes since Test Release 5.11.6:

The full list of included changes is available from our GitHub code repository.

Hardware Support

CBUS

• Node Manager highlights duplicate CAN IDs.

DCC++ and DCC-EX

• Create and update Meters for newer Current messages , , etc.

drM

• Added initial support for the SPC200R Speedo meter. Speed will correctly show. Further support pending.

LocoNet

• The FollowSE*c.py script was broken at some unknown point in the past. The script is updated in this release to fix that.

OpenLCB / LCC

• Added a power manager (which activates e.g. the power control) for use with LCC command stations<>/li>

New / Updated decoder definitions

Digitrax

• Updated the Digitrax BDL716's "Roster Entry" with better information on its "Notes" page.

LogixNG

• The LogixNG action Send MERG CBUS event has been added. It's available in the category Merg Cbus if there is a Merg Cbus connection.
• The semicolon has been added as field delimiter for CSV files used to create LogixNG Tables.
• Where Used support has been added to the Formula actions and expressions. This is a text based search using the item's system and user names. False positive matches are possible.
• The formula function evaluateReference() has been added to the NamedBean module.

Meters and MeterFrames

• Add name of meter to display area, helps when stacking multiple windows.

OperationsPro

• The train icon now shows the number of local moves in the train's route.
• New feature, a turn can now drop and pull the same car on a turn. See Quick Load Service under spurs, load options.
• Added local moves enabled to route export and printing.
• Header lines are now optional for Manifests and switch lists. See Edit Manifest Header Text.
• Added track used, number cars and locos to location export

Scripting

• The script InitUnknownTurnoutsSensorsExceptInternal.py has been added.
  InitUnknownTurnoutsSensorsExceptInternal.py sets "Unknown" hardware states to default values for sensors (Inactive) and turnouts (Closed). This prevents overriding known states.
  The existing script InitAllTurnoutsSensors.py would override sensor Active and turnout Thrown states.
• Upgrade YetAnotherAutoTrain.py (YAAT) to version 3.3. There are two new statements.
  • Wait for memory <memory name> value to change
  • If value for memory <memory name> is <eq | ne | lt | gt | le | ge> <value>

Signals

Signal Systems

• The aspect mapping in the Italian FS-1987 signal system has been updated.

Miscellaneous

• The PlantUML library we use for various documentation images has been updated to the current 1.2025.2 version.
• Fixed a bug where Dark Mode would fail due to a missing library.
• There is a new Load and store pane in Preferences, that has options to exclude dynamic content in the tables and panels file. Without those dynamic contents, it will be much easier to keep JMRI's XML files in a version control system (e.g. GitHub) without having un-necessary merge conflicts.

---