开云体育

As you are encountering issues with both Soundloader AND DiGIIPL, I think it is a safe bet to call Digitrax for help. It works, then it does not work points to a PR3 or USB cable fault. Cable could be

It would be better to copy and paste the system console here. What version did you update from? -- Peter Ulvestad JMRI Users Group Moderator - https://www.jmri.org ( http://www.jmri.org ) Tam Valley

How about considering just getting a Sprog and start fresh ? I know nothing about A PR anything but I do Know I have been using sprog and decoder pro for about fifteen years and have upgraded many

Bob Unfortunately the work-around didn't work for me. When used on the 'test' file (v29) it yielded the same error. On my latest panel (v36) it produced 'gibberish' - no formatting at all, just a long

John, I think Ken meant to say Store instead of save. Some how, for whatever reason, the save command has been changed back to Store.

Sorry for the problem, thanks for the file to confirm. There will be a fix later today. In the meantime, if you change this line near the top of the file from <?xml-stylesheet

Dave, Is this what your asking for? User Files Location: C:\Users\Mike Swederska\Dropbox\JMRI\ Roster Location: C:\Users\Mike Swederska\Dropbox\JMRI\ Profile Location: C:\Users\Mike

Hi Bill. Glad you were able to program the decoder so leave well alone. Do you have a catalogue number for the Thomas loco in question as a matter of interest ? Regards. Tony.

This means you don’t have the PR3 software installed so that the computers see it on the Com port. Look in device manager to see this. David Klemm Sent from my iPhone 11 PRO Max

Saying that the IPL tool also gives com port errors points to either hardware (the device, the cable, the port on the computer) or driver issues. The later is where using the Windows Device Manager

gjs1010, The PR3 doesn't need any drivers on the Mac. If you have followed the instructions at: <https://jmri.org/install/MacOSX.shtml#usb> and cannot get a /dev/cu.usbmodem... type device to

Hi Bob This looks very useful and I hadn't realised it was built in. Is there an easy way to debug it when it fails? I have a panel that simply returns "Error loading stylesheet: Parsing an XSLT

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

By the way, any media images you used in your roster are not exported / imported.? You must manually bring them over or they are lost. Marc

John is correct.? The Export/ Import does not handle the roster index file so you must recreate it. In Decoderpro this? is under ACTIONS. Recreate Roster Index In DecoderPro it is also under FIles >

Mike, Did you set both of User Files Location and Roster Location to point to your new jmri folder on Dropbox? If you use both DecoderPro and PanelPro, you'll need to check both. Please do a

This sounds like the problem that I was having when moving files to a newer computer. The directory path in the newer computer, a Mac, had an extra level in the file locations. If I recall it should

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

I improved the handling of the blocks section and track segments. I also cleaned up the instructions: https://www.jmri.org/help/en/html/apps/PanelPro/ShowPanel.shtml Let me know what’s missing;

I just upgraded to the latest production release of JMRI and I'm getting errors when opening my panel file. First I got an error that one of my sensors could not be created - "Could not create sensor