Release Notes for JMRI 3.11.10 release
Date: July 05, 2015
From: Matthew Harris
Subject: Test version 3.11.10 of JMRI/DecoderPro is available for download.
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 versions. We expect this series to end in the next JMRI production release around the middle of 2015.
Some of the changes involved are quite extensive. They may require a certain amount of experience before they are working well. Therefore, this test version should be considered experimental.
Known problems with this releaseNone at release time.
New warnings for this version:
This release, and all later releases in this cycle, require Java 1.8 or higher. To use this or any later JMRI releases, you'll have to update the Java on your computer to Java 1.8 or higher.
The old DecoderPro has been removed from the distribution package and DecoderPro 3 has been promoted to be the only available DecoderPro version. Existing custom launchers that launched the old DecoderPro should continue to function without change or issue. If you absolutely cannot use the new DecoderPro user interface, we suggest using PanelPro instead, as with the exception of a different icon and different fixed buttons on the main window, PanelPro has an identical user interface to the old DecoderPro.
JMRI 3.11.3, and therefore this version, removes some files that were present in earlier versions. Failure to remove these can result in some portions of JMRI (notably the web server) failing to function correctly. If you are updating an existing JMRI installation to this version on Linux, you must remove any older version of JMRI or unpack this version of JMRI in an alternate location. The recommended update procedures for JMRI on Microsoft Windows (run the installer) and Mac OS X (open disk image and drag to final location, e.g. Applications folder) remove/replace the older version of JMRI, ensuring that these obsolete files are not present.
This release uses JDOM 2.0.5, which requires some code changes if you are directly calling the parts of JMRI that interchange XML objects.
There are now separate settings for the default Service Mode Programmer and for the default Ops Mode Programmer. If you're using two or more system connections, this lets you use one connection for ops mode (on track) programming and another connection for your programming track. If you're using two separate connections, you should go to the Defaults pane on the Preferences window and check that those defaults were set properly.
If you are making a direct connection to a Intellibox unit via serial or USB, you will have to reselect your preferences. See the Uhlenbrock support page for instructions.
If you are using an NCE USB adapter, you will have to reselect your preferences the first time you use a JMRI 3.11 version (if you set them using JMRI 3.10 or earlier). See the page on configuring JMRI for NCE for instructions.
The Save button in the Preferences window now only prompts for restarts if required. There may be instances when pressing save incorrectly fails to prompt to restart JMRI or prompts to restart JMRI when it should not.
Because of internal code changes, this version of JMRI may not be compatible with CATS 2.34 or earlier. Keep using JMRI 3.10 with CATS until there's a CATS update that says it will work with JMRI 3.11.
The XmlIO web service has been removed. All users who were relying on the XmlIO API are recommended to begin using the JSON API. inControl web throttle users are recommended to begin using webThrottle instead, or invest in devices that can support webThrottle, the iOS WiThrottle, or the Android Engine Driver.
We recommend that you verify the downloaded files using the provided sha256 key.
Please use these links for downloading:
Changes since test release 3.11.9:
- Randall Wood fixed a NullPointerException error sometimes seen when using signal definitions from a user's own files.
New / Updated decoder definitions
- Dick Bronson provided an update to the SignalMan decoder file
An improvement has been made in calculating distances and times when speed changes are done due to signal aspects or block speed specifications. Warrants now use the Roster Speed Profile for engine speed characteristics.
- NXWarrants can be used to add data to the Roster Speed Profile. See "Compute Factor" checkbox.
- Fixed problems with Warrants calculating the correct point to begin and end signaled Speed changes
- Signal table for OBlocks Offset column now specifies a distance rather than a time to adjust speed change points to conform to signal placement on the layout.
- Randall Wood fixed a problem with invalid schema locations in the BR-2003 signal aspects definition and one of the decoder definition tests.
- Pete Cressman fixed the Portal/Signal tables to now conform with Speed Profiling.