Release Notes for JMRI 3.11.1 release
Date: January 11, 2015
From: Bob Jacobsen
Subject: Test version 3.11.1 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 first 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
This release has problems with:
- LocoNet connections using the LocoNet TCP Server (only, not local hardwired connections) may not work with old configuration files
- Crashes on startup if configured to connect via the NCE USB device to SB5 smart boosters
- Rebuilding the roster (from the Debug menu) can lose roster groups
- Strange sound slot names are displayed with LokSound Select decoders
- Operation manifests and switch lists won't preview or print unless there's a logo specified
- Some SoundTraxx decoders won't be recognized (fixed in JMRI 3.11.3)
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.
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 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 production release 3.10:
This release was built with Java 1.8, which is now required for JMRI.
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's more information in the migration section of the JMRI Tech Road Map.
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. Some tools, like the Single CV Programmer and the DecoderPro main windows, will also allow you to select which system to use instead of relying on just the default setting.
The Uhlenbrock Intellibox support has been improved:
- Enhancements to Loconet Monitor to parse the special IB-COM / Intellibox II CV programming messages.
- Implementation of CV programming through IB-COM / Intellibox II.
- Turnout control added for some Intellibox command stations
- Full handling of decoder functions beyond F8 from/to throttles for Intellibox-II.
- Partial handling of decoder functions beyond F8 from throttles for Intellibox-I with SW version 2.x (changes from IB-I keyboard not handled by throttle).
- Improvements in message transfer from and to the LocoNet connection
As part of this, the Fleishmann connection type has been merged into the Uhlenbrock type. If you are making a direct connection to your Intellibox unit via serial or USB, you will have to reselect your preferences. See the Uhlenbrock support page for instructions.
The aspects.xml file in each signal definition defines the speeds used for automated operation. These values are now required (by the schema check) for a valid XML file. Basic values have been added for all signal systems included in JMRI.
Egbert Broerse improved the signal-system and signal mast setup help files.
New / Updated decoder definitions
SoundTraxx now appears in the manufacturer list as "SoundTraxx (Throttle-Up)" instead of the original "Throttle-Up (SoundTraxx)". It's a long story....
Michael Mosher updated the TCS WOW definition.
Mathias Rufer and Dave Heap added an ESU LokPilot Standard V1.0 definition.
Dave Heap has completely redone the ESU Function Map pane to make it easier to read and use. It is now more like the LokProgrammer Function Map pane.
Dan Boudreau made the following changes to operations:
- When a car is placed at a spur, without a schedule, but with a custom load of type "Empty", the program now changes the car's load name to the default load name "L" rather than "E".
- Improvements to the "Timetable" window to allow the building, printing, and termination of selected trains. Also allows for the updating or printing of switch lists. This should help simplify things when building and terminating multiple sets of trains for a session.
- You can now print out all location and track comments using the print tool under "Locations".
- New switch list option to print out a new sheet of paper each time a train visits a location.
- The file path name for manifest and switch list logos are now stored as a relative path name.
Pete Cressman made the following changes to warrants:
- Fixed bug #481 "Warrant Logix not working as of 3.7.2". Warrants can be executed from Logix.
- Warrant command "Run Warrant" that allows one warrant to launch another is now fully implemented.