开云体育

My original project was to combine two LE Panels, the Main railroad panel and the 5 track passenger station panel. Knowing there isn’t a quick way to join them, I proceeded to redraw the 5 track station onto the Main panel. Without realizing that the > Track Options > Automatically Assign Blocks to Tracks was turned on, every piece of track was assigned an AUTOBLK: ##, which I didn’t want nor need. I won’t need block detectors nor signaling. Any signals will be SSL to determine the turnout positions. Now I want to know how to remove block assignments from the newly drawn tracks since, as I see it, nothing can be deleted while they are assigned. I attempted to rename the unwanted blocks to a common name so when I could break the assignments I might only need to delete one large block. What I ended up with was, upon restarting JMRI everything opened properly the Main LE panel, The WiThrottle window, and the JMRI (center of screen) logo. The PanelPro control window did _not_. I didn’t have a way to close the program or make any preference changes. Since I put in so much work, so far, is there a fix to get JMRI to launch completely or is it easier to cut my losses and go back to a previous .xml file. Still how do I remove block assignments properly? I’m stumped. Thanks in advance for reading. John Bauchiero - NCE PH-Pro & PowerCab, RasPi4, DCC-EX - JMRI 5.11.4 - Java 17.0.12

Hopefully this can help others who experience the same problem. This has happened 3 or 4 times in the last 5 years - so not often. When opening JMRI, you get the dreaded unexpected EOF error loading the profile. Sure enough - the profile file is zero bytes. Easy fix - in the active jmri-profile folder there is a backupPanels folder under the railroad name. Simply copy that file back under the railroad folder - rename to whatever the profile file is called in your settings. Hopefully it is recent enough you didn't lose much of anything. The backup interval looks like when the profile is saved. All shutdowns have been nominal. No idea why it happens...Maybe it's an RPI thing, maybe it took to long to write and I did a system shutdown before it was ready? Who knows. The folder structure is below. For more info - Specs: RPI 5 bookworm with all latest updates running JMRI 5.10. The log file is below - it shows whenever this happens there is a compare failure. Guess that writes out 0 bytes and keeps on truckin...

I created/uploaded a small test case to show the issue I'm having with my layout. /g/jmriusers/files/ProblemsBeingWorkedOn/sml_test_5_multiple_turnouts.xml I may be confused but I'd expect both of these incoming masts to display aspect similarly. The top row works as expected based on which route is clear based on exiting turnout. The bottom row for diverging works differently.

I have a simple 3 train yard connected to another block with several turnouts as below My desire is to have a train leave the yard then run another transit continuously. Since a continuous transit requires first/last section to be the same it seems this requires two transits. I thought I could create a transit to start in BY1 and end in Central then chain to the next transit. My problem is with the leaving yard transit (which is terminate when done for testing). As soon as it allocates the Central section, the mast turns red/red and the train never moves. If I click the mast green the train moves and stops in Central as expected. So, how can I make this to allow move train out automatically after allocation?

I am not sure what happened, but I have one turnout that ended up in the wrong orientation. I have the turnout and block detection and turnout position sensors all working, so I am trying to figure out if there is a way to just reorient the turnout without completely deleting it and then setting everything up again. I was looking for a way to "disconnect" the turnout, like you can do in Anyrail, but was able to figure out how to make that work. Any simple solutions or do I just need to delete and then re-add a new turnout in the correct orientation? -- Heath @ Human[c]ity http://www.humancity.org http://www.riversidetransfer.nyc http://www.manhattanmodelers.com

Sometimes it's only one or two loops. This time the train went maybe 5-6 then stopped presumedly because of the double mast stop (I don't see that specific aspect at https://www.jmri.org/xml/signals/basic/aspects.xml). It's not always the same mast sometimes it's the other double mast. Why can't it allocate sections when nothing else is on the track? Notes: I'm using 5.11 and all turnouts are ghost blocks between hardware detection blocks. Everything is auto-generated (paths, sections, SML). After this screen I restarted JMRI and tried again it only made it to the second block (pic 2) even though I manually clicked "Allocate Next" until all blocks allocated but it never restarted. There is nothing in the session.log

Hi All Would anyone be able to assist with this issue. History back ground I have been using windows 10 PC's for many years with no issues and dropbox to store the information. This has been working without any issues for over 10 years. Now the PC's have been at different locations and still operating. Now one of the PC's is normally has the preferences configured to the railway hardware and the other PC the preferences are set to Simulator. Absolutely nothing new there works amazing. Loading Issue using Montgomery OS Now Moving on to the issue now. I was presented with the opportunity to change to a Mac mini using Catalina OS and Montgomery OS. I loaded the latest test version of JMRI onto Montgomery and all set up correctly in simulation mode and again using dropbox . When I tried to load table content and panels and selecting the correct xml file version. I get these error messages as shown below So then I decided to try using Catalina OS and repeat the same JMRI set up with Dropbox again. To my surprise when I selected load table contents and panels and the same xml file version. Every thing loads correctly as expected with no issues appreciate any assistance or ideas to resolve the issue Regards Peter