开云体育

I have a number of crossovers on my layout. I have created them out of 2 single turnouts (either RH or LH).

Each turnout is assigned its own block because I am using signal masts.

?

The problem is that when I right click on a turnout and bring up context menu and select 'view block routing', it only shows straight track blocks connected to it. It doesn't show any connection to the other diverging path that is connected to companion turnout in the crossover.

?

Because of this, I am not able to create transits through the diverging paths of the crossovers.

?

Here is a rough sketch:

?

? ?BLK0 --- ?TL0. --- ?BLK1

? ? ? ? ? ? ? ? ? ? ? ? \

? ? ? ? ? ? ? ? ? ? ? ? ?\

? ?BLK2 ----- TL1 --- BLK3

?

The block routing for TL0 turnout only shows BLK0, BLK1 connected. It doesn't show block TL1. (same for TL1's block routing)

?

What am I doing wrong?

?

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

Vimal,

Does the connecting track segment between the diverging legs have a block assigned? ?It gets the block from either TL0 or TL1. ?From the Layout Editor menu, look at the Tools -> Check menu items.

Dave Sand

If I move the ?TL0 slightly to look at that zero length track segment, it has the same block name as TL0.?

Tools-> Check doesn’t show any errors

?

yet the block route still shows no connection between the turnouts

?

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

Vimal,

If you upload the xml file to the group's ProblemsBeingWorkedOn file folder I can see what the issue is.

Dave Sand

Correction. The track segment between TL

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

Dave

i deleted the segment between TL0 and TL1 and reconnected the two turnouts. Now the block route shows all three connected blocks.?

The next problem is setting a transit. I assigned sections as follows:

?

SEC0 = BLK0:TL0

SEC1 = BLK1

SEC2 = BLK2

SEC3 = TL1:BLK3

?

in the transit, I want to go from SEC0 to SEC3 but that option is not given in the next section drop down menu. Only SEC1 is listed?

?

?

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

Vimal,

I don't have the current version of your xml file so things may have changed.

You can't physically get from BLK0 to BLK3 via the crossover.

Dave Sand

Dave

?

I have uploaded my actual layout file in ProblemsBeingWorkedOn/Vimal Parikh folder (file: scenic_ridge_sm_new.xml)

The above example was an abstract from above layout to simplify the message. ?

The actual layout has 3 cross overs with turnout names of TL0 & TL1, TR0 & TR1, TR2 & TR3

?

You can look at either TL0 & TL1 or TR0 & TR1 crossovers.

?

TL0 is connected to BLK0, BLK1 and TL1.

TL1 is connected to BLK3, BLK4 and TL0

The sections are created one per block and has the same indices as blocks (i.e SEC0, SEC1 ...)

?

My preferred path is to go from BLK3 to BLK1 via TL1 -> TL0 crossover (Or BLK2 to BLK3 via TR0/TR1 crossover)

All logic works upto creating the sections but when I try to create a transit involving above paths, it doesn't work.

?

Thanks for you help

?

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

Vimal,

Your latest upload has several errors.

The block for TL0 block is BLK1, it should be BLK_TL0.

There is no block assigned to the track segment between TL0 and TL1. ?I am using BLK_TL0.

There is no block assigned to the track segment between TR0 and TR1. ?I am using BLK_TR0.

The block for TR1 block is BLK3, it should be BLK_TR1.

There is no block assigned to the track segment between TR2 and TR3. ?I am using BLK_TR2.

Dave Sand

Thanks

I fixed those errors.

Then I had to reconfigure the sections again

and now the transits are working as I wanted.

?

Thanks again.

?

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

On Wed, Dec 18, 2024 at 06:35 AM, <tour-mayors.0e@...> wrote:

I fixed those errors.

One thing to keep in mind with blocks and their boundaries is to consider how a train moves from one block to the next across a common boundary. In the case of a crossover, a train travelling from BLK1 to BLK 3 or reverse is logically impossible.

?

?

I know with warrants this is enforced by portals, a defined boundary between two oblocks and the path traversing that portal.

?

--

Nags,

You also cannot create a transit either.

Dave Sand

Dave

?

Since I have created separate blocks for each turnout in my layout, do I also need to create separate sections for each turnout?

I don't have any occupancy sensors attached to the turnouts so a separate section may not work

?

Will the transits work if I don't have a separate sensor attached to the turnouts? ?

(On my physical layout, the turnouts are part of the block that is connected at the point end (i.e. throat)).

?

--

+===============================
|. Vimal Parikh

+------------------------------------------

+===============================

Vimal,

I prefer to use one block per section. ?Multiple block sections are fine.

Dispatcher requires that all Dispatcher controlled blocks have detection and that the blocks become occupied in the proper sequence based on the transit direction.

You actually have a number of possiblities due to the physical block arrangement.

You can cut gaps and add additional detection sensors.

You can use signal heads and SSL instead of signal masts and SML. ?Signal heads are placed at turnouts instead of block boundaries. ?They are also required if an anchor point is a block boundary. ?SSL only supports one turnout per signal head set. ?Special logic is needed for crossovers and slips. ?Sections require direction sensors which is added to the SSL.

For signal masts and SML, you can use virtual blocks and sensors for the turnout block. ?The logic is provided by Logix or LogixNG.

Dave Sand

On Wed, Dec 18, 2024 at 11:06 AM, <tour-mayors.0e@...> wrote:

Since I have created separate blocks for each turnout in my layout, do I also need to create separate sections for each turnout?

--

Nags,

Some people don't like stopping a potentially long distance prior to a turnout. ?Consider the scenario where there is one block between sidings which includes the turnouts for each siding. ?Now you don't need the toe/points/throat signal.

Dave Sand

On Thu, Dec 19, 2024 at 07:48 AM, Dave Sand wrote:

Some people don't like stopping a potentially long distance prior to a turnout. ?Consider the scenario where there is one block between sidings which includes the turnouts for each siding. ?Now you don't need the toe/points/throat signal.

?

Dave Sand

Yep, depends on the configuration.?

--