Release Notes for JMRI 4.25.10 release

Date: MM NN, 2021

From: Bob Jacobsen

Subject: Test Release 4.25.10 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 test releases. We expect this series to end in the next JMRI production release at the end of 2021. (See the tentative release schedule)

We are getting close to the production release, so it would be very helpful if you could try this test release and let us know of any problems you find.

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 4.20, 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 relese.

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 and use those from now on.
3. 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

New warnings for this release:

Older warnings

See 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.4 If you use a Safari browser on macOS X, the local help system might not work. There are two workarounds:
  1. If your computer is connected to the internet, use the web-based help. Go to JMRI Preferences, then select Help on the left, then click "Open help pages online"; save and restart
  2. To get local access, you can select Safari's Preferences, then the Advanced pane, then checkmark "Show Develop menu in menu bar"
  If you're using another browser, like Chrome or Firefox, you shouldn't encounter this issue.
• 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.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
  Pi-SPROG One with version 2.4 or earlier firmware will cause a timeout after a track short circuit. A dialog box will open to inform the user of this. The track power will be turned off and must be turned on again using the power control.

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.25.9:

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

Hardware Support

Acela CTI

Anyma DMX512

Bachrus Speedo

BiDiB

CBUS

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

OpenLCB / LCC

• Fixed a bug in the LccPro search function on large LCC networks.
• Added "Node Groups" to LccPro and the Event Table.

Powerline

RFID

Roco z21/Z21

Secsi

SPROG

TAMS

TMCC

Uhlenbrock Intellibox

Zimo MXULF

ZTC

New / Updated decoder definitions

Arnold

Bachmann

BLI

BNM Hobbies

CT Elektronik

Digikeijs (Digirails)

Digitrax

Doehler & Haas

ESU

Hornby

Kuehn

LaisDCC

LDH

Lenz

MD Electronics

MGP

Mistral Train Models

MTH

MRC

NCE

Norsk Modelljernbane (NJM)

Public Domain and DIY decoders

QSI

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

• Add the ability to use an AdHoc transit, which is created dynamically between 2 blocks Dynamic Transits are always run "No Signals". Dynamic Transits are removed at train termination. If they are not removed for any reason they will not be saved. Currently the route must be clear from end to end and any flaws in the routing table will cause grief. Avoid having the train stop in them.
• Add Ghost type block. It must have a "not real" sensor, internal is best. The sensor should not be manipulated by logix or logixNG or scripts. Auto trains will set and clear these sensors automatically, manual run trains simply ignore them. They are useful for adding blocks between 2 turnouts where you would normally add a tiny block with the same block as one of the turnouts which causes errors in the routing tables. With care they can be used for placing turnouts in their own block.

Dispatcher System

Internationalization

Layout Editor

NX - Entry/Exit Tool

LccPro

• Fixed a bug in the LccPro search function on large LCC networks.
• Added "Node Groups" to LccPro and the Event Table.
• Fixed a bug in Event Table display if using large fonts.

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

Timetable

Tracker

Turnouts, Lights, Sensors and other elements

Warrants

Web Access

Web Server

Where Used

WiThrottle Server

Virtual Sound Decoder

Z21 Server

Miscellaneous

---