Release Notes for JMRI 5.3.2 release

Date: January 14, 2023

From: Bob Jacobsen

Subject: Test Release 5.3.2 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.3.* 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.4 production release in June 2023. (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 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:

• Some images in the resources/icons folder have been renamed. Spaces have been changed to underscore. It's images in the resources/icons/ItalianSignals/ACEI, resources\icons\ItalianSignals\Prototypical, resources/icons/smallschematics/aspects/NW-1981, resources/icons/smallschematics/aspects/NYC-1956, xml/signals/FS-1987, xml/signals/NW-1981, xml/signals/NYC-1956 and resources/icons/SNCF/Small folders that have been renamed. If you are using these images directly, you will need to update the reference.

Older warnings

See the JMRI 5.2 release note for more warnings predating the 5.3 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 5.1.7 The way defaults for some LocoNet connections are handled has changed. Existing LocoNet connections might give a "The Defaults preferences are invalid" warning when saving preferences. In that case, click "yes" and then go set all the default radio buttons on the "Defaults" pane to the LocoNet connection. (You can also click "no", but you'll get the message next time you store too)
• 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.

Download links:

Changes since Test Release 5.3.1:

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

Hardware Support

LocoNet

• Support for expanded slots and associated protocol. To enable this the advanced LocoNet preferences must be set XPSlots Auto Detect. If using DCS240(+) limited to less than 120 slots use DCS210 or DCS210+ to avoid needless reading of slots. When using a DCS240(+) be aware that when first opening a Slot Monitor window 430 odd slots are read, so avoid doing it during layout start. If using throttles that cannot access XP Slots along side those that can you may see the same loco number twice in the slotmon, which slot actually has control may vary.

MQTT

• A Reporter implementation is now available for MQTT connections.

OpenLCB / LCC

• Programmer support added. Enables using DecoderPro on the TCS CS-105 and LT-50 command stations. Service Mode (Programming Track, with Direct Mode) and Ops Mode (Programming on Main) are both supported. RailCom-aware decoders can read CVs on the main (in Ops Mode), which is a lot faster than reading on the Programming Track.

New / Updated decoder definitions

Piko

• Piko Smart Decoder 4.1 and XP5.1
• Add CVs 100, 101 for Function Mapping Shift on Piko Smart Decoder 4.1

Uhlenbrock

• Added Tillig BR 89 steam loco on several panes

DecoderPro

• Some internal state constants have been changed from integer values to an enum. This should not have any external effect.

LogixNG

• Fixes a bug when importing a Logix to LogixNG, where the Conditional uses Mixed. The Not is ignored for the conditional variables when using Mixed.
• Fixes a bug with the action Entry/Exit and the expression Entry/Exit. The action and expression stored the user name instead of the system name if the Entry/Exit. The user name of an Entry/Exit changes when the NX sensor or related signal mast is changed.
• Fixes a bug with the action Timer. If the same sensor is used for both start and stop of the timer, the timer didn't restarted after a stop.
• The action Timer can now use the expression Start to both start and stop the timer. This is useful if you want to start and stop the timer from a single sensor.
• Adds panel file XSLT formatting for display of Digital Actions, Expressions, and Boolean Actions in web browser.

Operations

• Fixed a problem when a location has multiple spurs and the spur's schedule forwards the car to another spur at the same location with a schedule. The car's load can incorrectly change to the default "E" or "L" load.

Scripting

• Kevin Appleby provided a script for doing serial transfer from the Light Table.

Signals

Signal Systems

• Pino Di Biasi provided an Italian signal system
• Spaces are no longer allowed in image file names for signal systems. Use underscore instead of space. For example ACEI_Acc_1_vela_giallo.gif instead of ACEI Acc 1 vela giallo.gif

---