Jmri - User contributions [en]

Talk:Main Page

Admin — Wed, 22 Mar 2006 06:01:40 GMT

Admin:

No offence meant to the original author but what does everyone think about all the click 'here' style links?
Take a look at [http://www.cs.tut.fi/~jkorpela/www/click.html Why "Click here" is bad linking practice] for more information. Regards, Mark R.

Very good comment, and even better link - Thanks, I'll bear it mind. [And, no offense taken - If we're gonna do this, we're gonna need thick skin before it's 'right'!]

Most of the JMRI info is available on the JMRI site at sourceforge.net

Bob

== Where to place link to external sites? ==

I see it's a new site, congrats! I don't know anything about JMRI, otherwise I would contribute. I was wondering, where could I place a link to the DCCWiki ([http://wiki.dccforall.com/]). Any ideas? For now, I'll create a simple "References" type page, which feel free to change/delete/whatever. [[User:TazzyTazzy|TazzyTazzy]] 22:23, 13 March 2006 (PST)

== Will to add interwiki link to DCCWiki? ==

Was wondering if you would want to add an interwiki link to the DCCWiki. This would probaly help with doco since a statement like:

<nowiki>"For Digitrax systems, you will need to connect your [[dcc:LocoNet|LocoNet]] to your computer." or "The [[dcc:Command station|command station]] is used to route programming codes to the [[dcc:Decoder|decoder]]."</nowiki>

This would change the link from your Wiki to point to the DCCWiki where LocoNet (and other DCC topics) are already defined. This will be helpful because people could just simply use this for pretty much any general DCC (non-JMRI specific) topic so that people reading your wiki can quickly lookup items easier.

The alternative is to copy/recreate all the general DCC topics here.

Let me know what you decide, and if you need help doing this, let me know. [[User:TazzyTazzy|TazzyTazzy]] 23:06, 13 March 2006 (PST)

Mitch - Yes *please* help! And I wish this hadn't become 'My' Wiki all of a sudden! - It's *not* mine, I just tried to get the ball rolling, and your offer is willingly accepted - Go for it - We have no intention of duplicating what's already been done....

1.7.3 release notes

Admin — Wed, 22 Mar 2006 05:35:46 GMT

Admin: /* Digitrax Command Station Editor */

Please note that test version 1.7.3 is '''not''' yet generally available. This page will be updated with additional links when it is. In the meantime, the rest of this page is being developed in advance of the general release.

The [http://jmri.sf.net/releasenotes/jmri1.7.3.html original release note] contains a list of changes in the release. This page contains more recent information.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer-USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration. The LocoBuffer-USB is a "Plug and Play" device. This means that if it is not connected to the computer it does not exist to the software. Be sure that the drivers are installed and the LocoBuffer-USB is connected BEFORE starting JMRI or the startup will fail for lack of a connection, and the unit will not show up in the Preferences window.

==MacOS X with Locobuffer-USB==
For reasons that need not concern us here, there was an error in the original FTDI file for the LocoBuffer-USB. There is a patched version of the driver available on the RR-CirKits web site. [http://www.rr-cirkits.com/locobuffer-usb/osx/mac-patch.html here]
Be sure to download this file and use it instead of the driver that came on your driver CD if the disk is older than Rev E.

If you are using MacOS X 10.3.9 and QuickTime 7.0.4, you might encounter a problem getting JMRI 1.7.3 to start.
There are posts on the [http://groups.yahoo.com/group/jmriusers/ jmriusers discussion group] that talk about how to fix this:
*) [http://groups.yahoo.com/group/jmriusers/message/16832 Diagnosis and some workarounds]
*) [http://groups.yahoo.com/group/jmriusers/message/16837 How to fix the problem] using an [http://groups.yahoo.com/group/jmriusers/files/Update%20JMRI%20for%20QT%207.0.4%20and%20OS%20X%2010.3.9.zip AppleScript].

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows you to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your own risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to a Zephyr command station you should see (something like) --CS-- flash *very*briefly* in the command station display.

Main Page

Admin — Wed, 22 Mar 2006 05:32:24 GMT

Admin: Requested Windoze input.....

This Wiki is an attempt to document the extensive JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We've already had some great contributions from a few dedicated souls!

The JMRI project is aimed at building tools to help the model railroader employ computers to assist in using and running their layouts. We want it to be usable to as many people as possible, so we're building it in Java, which allows it to run on nearly any operating system and a wide range of hardware.

If you are new to DCC in general, the [http://wiki.dccforall.com/Main_Page DCCWiki] will prove very enlightening!

=What is the ''JMRI Suite''? Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

JMRI is a suite of programs which helps you get along with [[DCC]] easier. Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

- [[DecoderPro]] - For programming and managing decoders

- [[PanelPro]] - For running a layout

- [[LocoNet Tools]] - A set of Digitrax specific LocoNet Tools

- [[DispatcherPro]] - (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux. '''However''', experience tells us that you would be wise to study the
[[What do I need to run JMRI?]] link '''before''' actually downloading and trying to install the software.....

==Donations==
Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

==[[What do I need to run JMRI?]]==
In short, JRMI is a cross platform application. For full details, see: [[What do I need to run JMRI?]]

==[[Can I try the program without any layout connection?]]==

=Where next?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow. Note that although it appears MacOS users are happier to post their notes herein, the instructions that follow are also pretty much applicable to other operating systems..... It would still be nice if someone would add some Windows specific notes though.....[and Linux users don't need no stinkin' instructions :-) ]

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

Can I try the program without any layout connection?

Admin — Wed, 22 Mar 2006 05:02:37 GMT

Admin: rm'd "need for 1.6.1 before 1.7.3"

Yes.

If your computer does not have JAVA installed, download and install the latest version of JAVA from [http://java.sun.com/j2se/1.4.2/download.html Suns Java site].

THEN download and install the ''JMRI'' suite from [http://jmri.sourceforge.net/download/ here].

Start the program; set the preferences to "LocoNet Simulator" as a protocol. That's a simulated LocoNet connection which will allow you to play with all of the various capabilities.

Don't forget that the download is free, so there's no economic risk to trying it!

Main Page

Admin — Wed, 22 Mar 2006 04:42:15 GMT

Admin: /* 1.7.3 Release Notes */

This Wiki is an attempt to document the extensive JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We've already had some great contributions from a few dedicated souls!

The JMRI project is aimed at building tools to help the model railroader employ computers to assist in using and running their layouts. We want it to be usable to as many people as possible, so we're building it in Java, which allows it to run on nearly any operating system and a wide range of hardware.

If you are new to DCC in general, the [http://wiki.dccforall.com/Main_Page DCCWiki] will prove very enlightening!

=What is the ''JMRI Suite''? Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

JMRI is a suite of programs which helps you get along with [[DCC]] easier. Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

- [[DecoderPro]] - For programming and managing decoders

- [[PanelPro]] - For running a layout

- [[LocoNet Tools]] - A set of Digitrax specific LocoNet Tools

- [[DispatcherPro]] - (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux. '''However''', experience tells us that you would be wise to study the
[[What do I need to run JMRI?]] link '''before''' actually downloading and trying to install the software.....

==Donations==
Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

==[[What do I need to run JMRI?]]==
In short, JRMI is a cross platform application. For full details, see: [[What do I need to run JMRI?]]

==[[Can I try the program without any layout connection?]]==

=Where next?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

Main Page

Admin — Fri, 17 Mar 2006 16:51:48 GMT

Admin: Added link to the dccwiki

This Wiki is an attempt to document the extensive JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We've already had some great contributions from a few dedicated souls!

The JMRI project is aimed at building tools to help the model railroader employ computers to assist in using and running their layouts. We want it to be usable to as many people as possible, so we're building it in Java, which allows it to run on nearly any operating system and a wide range of hardware.

If you are new to DCC in general, the DCCWiki page [http://wiki.dccforall.com/Main_Page] will prove very enlightening!

=What is the ''JMRI Suite''? Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

JMRI is a suite of programs which helps you get along with [[DCC]] easier. Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

- [[DecoderPro]] - For programming and managing decoders

- [[PanelPro]] - For running a layout

- [[LocoNet Tools]] - A set of Digitrax specific LocoNet Tools

- [[DispatcherPro]] - (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux. '''However''', experience tells us that you would be wise to study the
[[What do I need to run JMRI?]] link '''before''' actually downloading and trying to install the software.....

==Donations==
Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

==[[What do I need to run JMRI?]]==
In short, JRMI is a cross platform application. For full details, see: [[What do I need to run JMRI?]]

==[[Can I try the program without any layout connection?]]==

=Where next?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

1.7.3 release notes

Admin — Wed, 22 Feb 2006 06:24:54 GMT

Admin: /* MacOS X with Locobuffer USB */

Please note that test version 1.7.3 is '''not''' yet generally available. This page will be updated with additional links when it is. In the meantime, the rest of this page is being developed in advance of the general release.

The [http://jmri.sf.net/releasenotes/jmri1.7.3.html original release note] contains a list of changes in the release. This page contains more recent information.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Download the Info.plist file [http://www.rr-cirkits.com/locobuffer-usb/osx/mac-patch.html from here]to this account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present) '''Note''' - When you select this file download link use a 'control-click' and ensure that the file is named 'Info.plist' - Some browsers will append a '.txt' extension if you're not careful, and that will break things. Also note Info.plist (first 'I' is uppercase....)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (3), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/

sudo touch /System/Library/Extensions

Note the 'space' between 'Info.plist' and '/System' in the first command line. [The other 'spaces' are hopefully easily read]

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to a Zephyr command station you should see (something like) --CS-- flash very briefly in the command station display.

1.7.3 release notes

Admin — Wed, 22 Feb 2006 06:24:02 GMT

Admin: /* MacOS X with Locobuffer USB */ Added Info.plist note

Please note that test version 1.7.3 is '''not''' yet generally available. This page will be updated with additional links when it is. In the meantime, the rest of this page is being developed in advance of the general release.

The [http://jmri.sf.net/releasenotes/jmri1.7.3.html original release note] contains a list of changes in the release. This page contains more recent information.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Download the Info.plist file [http://www.rr-cirkits.com/locobuffer-usb/osx/mac-patch.html from here]to this account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present) '''Note''' - When you select this file download link use a 'control-click' and ensure that the file is named 'Info.plist' - Some browsers will append a '.txt' extension if you're not careful, and that will break things. Also note Info.plist (first 'I' is uppercase....)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/

sudo touch /System/Library/Extensions

Note the 'space' between 'Info.plist' and '/System' in the first command line. [The other 'spaces' are hopefully easily read]

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to a Zephyr command station you should see (something like) --CS-- flash very briefly in the command station display.

LocoNet Tools

Admin — Wed, 22 Feb 2006 03:13:30 GMT

Admin:

These tools comprise some programs that you never knew you couldn't live without!

This page attempts to provide an overview of these tools:

==The Loconet Monitor==
If you want to know what is going on with your Loconet, this is the tool for you. Simply select 'Loconet -> Loconet monitor' and a window similar to this will open:

[[Image:Loconet-monitor.gif]]

Now, any Loconet traffic is displayed in this window pretty much as it happens - Pretty cool Huh! In fact, opening this tool and turning your layout power on is one of the best confirmations that all is well if you see the following:

- The power does indeed come on to your layout - ie, at least that's correct!

- "Global Power on" appears in the window - ie, your command station can communicate with your computer

Please note that if your Loconet is busy you're going to see '''lots''' of data flashing by. Hopefully the plain text nature of this display proves to be a wonderful help to you in terms of answering the 'what the heck is this thing doing?' questions. Enjoy.

==The Turnout Tool==

==The Turnout Table==

==Please add more==

LocoNet Tools

Admin — Wed, 22 Feb 2006 03:00:03 GMT

Admin: loconet monitor

These tools comprise some programs that you never knew you couldn't live without!

This page attempts to provide an overview of these tools:

==The Loconet Monitor==
If you want to know what is going on with your Loconet, this is the tool for you. Simply select 'Loconet -> Loconet monitor' and a window similar to this will open:

[[Image:Loconet-monitor.gif]]

Now, any Loconet traffic is displayed in this window pretty much as it happens - Pretty cool Huh! In fact, opening this tool and turning your layout power on is one of the best confirmations that all is well if you see the following:

- The power does indeed come on to your layout - ie, at least '''that's''' correct!

- "Global Power on" appears in the window - ie, your command station can communicate with your computer

File:Loconet-monitor.gif

Admin — Wed, 22 Feb 2006 02:48:04 GMT

Admin:

LocoNet Tools

Admin — Wed, 22 Feb 2006 02:37:45 GMT

Admin:

LocoNet Tools

Admin — Wed, 22 Feb 2006 02:23:02 GMT

Admin:

These tools comprise some programs that you never knew you couldn't live without!

This page attempts to provide an overview of these tools:

==The Loconet Monitor==

Main Page

Admin — Wed, 22 Feb 2006 00:46:41 GMT

Admin:

This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''? Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

- [[DecoderPro]] - For programming and managing decoders

- [[PanelPro]] - For running a layout

- [[LocoNet Tools]] - A set of Digitrax specific LocoNet Tools

- [[DispatcherPro]] - (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux. '''However''', experience tells us that you would be wise to study the
[[What do I need to run JMRI?]] link '''before''' actually downloading and trying to install the software.....

==[[What do I need to run JMRI?]]==

==[[Can I try the program without any layout connection?]]==

=Where next?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

1.7.3 release notes

Admin — Wed, 22 Feb 2006 00:43:07 GMT

Admin:

The 'official' release notes are on the Sourceforge pages somewhere, but I can't find 'em! - If you do, please update to a link here - Thanks.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Copy Kevin's Info.plist file [http://rr-cirkits.com/ from here]to the account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/

sudo touch /System/Library/Extensions

Note the 'space' between 'Info.plist' and '/System' in the first command line. [The other 'spaces' are hopefully easily read]

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to a Zephyr command station you should see (something like) --CS-- flash very briefly in the command station display.

1.7.3 release notes

Admin — Wed, 22 Feb 2006 00:39:06 GMT

Admin:

The 'official' release notes are on the Sourceforge pages somewhere, but I can't find 'em! - If you do, please update to a link here - Thanks.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Copy Kevin's Info.plist file [http://rr-cirkits.com/ from here]to the account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/

sudo touch /System/Library/Extensions

Note the 'space' between 'Info.plist and '/System' as well as between 'touch' and '/System' in the above command lines!

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to a Zephyr command station you should see (something like) --CS-- flash very briefly in the command station display.

DecoderPro

Admin — Wed, 22 Feb 2006 00:13:40 GMT

Admin:

Is, quote, "a better tool for programming decoders. DecoderPro simplifies the job of configuring complicated DCC decoders by providing screens on which you can select the various options and values you want."

In other words, it's a collection of screens with input buttons, boxes, sliders and the like that display data as read from, or which may be written to, your decoders. This visual approach hides the complexity of calculating hex values and programming with arcane single button commands. Furthermore, a '''huge''' number of decoders are 'known' by the system, thereby ensuring only relevant options and settings are permitted. For exampe, options in a QSI sound decoder are very different to the options in a Digitrax DZ123.

This page assumes you already have a working installation. If not, please refer to the relevant section in [[JMRI Preferences setup]] for instructions. Note that until you can start Decoderpro and the initial screen says something like that shown below that '''there is no point in proceeding'''.

[[Image:DP-welcome.gif]]

Given a working install its probably best to start by reading the data from your existing decoders into the program.

Having done that, you can start changing things. Oh, you want to know how to do that!? :-)

The notes that follow are from my install using a Digitrax Zephyr, MacOSX on a Powerbook G4 and a LocoBuffer II connected via a Keyspan adaptor to a USB port. However, as long as you have a working installation pretty much everything is platform and OS indepedent and should therefore apply equally to people using Windows PCs and Linux.

==Programming using a programming track==

The Zephyr (and many others) have seperate outputs to feed an isolated programming track. This isolated track can be as simple as a section of track connected to the programming outputs on the command station with a couple of test leads through to a siding connected to the main layout via insulating joiners and a DPDT switch. The DPDT passes regular track power in one position and the programming outputs in the other. [See the 'discussion' page (above) for some notes on this setup.]

Whatever approach you take, selecting 'Program on programming track' will open this window:

[[Image:programmer setup.gif]]

Once you have this screen up, put (or drive, on the layout!) a decoder equipped loco onto your programming track and click the '''lower''' of the two 'ident' buttons. This 'probes' the decoder in an attempt to discover the manufacturer id and model id numbers. In general, it's pretty good at finding the correct one, but sometimes it appears to misidentify your decoder [Digitrax DHs are identified as DZ's for example] - This is not an issue as other than their power handling capability they are indeed the same decoder, and hence have the same programming options.] Once Decoderpro has indetified the decoder, you can open the programmer itself.

Surprisingly enough, you do this with the 'Open Programmer' button at the bottom of setup screen :-). I have also always chosen the 'comprehensive' option, just because I'm like that I guess :-) [Same as always selecting 'custom' versus 'auto' install - You learn more that way IMHO.] More on the differences between basic and comprehensive options is on the [[basic-v-comprehensive]] page. In any event, a window very similar to that below should open:

[[Image:roster-empty.gif]]

'''Note''' that the exact 'tabs' at the top of the window will vary depending on which decoder has been detected. This page also allows you to complete the [[RosterEntry]] for this loco. Many words have been written on different ways to complete this (hopefully some of them will be discussed in the 'discussion' page above?) but here's what I entered:

[[Image:roster-editted.gif]]

Do a '''Save''' at this point! - Next time you want to program this loco you can now use the 'ident[ify]' loco button and the program will automagically load everything it thinks it knows about this loco. However, as of right now, all we've done is identify the decoder in the sucker - Next step is (IMHO, again, this can be debated) to "read all sheets". This can take a while, but you should be seeing activity in the bottom of the screen as different CV's are read from the decoder. Many locos also flash their lights and jerk along the track at this point - In some instances far enough that they'll fall right off the end of the track (don't ask)..... Also remember we're trying to transfer a bunch of data over the worst possible connection example - Some wheels resting on a flat rail.... You may see messages along the lines of 'no acknowledge from loco', 'timeout' etc - If you've been watching your Locobuffer you've also noticed the Loconet data led flashes whenever the program 'wants' another CV value.

If it all suddenly "stops working" (no acknowledge etc), a gentle prod from the old 0-5-0 normally gets things going again - Remember the horrible path the data has to flow! - It will get there in the end! - And when it does, do another 'SAVE' pretty darn quick! You now have a [[RosterEntry]] in the computer that shows exactly how the decoder is currently programmed. Life is good :-)

However, now the fun really begins because you can start a clickin' on them tabs and changin' things!

Changing a locos address is illustrated in the [[address change]] example.

RosterEntry

Admin — Wed, 22 Feb 2006 00:10:37 GMT

Admin:

Once [ident]ified by DecoderPro all the details of the currrent setup are stored in a file named <loco_id>.xml where <loco-id> is whatever you put in to that field.

If your locos ever get 'reprogrammed' (typically on another layout) or, as is often reported, simply ''go crazy for no reason'' it is an easy task to 'write all sheets' back to the offending loco and thereby return it to a sane state. DecoderPro also includes the usual tools to print and view roster entries.

DecoderPro

Admin — Wed, 22 Feb 2006 00:02:15 GMT

Admin:

Is, quote, "a better tool for programming decoders. DecoderPro simplifies the job of configuring complicated DCC decoders by providing screens on which you can select the various options and values you want."

In other words, it's a collection of screens with input buttons, boxes, sliders and the like that display data as read from, or which may be written to, your decoders. This visual approach hides the complexity of calculating hex values and programming with arcane single button commands. Furthermore, a '''huge''' number of decoders are 'known' by the system, thereby ensuring only relevant options and settings are permitted. For exampe, options in a QSI sound decoder are very different to the options in a Digitrax DZ123.

This page assumes you already have a working installation. If not, please refer to the relevant section in [[JMRI Preferences setup]] for instructions. Note that until you can start Decoderpro and the initial screen says something like that shown below that '''there is no point in proceeding'''.

[[Image:DP-welcome.gif]]

Given a working install its probably best to start by reading the data from your existing decoders into the program.

Having done that, you can start changing things. Oh, you want to know how to do that!? :-)

The notes that follow are from my install using a Digitrax Zephyr, MacOSX on a Powerbook G4 and a LocoBuffer II connected via a Keyspan adaptor to a USB port. However, as long as you have a working installation pretty much everything is platform and OS indepedent and should therefore apply equally to people using Windows PCs and Linux.

==Programming using a programming track==

The Zephyr (and many others) have seperate outputs to feed an isolated programming track. This isolated track can be as simple as a section of track connected to the programming outputs on the command station with a couple of test leads through to a siding connected to the main layout via insulating joiners and a DPDT switch. The DPDT passes regular track power in one position and the programming outputs in the other. [See the 'discussion' page (above) for some notes on this setup.]

Whatever approach you take, selecting 'Program on programming track' will open this window:

[[Image:programmer setup.gif]]

Once you have this screen up, put (or drive, on the layout!) a decoder equipped loco onto your programming track and click the '''lower''' of the two 'ident' buttons. This 'probes' the decoder in an attempt to discover the manufacturer id and model id numbers. In general, it's pretty good at finding the correct one, but sometimes it appears to misidentify your decoder [Digitrax DHs are identified as DZ's for example] - This is not an issue as other than their power handling capability they are indeed the same decoder, and hence have the same programming options.] Once Decoderpro has indetified the decoder, you can open the programmer itself.

Surprisingly enough, you do this with the 'Open Programmer' button at the bottom of setup screen :-). I have also always chosen the 'comprehensive' option, just because I'm like that I guess :-) [Same as always selecting 'custom' versus 'auto' install - You learn more that way IMHO.] More on the differences between basic and comprehensive options is on the [[basic-v-comprehensive]] page. In any event, a window very similar to that below should open:

[[Image:roster-empty.gif]]

'''Note''' that the exact 'tabs' at the top of the window will vary depending on which decoder has been detected. This page also allows you to complete the [[RosterEntry]] for this loco. Many words have been written on different ways to complete this (hopefully some of them will be discussed in the 'discussion' page above?) but here's what I entered:

[[Image:roster-editted.gif]]

Do a '''Save''' at this point! - Next time you want to program this loco you can now use the 'ident[ify]' loco button and the program will automagically load everything it thinks it knows about this loco. However, as of right now, all we've done is identify the decoder in the sucker - Next step is (IMHO, again, this can be debated) to "read all sheets". This can take a while, but you should be seeing activity in the bottom of the screen as different CV's are read from the decoder. Many locos also flash their lights and jerk along the track at this point - In some instances far enough that they'll fall right off the end of the track (don't ask)..... Also remember we're trying to transfer a bunch of data over the worst possible connection example - Some wheels resting on a flat rail.... You may see messages along the lines of 'no acknowledge from loco', 'timeout' etc - If you've been watching your Locobuffer you've also noticed the Loconet data led flashes whenever the program 'wants' another CV value.

If it all suddenly "stops working" (no acknowledge etc), a gentle prod from the old 0-5-0 normally gets things going again - Remember the horrible path the data has to flow! - It will get there in the end! - And when it does, do another 'SAVE' pretty darn quick! You now have a [[roster entry]] in the computer that shows exactly how the decoder is currently programmed. Life is good :-)

However, now the fun really begins because you can start a clickin' on them tabs and changin' things!

Changing a locos address is illustrated in the [[address change]] example.

Main Page

Admin — Tue, 21 Feb 2006 23:50:57 GMT

Admin:

This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''? Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

- [[DecoderPro]] - For programming and managing decoders

- [[PanelPro]] - For running a layout

- [[LocoNet Tools]] - A set of Digitrax specific LocoNet Tools

- [[DispatcherPro]] - (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux. '''However''', experience tells us that you would be wise to study the
[[What do I need to run JMRI?]] link '''before''' actually downloading and trying to install the software.....

==[[What do I need to run JMRI?]]==

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

Main Page

Admin — Tue, 21 Feb 2006 23:49:27 GMT

Admin: added more internal links

This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''? Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

- [[DecoderPro]] - For programming and managing decoders

- [[PanelPro]] - For running a layout

- [[LocoNet Tools]] - A set of Digitrax specific LocoNet Tools

- [[DispatcherPro]] - (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux. '''However''', experience tells us that you would be wise to study the
[[What do I need to run JMRI?]] link '''before''' actually downloading and trying to install the software.....

==[[What do I need to run JMRI?]]==

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

An [[DecoderPro|introduction to Decoderpro]] page also exists, but you couldn't get there-from-here....

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

1.7.3 release notes

Admin — Tue, 21 Feb 2006 23:06:33 GMT

Admin:

The 'official' release notes are on the Sourceforge pages somewhere, but I can't find 'em! - If you do, please update to a link here - Thanks.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Copy Kevin's Info.plist file [http://rr-cirkits.com/ from here]to the account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/
sudo touch /System/Library/Extensions

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to the command station you should see (something like) --CS-- flash very briefly in the command station display.

Address change

Admin — Tue, 21 Feb 2006 23:03:24 GMT

Admin:

This is usually one of the first tasks performed on a 'new' decoder equipped Loco. Hopefully, details of the decoder and the Loco have already been saved, as illustrated on the [[DecoderPro]] page. Clicking on the 'Basic' tab should open this window:

[[Image:Dp-basic.gif]]

All that is needed is to decide if you want 2 or 4 digit addressing, and to enter the correct address in the correct box! - No need to worry about which CV's are involved!

Note that JMRI makes extensive use of colors to try and give you information:

#White Is used when the program is sure that the data it is displaying is the same as that contained in the decoder.
#Yellow is used when the program isn't sure - ie, if it has been read from a roster entry and not compared with the data actually in the decoder. This is the reason the input boxes will be yellow until you do a 'read full sheet' for example.
#Red is used for data that the program 'knows' to be different from that stored in the Decoder. Hence, when you change data in JMRI you will see it turn red when you do a 'write', and then back to white after a successful write.

The other options on this screen should be fairly self explanatory and should be set in accordance with whatever you want! For example, if you want to reverse the direction your loco moves when you select 'forward' or 'reverse' on your throttle, simply change the 'NDOT' box and '''write''' the sheet.

That's it! - As long as the input boxes display the address (etc) that you're expecting, and are white in color, you're done and can continue with changes to the other sheets. Sheets available vary depending on the Decoder detected, so go ahead and select 'em and see what you can find!

As with all things computer based, it's a really good idea to 'save' the data '''just''' before the computer and/or software crashes :-) Assuming you can't do that, save it at whatever point you will be upset if you lose the changes you've made and/or you want to be able to back up to a previous known 'sane' state.

1.7.3 release notes

Admin — Tue, 21 Feb 2006 22:51:40 GMT

Admin: Addded link to RR-Cirkits for 'info.plist' file

=Release Notes - JMRI 1.7.3=
The 'official' release notes are on the Sourceforge pages somewhere, but I can't find 'em! - If you do, please update to a link here - Thanks.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Copy Kevin's Info.plist file [http://rr-cirkits.com/ from here]to the account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/
sudo touch /System/Library/Extensions

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to the command station you should see (something like) --CS-- flash very briefly in the command station display.

Address change

Admin — Tue, 21 Feb 2006 22:22:35 GMT

Admin:

Address change

Admin — Tue, 21 Feb 2006 22:21:11 GMT

Admin: Added 'Basic' prog pane

File:Dp-basic.gif

Admin — Tue, 21 Feb 2006 22:17:25 GMT

Admin:

DecoderPro

Admin — Tue, 21 Feb 2006 22:03:37 GMT

Admin:

Is, quote, "a better tool for programming decoders. DecoderPro simplifies the job of configuring complicated DCC decoders by providing screens on which you can select the various options and values you want."

In other words, it's a collection of screens with input buttons, boxes, sliders and the like that display data as read from, or which may be written to, your decoders. This visual approach hides the complexity of calculating hex values and programming with arcane single button commands. Furthermore, a '''huge''' number of decoders are 'known' by the system, thereby ensuring only relevant options and settings are permitted. For exampe, options in a QSI sound decoder are very different to the options in a Digitrax DZ123.

This page assumes you already have a working installation. If not, please refer to the relevant section in [[JMRI Preferences setup]] for instructions. Note that until you can start Decoderpro and the initial screen says something like that shown below that '''there is no point in proceeding'''.

[[Image:DP-welcome.gif]]

Given a working install its probably best to start by reading the data from your existing decoders into the program.

Having done that, you can start changing things. Oh, you want to know how to do that!? :-)

The notes that follow are from my install using a Digitrax Zephyr, MacOSX on a Powerbook G4 and a LocoBuffer II connected via a Keyspan adaptor to a USB port. However, as long as you have a working installation pretty much everything is platform and OS indepedent and should therefore apply equally to people using Windows PCs and Linux.

==Programming using a programming track==

The Zephyr (and many others) have seperate outputs to feed an isolated programming track. This isolated track can be as simple as a section of track connected to the programming outputs on the command station with a couple of test leads through to a siding connected to the main layout via insulating joiners and a DPDT switch. The DPDT passes regular track power in one position and the programming outputs in the other. [See the 'discussion' page (above) for some notes on this setup.]

Whatever approach you take, selecting 'Program on programming track' will open this window:

[[Image:programmer setup.gif]]

Once you have this screen up, put (or drive, on the layout!) a decoder equipped loco onto your programming track and click the '''lower''' of the two 'ident' buttons. This 'probes' the decoder in an attempt to discover the manufacturer id and model id numbers. In general, it's pretty good at finding the correct one, but sometimes it appears to misidentify your decoder [Digitrax DHs are identified as DZ's for example] - This is not an issue as other than their power handling capability they are indeed the same decoder, and hence have the same programming options.] Once Decoderpro has indetified the decoder, you can open the programmer itself.

Surprisingly enough, you do this with the 'Open Programmer' button at the bottom of setup screen :-). I have also always chosen the 'comprehensive' option, just because I'm like that I guess :-) [Same as always selecting 'custom' versus 'auto' install - You learn more that way IMHO.] More on the differences between basic and comprehensive options is on the [[basic-v-comprehensive]] page. In any event, a window very similar to that below should open:

[[Image:roster-empty.gif]]

'''Note''' that the exact 'tabs' at the top of the window will vary depending on which decoder has been detected. This page also allows you to complete the [[RosterEntry]] for this loco. Many words have been written on different ways to complete this (hopefully some of them will be discussed in the 'discussion' page above?) but here's what I entered:

[[Image:roster-editted.gif]]

Do a '''Save''' at this point! - Next time you want to program this loco you can now use the 'ident[ify]' loco button and the program will automagically load everything it thinks it knows about this loco. However, as of right now, all we've done is identify the decoder in the sucker - Next step is (IMHO, again, this can be debated) to "read all sheets". This can take a while, but you should be seeing activity in the bottom of the screen as different CV's are read from the decoder. Many locos also flash their lights and jerk along the track at this point - In some instances far enough that they'll fall right off the end of the track (don't ask)..... Also remember we're trying to transfer a bunch of data over the worst possible connection example - Some wheels resting on a flat rail.... You may see messages along the lines of 'no acknowledge from loco', 'timeout' etc - If you've been watching your Locobuffer you've also noticed the Loconet data led flashes whenever the program 'wants' another CV value.

If it all suddenly "stops working" (no acknowledge etc), a gentle prod from the old 0-5-0 normally gets things going again - Remember the horrible path the data has to flow! - It will get there in the end! - And when it does, do another 'SAVE' pretty darn quick! You now have a [[roster entry]] in the computer that shows exactly how the decoder is currently programmed. Life is good :-)

However, now the fun really begins because you can start a clickin' on them tabs and changin' things!

Changing a locos address is illustrated in the [[address change]] example coming soon.

JMRI Preferences setup

Admin — Tue, 21 Feb 2006 22:02:14 GMT

Admin:

In general, if things are working as expected, you shouldn't need to change any of the settings herein. However, if this is not the case, please read on....

After you have started any of the JMRI programs you can access this page via the usual 'file -> preferences' or similar choice - Something similar to this window should open:

[[Image:prefs.gif]]

Clicking on the 'layout connection' box will open a list of ways that the program supports connecting to your layout. Hopefully you can find the relevant option in this list - Select it and '''save'''.

Hopefully the remaining options can be figured out from a combination of your user manuals and common sense! [No offense, but if you don't know what command staton you're using we probably can't help :-) ]

Once these are set appropriately, you should be able to get to the 'start screen' shown in the [[DecoderPro]] page without either option being 'greyed out'

FAQ

Admin — Tue, 21 Feb 2006 21:58:56 GMT

Admin: added upgrading note

This FAQ should be the first place to check for answers to your questions. Many times the answer is hidden in the mists of our [http://groups.yahoo.com/group/jmriusers Yahoo group archives]. Hopefully this page will help clear that mist!

==How can I upgrade?==

Every release of JMRI is carefully tested to try and ensure compatability with previous releases. To quote Bob:

Backups are always good!!

Your config files, roster, etc, are stored in ~/Library/Preferences/JMRI (That's your own Library folder, in your home directory) If you make a copy of that, you've got everything that might get damaged if something Really Bad happens. But nothing like that is _supposed_ to happen; since JMRI 1.0 all formats have been (and will be, I hope) backward compatible. Note that they're not _forward_ compatible; if you create a new panel in N+1, you might not be able to read it in version N (or you might, there are just no guarantees)

==No Loco Detected==
With thanks to Paul Bender for the following notes:

Basically, the error "no loco detected" means that the decoder didn't
respond when the command station sent out the programming request. On a
Lenz system, this is the same as getting an "Error 2" when programming
from a hand held throttle.

One possible cause of this is that the CV requested isn't actually
defined in the decoder. See if you can read the problem CV using a hand
held throttle. If you get the same result on the handheld, then the CV
may not actually be defined.

==Timeout talking to command station==
This message is saying that your command station and JMRI are not communicating. Typical causes are incorrect 'com' port settings, baud rate, and other arcane H/W stuff that is discussed in, at present, various different places unfortunately. If the program is starting up, but the programming options are 'greyed out' the [[JMRI Preferences setup]] page may be able to help.

JMRI Preferences setup

Admin — Tue, 21 Feb 2006 21:40:45 GMT

Admin:

DecoderPro

Admin — Tue, 21 Feb 2006 21:32:07 GMT

Admin: changed debugging link to prefs setup

==DecoderPro==
Is, quote, "a better tool for programming decoders. DecoderPro simplifies the job of configuring complicated DCC decoders by providing screens on which you can select the various options and values you want."

In other words, it's a collection of screens with input buttons, boxes, sliders and the like that display data as read from, or which may be written to, your decoders. This visual approach hides the complexity of calculating hex values and programming with arcane single button commands. Furthermore, a '''huge''' number of decoders are 'known' by the system, thereby ensuring only relevant options and settings are permitted. For exampe, options in a QSI sound decoder are very different to the options in a Digitrax DZ123.

This page assumes you already have a working installation. If not, please refer to the relevant section in [[JMRI Preferences setup]] for instructions. Note that until you can start Decoderpro and the initial screen says something like that shown below that '''there is no point in proceeding'''.

[[Image:DP-welcome.gif]]

Given a working install its probably best to start by reading the data from your existing decoders into the program.

Having done that, you can start changing things. Oh, you want to know how to do that!? :-)

The notes that follow are from my install using a Digitrax Zephyr, MacOSX on a Powerbook G4 and a LocoBuffer II connected via a Keyspan adaptor to a USB port. However, as long as you have a working installation pretty much everything is platform and OS indepedent and should therefore apply equally to people using Windows PCs and Linux.

==Programming using a programming track==

The Zephyr (and many others) have seperate outputs to feed an isolated programming track. This isolated track can be as simple as a section of track connected to the programming outputs on the command station with a couple of test leads through to a siding connected to the main layout via insulating joiners and a DPDT switch. The DPDT passes regular track power in one position and the programming outputs in the other. [See the 'discussion' page (above) for some notes on this setup.]

Whatever approach you take, selecting 'Program on programming track' will open this window:

[[Image:programmer setup.gif]]

Once you have this screen up, put (or drive, on the layout!) a decoder equipped loco onto your programming track and click the '''lower''' of the two 'ident' buttons. This 'probes' the decoder in an attempt to discover the manufacturer id and model id numbers. In general, it's pretty good at finding the correct one, but sometimes it appears to misidentify your decoder [Digitrax DHs are identified as DZ's for example] - This is not an issue as other than their power handling capability they are indeed the same decoder, and hence have the same programming options.] Once Decoderpro has indetified the decoder, you can open the programmer itself.

Surprisingly enough, you do this with the 'Open Programmer' button at the bottom of setup screen :-). I have also always chosen the 'comprehensive' option, just because I'm like that I guess :-) [Same as always selecting 'custom' versus 'auto' install - You learn more that way IMHO.] More on the differences between basic and comprehensive options is on the [[basic-v-comprehensive]] page. In any event, a window very similar to that below should open:

[[Image:roster-empty.gif]]

'''Note''' that the exact 'tabs' at the top of the window will vary depending on which decoder has been detected. This page also allows you to complete the [[RosterEntry]] for this loco. Many words have been written on different ways to complete this (hopefully some of them will be discussed in the 'discussion' page above?) but here's what I entered:

[[Image:roster-editted.gif]]

Do a '''Save''' at this point! - Next time you want to program this loco you can now use the 'ident[ify]' loco button and the program will automagically load everything it thinks it knows about this loco. However, as of right now, all we've done is identify the decoder in the sucker - Next step is (IMHO, again, this can be debated) to "read all sheets". This can take a while, but you should be seeing activity in the bottom of the screen as different CV's are read from the decoder. Many locos also flash their lights and jerk along the track at this point - In some instances far enough that they'll fall right off the end of the track (don't ask)..... Also remember we're trying to transfer a bunch of data over the worst possible connection example - Some wheels resting on a flat rail.... You may see messages along the lines of 'no acknowledge from loco', 'timeout' etc - If you've been watching your Locobuffer you've also noticed the Loconet data led flashes whenever the program 'wants' another CV value.

If it all suddenly "stops working" (no acknowledge etc), a gentle prod from the old 0-5-0 normally gets things going again - Remember the horrible path the data has to flow! - It will get there in the end! - And when it does, do another 'SAVE' pretty darn quick! You now have a [[roster entry]] in the computer that shows exactly how the decoder is currently programmed. Life is good :-)

However, now the fun really begins because you can start a clickin' on them tabs and changin' things!

Changing a locos address is illustrated in the [[address change]] example coming soon.

JMRI Preferences setup

Admin — Tue, 21 Feb 2006 21:19:26 GMT

Admin:

JMRI Preferences setup

Admin — Tue, 21 Feb 2006 21:18:07 GMT

Admin:

File:Prefs.gif

Admin — Tue, 21 Feb 2006 21:12:54 GMT

Admin: JMRI preferences screen shot

JMRI preferences screen shot

Main Page

Admin — Tue, 21 Feb 2006 21:04:37 GMT

Admin:

=Whats this?=
This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''?, Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

-- DecoderPro (to program decoders)
-- PanelPro (to run a layout)
-- LocoNet Tools (a set of Digitrax specific LocoNet Tools)
-- DispatcherPro (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux.

=[[What do I need to run JMRI?]]=

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

An [[DecoderPro|introduction to Decoderpro]] page also exists, but you couldn't get there-from-here....

=FAQ=
The [[FAQ]] page (will) contain(s) some notes on upgrading from previous releases and other useful 'tidbits'.

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news.

Can I try the program without any layout connection?

Admin — Tue, 21 Feb 2006 21:02:07 GMT

Admin:

Yes.

If your computer does not have JAVA installed, download and install the latest version of JAVA from [http://java.sun.com/j2se/1.4.2/download.html Suns Java site].

THEN download and install the ''JMRI'' suite from [http://jmri.sourceforge.net/download/ here].

at present it is necessary to download and install ''JMRI'' version 1.6.1
before installing any later version

Start the program; set the preferences to "LocoNet Hexfile" as a protocol. That's a simulated LocoNet connection which will allow you to play with all of the various capabilities.

Don't forget that the download is free, so there's no economic risk to trying it!

FAQ

Admin — Tue, 21 Feb 2006 20:58:41 GMT

Admin:

This FAQ should be the first place to check for answers to your questions. Many times the answer is hidden in the mists of our [http://groups.yahoo.com/group/jmriusers Yahoo group archives]. Hopefully this page may help those mists clear!

==No Loco Detected==
With thanks to Paul Bender for the following notes:

Basically, the error "no loco detected" means that the decoder didn't
respond when the command station sent out the programming request. On a
Lenz system, this is the same as getting an "Error 2" when programming
from a hand held throttle.

One possible cause of this is that the CV requested isn't actually
defined in the decoder. See if you can read the problem CV using a hand
held throttle. If you get the same result on the handheld, then the CV
may not actually be defined.

==Timeout talking to command station==
This message is saying that your command station and JMRI are not communicating. Typical causes are incorrect 'com' port settings, baud rate, and other arcane H/W stuff that is discussed in, at present, various different places unfortunately. If the program is starting up, but the programming options are 'greyed out' the [[JMRI Preferences setup]] page may be able to help.

FAQ

Admin — Tue, 21 Feb 2006 20:56:42 GMT

Admin: Addded timeout-talking-to-cmd-stn notes/link

This FAQ should be the first place to check for answers to your questions. Many times the answer is hidden in the mists of our [http://groups.yahoo.com/group/jmriusers Yahoo group archives]. Hopefully this page may help those mists clear!

==No Loco Detected==
With thanks to Paul Bender for the following notes:

Basically, the error "no loco detected" means that the decoder didn't
respond when the command station sent out the programming request. On a
Lenz system, this is the same as getting an "Error 2" when programming
from a hand held throttle.

One possible cause of this is that the CV requested isn't actually
defined in the decoder. See if you can read the problem CV using a hand
held throttle. If you get the same result on the handheld, then the CV
may not actually be defined.

==Timeout talking to command station==
This message is saying that your command stationand JMRI are not communicating. Typical causes are incorrect 'com' port settings, baud rate, and other arcane H/W stuff that is discussed in, at present, various different places. If the program is starting up, but the programming option are 'greyed out' the [JMRI Preferences setup] page may be able to help.

FAQ

Admin — Tue, 21 Feb 2006 20:42:04 GMT

Admin:

This FAQ should be the first place to check for answers to your questions. Many times the answer is hidden in the mists of our [http://groups.yahoo.com/group/jmriusers Yahoo group archives]. Hopefully this page may help those mists clear!

==No Loco Detected==
With thanks to Paul Bender for the following notes:

Basically, the error "no loco detected" means that the decoder didn't
respond when the command station sent out the programming request. On a
Lenz system, this is the same as getting an "Error 2" when programming
from a hand held throttle.

One possible cause of this is that the CV requested isn't actually
defined in the decoder. See if you can read the problem CV using a hand
held throttle. If you get the same result on the handheld, then the CV
may not actually be defined.

==Timeout talking to command station==
Anyone?

Main Page

Admin — Tue, 21 Feb 2006 20:25:42 GMT

Admin: Added FAQ link

Loconet simulator

Admin — Tue, 21 Feb 2006 20:22:46 GMT

Admin:

This used to be known as the 'Loconet Hexfile' but that:

a - Wasn't very descriptive and

b - Scared people! :-)

Hence, it is now known by this new name, but still achieves the same goals of allowing you to run JMRI without being connected to a command station.

Loconet simulator

Admin — Tue, 21 Feb 2006 20:22:26 GMT

Admin:

This used to be known as the 'Loconet Hexfile' but that:

a - Wasn't very descriptive and
b - Scared people! :-)

Hence, it is now known by this new name, but still achieves the same goals of allowing you to run JMRI without being connected to a command station.

1.7.3 release notes

Admin — Tue, 21 Feb 2006 20:18:08 GMT

Admin: CS editor notes added

=Release Notes - JMRI 1.7.3=
The 'official' release notes are on the Sourceforge pages somewhere, but I can't find 'em! - If you do, please update to a link here - Thanks.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Copy Kevin's Info.plist file to the account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/
sudo touch /System/Library/Extensions

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

==Digitrax Command Station Editor==
This is a new feature in this release. Opened from the 'tools' menu it allows to program (mess up?) your command station from within JMRI. Unfortunately, Digitrax' naming convention and defaults for these options remains about as clear as mud, so use at your ownn risk, probably only after saving the current configuration.

Also note, it reads and writes these values '''very''' quickly, so it's probably working even if you think it isn't! (Don't ask) - When you '''write''' anything back to the command station you should see (something like) --CS-- flash very briefly in the command station display.

1.7.3 release notes

Admin — Tue, 21 Feb 2006 19:56:37 GMT

Admin: XP drivers & Mac LBUSB notes

=Release Notes - JMRI 1.7.3=
The 'official' release notes are on the Sourceforge pages somewhere, but I can't find 'em! - If you do, please update to a link here - Thanks.

Recent experience suggests that you need to be aware of a few ''gotcha's'' if you're installing for the first time. Specifically:

==Windows XP with Locobuffer USB==
An important [http://rr-cirkits.com/locobuffer-usb/XP-driver-install.html note] about this configuration.

==MacOS X with Locobuffer USB==
For reasons that need not concern us here, this configuration needs a little fancy footwork in order to work correctly. Thanks, as always, to Bob and in this particular case, Kevin Avery for the workround:

# Sign into the administrator account on the computer. If there's only one user account, you're already all set. If not, you may need to logout and login under a different name; the administrator account is the one normally used to do software updates.
# Copy Kevin's Info.plist file to the account's Documents folder. (This is because we need to be able to find it from the Terminal, and that's a well-known location always present)
#Open the Terminal application from either the Applications or Applications/Utilities folders, depending on your MacOS X version.
# Run the FTDI installer. When it asks you to restart, don't click yet. If it doesn't ask to restart, that's OK too.
# In the Terminal window that opened in (2), type the following two commands. Each one is followed by hitting the return key. You might get prompted for your password; if so, type the password for the account you're currently using.
sudo cp ~/Documents/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/
sudo touch /System/Library/Extensions

Last, we need to restart the computer. If the FTDI installer is waiting for you to click on its restart button, that will do the restart. Otherwise, select Restart... under the Apple menu.

Main Page

Admin — Tue, 21 Feb 2006 19:26:40 GMT

Admin:

=Whats this?=
This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''?, Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

-- DecoderPro (to program decoders)
-- PanelPro (to run a layout)
-- LocoNet Tools (a set of Digitrax specific LocoNet Tools)
-- DispatcherPro (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux.

=[[What do I need to run JMRI?]]=

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

An [[DecoderPro|introduction to Decoderpro]] page also exists, but you couldn't get there-from-here....

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release notes]] page is the place to go for late breaking news and, hopefully, an FAQ.

Main Page

Admin — Tue, 21 Feb 2006 19:26:09 GMT

Admin:

=Whats this?=
This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''?, Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

-- DecoderPro (to program decoders)
-- PanelPro (to run a layout)
-- LocoNet Tools (a set of Digitrax specific LocoNet Tools)
-- DispatcherPro (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux.

=[[What do I need to run JMRI?]]=

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

An [[DecoderPro|introduction to Decoderpro]] page also exists, but you couldn't get there-from-here....

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [[1.7.3 release note]] page is the place to go for late breaking news and, hopefully, an FAQ.

Main Page

Admin — Tue, 21 Feb 2006 19:25:38 GMT

Admin:

=Whats this?=
This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''?, Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

-- DecoderPro (to program decoders)
-- PanelPro (to run a layout)
-- LocoNet Tools (a set of Digitrax specific LocoNet Tools)
-- DispatcherPro (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux.

=[[What do I need to run JMRI?]]=

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

An [[DecoderPro|introduction to Decoderpro]] page also exists, but you couldn't get there-from-here....

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet' for the JMRI suite! The [1.7.3 release note]] page is the place to go for late breaking news and, hopefully, an FAQ.

Main Page

Admin — Tue, 21 Feb 2006 19:17:37 GMT

Admin: release note link included

=Whats this?=
This Wiki is an attempt to document the JMRI suite. We're hoping to utilize the power inherent in the Wiki approach to get it done by the JMRI community at large. We don't know whether this will work, but we've already had some great contributions from a few dedicated souls!

Donations to the JMRI project can be made on the [http://sourceforge.net/donate/index.php?group_id=26788 donations] page should you wish to contribute some of your hard earned! Contributions made via this link also ensure that Sourceforge is happy to host 'our stuff', which is nice!

=What is the ''JMRI Suite''?, Where can I get it? =

Firstly, JMRI (''Java Model Railroad Interface'') is free and open-source software, but there are some restrictions. Generally, you have to give us credit if you use all or part of it to build your own software. For more details, see the [http://jmri.sourceforge.net/Copyright.html copyright, trademark and license page].

Briefly, it comprises a number of programs which can be used to program DCC decoders, to run a DCC layout, or to monitor a LocoNet environment.

-- DecoderPro (to program decoders)
-- PanelPro (to run a layout)
-- LocoNet Tools (a set of Digitrax specific LocoNet Tools)
-- DispatcherPro (??)

[http://jmri.sourceforge.net The JMRI homepage] is the 'official' homepage of the project.

The suite may be downloaded from the [http://jmri.sourceforge.net/download JMRI software download] page. Prebuilt versions exist for computers running Windows (98se on), Mac (Classic and OSX) and Linux.

=[[What do I need to run JMRI?]]=

==[[Can I try the program without any layout connection?]]==

=Now what?=

Assuming you've visited the above links and determined that you have the necessary prerequisites the next thing is to connect it to the command station, or the [[Loconet simulator]]. Instructions on various configurations follow:

* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
* [[OsxDtrax | MacOS X with Digitrax]]
* [[MacOS X with Lenz]]
* [[ScriptMain | Information on scripting]].
* Please add others!

An [[DecoderPro|introduction to Decoderpro]] page also exists, but you couldn't get there-from-here....

=1.7.3 Release Notes=
The (very) imminent release of this long awaited new version is likely to be 'the biggest yet!' for the JMRI suite. [[The 1.7.3 release note]] page is the place to go for late breaking news and, hopefully, an FAQ.

Main Page

Admin — Tue, 21 Feb 2006 19:09:36 GMT

Admin:

Can I try the program without any layout connection?

Admin — Tue, 21 Feb 2006 18:48:07 GMT

Admin:

Yes.

If your computer does not have JAVA installed, download and install the latest version of JAVA from [http://java.sun.com/j2se/1.4.2/download.html Suns Jave site].

THEN download and install the ''JMRI'' suite from [http://jmri.sourceforge.net/download/ here].

at present it is necessary to download and install ''JMRI'' version 1.6.1
before installing any later version

Start the program; set the preferences to "LocoNet Hexfile" as a protocol. That's a simulated LocoNet connection which will allow you to play with all of the various capabilities.

Don't forget that the download is free, so there's no economic risk to trying it!