Differences

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

--- action-example-en [2018/11/12 08:56] – external edit 127.0.0.1
+++ action-example-en [2020/04/20 00:49] (current) – smitt48
@@ Line 26: / Line 26: @@
 \\
   * {{:actions:dualswitch-example.zip}}
-\\
+  * **Note:** This example is no longer needed, because several switch objects in the track plan can now be defined with the same address data (address/port).
 ===== Display a variable in a text-element (e.g. 'counter') =====
 . define a text element, eg. "counter" ("zaehler")\\
@@ Line 48: / Line 48: @@
 \\
 The plan uses a dummy loc, either assign this loc to the virtual command station or give the loc an unused address (and make sure that that address remains unused in future). For each "set" of blocks in a row you will need a seperate dummy loc, because one dummy can not occupy multiple blocks.\\
-Four routes are made manually, named manual-[start]-[destination]. The rest of the routes were done by the analyzer. Some routes have permissions set, so that either only long or only short trains use that route.\\
+Four routes are made manually, named manual-[start]-[destination]. The rest of the routes were done by the router. Some routes have permissions set, so that either only long or only short trains use that route.\\
 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.\\