Date: May 10, 2015
From: Matthew Harris
Subject: Test version 3.11.6 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.
JMRI is now only available under the GNU General Public License. For more information, please see our copyright and licensing page.
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.
Downloading of JMRI 3.11.6 has been suspended due to discovery of a bug in Operations that could cause user data loss. See Known problems with this release above.
We are currently testing a fix for this problem and will release the JMRI 3.11.7 release as soon as possible.
Please do not use JMRI 3.11.6 for Operations.
Dave Heap made the following changes:
Dave Heap made the following changes:
Alain Le Marchand made a complete overhaul of the MRC Sound decoders:
Digikeijs (Digirails): Added definition for Function decoder DR80015 (Alain Le Marchand)
Hornby: Added definitions for Hornby TTS Class 37 and Class 40 (Nigel Cliffe)
Trix: Added definitions for Trix Sound HO BR V160 and BR 41 (Alain Le Marchand)
Dan Boudreau made the following changes to operations:
Paul Bender updated support for IdTag readers in Operations. Rolling Stock location and last moved date will now be automatically updated when an IdTag associated with the piece of rolling stock is seen by a reader associated with a location.