Release Notes for JMRI 4.21.4 release
Date: mmm dd, 2020
Subject: Test Release 4.21.4 of JMRI/DecoderPro is available for download.
This is a draft release note only; the download links do not yet work
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 test releases. We expect this series to end in the next JMRI production release in early summer 2020. (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.
Update From Older JMRI VersionsIf you are currently using a version older than JMRI 4.20, 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 relese.
- 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 Store your configuration and panel files under a new name and use those from now on.
- You can then install this release.
Known problems with this release
New warnings for this release:
- None yet
Older warningsSee the JMRI 4.20 release note for more warnings predating the 4.21 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 JMRI 4.20 installing this test release.
- Since JMRI 4.21.1 The jmri.jmrix.SystemConnectionMemo class has become a jmri.SystemConnectionMemo interface and a jmri.jmrix.DefaultSystemConnectionMemo class. This may require changes to scripts. If you have a script that references jmri.jmrix.SystemConnectionMemo, please change it to either jmri.SystemConnectionMemo or jmri.jmrix.DefaultSystemConnectionMemo (it's easier to have you just try the two than to explain which one will work in which case)
- Since JMRI 4.21.1 The way preferences are loaded at startup has been slightly modified. There is no impact to JMRI applications, but Non-JMRI applications that are not derived from apps.Apps or apps.AppsBase but are using jmri.implementation.JmriConfigurationManager to load preferences will no longer see preferences if an error occurs. To restore the old behavior, use apps.AppsConfigurationManager instead.
- Since JMRI 4.19.1
getBeanBySystemNamecalls in the various
Managerclasses are no longer needed with Java 8 and have been deprecated for eventual removal. Their replacements are
getBySystemNamerespectively. If you use
getBeanBySystemNamein script or Java code you've written, please switch to the new names.
- Since JMRI 4.11.4
There are issues with the Pi-SPROG One command station operation. A number of workarounds should be applied:
- Do not turn on the track power until the power supply to the Pi-SPROG ONE is turned on
- Do not enable extra debugging through default.lcf, nor open the system console window
- Do not open the SPROG console window
- Disable power conversion (CV 29) in all locos
- If connecting via VNC (or similar), setup the screen layout before turning on the track power
Download links:During development leading to the actual release, you can find test download files on the continuous integration build page. These are development files, and might not be working at any particular time.
Changes since Test Release 4.21.3:The list of included changes is available from our GitHub code repository.
- messaging enhancements and cleanup, retry some failed messages
JMRI Simple Server/JMRI Client
- New LNCV Programming tool (Uhlenbrock protocol), available from LocoNet menu, with window specific help.
- Added hardware connection support for the (LocoNet) Uhlenbrock USB Adapter part #63120. Manufacturer states their USB drivers only support Windows OS.
New / Updated decoder definitions
- Added DR5033 LocoBoost configuration support, using the new LNCV service mode programming.
You can access the DecoderPro programming panes from the LNCV Tool table matched by article number (5033 in this case).
- Allow configuration of more function outputs for FX3 decoders.
Doehler & Haas
Mistral Train Models
Norsk Modelljernbane (NJM)
Public Domain and DIY decoders
- New Switch Module 63410 decoder support, using the new LNCV service mode programming.
You can access the DecoderPro programming panes from the LNCV Tool table matched by article number (6341 in this case).
NX - Entry/Exit Tool
Meters and MeterFrames
- New feature for cars, Return When Loaded. Now you can set a load name and destination for a car when it's load status changes to loaded. See operations help for more details.
Control Panel Editor
Turnouts, Lights, Sensors and other elements
- Better set row height in table.
Simple Signal Logic
USS CTC Logic
- Set the default start time for a new train to match the schedule start time.
- A button to translate the throttle settings to track speed in inches/sec or millimeters/sec or scale speed on miles/hr or kilometers/hr has been added to the windows used for editing Warrants or creating NXWarrants.
Virtual Sound Decoder
- YetAnotherAutoTrain.py (YAAT) has been updated to version 2.2. This version includes support for compiling train definitions for faster startup. It also includes the ability to create extensions to the command language. A Help document has been added to the JMRI Help pages.
- The Comments columns in Tools ⇒ Tables have support for multi-line comments. The Edit Comment option has been added to the right click pop-up menu that is normally used to move user names. A tooltip will be displayed with the comment content.