Differences

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

--- route-generate-en [2025/10/11 12:53] – hermannk
+++ route-generate-en [2025/10/15 12:09] (current) – hermannk
@@ Line 5: / Line 5: @@
  \\
-With Rocrail 2.1.6171 a dialog to define "via-routes" has been introduced. \\
+With Rocrail 6197 a dialog to define "via-routes" has been introduced. \\
 The dialog can be opened by clicking to "Rocview Menu -> Track plan -> Generate via route..." \\
 {{:route:generate_via_route_menue-en.png?}} - {{:route:generate_via_route_dialog-en.png?}}\\
@@ Line 41: / Line 41: @@
 ====Generated route====
 If a route could be generated the Route dialog will popup with the new generated route.\\
-| {{:route:generate_via_route_route_general-en.png?427|}} | The ID will get the extension "_via_[list of blocks]" \\  \\ The ID may be edited by the user. \\ \\ The "Description" field is with filled a verbal description of the generated route for example \\ "from [bk04] via [bk03,bk02] to [bk01]" \\ \\ "Automatic generated" will be unchecked \\ \\ **Attention:** in case of alternative routes between two blocks \\ the user should check the command list of the generated route \\ and modify the command list appropriately! |
+| {{:route:generate_via_route_route_general-en.png?427|}} | The ID will get the extension "_via_[list of blocks]" \\  \\ The ID may be edited by the user. \\ Most of the other values must be left unchanged! \\ \\ The "Description" field is filled with a verbal description of the generated route for example \\ "from [bk04] via [bk03,bk02] to [bk01]" \\ \\ "Automatic generated" will be unchecked |
 Clicking the **OK** button will **save** the generated route. \\
 In addition the list of route IDs of the attribute "routeids" of the affected elements is updated with the newly generated route ID. This ensures that the affected plan elements will be properly illuminated.\\
@@ Line 52: / Line 52: @@
 ====</> button====
 The </> button shows the temporary XML code of the generated route. \\
-| {{:route:generate_via_route_xml_code.png?|}} | The code shows the list of commands. \\ \\ The code shows the list of elements that will receive a new "routeids" entry. |
+| {{:route:generate_via_route_xml_code-en.png?|}} | The code shows the list of commands. \\ \\ The code shows the list of elements that will receive a new "routeids" entry. |
  \\
@@ Line 65: / Line 65: @@
 =====Examples=====
---- will come soon --- \\
+====Workspace====
+This plan is used for the examples. \\
+{{:route:generate_via_route_plan.png?606|}} \\
+{{ :route:via_routes_generator_20251014.zip |}} \\
+====Via route 1====
+This example shows a normal situation for via routes. \\
+In this case two blocks should be run through by the locomotive. The reason for that does not matter. \\
+|  {{:route:generate_via_route_example01_plan.png? 624 |}}  ||
+|  {{:route:generate_via_route_example01_via-en.png?327|}}  |  {{:route:generate_via_route_example01_route-en.png?488|}}  |
+The locomotive runs from right to left - from block bk04 (plus side) to block bk01 (minus side) with the via blocks bk03 and bk02. \\
+The sequence of blocks is important for the list of via blocks. \\
+{{:route:generate_via_route_example01_reserved.png?624|}} \\
+The track elements are illuminated correctly. \\
+====Via route 2====
+This example shows a normal situation for via routes. \\
+In this case two blocks should be run through by the locomotive. The reason for that does not matter. \\
+|  {{:route:generate_via_route_example02_plan.png? 624 |}}  ||
+|  {{:route:generate_via_route_example02_via-en.png?327|}}  |  {{:route:generate_via_route_example02_route-en.png?488|}}  |
+The locomotive runs from left to right - from block bk01 (minus side) to block bk04 (plus side) with the via blocks bk02 and bk03. \\
+The sequence of blocks is important for the list of via blocks. \\
+{{:route:generate_via_route_example02_reserved.png?624|}} \\
+The track elements are illuminated correctly. \\
+The signal command is not generated by the via route generator. The command has to be configured afterwards by hand. \\
+====Via route 3====
+This is a negative example. \\
+The via route can not be generated because of a direction track element being placed in the wrong direction. \\
+|  {{:route:generate_via_route_example03_plan.png? 624 |}}  ||
+|  {{:route:generate_via_route_example03_via-en.png?327|}}  |  {{:route:generate_via_route_example03_nofittingroute-en.png?195|}}  |
+The user will receive the message "No fitting route available.". \\
+====Via route 4====
+This example shows a more complex situation for via routes. \\
+The destination block can be reached by two alternative routes. \\
+The via route generator takes one route of the alternative routes. \\
+If a not wanted route is taken the user must modify the command list for the generated route afterwards by hand. \\
+|  {{:route:generate_via_route_example04_plan.png? 624 |}}  ||
+|  {{:route:generate_via_route_example04_via-en.png?327|}}  |  {{:route:generate_via_route_example04_route-en.png?488|}}  |
+The locomotive runs from right to left - from block bk04 (plus side) to block bk11 (plus side) with the via blocks bk03 and bk02 and bk01. \\
+The sequence of blocks is important for the list of via blocks. \\
+{{:route:generate_via_route_example04_reserved.png?624|}} \\
+The signal command is not generated by the via route generator. The command has to be configured afterwards by hand. \\
+The track elements are illuminated correctly for the left alternative route to bk11. \\
+If the right alternative route should have been taken to bk11 the command list must be modified afterwards. \\
+The routeIDs of the affected previous and actual track elements must also be corrected by hand. \\