DESCRIPTION
JMRI: DecoderPro... Modern DCC decoders are complicated beasts to program. The simple idea of "put the address in CV01" doesn't cope well when you program complicated functions using combinations of bit patterns. A friendlier interface is needed. There are programs that provide better ways of programming specific decoders. Unfortunately, they are limited to specific types of computers, and only their authors can customize them for new types of decoders.
The DecoderPro symbolic programmer is meant to improve this. It is configured using text files, so that it can be adapted to additional decoder types easily. It talks to the decoders using the JMRI programming interface, so that it can run on any computer and layout hardware that JMRI has been ported to. It's freely available for download. And since the code is available via open source, if you want to improve on it you can.
WHAT'S NEW
Version 2.7.8:
- Lionel Jeanson added a window listing active throttles.
- The default memory limit on Mac OS X has been increased.
- Kevin Dickerson fixed a problem with multi-sensor icons.
- Randy McKenzie contributed some additional background images for CTC panels.
- XML input processing has been reworked. This shouldn't have any impact on users, but might effect people who have written scripts to read or write XML files. See the XmlFile JavaDoc for more information.
- Kevin Dickerson added features to add locos to the roster from an Ecos command station, and to add locos from the Ecos to the Roster.
- Kevin Dickerson fixed a problem using an SPROG command station with multiple layout connections.
- Nigel Cliffe contributed an update for the CT Elektronik SL version 40 decoder definition
- Nigel Cliffe contributed an update for the ZTC 471 decoder definition
- Paul Bender improved error handling and reporting for the XPressNet ops-mode programmer
- Giorgio Terdina added an Entry column to the Entry Point table in the Add/Edit Section window of the Section table to make it easier to set entry point direction.
- Dan Boudreau added code to detect and report when any changes occur to a train. He also improved save coverage when terminating the program.
- Kevin Dickerson added lunar signals to the Layout Editor.
- Paul Bender added ops mode programming for the Hornby command station.
- Lionel Jeanson added initial support for "Jynstruments", a was to extend the JMRI user interface with scripts. For more information, see the README file.
- Lionel Jeanson added a button so you can remove images from a roster entry.
- Lionel Jeanson did some code cleanup and minor fixes in the throttle GUI, and in the abstract throttle internal code.
- Lionel Jeanson improved the way release/dispatch is handled for multiple LocoNet throttles.
- John Plocher improved the DS54 help page.
- Peter Ulvestad added the Digitrax DZ123MO decoder.
- Lionel Jeanson fixed the multi-throttle release issue in LocoNet by better monitoring slot status in LocoNet Throttle.
- Kevin Dickerson made a number of internal changes to the layout and panel editors.
- Peter Ulvestad updated the Atlas Dual Mode and four function (342 and 345) decoder definitions to add the factory reset and update some limits and defaults.
- The "Send Problem Report" option in the main Help menu now works. The messages are filed in a dedicated Google group.
- Kevin Dickerson improved the file-load dialog so that it doesn't give an error message if the user cancels the load.
- Dan Boudreau made a small change in how operations staging works. Previously any car in staging could be assigned to a train. Now the cars in staging must also be serviced by the train being built. Also, users can name tracks using -number suffix. Suffix isn't printed for manifests or switch lists.
- Pete Cressman modified the create/edit dialogs for state variables and actions in Logix to organize them according to item type (e.g. Senors, turnouts, etc.). The column expandability has been somewhat improved.
- Pete Cressman added new sub-menu under "Tools - Tables" called "Occupancy Blocks". This is a sub-system for defining elements needed to run trains with automated commands through "Warrants". Some of the features of Warrants are:
- Routes can be determined by merely choosing the start and end points.
- Throttle commands are recorded in a "Learn Mode" that are then played back for automated running.
- Turnout and Signals are set automatically for automated running.
Warrants need to have the layout decribed in terms of the elements defined by the Occupancy Block Table. Although intended to operate with block detection, warrants can run trains without it, however in this case, there is no protection against misaligned turnouts or cornfield meets. Detailed information can be found in the Help files on the Occupancy Block Table menu.
REQUIREMENTS
- Mac OS X 10.4 or later
- You need to have a serial port available, either on the computer itself, or via a USB adapter. For more information, please see the download pages.
- You also need to have a serial connection to your DCC system. For more information, please see the DCC hardware pages.
|
|
