Multiple <ourAspect> Entries in Signal Mast Mapping #sml
|
I'm trying to understand a mast response to the <advancedAspect>.
In AAR1946, 3 high searchlight, there are multiple <ourAspect> responses.
What determines the aspect to display for the presented next mast aspect?
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel
|
|
Oh I wish we had "edit" on these ...
Further:
I have a mast entry:
<aspectMapping>
<advancedAspect>Advance Approach</advancedAspect> <ourAspect>Clear</ourAspect> </aspectMapping> However, the <advancedAspect> presented "Advance Approach" but <ourAspect> presents "Approach".
Trying to understand.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel
|
|
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 is:
<aspectMapping>
<advancedAspect>Advance Approach</advancedAspect> <ourAspect>Clear</ourAspect> </aspectMapping> The triple searchlight displays:
Based on that, I'd expect "clear", but:
The path between has two blocks, the turnout and the track.
The turnout is "medium" and the track is "global".
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel
|
|
Ken, In the SML definition, what is the path speed and is any turnout thrown? Dave Sand ----- Original message ----- From: "Ken Heywood via groups.io" <kheywood=comcast.net@groups.io> Subject: Re: [jmriusers] Multiple <ourAspect> Entries in Signal Mast Mapping #signalmasts Date: Monday, December 30, 2024 4:30 PM 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 is: <aspectMapping> <advancedAspect>Advance Approach</advancedAspect> <ourAspect>Clear</ourAspect> </aspectMapping> The triple searchlight displays: Based on that, I'd expect "clear", but: The path between has two blocks, the turnout and the track. The turnout is "medium" and the track is "global". -- Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel |
|
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 Youtube: Ken's Channel
|
|
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 a semaphore definition to a local copy of AAR later.
There's pros and cons to that: only B&O needs a local copy leaving AAR part of the distribution.
If I add a semaphore to AAR, then it needs to be local and doesn't benefit as part of the distribution.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel
|
|
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 aspects our mast could display. It has multiples to cover the issue of when we have mixes of simple signals, like three aspects and other masts that might have five or six aspects to choose from. Remember as mast might be configured to only show some of the possible aspects. It starts at the top of the list and tries to match them one by one. If they don’t match, it goes to the next in the list, etc… and eventually if nothing else matched, it uses the <danger> aspect. That’s generally why you end up with stop if something didn’t match right on something else in the aspects.
When mixing two different signal systems, it is still matching exact text of one and the other. Capitalization, spaces, punctuation, spelling, they all matter.
On top of that you start adding things like route for diverging or not or speed limits into the mix. But key is the logic is trying to match exact text of the aspects.
-Ken Cameron, Member JMRI Dev Team www.fingerlakeslivesteamers.org
|
|
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 book.
I do get stop and advance.
In this instance, the only choice is "Clear" for next signal "Advance Approach".
I assume the semaphore is dropping to a more restrictive aspect.
I'm trying to figure out why.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel
|
|
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 instead.
Are you having success with other signal combos or was this the first one? If you’ve edited them, could you post or upload those exact files so we might see them? The slightest differences will matter.
-Ken Cameron, Member JMRI Dev Team www.fingerlakeslivesteamers.org
|
|
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 those combos are missing, you don’t see what you wanted to see.
-Ken Cameron, Member JMRI Dev Team www.fingerlakeslivesteamers.org
|
|
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 Youtube: Ken's Channel
|
|
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 would also say that I’d order the mappings so all of the home aspect clear is together, then all the ones giving Approach, and finally those that give Stop and Proceed. I’d also clean up the whitespace to be consistent, but that’s more for looks and easy reading. That shouldn’t make a difference for the xml.
-Ken Cameron, Member JMRI Dev Team www.fingerlakeslivesteamers.org
|
|
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 pair.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel
|
|
Ken, I suspect the SML path speed for signal mast pair is not Normal. Normal should give you a Clear. Dave Sand ----- Original message ----- From: "Ken Heywood via groups.io" <kheywood=comcast.net@groups.io> Subject: Re: [jmriusers] Multiple <ourAspect> Entries in Signal Mast Mapping #signalmasts Date: Monday, December 30, 2024 8:45 PM 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 pair. -- Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel |
|
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 how they work together in the same signal system let alone how they impact when you have two different signal systems. Like which one is used for which mast. May have time in the morning to look into it.
-Ken Cameron, Member JMRI Dev Team www.fingerlakeslivesteamers.org
|
|
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 diverging leg for LT18 is Global Restricting. If LT18 is removed, the SML path speed changes to Medium. This is caused by the Medium block speed for YD-LT59. If the block speed is changed to Normal, then the semaphore displays Clear for several LM394 aspects including Advanced Approach. Note: I have a modified appearance file from May 2023. Dave Sand ----- Original message ----- From: Dave Sand <ds@...> Subject: Re: [jmriusers] Multiple <ourAspect> Entries in Signal Mast Mapping #signalmasts Date: Monday, December 30, 2024 9:08 PM Ken, I suspect the SML path speed for signal mast pair is not Normal. Normal should give you a Clear. Dave Sand ----- Original message ----- From: "Ken Heywood via groups.io" <kheywood=comcast.net@groups.io> Subject: Re: [jmriusers] Multiple <ourAspect> Entries in Signal Mast Mapping #signalmasts Date: Monday, December 30, 2024 8:45 PM 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 pair. -- Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu Youtube: Ken's Channel |
Ken Heywood
Ken Cameron