I recently installed JMRI version 4.18+R37ad3d0 on a relatively new desktop PC running Windows 10 home, using a Digitrax PR3 with intent to use the Decoder Pro application. ?The install went fine, but the connection was a bit more challenging. My PC has two serial ports on the front; ?after a few trial-and-error changes of moving the PR3 USB cable between the two ports, and changing the serial port designation on the "Connections" screen between the various choices (COM 4, 1, and 3) I was pleased that communication was established with the loco on the programming track using one of the physical USB ports and COM3. ?I was able to program several locomotives, JMRI is a real pleasure to use. I used direct byte and specified programming track.

I shut down for the night, and returned the next day to program a few more locos. ?I cannot get the connection to work. ?I don't recall changing anything.?

By 'work', my experience is that the loco on the programming track moves a bit and may flash its lights when read/write is working correctly. The PR3 unit also flashes a combination of green and red lights (sorry for the non-technical description). I cannot find any combination of selecting different usb ports and changing the "COM" settings on the connection screen that establish communication with the loco.

I typically get the following error message box when attempting to start the Decoder Pro: "Unable to create connection "LocoNet" (L). Serial port COM4 not found. Unable to run startup actions due to earlier failures. Please check the log for more details. ?If you need to plug in or turn on anything, do so before restarting".?

I am stumped. ?It seems to be a connection issue, as Decoder Pro worked flawlessly before. There don't seem to be all that many connection items that I can change (I've now spent several hours changing every permutation and combination (where I change the PR3 cable attach port on the computer, and change COM port settings on the connection pane). ?When I move the cable between USB ports the Decoder Pro seems to see it, as it then gives alternative COM settings to choose from (sometimes just COM 1, then sometimes adds COM3 or COM4 or other choices when I move the cable around).

As I attempt to write to the loco, the programming pane (basic speed control for example) gives messages saying it is writing to the CV, but always then says "Programmer error: Timeout talking to the command station (306)". ?The loco does not move or flash, the graphics on my computer screen around the speed variables turn red and stay red. ?When Decoder Pro worked correctly it cycled quickly through the variables and the screen didn't stay red, as I recall. I don't think the loco is talking to anything.

I've tried other usb ports. ?Both the PC and Decoder Pro seem to recognize that something has changed - Windows tells me it has set up the new serial port (say COM6), and that COM selection appears on the connection screen in Decoder Pro, but I always get an error message on startup saying that port (COM6 in this example) is in use.

I've restarted the system a couple dozen times as I change combinations of the cable attach point/ COM setting. I've read the documentation on error messages and couldn't figure out a debug approach. I don't know what else to try. ?Any suggestions are welcome, thank you for reading this far.

Replace the USB cable.

If your operating system is 64, the PR3 might need a firmware update. USe the Digitrax supplied DIGIIPL to apply the update
DIGIIPL :

Firmware update :


" This is a product upgrade to expand the PR3 beyond the original 32 bit operating system design capability. Users on 32 bit systems and whose PR3's are working fine do not need to modify their PR3's. This IPL is only recommended for users with 64 bit systems or have had issues with Vista/Win7/Win8. "

This also helps proves the connection is valid and that the PR3 is operational.

Apart that the usual driver update (Win10 provides the proper driver)

If issue persists, call Digitrax and arrange service for the PR3.

Marc

Thanks Marc. ?I tried the update about 5 times, "program failed", "port not recognized" error messages. ?

Please note, I successfully connected once with this PR3 unit and cable and was able to run Decoder Pro perfectly- I don't understand how it could be a hardware failure. ?

So, you never did give the results of the log....have you read it? . I think you'll find an idea as to what's going on there.

One remote but possible case is where part of the software for some reason
doesn't exit with the rest of the program and it holds the port. This is the
case where it works fine right after a reboot of the computer but doesn't
work starting JMRI a second time. To figure this out it is critical to keep
everything plugged in the exact same places. Use Windows device manager to
confirm where the device is plugged in to confirm the port number.

Any time you check/change the preferences in JMRI to see the connection
settings, save it to make sure that's what you use next time, but do not ask
it to restart. My reason is after the save, check the Help->System Console,
it may have error messages from it trying to save and that would help to
know if that happens. Then I'd do an exit of JMRI to let it try to close
down.

Now use the Windows File Manager to find the username\JMRI\log directory,
look at the session.log file, notepad or WordPad would do. Look at the end
of it for any error messages. It may give us a clue.

If you see anything suspect in the log files, cut/paste them into an email
for us to see. I'm hoping we can spot a clue.

One long shot is a problem with firewall or antivirus programs interfering.
To test that, disconnect from the network, shut down those programs. If you
can suddenly open and close JMRI and have no problems, we know the area of
the issue.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Are you 'hot' connecting the Cable to the PR3 and the computer, i.e. with the computer already booted up are you connecting the serial cable? Some devices do function well when connected that way. Also if this is a USB connection into the computer are you using the same USB port and more importantly, ejecting the usb connection before unplugging the cable? Device drivers can get corrupted when the device is not ejected from windows or Mac OS. Typically the device will create a new port if you use a different USB port on the computer, or if the device was not ejected properly. This can create issues when the device tries to talk with the computer, 'am I port 1, am I port 3, am I port 4?', the computer is looking for a specific port, the device randomly grabs one and uses it. By ejecting the device you clear it's driver so it doesn't remember the wrong port.
Try reinstalling the device driver, if that doesn't correct delete the device from the computer in device manager and reinstall.?
P.S. Getting in a hurry once and not properly ejecting a USB thumbdrive cost me my entire Decoderpro backup data, along with several hundred pictures.?

Thank you for all your replies. Sadly, smartphones and Macs have spoiled me and my troubleshooting skills on PCs are meager. ?I use the PC strictly for running flight simulators which so far have run ok, not requiring troubleshooting. ? I found the log, used Device manager attempting to apply the advice received. ?No connection.

Given my humble/non-existant ability to troubleshoot the Windows connection issue, I've spent several hours today upgrading my Mac to Java 11 and trying to install the newest production version of JMRI/Decoder Pro. Another long story, don't want to try the patience of those tying to help by describing that connection battle other than to say I cannot get the Mac to connect to the PR3.?

I'm thinking my best option might be to get a new PR4, and try again on Windows? ?

One last update for the benefit of others who might find this thread. Exploring based on Marc's comments, I found Digitrax's Soundloader 2 software and installed.? My PR3 worked the first time, no issues with the communication.

Soundloader is very crude compared to Decoder Pro, but at least I can read the CVs (my Digitrax system uses a 20-year old DB150 command station that can't read CVs) and get a couple new locos speed matched which is what started this project. My brother is a true computer expert, next time he visits I look forward to returning to this thread to get JMRI/Decoder Pro up and running someday soon - your kind help will not go to waste.??

On Sat, Feb 1, 2020 at 01:35 AM, <gjs1010@...> wrote:

Thanks Marc. ?I tried the update about 5 times, "program failed", "port not recognized" error messages.

There is a specific process to update the PR3 and it is documented on the Digitrax web site you should read it:

http://www.digitrax.com/media/apps/software/download/24/PR3_Update_v1.0_for_64bit.pdf

1 -. The PR3 must be in a specific mode for the update.
2 -? DIGIIPL will indicate a failure of the update run.? This is normal.
3 -? If you are still encountering COM port issues with DIGIIPL,? some thing is faulty with the hardware involved..

You tried to run the DIGIIPL firmware update 5 times and it failed, you have either a bad USB socket, bad USB cable, bad PR3 device.? Using DIGIIPL? rules out anything JAVA or JMRI related.

Try uninstalling the PR3 from Device Manager and reinstalling it. Win10 will use it's own driver? ( usbser.sys )? but if Windows does not even see the PR3 on occasion, playing with driver will not help you.

Marc

On Sat, Feb 1, 2020 at 12:55 PM, <gjs1010@...> wrote:

I'm thinking my best option might be to get a new PR4, and try again on Windows?

I would not waste my time / money. To Windows, PR3 or PR4 are one and the same. Same driver, same setup.? If you can't get the PR3 to work, you will hit the same wall with the PR4.
Also the PR4 does not like PAGE mode and causes it's own garbage.? The PR3 is not prone to this and works as well under Page or Direct.?

I have both a PR3 and a PR4. spend most of the time using the PR3.? Used it under WinXp, Win7, Win8, Win10. I still use it under WinXP on a very old Lenovo T60 2Ghz/2Gbram.?
Used it since NEW and currently under JMRI 4.19.3 ..? I arranged Device Manager so that no matter where I plug the PR3 in, it is always seen as the same COM port. Saves a bunch of aggravation.

If the PR3 runs under Digitrax Soundloader (even after power off/on :-) ), that rules out a driver, cable, port, PR3 issue...? unfortunately..?

Marc

Thanks Marc you just saved me couple hours of car time and the cost of a PR4. ?Interestingly, on a second try with the PR3/Soundloader setup on the PC I get a COM error message and cannot connect. ?So the issue is isolated to the PC/ports, it's not a JMRI/ Decoder Pro issue. A bit of a time consuming process to learn this and I regret taking the time of JRMI experts when it is not really a JRMI issue. ?But again, thanks to all who helped. ? I have been thinking of getting a dedicated laptop for the layout and this pushes me in that direction.

If SoundLoader is working, try to make sure that JMRI is using the same
settings (Port). Make sure you try exiting SoundLoader and restarting it
too. If the issue is down at the driver level, that would also hang.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Ken I did use the same port. I also tested the serial ports just now with other devices; the ports work fine. ?So I think the issue is my computer doesn't like the PR3.

That I'm having a connection issue with PR3/Soundloader presents an opportunity to get Digitrax help desk to assist.

Make sure the PR3 has the latest updates from Digitrax. Use the Digitrax
program Digi-Loader to perform the update. If it isn't, there are many
problems.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Ken searching both Digitrax and Google I get no hits for 'Digi-Loader"?

开云体育

Sorry, it should have been the Digi-IPL. Here is the page.



-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Second post of this thread, ? I provided the link to both the firmware update and DIGIIPL.

Marc

Actually I downloaded Digi-IPL some time ago. ?I get COM port errors when I try to use it and like all COM errors in this project, I am unable to find a solution.

I think I'm done. I've easily spent 10+ hours trying to get computers talking to the PR3. I can't get the Mac or the PC to talk to it. ?I just don't have the knowledge to debug this.I am a computer user not a computer expert and the later is needed. I'll revisit if I can locate a local expert in COM issues, as Decoder Pro is most impressive when it can be accessed. Thanks again, sorry to use so much time for no result. ??

开云体育