Release Notes for JMRI 5.9.2 release
Date: July 16, 2024
From: Bob Jacobsen
Subject: Test Release 5.9.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.9.* 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 December 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
New warnings for this release:
Older warnings
See the
JMRI 5.8 release note for more warnings predating the 5.9 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.
- 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.
- Since JMRI 4.7.7
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.
Download links:
These files are located in the
JMRI 5.9.2 GitHub release.
The
full list of included changes is available from our
GitHub code repository.
Hardware Support
LocoNet
- Significant updates for programming the Digitrax DS74, DS78V, PM74, SE74 boards
- Provides corrected code for accessing the CVs for the DS74, DS78V, PM74, and SE74
- Can handle certain odd behaviors seen with some firmware updates
Users should delete any "Roster Entries" which were created using previous
decoder definitions and create new entries using these new definitions.
- Fixed a bug that would cause the Memory Tool to fail
when putting data.
TMCC
- Now sends repeated function commands so long as
the throttle function is active.
- TMCC2 Legacy 200 speed step mode is now available.
Select it from the combo box at the top of the Throttle's speed subwindow.
- Add support for sending two function commands on a button
push/release. First examples of this are
Fn28 Start Up Sequence 1 (Delayed Prime Mover, then Immediate Start Up)
Fn30 Shut Down Sequence 1 (Delay w/ Announcement, then Immediate Shut Down)
New / Updated decoder definitions
Digitrax
- Updated DS74, DS78V, PM74, and SE74 decoder definitions.
Includes options which can be used with recent firmware.
Be aware that previous JMRI versions had erroneous decoder definitions
for the DS74, DS78V, PM74, and SE74. All Roster Entries for these
devices should be discarded then re-created using the newer
definitions.
Provides corrected code for accessing the
CVs for the DS74, DS78V, PM74, and SE74 decoders.
LogixNG
- Prepend the proper prefix when using short system names, such as 123 or abcd. For
alpha suffixes include the required $ character.
Preferences
- Do not create blank profiles.
When deleting blank profiles do not remove directory.
Explicitly warn that a directory and its contents will be deleted when deleting a profile.
Resources
- Added an
"/extras/"
directory to contain large/specialized downloadable resource files.
- Added Jim Well's coal tipple sound file to
/extras/sounds
Scripting
- Add the SetBlockValues.py script to the JMRI distribution.
Warrants
- Add the Set Memory Value action to the Throttle Commands script.