Release Notes for JMRI 5.19.2 release
Date: MM DD, 2026
From: Release Pumpkin
Subject: Test Release 5.19.2 of JMRI/DecoderPro is available for download.
This is a draft release note only; the download links do not yet work
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.19.* test releases.
It requires at least Java 11 to work.
We recommend that you use Java 21 if possible.
(See our page on downloading Java)
We expect this series to result in the next JMRI production release in December 2026.
(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.18 release note
for more warnings predating the 5.18 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.19.1
Dispatcher: with "Place train name in allocated Blocks" on,
the value of an allocated Block no longer holds the train it is
allocated to.
A Logix, LogixNG or script that reads the value of an allocated Block
now gets only the train Block tracking has placed there: nothing
where the Block is empty, or where Block tracking could not tell
which train entered. To get what the value gave before, use
getDisplayValue(); for only the train the Block is
allocated to, getAllocatedValue(). Dispatcher logs a
note the first time this applies in a session. With the option off,
nothing changes.
See the
Dispatcher section of the 5.19.1 release notes.
- Since JMRI 4.99.1
If you're using a Firefox web browser and opening JMRI
help files locally (not over the web), a Firefox bug
can sometimes cause it to enter a loop. There's a
workaround in
this JMRIusers post.
Download links:
During development leading to the actual release, you can download a
development build installer.
These are development files, and might not be working at any particular time.
The
full list of included changes is available from our
GitHub code repository.
Hardware Support
- A serial connection that recovers from a failure (such as a
CANUSB4 or other GridConnect adapter, or a LocoBuffer) is now
set up again when the port reopens at the first attempt; before,
it showed as connected but sent and received nothing. An error
opening the port at the first attempt no longer stops the
retries.
- Connections (NCE, C/MRI, CAN, XpressNet and others): after a
connection recovers from a failure, messages are no longer
sent out of turn or their replies given to the wrong
listener.
Acela CTI
Anyma DMX512
Bachrus Speedo
CBUS
- CBUS Node Manager: dragging the divider between the
node table and the tabs no longer writes all of CBUS's
preferences to disk for every pixel it moves. Where it
is left is saved once it stops.
C/MRI
DCC++ and DCC-EX
DCC4pc
Direct
ESU
Hornby
Internal
IPOCSMR
JMRI Simple Server/JMRI Client
KPF-Zeller
Lenz XPressNet
LocoNet
Maple
Marklin CS2
MERG
MQTT
MRC
NCE
Oak Tree
Powerline
RFID
Raspberry PI
Roco z21/Z21
Secsi
SPROG
SRCP
TAMS
TMCC
Uhlenbrock Intellibox
Zimo
ZTC
New / Updated decoder definitions
AE Model
Arnold
Bachmann
BLI
BNM Hobbies
CT Elektronik
DCC Concepts
Digikeijs (Digirails)
Digitrax
Doehler & Haas
ESU
Hattoms
Hornby
Kuehn
LaisDCC
Lenz
MD Electronics
MGP
Mistral Train Models
MTH
MRC
NCE
Norsk Modelljernbane (NJM)
Piko decoders
Public Domain and DIY decoders
QSI
Rampino Elektronic
Rautenhaus
RR-CirKits
SoundTraxx
Tam Valley Depot
TAMS
TCS
Team Digital
Technologistic (train-O-matic)
Trix Modelleisenbahn
Uhlenbrock
Umelec
Viessmann
Wangrow
ZIMO
Miscellaneous
Control Panel Editor
Circuit Builder
Palette
CTC Tool
DecoderPro
Dispatcher
- With automatic allocation and the new option
Prevent
Deadlock, off unless checked, Active Trains can no longer
end up waiting for each other for good, such as two trains
each holding half of a single line. A train is then given
track from one place it can stop to the next, all at once,
and only where every Active Train can still run its Transit.
A train waiting for track gains a step of priority for each
minute it waits. Trains started where they can't all run
their Transits are named in a warning. Unchecked, Sections
are allocated as before.
held for good by a meet planned after it had already been given
the road beyond its meeting place. Two trains running the same
way round a circuit could be taken for trains coming towards
each other; one was then told to wait in a station for the
other, which needed track the waiting train already held.
Dispatcher now drops such a meet, as it does when a train is
already past the meeting place.
- With automatic allocation, an automatic train is no longer
Dispatcher System
Internationalization
Layout Editor
NX - Entry/Exit Tool
LccPro
Logix
LogixNG
Meters and MeterFrames
OperationsPro
Panel Editor
Permissions
Preferences
Resources
Roster
Routes
Scripting
Signals
Signal Systems
Signal Heads
Signal Masts
Signal Groups
Cab Signals
Simple Signal Logic
USS CTC Logic
Switchboard Editor
Throttle
- JMRI no longer freezes when a throttle window shows that a
loco couldn't be acquired (for example a LocoNet slot refused
or timed out) while another throttle request is answered or a
throttle window is opened or closed.
Timetable
Tracker
Turnouts, Lights, Sensors and other elements
- With a debounce set, a sensor state the hardware reports
twice no longer skips the debounce.
Warrants
Web Access
Web Server
- Web panels: a panel showing a sensor as text no longer
reloads in the browser each time the sensor changes.
Where Used
WiThrottle Server
Virtual Sound Decoder
Z21 Server
Miscellaneous
- The first-time start-up wizard finds its list of languages
into a list of its own, so building that page twice at
once can no longer break the sort with "Comparison method
violates its general contract".