开云体育

Note that Bob’s suggested fix will need to be redone every time you upgrade JMRI. A better fix may be to keep jdom.jar outside of lib and add ‘--cp:p=“C:\path\to\jdom.jar”’ to the launcher

Bob, Cliff, I believe I have found the bug that causes the lack of image icons for signal heads. Since I rarely work in the Control Panel Editor code, I need to do more research to confirm my

I dispatch on a fiends layout using Panel Pro. Every session the program stalls 2 to 3 time. He just told me tonight that when he does his restaging it stall also. Is there some setting that needs to

Well those train IDs sure sound like the good old Espee to me... All my years of listenng to the scanner as trains left Taylor Yard, the crew would report to the DS train length, MTs, and Loads (as

DaveS / DaveH Thanks very much for your comments.? Between your thoughts and CliffA's comments, I was able to migrate the icons.? The "Preferences" option did not show up previously, but when I

I should add that I do not have this problem with turnout or sensor icons. BobE

Cliff I definitely think we are on the same page.? When I drag-and-drop from ADD ITEMS - ITEM PALETTE - SIGNAL HEAD, this is exactly what I get - an empty list of icons in the XML file and an "X" on

Bob, From the comparison of your uploaded screenshot with what is shown on the screen of this computer, it now seems likely that we are working on the same page of the same choir book. First, to

JMRI Panel Pro Version 4.14 +Rd060e0b JAVA Version 1.8.0_241(en) PRINTER Canon TS6120? -? Wireless Have searched the problem below with no results. Cannot print manifest when “Preview” is

No, it doesn't. The bug in the firmware applies only to the Power Pro system. The heading in Dave's post specifically states: "Power Pro CV Limitations". Best regards, Steve Steve Haas Snoqualmie, WA

tylergrote, It is, and I'm afraid it's possibly a hardware problem. The baud rate settings in Device Manager are irrelevant. They are overridden by JMRI. What matters is that the JMRI baud rate and

Okay might have part of my problem solved. Managed to get the trains moving and one even stopped where I think it should have. Still need to figure out how to stop them from running in each other.

Bob, The big problem right now is that I DO NOT get the warnings when I load your panel. The main difference is that I have a new profile to setup the test. After you start JMR and get the warnings,

Bob Z, No, the latest ESU decoders (Essential Sound Unit and LokSound 5) require new Java code in JMRI. Your way forward is to upload your broken panel to a folder with your name in Files Being Worked

Hello, I recently purchased a ScaleTrains Operator locomotive with the ESU Essential Sound Decoder in it.? Unfortunately, the version of JMRI I was running did not include this decoder definition.?

For instance,? in an earlier post you said "The "not compatible" error occurs when the neighboring blocks are not consistent between two panels.".? What does that mean?? Can you give me an example?

Dave, Well, I'm still getting the warnings and using 4.18 as well. Java 1.8.0_241 in case that matters If you could explain to me what these warnings mean, maybe I can figure out the problem Thanks,

I don’t have any signals. I am just on a test train trying to get things working better installing on the main layout. I have been looking at the dispatch panel and can not see how to start the

Thanks Cliff I uploaded the revised panel.? And if I am correct, the only changes as you suggest were done to the XML file was?to the URL pointers.? For example:

Dear Alan and Marc, Are they slower than expected?- YES Are they slower than another loco?- YES Are they slower than another identical loco?- YES, To be accurate the decoders in question are slower