Release Notes for JMRI 5.7.2 release
Date: December 31, 2023
From: Bob Jacobsen
Subject: Test Release 5.7.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 the 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)
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.
We would appreciate your feedback on it.
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:
- 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.
- 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.
- 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.
- 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.
- 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
- MRC serial connections do not work in this release.
If that affects you, please either
wait for
JMRI 5.7.4/a>, due out shortly after this one,
or pick up a
JMRI development build installer
from
Jenkins.
New warnings for this release:
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.2 GitHub release.
The
list of included changes is available from our
GitHub code repository.
Hardware Support
Acela CTI
- Acela CTI serial connections have been updated to use a new serial library.
C/MRI
- C/MRI serial now uses 2 stop bits, which solves communication
issues on certain hardware.
DCC++ and DCC-EX
- A problem with serial communications introduced in 5.7.1 has been fixed.
Direct
- Direct DCC serial connections have been updated to use a new serial library.
Lenz XPressNet
- A problem with serial communications introduced in 5.7.1 has been fixed.
Maple
- Maple serial connections have been updated to use a new serial library.
MQTT
- The new Jython script jython/MQTT/MqttSignalHead2.py
has been added. It's an improvement of jython/MQTT/MqttSignalHead.py
as it doesn't need any manual configuration to work.
- Made certain error messages specific to a single device.
NCE
- NCE serial connections have been updated to use a new serial library.
- Clock, Macro, and Consist added and improved error notification to user
when invalid inputs entered. Prior these were silently ignored or only
logged to the console.
- NCE Packet Analyzer has internal improvements to prevent errors due to port not
being open. Duplicates are now given as a count instead of a row of +++ as
the time stamp wasn't being placed correctly and a count is more meaningful.
The option to close the connection was added to manage selecting a different
port. It now supports the old and new versions of the analyzer. Reworked the
user interaction options to be easier to use and understand.
Oak Tree
- Oak Tree serial connections have been updated to use a new serial library.
Secsi
- SECSI serial connections have been updated to use a new serial library.
SPROG
- A problem with serial communications introduced in 5.7.1 has been fixed.
TAMS
- TAMS serial connections have been updated to use a new serial library.
New / Updated decoder definitions
Digitrax
- Updated LocoNet Monitor to display PM74 and SE74 device
types for certain LocoNet messages.
- Added DN163K5B decoder
Leb
- Fixed XML files when cross-referencing additional decoder details.
SoundTraxx
- Fixed XML files when cross-referencing additional decoder details.
Trix Modelleisenbahn
- Fix URIs in the xml/decoders/trix/mLD_mSD_functionmap.xml that were pointing to
http://jmri.oSound6/xml/ This should be pointing to: http://jmri.org/xml/
DecoderPro
- Added a SplitHundredsVal which defines a large value
split across multiple CVs in groups of two decimal digits.
This is used by the new Logic Rail Tech definition.
Layout Editor
- Do not display tooltips for hidden items.
- Do not reset all tooltip settings for Always or Never tooltip selections when changing
the editor mode.
LogixNG
- Note: If tables and panels are stored
with this JMRI version, the file might not load in a
previous version of JMRI if it includes LogixNG. This is
because JMRI now stores some LogixNG data in a different
way than before.
- Add Audio support to Where Used.
- The action Local Variable can now set
a constant of different types: String,
Integer, Floating number,
Boolean.
- The LogixNG table now shows whenether the ConditionalNGs
of a LogixNG has Startup enabled or not.
The Startup checkbox in the LogixNG
table can have three states: Checked, unchecked and
partially checked. If the user checks/unchecks the
checkbox, all the ConditionalNGs will have the
Startup enabled/disabled.
The column Startup is at the far right
in the LogixNG table. You might need to resize the table
to see the new column.
Note: Due to a bug, Startup might not
be shown as checkboxes but of text labels that cannot be
changed. To change Startup in this case,
edit the LogixNG and change Startup for
each ConditionalNG.
Panel Editor
- Do not display tooltips for hidden items.
Control Panel Editor
- Do not display tooltips for hidden items.
Where Used
Z21 App Server
- Added basic throttle function with the Roco Z21 Application on smartphones and tablets
Web Server
- Now displays "index.shtml" files if present in a directory.
