User Tools

Site Tools


userpages:hermannk:longtrainshortblocks-en

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
userpages:hermannk:longtrainshortblocks-en [2020/06/22 16:18] – [Circumstances] hermannkuserpages:hermannk:longtrainshortblocks-en [2021/02/28 09:02] (current) hermannk
Line 1: Line 1:
 ====== Long Train - Short Blocks ====== ====== Long Train - Short Blocks ======
-Version 2; the actual version. \\ +[[:userpages#Hermann (hermannk)|Userpages - Hermann (hermannk)]] \\ 
-{{menatwork40left.png?|}} under construction {{menatwork40right.png?|}} \\+ \\ 
 +Version 2; the actual version. Completed on June 23, 2020. \\ 
 + \\
 **Foreword 1:** \\ **Foreword 1:** \\
 This documentation has been created with: \\ This documentation has been created with: \\
Line 11: Line 13:
 | Rocrail-Client  | MacBook Pro 13" (2009)  | running macOS 10.11.6 (El Capitan) | | Rocrail-Client  | MacBook Pro 13" (2009)  | running macOS 10.11.6 (El Capitan) |
 | Rocrail-Client  | iPhone  | running iOS 13.x and RocWeb using the Safari web-browser | | Rocrail-Client  | iPhone  | running iOS 13.x and RocWeb using the Safari web-browser |
-| Rocrail Workspace | {{longtrainshortblocks.zip|}} |  |+| Rocrail Workspace | {{longtrainshortblocks_02b.zip|}} |  |
  
 **Foreword 2:** \\ **Foreword 2:** \\
Line 17: Line 19:
  
 ===== Circumstances ===== ===== Circumstances =====
-A layout (1200mm x 3000mm) was designed for test purposes, which \\+A layout (1200mm x 3600mm) was designed for test purposes, which \\
 - consists of two ovals and \\ - consists of two ovals and \\
 - a storage area for trains and \\ - a storage area for trains and \\
 - a storage area for locomotives (or short trains). \\ - a storage area for locomotives (or short trains). \\
 For this documentation only the inner oval is considered (here marked with gray and colored tracks).\\ For this documentation only the inner oval is considered (here marked with gray and colored tracks).\\
 +{{hs03c2_pro_lzkb_montage_02b.png?|}} \\
  
 Since there should be at least three Rocrail blocks in an oval, the oval was divided into four blocks: \\ Since there should be at least three Rocrail blocks in an oval, the oval was divided into four blocks: \\
 - the two straight lines and \\ - the two straight lines and \\
 - the two arches. \\ - the two arches. \\
-Since the upper straight line is intersected by a switch, two small blocks were provided on the left and right side of the switch. \\+Since the upper straight line is intersected by a switch, two small blocks were provided on the left side and one on the right side of the switch; these two blocks bk15 and bk16 are concatenated to one long virtual block bk1516v \\
 {{hs03c2_pro_lzkb_beschriftung_02b.png?|}} \\ {{hs03c2_pro_lzkb_beschriftung_02b.png?|}} \\
-A short train can now travel on each block, while a long train can only travel on the two straight lines if you combine the two blocks into one block on the upper straight line. This documentation describes how to define this in Rocrail. \\+A short train can now travel using each block. \\ 
 +long train can travel from the upper straight line to the right arch and to the bottom straight line. The left arch is then too short for a long train. To continue via the left arch to the upper straight line a manual route ist defined using a "via block" configuration. This documentation describes how to define this in Rocrail. \\
 The colored tracks represent the sensors. The block lengths were calculated from the length between the sensors plus the length of the "enter" sensor (but without the "in" sensor). \\ The colored tracks represent the sensors. The block lengths were calculated from the length between the sensors plus the length of the "enter" sensor (but without the "in" sensor). \\
  
 ===== Rocrail: Plan ===== ===== Rocrail: Plan =====
-The Rocrail blocks are shown in the first picture. They are arranged in a clockwise direction; the train always moves from the plus side into a block. This is not mandatory, but should be dealt with in this way in this documentation. \\ +The Rocrail blocks are shown in the first picture. Compact blocks are short and long blocks are long. They are arranged in a clockwise direction; the train always moves from the plus side into a block. This is not mandatory, but should be dealt with in this way in this documentation. \\ 
-{{rocrail_lzkb_plan_01.png?500|}} \\+{{rocrail_lzkb_plan_01_02b.png?500|}} \\
 The Rocrail - **blocks** require an "identifier". It consists of the two letters "bk" (for the English word "block") and a two-digit number. The entire Rocrail layout uses  \\ The Rocrail - **blocks** require an "identifier". It consists of the two letters "bk" (for the English word "block") and a two-digit number. The entire Rocrail layout uses  \\
 - block number 10 to 19 in the northern part,  \\ - block number 10 to 19 in the northern part,  \\
Line 42: Line 46:
 The Rocrail - **sensors** need an "identifier". It consists of the two letters "fb" (for the English word "feedback"), a two-digit number and a plus sign or a minus sign, depending on whether the sensor is arranged on the plus side of the block or on the minus side of the block. None of this is mandatory either, but should ... \\ \\ The Rocrail - **sensors** need an "identifier". It consists of the two letters "fb" (for the English word "feedback"), a two-digit number and a plus sign or a minus sign, depending on whether the sensor is arranged on the plus side of the block or on the minus side of the block. None of this is mandatory either, but should ... \\ \\
 The Rocrail - **switches** require an "identifier". It consists of the two letters "sw" (for the English word "switch") and a two-digit consecutive number. This is ... \\ The Rocrail - **switches** require an "identifier". It consists of the two letters "sw" (for the English word "switch") and a two-digit consecutive number. This is ... \\
-{{rocrail_lzkb_plan_02.png?500|}} \\+{{rocrail_lzkb_plan_02_02b.png?500|}} \\
 The Rocrail router assigns the sensors to the blocks and generates these block properties: \\ The Rocrail router assigns the sensors to the blocks and generates these block properties: \\
 ^  Block  ^  General  ^  Routes  ^^^^ ^  Block  ^  General  ^  Routes  ^^^^
Line 49: Line 53:
 |  bk15  |  532    fb15+  |  fb15-  |  fb15-  |  fb15+  | |  bk15  |  532    fb15+  |  fb15-  |  fb15-  |  fb15+  |
 |  bk16  |  802    bk16+  |  bk16-  |  bk16-  |  bk16+  | |  bk16  |  802    bk16+  |  bk16-  |  bk16-  |  bk16+  |
-|  bk22  |  565   |  bk22+  |  bk22-  |  bk22-  |  bk22+  |+|  bk22  |  1695   |  bk22+  |  bk22-  |  bk22-  |  bk22+  |
 |  bk32  |  1695    bk32+  |  bk32-  |  bk32-  |  bk32+  | |  bk32  |  1695    bk32+  |  bk32-  |  bk32-  |  bk32+  |
 |  bk42  |  565    bk42+  |  bk42-  |  bk42-  |  bk42+  | |  bk42  |  565    bk42+  |  bk42-  |  bk42-  |  bk42+  |
Line 58: Line 62:
 - bk1516v = bk15 and bk16 \\ - bk1516v = bk15 and bk16 \\
 Rocrail outlines virtual blocks with dashed lines. Virtual blocks have to be created manually. While the Rocrail router can assist us with the configuration of sensors, signals, routes, commands for switches and signals, etc., all of this has to be configured manually for virtual blocks. \\ Rocrail outlines virtual blocks with dashed lines. Virtual blocks have to be created manually. While the Rocrail router can assist us with the configuration of sensors, signals, routes, commands for switches and signals, etc., all of this has to be configured manually for virtual blocks. \\
-{{rocrail_lzkb_plan_03.png?500|}} \\+{{rocrail_lzkb_plan_03_02b.png?500|}} \\
 The orientation of the individual blocks that make up the virtual block is mandatory here! This and other important basic requirements can be found in the wiki at https://wiki.rocrail.net/doku.php?id=block-gen-en#virtual \\ The orientation of the individual blocks that make up the virtual block is mandatory here! This and other important basic requirements can be found in the wiki at https://wiki.rocrail.net/doku.php?id=block-gen-en#virtual \\
  \\  \\
Line 114: Line 118:
  
 1) route [bk32-]-[bk42+]: for a short train the next block bk42 is reserved: \\ 1) route [bk32-]-[bk42+]: for a short train the next block bk42 is reserved: \\
-{{lc_short_start.png?|}} \\+{{lc_short_start_02b.png?|}} \\
  
 2a) route [bk32-]-[bk1516v+] via bk42: for a long train the blocks bk42, bk15, bk16 and the virtual block bk1516v are reserved: \\ 2a) route [bk32-]-[bk1516v+] via bk42: for a long train the blocks bk42, bk15, bk16 and the virtual block bk1516v are reserved: \\
-{{lc_long_start.png?|}} \\+{{lc_long_start_02b.png?|}} \\
  
 ==== Fine-tuning the routes ==== ==== Fine-tuning the routes ====
 2b) route [bk32-]-[bk1516v+] via bk42: a short train can of course also choose the route to the virtual block: \\ 2b) route [bk32-]-[bk1516v+] via bk42: a short train can of course also choose the route to the virtual block: \\
-{{lc_short_start_bad.png?|}} \\ +{{lc_short_start_bad_02b.png?|}} \\ 
-If this is not desired, you can define **conditions** in the route to the virtual block, e.g. **"Minimum train length"** [millimeters] \\+If this is not desired, just define **conditions** in the route to the virtual block, e.g. **"Minimum train length"** [millimeters] \\
 {{route_min_train_length-en.png?720|}} \\ {{route_min_train_length-en.png?720|}} \\
 The value can be set like this: \\ The value can be set like this: \\
Line 132: Line 136:
 {{switch_belongs_to_virtual_block_properties-en.png?615|}} \\ {{switch_belongs_to_virtual_block_properties-en.png?615|}} \\
 The switch is now marked in red when the virtual block is occupied. \\ The switch is now marked in red when the virtual block is occupied. \\
-{{switch_belongs_to_virtual_block_plan.png?443|}} \\+{{switch_belongs_to_virtual_block_plan_02b.png?443|}} \\
  
 ===== Rocrail Workspace ===== ===== Rocrail Workspace =====
-All tests have been done  with this {{longtrainshortblocks.zip | Rocrail workspace}}, whereby only the direction of travel from block "bk32" via block "bk42" to the virtual block "bk1516v" was examined and checked. Other driving options have not been checked and may contain discrepancies. \\+All tests have been done  with this {{longtrainshortblocks_02b.zip | Rocrail workspace}}, whereby only the direction of travel from block "bk32" via block "bk42" to the virtual block "bk1516v" was examined and checked. Other driving options have not been checked and may contain discrepancies. \\
  
 ===== further ideas ===== ===== further ideas =====
 A train of length 545 mm can drive from block "bk32" to block "bk42", but not to block "bk15" because block "bk15" is only 532 millimeters long. So it will occupy the long virtual block. To avoid this, manually create a route from block "bk42" to block "bk16" via block "bk15" and inside the permissions of the route set a minimum length of 512 mm. Have fun. \\ A train of length 545 mm can drive from block "bk32" to block "bk42", but not to block "bk15" because block "bk15" is only 532 millimeters long. So it will occupy the long virtual block. To avoid this, manually create a route from block "bk42" to block "bk16" via block "bk15" and inside the permissions of the route set a minimum length of 512 mm. Have fun. \\
  
userpages/hermannk/longtrainshortblocks-en.1592835487.txt.gz · Last modified: 2020/06/22 16:18 by hermannk