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

Ken H, I'm off to bed for my night. But I think the aspect.xml also matters here since it says that a given aspect is valid for a speed, speed2, or route modifier. This is where I'm not so sure of

Ken, I suspect the SML path speed for signal mast pair is not Normal. Normal should give you a Clear. Dave Sand

Ken C. That's the semaphore. I uploaded the xml for the triple searchlight. Semaphore protects a turnout and approaches the triple. There are only 3 aspects for the semaphore. LM59R1 to LM394

Ken H, Is the uploaded file the advance signal or the home signal? And which rules for which signal? The file appearance-Semaphore-1Arm.xml only knows Clear-Approach-Stop and Proceed. I

Ken C, Semaphore xml in "Problems" -- Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Blog: Cape Cod Railroad (HO) – Newbie of an Oldie (

Ken H, PS: The usual problem is that the rules for this mast needs to have every aspect from the advance signal showing as an <advanceAspect> entry followed by what this mast should do. If one of

Key H, As a test, add more aspects to <ourAspect> list. Also double check the space in the other signal. I've seen a number of rules that would put them into one word like AdvanceApproach

Thanks Ken When I copied B&O semaphore, I made sure all the aspects matched exactly and set the expected result for each. Obviously, I had to add some AAR aspects that B&O didn't have in their rule

I'm looking at creating a Module that may be called by different Conditionals but I want the Module not to act on any subsequent calls during a period of time - First In First Served. If I'm correct a

Ken H, Think of the aspect mapping this way, it might not be perfect but it is close. The <advancedAspect> is what the next signal is displaying. The <ourAspect> is the list of different

Understood billybob, My implementation was a quick and dirty job. I copied the B&O to my local resources and modified it to match the aspects of the AAR system. It's B&O in name only. I planned to add

<Your image not included here.> You have the advanced signal, "IF$VSM:AAR-1946:SL-3-high($0029)". <Again, image not included here.> Here, you have the targeted signal,

The turnout is closed as are the next two turnouts. The speed looks like 100. -- Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Blog: Cape Cod

Ken, In the SML definition, what is the path speed and is any turnout thrown? Dave Sand

I've been trying to understand in general, the logic in determining the displayed aspect. In particular, I have a semaphore and the next signal a triple searchlight. The semaphore aspect map

I would have expected that you would _only_ get "Clear" or (the most-restricting aspect, defined in JMRI as the <specificappearance> "<danger>"). It makes me wonder if the "mis-behaving" mast is

Ken, Where do you see this mast entry? What is the path speed between the signal mast pair? Dave Sand

Ken, The aspect selection is based on the "path speed" for the signal mast pair and whether the "route" is Normal, Diverging or Either. For example, if the next aspect is Clear, the possible aspects

Disregard (post deleted). -- H.O. Australia (Layout in Progress) Digikeijs DR5000 LocoNet JMRI v5.8 DecoderPro/Warrants/CPE/SML/LogixNG Windows 10