Ken, I looked at your upload from last June. The SML path speed to LM394 is Restricted. This is caused by the manual addition of LT18/Thrown. This makes the SML diverging and the speed of the divergin

Nick, Make sure the virtual mast is the same signal system as the rest. Also make sure that 411 is know to be at that boundary between T9106 and T9107. -Ken Cameron, Member JMRI Dev Team www.jmri.org

Hunter, If you look at the aspects at https://www.jmri.org/xml/signals/NS-2008/aspects.xml you can see that Medium Clear uses a Medium speed. Look at the "path speed" for the generated SML. I change t

Another temporary work-around is to run the jython/TurnOffXmlValidation.py script at startup, before you load any other files. Bob — Bob Jacobsen rgj1927@...

David, When you add the turnout to the panel, you can change the icons. If it is already on the panel, use "Edit Turnout Icon" from the pop-up menu. JMRI generally does not know about left-hand/right-

On Sun, Nov 10, 2024 at 07:52 AM, Nags wrote: However, I found it got a bit messy defining all the conditions in SML so I'm looking at having a single sensor set by LogixNG in the SML. Moving the cond

John, Q1: I change the global turnout speed for thrown. I don't see an issue with adding your enhanced signal system to JMRI as long as it provides consistent aspects using the default turnout speeds.

Scott, You only need to assign a new block to the lower half. This happens to be the A and B connections. You will need to remove and add SM6-77-78 since it now has a different block boundary. Once th

Dave, Signal mast logic supports a single route between the source and destination mast based on the state of the turnouts between two masts. If signal mast logics needs to support an alternate route,

Hey, thanks for the responses! I'll take a look at the provided links - seriously appreciate the time and assistance..

I see the bigger issue is that people forget that some signals are SSL and leave some of that logic lying around. I've used Logix to drive a virtual mast by reading a SSL driven signal and the other w

unknown means that jmri doesn't know the state.... either the sensor never sent a status message, jmri never received the message (hadn't started yet?), or (depending on system) it's messages colided

thanks! On 7/6/2024 4:50 AM, Ken Heywood wrote:

Dave, Ah ok cool. I have loaded the file, run the grand reset did the store/stop/start/load x 2 and save each time.. Then I ran the auto generate signalling pairs and did not tick the gernate sections

Thanks, Ken. Besides the throat to throat configurations (I have five of those) I do have two double slips. I see that they are handled similarly. Using the combined information from those of you who

Okay, that is what happens when you get in a hurry. Not even sure how I hit the enter key. I wanted to lay out the problem & then "adjust" the draft when I got back home. Now I will start over in the

interesting! and yes, that's why I qualified by saying NA... certainly elsewhere "your mileage may differ"

Dave, Very funny :). Since this an ABS implementation, the dispatcher better be careful when granting authority to move. Dave Sand

All tests gave required aspect except when the next signal went to Danger for an opposing crossover. I already have logix to set an internal sensor read by SML so I simply added a test for the next si

As a user, I prefer to have the layout panel match the hardware. It also helps the dispatcher who only sees the panel display on the computer. I use AAR-1946 but needed a single blade semaphore that i