I would like to use JMRI to help speed match a few locomotives. However can not get programming on the main to work. I can get it to work on my programming track.
I am using a Windows 10 computer connected to pr3 extra connected to a dcs100 via pocket.
Any tips to getting this to work?
Chris
I know that Decoder Pro and Windows 10 don’t play well together. I bought a new PC earlier this year with Windows 10, and I can’t even get my programming track / PR3 to work.
JMRI, Windows 10, and the PR3 work just fine together. I’ve been using that combination since the Windows 10 public beta in October of 2014.
When you use the programming track, are you using the PR3’s programming outputs or the DCS100’s programming outputs?
If you’re using the PR3’s, that means you’re using the PR3 as a stand-alone programmer. In that mode, it doesn’t pass anything to the LocoNet (and therefore nothing to the DCS100, either).
To use the PR3 for programming on the main, you need to set up your JMRI preferences (or create another profile) to use it as a LocoNet interface so it passes those POM commands along to the DCS100.
More info on the two modes and the required connections/preferences here:
Lots of users (myself included) use Win10, JMRI, and the PR3 without any issues at all. To help diagnose your issues:
What version of JMRI are you using?
What specific error messages are in the JMRI message log (under the Debug menu)?
If your new computer is running the 64-bit version of Win10, have you updated the firmware on your PR3?
I have two laptops that had Win 7 on them and a PR3. The Digitrax supplied drivers worked fine. Upgraded to Win 10, still work.
I just attached the clubs new Windows 10 computer to a DCS240 with the built-in PR3. The Win 10 system detected the PR3 and loaded a Microsoft driver - Works fine.
My question is what Digitrax system, or are you using the PR3 as a ‘standalone’ programmer. If as a standalone programmer - You cannot program on the main.
As a system programmer, make sure you have selected ‘on the main’…
Jim
I am using the pr3 extra as an interface only. My programing track is connected to my DCS100.
I am using the latest version of JMRI.
I am using 64 bit windows. I have not updated the firmware on the PR3 Extra. I purchased it in the past 2 months. How can I tell if I need to update it?
I will check the error message in JMRI tomorrow night when I get back to the layout.
Chris
Chris,
I assume you got JMRI configured correctly as you can program on the ‘Program Track’. You want to have your Program Track wired to the DCS100, not the PR3. You should be able to power on/off the track power from Decoder Pro. This is the basic test to make sure your connectivity is good.
Now on to the PR3 firmware. Go to the Digitrax web site and go to the Downloads page.
Make sure Decoder Pro is NOT running. Configure your DigiIPLII program to use the same com port as you have configured in JMRI. You can use the Find Device button to look at the device. I am not sure what it should look like from the factory as I just updated the firmware and never looked at it first. I doubt if the firmware in your new unit is current.
You now have the current firmware loaded in your PR3. Close the DigiIPLII program and restart Decoder Pro. Decoder Pro should come up - Test the track power on/off function to make sure it still works.
To program on the main, go to the lower right corner of the Decoder Pro screen and select ‘Programming on Main’. Be are that you cannot Read CV values from the Main Track - This only works on the Program Track. Also, some decoders will not use the new value you just
Okay, good. Does service mode programming on the DCS100’s programming track work okay?
Specific version, please. They create unreleased (but generally available if you know where to look) versions at least daily, often even more frequently. So the “latest version” could be just about anything…
If you just purchased it, you should be okay, unless your dealer sold you old stock. You can use the “DigiIPL” utility from Digitrax to check. If it’s version 1.0 you’re golden. I’m not sure if JMRI has the ability to check that or not, and I’m not near my layout at the moment.
That will be very helpful.
EDIT:
Jim and I were typing at the same time. His firmware upgrade instructions are excellent! But check the version first, if your PR3 really is recent production it should already have the 1.0 firmware.
Thank you for the directions on how to update the firmware.
I am able to read and write CV’s on the programing track.
I didn’t know that you can’t read CV’s from the main.
I won’t be able to get back to the layout until Friday night. I will check the firmware, specific version of JMRI and what the error message was.
It might be that everything is ok. I attempted to read the CV’s while on the main before programing the speed table and stopped when I got the error saying CV could not be read.
When I write changes to the speed table while on the main, do I need to remove all other locomotives or will the changes only take effect for the specific roster entry/address I am in in JMRI?
This is my first time using DCC, so far it’s been a fun but steep learning curve.
Thanks
Chris
Yup, that sounds like your issue - OPS mode (mainline) programming is write-only.
There are ways to get feedback from a decoder on the main (Transponding, RailCom), but they require additional equipment and aren’t generally used for run-of-the-mill programming purposes.
If the JMRI roster entry has an address set, OPS mode programming from within that roster entry will send the commands to any locos with that same address. So unless you have any duplicate addresses, you should be fine. (Just don’t use address 0 (zero) since OPS mode programming uses that as a broadcast address. In that case, it WILL reprogram everything!)
I’m glad you’re enjoying it! Yes, there is a learning curve, but there are lots of folks willing to help.
I was able to get away from the wife and kids for 15 minutes tonight and I was able to get JMRI to write CV changes while on the main.
Looks like everything is working correctly. As usual, user error. LOL
Thank you to everyone for all of your help!
Chris