开云体育

I would think of roster entries as a list of decoders, for each decoder you indicate which loco it is in. So I would use your existing roster entry and change the loco info once you put it in another

It’s not practical or indeed possible to do what you’re asking. This is because each decoder definition is different to all other except close siblings from the same manufacturer. Even then,

Short answer “no” Long answer “only if you’re comfortable editing XML AND there be decoder has the same cv structure as the old one. imho it’s easier to start again with a new roster

John, I suspect your dummy blocks between the crossover turnouts may cause problems. The main issue is that they can break block tracking. They do fix the double crossover problem. Dave Sand

John, I did one more test. I deleted all of the SML and the block paths. After a re-start, all of the SML was discovered without errors. However not always correctly. Here is the generated logic

John, The error appears to be caused by a change in signal mast placement. The destination mast is before the source mast so the logic searches around the entire layout and eventually has the

Ken, It also appears as if you use an additional formatter for your Manifests, but this technique should transfer across platforms, since, I believe it is basically the same .csv files... Happy to

Ken, In order to make this happen, you need to use the hyphenated location trick to create a new location of "FAIRFAX-(Loco tracks)".? Then copy over the "RW Yard Loco Track" from your current

Folder moved to 'Problems being worked on' -- Peter Ulvestad Linux Mint 22.1, JMRI 5.11.2plus, Java 21.0.5 JMRI Users Group Moderator ( /g/jmriusers ) JMRI Developers Group

done

John, The profile/profile.xml would be helpful. It has the CMRI configuration. Dave Sand

David, I should point out that the main purpose of this revision was to remove many of the virtual blocks and sequencing logic at crossovers. I found in a smaller test file that by using turnouts

I have uploaded the file along with some of the other resources. Let me know if I missed something. John Figie

John, The messages.log file is normally 1MB which rolls over. Since you are running 5.6, that is about the time the logging technology was upgraded. When you move beyond 5.6, the 55MB file will

Thanks much for your prompt reply and help on this. The messages file is 55MB so I just uploaded a small snippet from the end including many sessions. Please see comments in the

John, To expand on Ken's reply, I recommend that you upload the messages.log file to the group's ProblemsBeingWorkedOn file folder. This will provide the details of the problem along with a history

John, You'll have to provide the full length of that traceback. That's only showing where it failed in a Java utility. We need to see where it was leaving the JMRI code. -Ken Cameron, Member

I have a large layout editor file that had been working well , but we wanted to make improvements. After a number of editing sessions I now get an error when opening the layout editor file. The panel

I have changed the decoder of a locomotive already in my JMRI roster. Is there an editing function to change the decoder listing without re-making a new roster for that locomotive? Thanks William

From Dan B.: *The "day" can be anything.? You can create "Day Shift", "Night Shift" and "Graveyard Shift" when creating train schedules.* Wow, that's a game changer!? OK! Thanks for that insight