Hi Rich,

Yes, Rocrail allows a sensor to be shared by several blocks in this kind of a setting. Just define "Sensor 2" as the "enter" sensor for all five blocks and tick the box "Ignore events if not reserved". By this, only the block where the train is heading will see the "enter" event.

Likewise, the blocks sb1 ... sb5 could share a single "enter" sensor.

I am not sure if you really need the "exit" sensors. Rocrail documentation says that they are a safely measure covering the case that a train does not stop properly ad the "in" sensor.

I see that two pieces of track are not defined as blocks at all: the top track that bypasses the upper sidings and the track on the left. I think they should be defined as blocks with their own "enter" and "in" sensors to make things work.

The arrow-like block symbol is for setting "staging blocks" where you can park several trains, see https://wiki.rocrail.net...eblock:stagingblocks-en. This probably is not what you had in mind.

Very interesting, when you have time I would love to learn writing an .xml script!

I'll have to read up on this subject:

https://wiki.rocrail.eu/doku.php?id=xmlscripting-en

According to Rocrail documentation, the "Block enter side" setting only relates to whether or not a loco coming from a certain direction will stop and wait in a block.

If your problem is that occasionally a locomotive gets confused about forward / backward directions, then it sounds like a decoder issue outside the scope of Rocrail. I also occasionally experience this with my BRE 19 (Märklin 3769) that has a fairly early version of the 6090 decoder.

For some kind of immediate relief, you can try issuing both of "swap logical direction" and "swap block enter side" commands from the block pop-up menu, effectively making Rocrail believe that the locomotive has been reversed.

Hi Rich

Block signals
There are only ENTER, IN, ENTER2IN, ENTERSHORTIN etc to chose from
No exit signal, the exit (make the block free) is when the train reaches the designated destination block (IN)

Sidings: for those where the full train is stored, only ENTER2IN is needed
for those where the loco, leaves the cars, you need:
- one virtual block with ENTER and IN
- one slave block attached to the block above with a ENTER2IN (same signal as the ENTER of the virtual block

General remark on Rocrail
Rocrail allows HUGE possibilities but when starting do try to make things simple and add complications later

Staging blocks
- I have one (7 sections of various lengths) it works well but can be easily be affected especially at start of day or following a short circuit. In that case, the easiest is to empty the block (remove all locos and reset / clear all sections) and fill it again
- if a loco enters a staging block the normal way (being controlled by Rocrail since a few blocks before) then - in my experience - it will NEVER go the other way EXCEPT with old decoders that do not receive the direction bit (MM protocol and not MM2 / MFX)
- of course the train length must be verified and a gap between train must be set (I selected 3 cm)
- staging blocks are great for a long strech of track (2 to 5 m) to store multiple trains
- staging when in competition with normal block will always NOT HAVE precedence: when a choice is possible, RR will always send the train to the normal block

Direction change of trains
My experience is when I started using Rocrail, I did not fully understand the 3 concepts with train direction:
- block exit side : the little arrow in the block must point to the destination direction. Attention, it may change when you do manual controls
- loco logical side: RR remembers if you are using the loco forwards or reverse. When the loco control block and when the direction button shows a double arrow to the right then the locos headlights must be lit on the GOOD side, otherwise you need to perform a loco LOGICAL change (of direction)
- the loco orientation

In version version of RR, train change direction ONLY IF EXPLICITLY ASKED (by an XML action or equivalent "swap" command) and NEVER have I observed a train changing direction by itself.

I have observed that when you try to control the train direction by the doubble arrow button (now pointing to the right) the order may be executed but after a while when passing over a sensor, RR or your Central Station may send a "keep alive" message including the direction (RR's direction) thus causing the loco to change direction.
Conclusion: with RR, NEVER use the direction change button or your central station direction change (RR is controlling so, sooner or later it wil FORCE a direction change) but rather use the direction logical change button followed by pressing TWICE on the direction button and you will be fine.

I am not sure if I convered all the issues but this is my first try.
Cheers
Jean

Danke sehr! Thank you, worked like a charm….and using the WIKI Demo mode sure speeds up the testing & learning process…

Each block should have its own Enter sensor after the turnout and it should be the majority of the block (or at the start only if not using detection for the whole track length), the In sensor should be near the end, about 20-30cm.

You will set BBT delay to slow the locomotive down at the right time after Enter so that it is at minimum speed by the time it reaches the In sensor, which is when it sets speed to 0 (after a short timer if required)

Hi Rich

On a single direction block;, I recommend 18 cm before the signal for the IN and all the rest of the block for the ENTER.
One bi-directional block, I recommend 18cm in front of each signal (IN for each direction which is also the ENTER for the other one) and the central section is the ENTERSHORTIN
Cheers
Jean

I am am of no help, sorry. I'm worse than you at programming things. Rocrail is excellent, but still requires knowledge and work. It's still challenging for me setting up events with the CS3.

Hi Rich,

I agree with Jean: the IN sensor should be as far as possible to make most of the block length; placing it 18 cm before the signal is what I do as well. And as you already have experienced, a shared ENTER sensor for the sidings 1-5 is sufficient in this setting.

Martti & Jean, you might notice I did not use one "enter" sensor for the lower sidings (6-10), like I did for the upper sidings (1-5). Something I need to change to the track plan after finishing the wiring project. Martti, the single "enter sensor" works just like you said. Thank you. I would not have found this without your help.

"Just define "Sensor 2" as the "enter" sensor for all five blocks and tick the box "Ignore events if not reserved". "

Perhaps you can use XML to close those routes that you don't want Rocrail to select.

I found this useful when I tried automating the operations of the old 7186 turntable. For instance, this piece of code would prevent Rocrail from using any routes that enter the turntable bridge from the "-" orientation, thus making sure that a loco can only enter the bridge from the "+" side:

<?xml version="1.0" encoding="UTF-8"?>
<xmlscript>
<st id="[Track_0-]-[Marklin_7186-]" state="closed"/>
<st id="[Track_4-]-[Marklin_7186-]" state="closed"/>
<st id="[Track_12-]-[Marklin_7186-]" state="closed"/>
<st id="[Track_24-]-[Marklin_7186-]" state="closed"/>
<st id="[Track_36-]-[Marklin_7186-]" state="closed"/>
</xmlscript>

What remains is to figure out how to link this kind of code to the relevant Event (or whatever) via a Rocrail Action, and another Event + Action to open the routes again later. See the documentation for XMLScript for some help. Without a specific use case it is difficult to give more precise advice.