Release Notes for JMRI 5.7.7 release

Date: May 9, 2024

From: Bob Jacobsen

Subject: Test Release 5.7.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.7.* test releases. It requires Java 11 to work. (See our page on downloading Java 11) We expect this series to end in the next JMRI 5.8 production release in June 2024. (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:

• If you are using a RR-CirKits LocoNet to LCC gateway with this release, please upgrade its firmware to version B8g or later. B8f or earlier will have trouble updating the gateway's configuration.

Older warnings

See the JMRI 5.6 release note for more warnings predating the 5.7 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. Java 8 is explicitly not supported. There's more information on this migration on the JMRI Tech Road Map and JVM Capabilities pages.
• Since JMRI 5.5.3 Scripts that output Logging statements with log4jv1.x ( org.apache.log4j ) imports will stop working from JMRI 5.5.4 and should be updated to use SLF4J logging.
  See here for some examples on how to do this.
• Since JMRI 5.5.4 Custom default.lcf Logging Control Files will cease to take effect from JMRI 5.5.4
  To create a custom default_lcf.xml in the new Logging Configuration format, see JMRI Debugging and Logging
• Since JMRI 5.5.5 XML files with table contents and panels have been changed in JMRI 5.5.5. It's therefore not possible to load an xml file with tables and panels that has been created with JMRI 5.5.5 or later with a JMRI version pre 5.5.5.
• Since JMRI 5.5.5 MQTT Connection - Throttle loco address and function placeholders in MQTT topics have changed from $address and $function to {0} and {1} for consistency with other objects.
• Since JMRI 5.7.1 Several systems have had extensive updates to their serial support. If you have trouble connecting to your layout hardware after installing this version, please contact us on the JMRIusers list for assistance.

Download links:

These files are located in the JMRI 5.7.7 GitHub release.

Changes since Test Release 5.7.6:

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

Hardware Support

• Fixed a freeze that could happen when changing the connection preferences.

LocoNet

• DCS240+ has transponding built it, so that option is treated as selected.
• Improved how LACK responses are handled in ops mode programming; sped up ops mode programming
• Improved how threads are shutdown when changing connections in the settings.

OpenLCB / LCC

• Fixed the filtering in the Monitor window.
• If you enter an value that's outside the acceptable range in the configuration tool, the background will now turn blue to indicate that to you.
• Improved how the buttons are laid out at the bottom of the CDI window
• Improved handling and display of messages that flag Simple protocol
• Improve AME handling to make throttle connections more reliable in the face of command station resets.

New / Updated decoder definitions

Digitrax

• SFX Series 7 support updated for XF controls.

Mistral Train Models

• Updated Lokommander II definitions. Implement CV114, 115 and 116 according to the firmware version. Firmware V3 : treat as binary and only support up to F8 Firmware V6 : treat as decimal and support up to F28

Tam Valley Depot

• Updated the QuadLN_S decoder definition to support new features in version 3.3 firmware.

ZIMO

• new MS and MN decoders added
• minor optical corrections

Dispatcher

• Update controlling Signal on screen in a timely fashion.
• Stop train with profile in remaining blocks of a multi block section.
• Stop autotrains on program exit.

Layout Editor

• Fixed the ability to connect turnouts by dragging and dropping. When end points overlap, a track segment is automatically created. This works very nicely for creating yard ladders. The problem affected panels on Linux and Windows.

LogixNG

• The functions round(), ceil() and floor() has been added to the Math module. All three rounds a floating point value. ceil() rounds up and floor() rounds down.
• The constant oblocks has been added to the Layout module.
• Fixes a bug in LogixNG formula when calling a Java method that takes a boolean as parameter, like setVisible().
• Two new preferences have been added. Log all before and Log all after. If these are selected, LogixNG will log every action that's executed and every expression that's evaluated. For this to work, the LogixNG debugger must be installed (which it is by default).

Meters and MeterFrames

• Added a start-up action that will open the meters.
• Add a MeterToMemory.py sample script that copies Meter values to Memory variables

Control Panel Editor

• Fixed the popup context menu on Linux.

Scripting

• New ThrottleBridgeF0F8.py for bridging a throttle between Lenz and Digitrax systems including the F0 through F8 functions.

---