JMRI Decoder Pro and the Digitrax PR2

[MisterBeasley]

I know some people here have said they are able to use Decoder Pro with their PR2.  I've got the PR2, and it works with the Soundloader application, so I know it's not the hardware.  But, Decoder Pro times out trying to read decoders.

Can anyone provide he exact settings used to make this work?  I've already verified that the COM port matches the one used for Soundloader.  I've got Decoder Pro version 2.0.

Thanks.

[Stevert]

Since nobody has made any suggestions, I'll try to help even though I don't have a PR2 (I do have a PR3).

  First, be sure that the Soundloader software is shut down before you start JMRI.  You may want to shut Soundloader down, reboot, and then start JMRI.  I have found that the Soundloader software seems to "hang onto" my PR3, even after I shut it down.

  The next thing would be to check all your JMRI preferences.  Besides just the COM port, you want to check the baud rate, etc.  Sorry, but right now I'm not by a computer with JMRI installed so I can't offer any specifics.

  Finally, if all else fails, post your specifics in the JMRI Yahoo! group.  Lots of folks there (including the JMRI programmers) who are happy to help:  http://groups.yahoo.com/group/jmriusers/   

[rrinker]

 Does your version of DecoderPro have an option to select the PR2 under the Preferences? If not, you might have to download one of the test versions which are newer. I have 2.3.4 and there is an option for PR2 and PR3 (two different choices) plus the usual other stuff - Locobuffer, MS100, and all the otehr brands of DCC systems they support.

 In addition to making sure the speed matches in DecoderPro, also check in Device Manager in windows - chnaging the settings in JMRI does not seem to alter the Windows settings found there, and they can be just about anything. Critical is that the handshake matches. , best bet it to set Device Manager to exactly match what you need to be using for the PR2. Failure to do this will cause the problems you are having - my one computer could not see my Locobuffer until I matched up the settings.

                  --Randy