Release Notes for JMRI 3.11.5 release
Date: April 12, 2015
From: Bob Jacobsen
Subject: Test version 3.11.5 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 release
- Paths in panels that start with
home:will not load correctly.
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.
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.
Please use these links for downloading:
Changes since test release 3.11.4:
- Mark Riddoch provided a Reporter for CBus that allows for the connection of an RFID reader attached via a suitable CBus node.
- Ken Cameron has fixed significant issues in the NCE Macro editor when used with the serial connected PowerPro system (CS02). It seems to have been an issue since June 2014, release 3.7.8 when the NCE USB support was added.
- Dave Heap changed the SPROG and SPROG Command Station code so you can now use the full NMRA DCC address ranges of 0 to 10,239 long ("Extended") or 1 to 127 short ("Basic") addresses. The throttle now gives you a selector for Long or Short address.
- Dave Heap improved the Slot Monitor display.
"Direct" programming modeDave Heap added a new "Direct" programming mode choice for DCC systems (such as NCE) that use both the Direct Bit and Direct Byte operations when programming. Direct Bit and Direct Byte (when available) mean that the command station is told to use only one or the other, which might be useful with very old decoders.
New / Updated decoder definitions
Michael Mosher improved the BLI P2 definition
Alain Le Marchand added definitions for the MRC sound 1617 and 1618 decoders
Dan Boudreau made the following changes to operations:
- You can now control which destinations out of staging are allowed for custom loads. See under "Edit Staging Track" tools "Track Destinations". "
- Improved build report to show trains in the route when using detailed or very detailed.
- Bug #520 fixed. Actions Delayed Turnout and Delayed Sensor now toggle states correctly.
- Lengths of paths within a block can now be set individually.
- Fixed a bug in the Layout Editor, whereby a Cross-Over that has been snapped to grid then rotated by 90° fails to display correctly when the panel is reloaded. - KD
- Fixed an issue where WebThrottle could occasionally send unwanted emergency stops with LocoNet and CBUS systems. (Bug 516) - Randall Wood