John,
When thinking about signaling, think about the characteristics that you you want. I prefer western US practices which are primarily route signaling with implied speeds. Eastern US tends to be speed signaling which sometimes implies a route. Note: I will probably get some push back on my definitions.
The prototype deals with signal masts and their aspects. Signal masts have one or more signal heads. The aspect determines the signal head appearances. A ¡°diverging¡± aspect is normally indicated by red over green or yellow appearances.
Don¡¯t worry about implementation details when working out the signal head/mast question. DCC Signal masts can be signal head based masts or even turnout based masts.
A cross-over is always at least two blocks, one for each straight route. A slip (including throat to throat) is always one block, but has two turnouts.
Keep in mind that signals protect one or more blocks to the next signal. Including the approach track segment with the turnout moves the signal away from the turnout and makes the control point much larger.
A correctly drawn layout editor track plan with a prototypical block topology using signal masts and signal mast logic results in a fully functional ABS signaling system.
Dave Sand
toggle quoted message
Show quoted text
On Dec 2, 2018, at 4:21 PM, John Pearson <pearsonjohn99@...> wrote:
Dave
Quick response appreciated, thank you.
a few comments / observations / Questions
1) your listed order of actions easy to follow, I'll try it out tomorrow on a simple test diag
2) Found Quaker valley ok lots of writing but they sem to be persuing my objective , Not sure at this stage what the difference between Sig Heads and SSL & Sig Masts + Signal Mast logic might be, I'll think about and reasearch. ( SSL ? please, Single Signal Lamp ?)
3) Also your warning about turnouts becoming "blocks" is significant as I was lumping them in with track segments / bigger blocks..... A crossover between two main lines would become a block in its own right? Or does it split in the centre between the two parallel tracks ?
No doubt the reason that Interlocking drawings label turnouts with an OS number and detect vehicles on the OS.. Is joining two turnouts throat to throat acceptable as one OS item ? ( Guess it becomes a double slip ).
Many thanks for your assistance
John Pearson
On Sun, Dec 2, 2018 at 6:01 PM Dave Sand <ds@...> wrote:
John,
Take a look at
The signaling section is based on signal heads and SSL rather than signal masts and signal mast logic.
Listed below are the steps that I use for a new Layout Editor Panel. The steps are based on using the appropriate simulation mode for the hardware. I also use signal masts and signal mast logic for all of my designs.
? Place turnout icons on the panel and connect them with track segments.
? Create turnouts in the turnout table. Use default feedback settings.
? Assign turnouts to the turnout icons. Clicking on the turnout icons should change the turnout state and the icon.
? Turnout context menu: Edit item.
? Create occupancy sensors in the sensor table.
? Assign blocks to the turnout icons and track segments. Set the occupancy sensor for each layout block.
? Context menu: Edit item.
? Set Block
? Select Create/Edit
? Select Sensor tab and select sensor name.
? Verify that the panel is valid using the Tools >> Check items.
? Add sensor icons to the panel to simulated train movements. Verify that the correct tracks show occupied.
? Create signal masts in the signal mast table.
? Assign the signal masts to the appropriate block boundaries.
? Context menu: Set Signal Masts...
? Use the Signal Mast Logic table to generate the signal mast logic.
? Verify the SML works by setting blocks occupied and setting turnout positions.
Obviously there are a lot of details missing, but it provides a general flow.
Step 5 is very important. Since you are talking about interlocking plants, the block topology must be correct. The basic rule is that each turnout or turnout group must be its own block. This provides the necessary block boundaries for placing signal masts which protect the interlocking.
Dave Sand
On Dec 2, 2018, at 4:29 AM, John Pearson <pearsonjohn99@...> wrote:
Hello JMRI group, I¡¯m new to the group and looking for Help.
Intro I¡¯ve dabbled with Panel Pro over the last 2 years to the extent of creating a plausible US&S CTC panel with layout model board across the top. The board has NO working logic.
Now at the stage of needing to design the signaling system to work I¡¯ve started LAYOUT EDITOR, but having great difficulty getting in..... The only tutorial I can find is by Dave Duchamp¡¯s NMRA presentation dated 2008 does not cover the current version of Panel Pro, 4.12
Any guidance appreciated, starting from scratch.
MY INITIAL OBJECTIVE IS A WORKING LOGIC INTERLOCKING PLANT USING LAYOUT EDITOR
Eventual ambition Merging LAYOUT EDITOR drawing with WORKING CTC PANEL AND LAYOUT SIGNALS controlled by MRCS /CMRI logic
At the moment I cannot get past drawing a turnout, track segment and Tools-Tables-Turnouts, without them fighting each other !!!!!
My current set up
a) lap top Samsung - Windows 7
b) Panel Pro 4.12+Rb6a9bb1
c) Java 1.8.0_191
Previous set up - CTC panel
a) lap top Samsung - Windows 7
b) Panel Pro 4.10
c) Java 1.6
Guidance appreciated
John pearson
