Release Notes for JMRI 5.1.4 release

Date: September 14, 2022

From: Bob Jacobsen

Subject: Test Release 5.1.4 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.1.* 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.2 production release in December 2022. (See the tentative release schedule)

Some of the changes involved are quite extensive. They may require a certain amount of experience before they are working well. Therefore, this test release should be considered experimental.

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 4.24, 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. 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

• OperationsPro, there's a problem with car's custom load when upgrading to this release. Cars that were "scheduled" to get a custom load when terminated could instead get the default "E" or "L" loads. Before upgrading, please terminate or reset all trains if you're using custom loads and schedules. Also all car wait counts need to be reduced to zero by building and resetting trains. If you're not using custom loads, you can ignore this issue.

New warnings for this release:

• There's a problem with the generation of OpenLCB/LCC AMD frames in this version that can result in the bus locking up. This problem is not present in 5.1.3 or earlier, and will be fixed in JMRI 5.1.5.

Older warnings

See the JMRI 5.0 release note for more warnings predating the 5.1 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 4.20 before installing this test release.

• 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 4.99.1 This version no longer reads ZeroConf IPv4 and IPv6 preferences written with JMRI 4.16 and before. Please make sure to upgrade to JMRI 4.20 (or later) and save your preferences before updating to this version if you have configured the WiThrottle preference pane.

Download links:

Changes since Test Release 5.1.3:

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

Hardware Support

LocoNet

• The DCS240+ doesn't accept service-mode read requests for about 350-400msec after the completion of the prior one. A short delay has been added to handle this.

NCE

• Internationalization of the NCE tools was completed. New items are available for translation.

OpenLCB / LCC

• Updated openlcb.jar to pick up "send AMD in response to AME" fix.

SPROG

• Added option for offset between CBUS events and DCC accessory addresses for [Pi-]SPROG 3 Plus firmware 3.e Beta 2.

New / Updated decoder definitions

SoundTraxx

• Updates to ECO & TSU2, add Genesis Caboose

Uhlenbrock

• Added a new definition for Lissy Receiver #68600, 68610 and #68620. Use LNCV programming.
• Added definitions for the UB 73310 and UB 73416 decoders.

DecoderPro

• Menu items were harmonized with the button alternatives.

Internationalization

• See NCE tools above.

LogixNG

• The popup menu in the ConditionalNG editor is changed. All the categories are sub menus to the Add menu item. When a new action or expression is to be created, it is selected directly in the popup menu.
• The expression Local variable as analog value has been added.
• LogixNG now prints (Listen) or (No Listen) when memories are used as addressing. It also prints ::: No Listen for expressions where the option Listen is unchecked.

Web Server

• Added Camera webThrottle to Web Server.
  Camera webThrottle provides integrated support for controlling trains with integrated POV or overhead IP based cameras.
  Throttle Learn More page has been added for the camera throttle that covers setup and connecting the cameras to the engine throttle.

Miscellaneous

• The French JMRI Help pages were updated for responsive display.
  They will appear when using the French locale, or from their own starting page.
• SpotBugs has been updated to 4.7.2
• The local help stub file has been moved from the settings location to the home location. This fixes a problem introduced by recent versions of Ubuntu and its derivatives.

---