Differences

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

--- block-gen-en [2020/11/24 13:48] – rainerk
+++ block-gen-en [2024/01/25 14:43] (current) – rjversluis
@@ Line 2: / Line 2: @@
 [[:english#objects|{{  :objects.png}}]][[:english|{{  :rocrail-logo-35.png}}]]
 [[:english|Content]] -> [[:english#objects|Objects]] -> **[[:block-en|Blocks]]**
-  *  [[block-index-en|Index]] | **General** | [[:block-signals-en|Signals]] | [[:block-details-en|Details]] | [[:block-routes-en|Routes]] | [[:block-int-en|Interface]] | [[:block-permissions-en|Permissions]] | [[block-statistics-en|Statistics]] | [[:block-menu-en|Menu]] | [[:block:block-embededfb-en|Embedded sensors]]
+  *  [[block-index-en|Index]] | **General** | [[:block-signals-en|Signals]] | [[:block-details-en|Details]] | [[:block-routes-en|Routes]] | [[:block-int-en|Wiring]] | [[:block-permissions-en|Permissions]] | [[block-statistics-en|Statistics]] | [[block-td-en|Trackdriver]] | [[block-tracking-en|Tracking]] | [[:block-menu-en|Menu]] | [[:block:block-embededfb-en|Embedded sensors]]
@@ Line 28: / Line 28: @@
 In that case is also necessary, that the Block option __**[[#small_symbol|Small symbol]]**__ __and__ the Rocview option __**[[rocgui-gen-en#show_loco_image_in_block|Show loco image in block]]**__ must NOT be activated.
+>//**Example:**// With 'ID' = "**BK3**" and 'Platform' = "**5**", the Block symbol show "**BK3 (5)**".\\
  \\
@@ Line 66: / Line 67: @@
  \\
-=====FiFo size and gap=====
+=====FiFo=====
 This feature is only usable with automobiles which have infra red detectors to keep distance to the vehicles ahead.\\
 __In all other cases enabling this feature will lead to **accidents**.__\\
-\\
+====Size====
 The size is the number of allowed concurrently automobiles in this block.\\
-\\
+====Gap====
 In addition a gap can be specified here. This should be the gap the cars keep to each other due to their Infrared-Detectors.\\
 If this gap is >0 the length of the cars + the gap will be taken into account with regard to the block length.
@@ Line 80: / Line 81: @@
   * In combination with the __**[[#free_previous_block_on_free_or_enter|Free previous block on enter]]**__ option the throughput of following vehicle will increase.
   * Is not compatible with the **enter2route** event.
+> **Note on FiFo blocks for cars:** If the FiFo size is greater than 0 in a block, waiting is ignored, ... see also [[block-details-en#Wait]]
  \\
@@ Line 90: / Line 93: @@
 The **tripple dot** [...] button can be pushed to modify the loco properties. This is __not__ usable for selecting another loco. \\
- \\
+=====Image====
+If the block is occupied and the box is checked, the locomotive picture is displayed in the block symbol. \\
+The global Rocview option ** [[rocgui-gen-en #show_loc_image_in_block | Show loc image in block]] ** must be activated.
 =====Turntable ID=====
 The turntable ID is selected here if this block contains a turntable.
@@ Line 104: / Line 110: @@
 =====Virtual=====
 Virtual blocks are used to group a number of slave blocks to define it as one.\\
-Routes to and from virtual blocks are not automatically generated by the Router and must be defined manually including the route sensors.
-  * Use the __**[[:route-perm-en#min._train_length|Min. train length]]**__ to prevent running short trains in the virtual block.
-Use the **Show** flag to hide a virtual block from the layout.\\
+> **Important NOTES:**
-> **Tip:** The Master and slave blocks must have the plus sides all in the same direction to ensure a correct rendering.
+> The Master and slave blocks must have the plus sides ("+") all in the same direction to ensure a correct rendering.
-> :!: Overlapping or nesting with other virtual blocks is not supported; A block can only be in one virtual block, and a virtual block cannot be part of another virtual block.
+> :!: Overlapping or nesting with other virtual blocks is not supported.
+> A block can only be in __one__ virtual block and a virtual block __cannot__ be part of another virtual block.
+> Routes to and from virtual blocks must be defined manually including the route sensors, because they are not automatically generated by the Router.
+> The __**[[:route-perm-en#min._train_length|Min. train length]]**__ should be used to prevent running short trains in the virtual block.
+> The lengths of the __**[[block-gen-en#length|Blocks]]**__, the __**[[loc-gen-en#length|Locos]]**__ and - //if the train lengths are __not__ included in the locomotive lengths// - also the lengths of the __**[[car-details-en#length|Cars]]**__ must be defined.
+  * **Note:** If the selection of virtual block or slave block is __exclusively__ based on schedules, the definitions of the lengths are not necessary. __For random runs (aquarium mode) the length definitions are necessary.__
 Create a Virtual Block: \\
-  - Place Rocview in Edit mode.\\
+  - Using Rocview, Edit the plan (Track plan->Edit Panel).\\
   - Drag and Drop a Block Symbol on the wanted level and place.\\
-  - Reset edit mode.\\
+  - Go back in Operate mode (Track plan->Operate).\\
   - Specify in the new block properties that its a VB.\\
-====Slave blocks====
+The **[[#show|Show]]** option may used to show or hide the symbol of a virtual block in the layout.\\
-a) normal blocks are supported as slave blocks; \\
-b) [[block:block-embededfb-en|blocks with embedded sensors]] are supported as slave blocks; \\
-c) :!: a mixture of both types of blocks is **NOT supported**! \\
+====Slave blocks====
 A comma separated list of slave blocks __without blanks__. \\
+|< >|
+|  :!: Other virtual blocks and [[block:block-embededfb-en|blocks with embedded sensors]] are NOT supported as slave blocks \\ and also they must be NOT entered to avoid Malfunctions.  | \\
 Example:
 <code>
 B1,B2,B3
 </code>
+The "Three dot button" {{:icons:threedotbutton.png?25}} open a Selection dialog.
-====virtual block "Out of Operation"====
-a) a virtual block made up of normal blocks may be put "out of operation". \\
-b) :!: a virtual block made up of blocks with embedded sensors may **NOT be put "out of operation"** ! \\
 =====Configuration=====
 The block infrastructure is configured using the following flags:
-====Electrified====
+====Electrified (Catenary) ====
 This option can be activated for blocks equipped with a catenary. \\
-If NOT set this prevents locos with **engine type electric** (see **[[:loc-details-en|Locomotive Details]]**) from using this block in auto mode.
+If NOT set this prevents locos with **engine type electric** (see **[[:loc-details-en#engine|Locomotive Engine Type]]**) from using this block in auto mode.
@@ Line 142: / Line 150: @@
 ====Put out of operation====
 If activated, the block will not be used when running in auto mode. The train will stop in the previous block, if no alternate blocks are available.
+  * If the block is "out of operation", it can only be driven on manually and its ghost train detection is deactivated.
+  * The __ ** [[manual-tracking-en | Tracking none operational blocks ]] ** __ is then activated for manual driving. **Note:** Tracking is __not__ possible if [[#sleep_on_closed|Sleep on closed]] is active!
+  * This status can also be activated and deactivated during ongoing operation via __ ** [[block-menu-en#put_out_of_operation_put_into_operation|context menu of the block]] ** __.
 ====Wait====
@@ Line 147: / Line 159: @@
 ====Small symbol====
-Use the small representation of the block symbol. Only available in the SpDrS60 theme.\\
+Use the small representation of the block symbol. Only available in the SpDrS60 and SLIM-COLOR theme.\\
 {{:block:block-small-sym.png}}\\
@@ Line 153: / Line 165: @@
 ====Half automatic====
-Define if the block permits half automatic mode: [[:automatic-en|"Automatic and Half automatic mode"]].
+Define if the block permits half automatic mode. Cf. **[[:automatic-en|Automatic and Half automatic mode]]**.
 ====Accept a ghost train====
@@ Line 190: / Line 202: @@
 > **Note:** This option is disabled if [[#terminal_station|Terminal Station]] is selected (and //vice versa//). Either "Terminal Station" or "Allow change direction" (or none of these) can be selected.
-> **Note:** This option should be disabled if these blocks are part of a  [[blockgroups-props-en#critical_section|Critical Section]].
+> **Note:** This option should be disabled if these blocks are part of a  **[[:blockgroups-props-en#critical_section|Critical Section]]**.
 ====Stop controller====
@@ Line 206: / Line 218: @@
 ====BBT====
-Enable __**[[:loc-bbt-en|BBT]]**__ for this block; Default is enabled.\\
+Enable __**[[:loc-bbt-en|BBT]]**__ for this block.\\
-===Fixed===
-| :!: User option; No official support. |
+===Notes:===
-Keep the loco at enter speed for this number of BBT steps.\\
+>BBT is optimal for visible blocks in which trains must always stop (wait is set). In all other cases the loc should slow down according to the CV4 decoder setting.
->**Note:**
 >The function of BBT is defined for the driving distance between **enter** and **in**.
 >Is there for the block only one feedback **enter2in**, the timings of BBT with the timer of **enter2in** can collide.
+**Therefore it is strongly discouraged to use BBT __and__ enter2in sensors together in the same block**.
 >An **enter2in** defined sensor should be changed to **enter** and at the locomotives the option __**[[loc-bbt-en#generate_in|Generate In]]**__ is to activate.
->In this case the **in** event is determined only by the BBT timing and does not collide with another timer.
+>In this case the **in** event is determined only by the BBT timing and does not collide with another timer. \\
+===Fixed===
+| :!: User option; No official support. |
+Keep the loco at enter speed for this number of BBT steps.\\
+  * ** Attention: ** Do not ** confuse this option ** with the Lok-BBT-Option ** [[: loc-bbt-en#fixed | 'Fixed']] **:!:
 ====Mainline====
@@ Line 222: / Line 240: @@
 ====Sleep on closed====
-This option disables evaluating sensor events during the closed state; Ghost trains are not reported.\\
+Disables evaluating sensor events during the closed state (block out of operation). Without sensor events tracking is disabled. (cf. [[#put_out_of_operation|Put out of operation]]).\\
  \\
 ==== Free previous block on enter ====
@@ Line 229: / Line 247: @@
 With the Route option is it possible to free up the current route too.\\
 The value "Max. Length" defines that an early release, of the previous block, is only performed for trains up to this length.\\
-This prevents that the "From" block is released, before longer trains have completely exited.
+This prevents that the "From" block is released, before longer trains have completely exited. \\
+  * ** Caution: ** A GHOST warning can be triggered if this block is released too early. \\ This can e.g. due to missing or incorrect length specifications, as well as failure to observe the conditions. \\ If the "Route" option is also activated, it may happen that if the switch is released too early \\ turnouts that have not yet been cleared are modified by another route: "Risk of derailment:!:".
  \\
@@ Line 258: / Line 277: @@
 This option can only be used in case the enter detection is always free if the train is in the block.\\
 A ghost will be reported if the enter detection is triggered in case there is already a train __in__ the block.\\
-Look for __**[[:rocrailini-automode-en#auto_mode_off_at_ghost_train|Ghost options]]**__ in the server settings.\\
+Look for __**[[:rocrailini-automode-en#auto_mode_off_at_ghost_train|Ghost options]]**__ in the server settings.
  \\
+==== Check for free destinations until reaching IN ====
+Is only effective in this block for locomotives whose __**[[loc-details-en#check_for_free_destinations_until_reaching_in|corresponding option]]**__ is activated. //See notes there//.\\
+ \\
+==== Assign train ====
+If activated, a train in this block is automatically assigned to the incoming locomotive at the "ENTER" event. (Rev. 2.1.3664+) \\
+Disabled by default. \\
+==== Timer events ====
+This option displays the remaining seconds for the locomotive to wait in this block in a corresponding "State signal". \\
+Disabled by default. \\
+Consumes a lot of computing power in the Rocrail server and Rocrail clients. \\
+**Requirements:** \\
+- Rocrail Properties / Automatic / Event / Timer events = ON; (do not forget to restart Rocrail after having modified this value) \\
+- Block Properties / General / Configuration / Timer events = ON; \\
+- a "State signal" must exist and must be assigned to this block (otherwise you won't see anything). \\
+- the locomotive must wait in this block; \\
+- (Rev. 2.1.3680+) \\
 =====Actions=====