Differences

This shows you the differences between two versions of the page.

--- action-example-en [2020/04/20 00:49] – created - external edit 127.0.0.1
+++ action-example-en [2025/10/07 08:13] (current) – rjversluis
@@ Line 42: / Line 42: @@
 ===== How to handle two short blocks in a row with long trains =====
-| This is not officially supported and is regarded as a work-around for a design flaw. \\ Just let long trains run by route permissions directly in block 1a using the two short blocks as crossing block. |
+| This is not officially supported and is regarded as a work-around for a design flaw. \\ Just let long trains run by route permissions directly in block 1a using the two short blocks as via block. |
-This demo plan has -hopefully- self-explaining names for the objects. The idea behind this plan is that a (shadow)station can have two blocks behind each other. Each of these blocks 1a and 1b can contain a short train, whereas a long train will occupy both blocks, using a route to block 1b with block 1a as crossing block.\\
+This demo plan has -hopefully- self-explaining names for the objects. The idea behind this plan is that a (shadow)station can have two blocks behind each other. Each of these blocks 1a and 1b can contain a short train, whereas a long train will occupy both blocks, using a route to block 1b with block 1a as via block.\\
 {{:actions:shadowstation-two-blocks.png|}}\\
 Without measures, after arrival of a long train in block 1b, block 1a is free again and Rocrail could send a train there. Also, when the long train departs from 1b, it might trigger sensors in block 1a, causing a ghost event in block 1a.\\
@@ Line 51: / Line 51: @@
 Two of the manual routes have an action(control) in them and one has an action condition. One action puts the dummy loc in block 1a, the other action removes it again. Both actions are triggered at the end of the route, when the train has reached its destination block and the route is unlocked. Again, when more "sets" of blocks in a row exist, each set needs its own routes and actions.\\
 By putting a dummy loc in block 1a, Rocrail does not care when the sensors in block 1a go on because the long train in 1b triggers them when driving to block 3. This prevents a ghost state of block 1a.\\
-You can try it with the virtual command station, put the short train in block start2, the long train in block start and start both of them in automode. Train long will use the route from start to 1b with 1a as crossing block. After arrival in 1b, the dummy loc appears in block 1a by the action in the route. Train short will wait in block start, because block 1a is occupied by the dummy loc and block 2 is closed. After the wait in 1b, long will use the manual long route from 1b to 3. You can trigger the sensors of block 1a as much as you like, but because loc dummy is in it, no ghost will occur. After arrival in block 3, the second action removes the dummy loc from block 1a and train short will now go to block 1a.\\
+You can try it with the virtual command station, put the short train in block start2, the long train in block start and start both of them in automode. Train long will use the route from start to 1b with 1a as via block. After arrival in 1b, the dummy loc appears in block 1a by the action in the route. Train short will wait in block start, because block 1a is occupied by the dummy loc and block 2 is closed. After the wait in 1b, long will use the manual long route from 1b to 3. You can trigger the sensors of block 1a as much as you like, but because loc dummy is in it, no ghost will occur. After arrival in block 3, the second action removes the dummy loc from block 1a and train short will now go to block 1a.\\
 \\
 Have a go at it.\\
 {{:actions:two-short-blocks.zip|}}