Release Notes for JMRI 3.11.4 release

Date: March 20, 2015

From: Bob Jacobsen

Subject: Test version 3.11.4 of JMRI/DecoderPro is available for download.

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

Known problems with this release

None at release time.

New warnings for this version:

Older warnings

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.

Download links:

Please use these links for downloading:

Mac OS X: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.3.11.4-r28907.dmg/download

Windows: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.3.11.4-r28907.exe/download

Linux: https://sourceforge.net/projects/jmri/files/test%20files/JMRI.3.11.4-r28907.tgz/download

Changes since test release 3.11.3:

Hardware Support

Uhlenbrock Intellibox
ESU - ECOS

Signals

Egbert Broerse improved the signaling system documentation

Balazs Racz: For single output signal head, whenever the underlying turnout changes (due to change in the turnout table, turnout feedback, or JMRI listening on the command bus and picking up a turnout change event), the signal head will adjust the displayed output. Also fixed a bug at JMRI startup: The single output signal head implementation was generating a turnout change command every time JMRI started up (at panel.xml load time).

Oscar Moutinho updated the DB-HV-1969 signals definition to improve speed control and icons

The signal speed definition has been updated for consistent operation. Also, a release test has been added to keep it that way.

New / Updated decoder definitions

Digitrax

Economy Serie 6: version (CV7) starts with 51 instead of 52 (Alain Le Marchand)

Doehler & Haass

Global update (Pierre Billon)

Miscellaneous

Add DCCconcepts Zen series of decoders (Alain Le Marchand)

Peter MacKenzie added definitions for the Hattons MD4 and Gaugemaster Opti DCC25 decoders.

Operations

Dan Boudreau made the following changes to operations:

Blocks

Preferences

A Warrants panel is added to Preferences. Warrants can now interpret the Aspect Speed Map four ways: % of Normal, % of Full Throttle, Miles per Hour or Kilometers per hour. A global Throttle Factor to aid trains in running at scale track speed is added. Also added is a combo box to set the layout scale. See the warrant's help documentation for details.

Warrants

Miscellaneous

The name of the active profile is displayed on the PanelPro main window and in the status bar on all Roster windows (including the DecoderPro 3 main window). (Randall Wood)

Fixed an issue where editing the DecoderPro 3 Preferences could cause the configuration to be corrupted or destroyed. (Randall Wood)

Lisby made an enhancement to the train tracking as implemented in Block.java: When the existing code has not been able to track the train, i.e. the train ID in terms of block value will be lost. The enhancement stores the candidate Blocks that a train may have arrived from when a block becomes occupied and then when a block becomes unoccupied, it informs its neighbors who can then choose to use their candidate list to determine where their train came from.