Innovative Model Railroad Control System

User Tools

Site Tools

Trace:
locations-details-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
locations-details-en [2021/06/04 18:17] – old revision restored (2021/06/03 15:51) smitt48locations-details-en [2024/01/22 11:26] (current) – [Requirements] rjversluis
Line 5: Line 5:
 // \\ // \\ // \\ // \\
  
-{{:location-details-en.png?800}}\\+{{:location-details-en.png?801}}\\ 
  
  \\  \\
 +===== Prioritization =====
 +Normal or blocklist selection.\\
 +See: __**[[:rocrailini-automode-en#location_prioritization|Location prioritization]]**__ \\
  
 + \\
 ===== Flow management ===== ===== Flow management =====
-The flow management of a location controls outgoing trains and is very well suited to manage hidden yards: The minimal occupancy grants the yard remains partly filled while the FiFo option allows the trains to exit alternately.+The flow management of a location controls outgoing trains and is very well suited to manage hidden yards: The minimal occupancy grants the yard remains partly filled while the Fifo option allows the trains to exit alternately.
  
 ==== Requirements ==== ==== Requirements ====
Line 16: Line 21:
   * The block type should be set to **Others** (see **[[:block-details-en|Block Details]]**).   * The block type should be set to **Others** (see **[[:block-details-en|Block Details]]**).
   * The __**[[:block-gen-en#mainline|Mainline]]**__ Block option must be disabled. :!:   * The __**[[:block-gen-en#mainline|Mainline]]**__ Block option must be disabled. :!:
 +  * All blocks must have the same orientation for some flow options.
  
  
Line 38: Line 44:
  
   * Schedules may be used together with flow management. However, the **[[:schedules-dest-en#time_processing|Time Processing]]** of the respective schedule should be set to **Relative** as the flow management takes priority over the schedule's departure times.   * Schedules may be used together with flow management. However, the **[[:schedules-dest-en#time_processing|Time Processing]]** of the respective schedule should be set to **Relative** as the flow management takes priority over the schedule's departure times.
-  * If a train has already received the exit permit, but has not yet left the block, he is no longer counted in the minimum occupation. \\ Even if only because the minimum occupation of the location - seemingly - would be given no other train can drive out.+  * If a train has already received the exit permit, but has not yet left the block, it is no longer counted in the minimum occupation. \\ If this is the only reason why the minimum occupation of the locality - apparently - would still be given, no other train can leave.
  
  
Line 44: Line 50:
 In conjunction with **Minimal Occupied** (see above) this option will allow departing trains to regard the "First in, first out" rule.\\ In conjunction with **Minimal Occupied** (see above) this option will allow departing trains to regard the "First in, first out" rule.\\
  
-  * If the FiFo option is activated trains do depart in strict rotation.+  * If the Fifo option is activated trains do depart in strict rotation.
     * This can only be overwritten with a train (re)__**[[:loc-tab-en#start_stop|Start]]**__ command (see also [[#minimal_occupied|Minimal Occupied]] above).     * This can only be overwritten with a train (re)__**[[:loc-tab-en#start_stop|Start]]**__ command (see also [[#minimal_occupied|Minimal Occupied]] above).
   * __All__ trains in this location must be in automatic mode to enable flow and to prevent a deadlock situation.   * __All__ trains in this location must be in automatic mode to enable flow and to prevent a deadlock situation.
Line 54: Line 60:
 A random "Fifo" sequence is created at the start of a Rocrail session. A random "Fifo" sequence is created at the start of a Rocrail session.
 \\ \\
 +>**Remark:** The last locomotive arrival time, is taken into account if Fifo is set without random.
 +>**Remark:** Thus the block sequence in the location no longer plays a role.
 ==== Trains ==== ==== Trains ====
 Only locomotives with an assigned train are allowed in this location.\\ Only locomotives with an assigned train are allowed in this location.\\
Line 71: Line 79:
 Set the maximal occupancy in the location if it needs some free blocks to move trains without deadlocking. A value of zero disables the maximal occupied option.\\ Set the maximal occupancy in the location if it needs some free blocks to move trains without deadlocking. A value of zero disables the maximal occupied option.\\
 This option can be specified for both enter sides.\\ This option can be specified for both enter sides.\\
-The Number of Commuter trains plus Others should be set equal to the total. No train can enter this location if both are set to zero.\\+The Number of Commuter trains plus Others**(("Other" here does not mean the type, but __all other types, except commuter trains__))** should be set equal to the total.\\
 ====Commuter train==== ====Commuter train====
 Maximal number of commuter trains in this location. (Independent of the enter side)\\ Maximal number of commuter trains in this location. (Independent of the enter side)\\
Line 95: Line 103:
 In case of actions the __**[[:text-gen-en#variables|%callertext%]]**__ variable will be set with plain ASCII or HTML.\\ In case of actions the __**[[:text-gen-en#variables|%callertext%]]**__ variable will be set with plain ASCII or HTML.\\
  
-> Tip: See the __**[[:users:nice2have:iot-fahrplananzeiger-de|User page of Gerrit for a Node-RED implementation]]**__. (DE)\\ {{:users:nice2have:iot-fpa.jpg?300}}\\+> Tip: See the __**[[:userpages:nice2have:iot-fahrplananzeiger-de|User page of Gerrit for a Node-RED implementation]]**__. (DE)\\ {{:users:nice2have:iot-fpa.jpg?300}}\\
  
 ====Publish==== ====Publish====
 Publish the timetable to all clients.\\ Publish the timetable to all clients.\\
 Rocview will automatically __**[[:rocgui-gen-en#popup_timetables|popup Timetable dialogs]]**__ if wanted. (No actions needed.)\\ Rocview will automatically __**[[:rocgui-gen-en#popup_timetables|popup Timetable dialogs]]**__ if wanted. (No actions needed.)\\
 +
 +To reset the schedules to the last position and size shown, the option __**[[:rocgui-gen-en#restore_dialog_size|Restore dialog size]]**__ must be activated.\\
 +If this does not happen after Rocrail has been restarted, (then one time only) the popup windows will have to be closed manually.\\
  
 ====HTML==== ====HTML====
Line 134: Line 145:
 =====Flow management examples===== =====Flow management examples=====
 ==== Example 1==== ==== Example 1====
-Location 1 has FiFo active and minimal occupancy 3.\\ +Location 1 has Fifo active and minimal occupancy 3.\\ 
-Location 2 has FiFo active and minimal occupancy 2.\\+Location 2 has Fifo active and minimal occupancy 2.\\
 {{:location:location-test.png}}\\ {{:location:location-test.png}}\\
   * {{:location:location-test.zip}}   * {{:location:location-test.zip}}
Line 142: Line 153:
  
 ==== Example 2 ==== ==== Example 2 ====
-Location “Schattenbahnhof” has FiFo active, minimal occupancy 3, permission nothing chosen.\\ +Location “Schattenbahnhof” has Fifo active, minimal occupancy 3, permission nothing chosen.\\ 
-Location “Fernverkehr” has FiFo active, minimal occupancy 2, permission of type “Intercity”.\\ +Location “Fernverkehr” has Fifo active, minimal occupancy 2, permission of type “Intercity”.\\ 
-Location “Güterverkehr” has FiFo active, minimal occupancy 2, permission of type “Freight”.\\+Location “Güterverkehr” has Fifo active, minimal occupancy 2, permission of type “Freight”.\\
 {{:users:cds:bsp_ortschaften.png}}\\ {{:users:cds:bsp_ortschaften.png}}\\
   * {{:users:cds:test_ortschaften.zip}}\\   * {{:users:cds:test_ortschaften.zip}}\\
locations-details-en.1622823477.txt.gz · Last modified: 2021/06/04 18:17 by smitt48