1. Should I delete the SSL logic before creating SML logic or can they co-exist.

2. In the logic pane both Blocks and Sensors expect entries. Since the Blocks were created from Sensors why are there two different entries? Is the Sensor entry for something other than track occupancy (Blocks)? Can Sensors be used instead of Blocks?

3. As I understand it, masts are to be placed at block boundaries, but in my case when SSL was created, turnouts are connected by their point side to the adjacent block, which means for me the mast is placed at the point side of the turnout and not at the block boundary. The frog side of each leg are block boundaries. Should the turnouts be their own block or not necessary.?

John,

Q1. ?Are the signal masts going to use the existing heads for the layout connection (Signal Head Controlled Mast) or a different hardware driver for the signal masts. ? For the first option, you must delete the SSL. ?

Q2. ?Sensors are used for a wide variety of purposes, such as turnout feedback, CTC panel controls, infra red point detection, current based occupancy detection, etc. ?For automatically generated SML, only blocks and turnouts are discovered. ?For layouts using Control Panel Editor and OBlocks, the SML has to be manually created using turnouts and occupancy sensors. ?The sensors SML section can also be used for other purposes, such as upgrading the default ABS logic to APB by adding direction sensors.

Q3. ?Signal heads and SSL are based on being attached to turnouts. ?Signal masts are attached to block boundaries. ?If you want to place signal masts at turnout throats, you need a block boundary at the throat. ?This means that turnouts (or groups such as 3-way or ladder) need their own block. ?There are techniques using logic to simulate a virtual turnout block.

Dave Sand

John,

A control point (turnout) is protected at each entry point.

The throat (points) is one of the three.

As Dave says, the turnout needs its own block.

I too have the throat connected to the approach track.

You can assign the turnout to a virtual block and simulate the occupancy.

I describe one method I have built using Logix.

You can do the same with LogixNG.

My description to gaps, turnout powering, occupancy blocks, and occupancy on my .

--

Ken
NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959)
Loconet * JMRI 5.9.5 * OSX,Win10,Ubuntu

Dave wrote: Q3. ?Signal heads and SSL are based on being attached to turnouts. ?Signal masts are attached to block boundaries. ?If you want to place signal masts at turnout throats, you need a block boundary at the throat. ?This means that turnouts (or groups such as 3-way or ladder) need their own block. ?There are techniques using logic to simulate a virtual turnout block.

I my case, I don’t need or want to place a mast at the turnout throat, the mast will be at the legs. This turnout is one end of a single track main diverging to two destinations with the same for the other end, diverging to two other locations. The masts will be at legs of both turnouts at either end.?