开云体育

Hello All, I bench tested everything, everything being the command station, PM42, BDL168 and DS64s at home and got them setup properly in JMRI. I took it all to club and have started setting things up

Jan, Now I AM confused. What I want to know is this:F1 is the bell on my decoders. DP has function pads. If I connect something to the F1 pad, what happens to my F1 bell? Jim

Roger, It depends on your train and block length. If your train is shorter than that block, the train will slow waiting for the "tail" of the train to exit the previous block. --SteveT

Chris, Sorry, I missed your upload back in July. It appears that block connectivity cannot handle the same turntable definition on two different panels. If I remove the block assignments from one of

thanks, somehow I missed this thread when it first went up.?? I'll try a Pi4 as soon as I can get my hands on one!

Since I posted and uploaded the XML file, I've redrawn both the main, and the local panels pertaining to the turnatable.and the problem is still there. I've now upgraded to JMRI 4.16 on all machines

All, Running JMRI 4.16.3? ? Windows 10. While in auto trains Dispatcher and running continously is it normal for the loco to slow down to 10mph in the starting block each time around.? Just never

Some time ago I set up a PANEL for my railroad and I have been using it as my DISPATCHER position with a remote laptop computer for a couple years now. ?Each train has an ICON with its number on it.

Good news to report! After attempting to create a new panel, it made me certain this was some sort of connection issue as I could create Xpressnet turnouts but could not create any Acela objects even

Dave, No luck so far. I was hopeful removing the residual JMRI directory files after the uninstall would be the missing piece. Clean install of 4.11.6 still shows errors during panel load involving

Thanks Dave/Chris.? And I agree with Chris 100% - it is a very cool tool! Rick

Rick, Chris, I will not need any samples. I was able to re-create the scenario. Now the tough part. Dave Sand

Mike, 4.16 has a number of issues relating to connection speeds. You might try 4.17.3. 4.11.6 cannot open panel xml files saved at 4.16. It may also have problems due to profile structure changes. I

Rick and Dave, I've just replicated Rick's scenario, and see the same result.? I suspect, therefore, it's a program issue.? I won't post my xml, unless/until asked to. Thanks, Dave, it's a cool

Rick, If you upload your TimeTableData.xml file to the ProblemsBeingWorkedOn folder, I can see if it a data issue or a program issue. I suspect that it is a program issue since I did not take into

Updated to 4.16 from 4.11.6 and receiving panel load errors.? Also tried reverting to 4.14 with same results. Uninstalled and went back to 4.11.6 but now it will not load any panels without

I have created a new layout in the timetable tool.? In this layout I have multiple segments which include a 'Main' segment and a 'Reading Branch' segment.? I have created all the stations and set

I realized my reply wasn't clear as to which error I was seeing. I was seeing this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default-cli) on project jmri:

Thanks, Dan. Tried steps exactly as you describe. Ant build works fine and PanelPro starts. But I still get the same error when subsequently I try to run the "Maven Build" "JMRI PanelPro" from the

When I experience this problem, it is due to the meta-data not being created correctly.? One way to fix is to use ant, under targets, do a realclean, followed by PanelPro.? After the ant builds