Differences

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

@@ Line 1: / Line 1: @@
+======Routes======
+[[:english#objects|{{  :objects.png}}]][[:english|{{  :rocrail-logo-35.png}}]]
+[[:english|Content]] -> [[:english#objects|Objects]] -> [[:block-en|Blocks]]
+  *  [[block-index-en|Index]] | [[:block-gen-en|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]]
+     * [[block-sensor-en|How many sensors (feedbacks) per block make sense?]]
+// \\ // \\
+===== BlockDialog Routes Tab. =====
+{{:block-routes-en.png?800}}\\
+ \\
+> **Note:** The route tab will be disabled in case of a modular layout.\\
+ \\
+===== Route =====
+Select the route to setup the events for that route.\\
+ \\
+==== Specific-Routes and General-Routes ====
+//**General-Routes:**// \\
+The **all enter +** Route can be used as a default for all routes entering the PLUS(**+**) side. \\
+likewise, \\
+The **all enter -** Route can be used as a default for all routes entering the MINUS(**-**) side. \\
+//**Specific-Routes:**// \\
+If other sensors are used for a Specific-Route, then these sensors override the sensors in the General-Route. However all other Routes still use the sensors defined in the General-Routes. \\
+The use of the General-Routes (+ or -) significantly reduces the number of sensor entries to be made, especially when several Routes lead to a Block.
+ \\
+==== ID ====
+Select the sensor ID to use from this combobox.
+ \\
+=====Event=====
+Select the event for the sensor.
+{{  block:sensor-event-de.png}}
+  * enter
+  * enter2pre
+  * enter2route((enter2route is obsolete and was replaced by FiFo blocks. Since it will be removed from Rocrail someday, it should not be used anymore.))
+  * enter2in
+  * enter2shortin
+  * pre2in
+  * in
+  * exit
+  * occupied
+  * ident
+  * shortin
+  * free
+  * enter2free
+  * [empty] - without assignment to an event, usable for locomotive functions. See: **[[#sensor_without_event|Sensor without event]]**.
+For detailed explanation see chapter __**[[:sensors_and_blocks-en|Sensors and Blocks]]**__\\
+| Events maybe multiple defined to enable multiple sensor systems like magnets and current detection. |\\
+===Sensor without event ===
+A sensor, which is assigned to the block without event, are passed the parameters for actions. This provides the information about the current locomotive triggering the sensor (%lcid%) in order to trigger a loco function (whistle, high beam on, etc.). It is irrelevant whether this sensor is arranged before or after the block. It should be noted, however, that all sensors assigned to the block are checked for "free". \\
+:!: Without occupancy or reservation of the block, the triggering of this sensor also generates the state //GHOST//.
+ \\
+  * **Note:** See also __**[[route-sensors-en#sensor_without_event|Sensor without event]]**__ in a route.
+==== End pulse (endpulse) ====
+| Deprecated and no Forum support. | \\
+{{sensor-pulse-en.png}} \\
+Trigger at the down flank of the pulse.
+Better do not use this unless you can make sure the pulse will not have any disturbance.
+By using the up and down flank you can use one sensor generating two events.
+ \\
+==== T2====
+"Event timer 2" will be used if this option is activated.
+ \\
+==== Button [...] ====
+Calls the properties dialogue of the sensor defined under [[#id|ID]] in this line.
+ \\
+==== Event timer 1 and Event timer 2 ====
+Time (in milliseconds) the events specified above will be delayed. Event timer 2 is used for events with option [[#t_2|T2]] activated only. \\
+For details see chapter [[#event_timer|Event timer]] below.
+ \\
+==== Force block timer ====
+Overrules the optional **[[:loc-details-en#event_timer|loco event timer]]**.\\
+ \\
+==== Select shortest block ====
+See: __**[[:rocrailini-automode-en#select_shortest_block|Select shortest block]]**__\\
+This flag is only evaluated if the global flag in the Rocrail options is not set and will be only active from this block to the next.\\
+ \\
+==== Ignore events if not reserved ====
+This option can be used to share sensors between blocks.\\
+Sensor events will only processed if the block is in reserved state. (Yellow or blue.)\\
+Ghost detection will not work if this option is set; Use only in case it is really needed. \\
+ \\
+==== Properties ====
+Shows the properties dialog for the selected route.
+ \\
+==== Test ====
+With the Test button you can activate all switch and output commands for the selected route.\\
+ \\
+===== Event timer =====
+Advice: // Use __**[[:loc-bbt-en|BBT]]**__ instead of timers.//
+^ :!: **Event timers can mix up the actual sequence of events which leads to unexpected automatic behavior. :!:\\ :!: Use with care or use real sensors instead.** :!: |\\
+ \\
+__All event timers must be set to zero or reduced to a minimal value before reporting any problem in the Forum regarding unexpected event warnings.__\\
+ \\
+^Adjusted event^Timer effect((of event timer 1 or event timer 2, depending on which one was activated for the event, see [[#t_2|T 2]] above))^
+| **enter**  | __None__, **enter** events will not be delayed. |
+| **enter2in**  | Delay between events **enter** and **in**.  |
+| **pre2in**  | Delay between event **pre2in** and speed **Vmin**.  |
+| **enter2pre**  | Delay between the events **enter** and **pre2in** \\ If a block contains the feedbacks **enter** and **in** then a third feedback **pre2in** is simulated. \\ The **enter** is immediate, but the **pre2in** trigger follows after the time in ms.  |
+| **in**  | Delay between events **in** and speed **0**.  |
+:!: If the timer is set too long the **in** event will get delayed.\\
+\\
+^ Selection order of only the first active timer between event and zero ^^^
+^ Result ^ Delay ^ Force delay with "Block timer" ^
+| **enter** | Lok event timer -> zero | Lok event timer -> zero |
+| **pre2in** | Lok event timer -> Block event timer -> zero | Block event timer -> Lok event timer -> zero |
+| **in** | Schedule IN delay -> Lok event timer -> Block event timer -> zero | Schedule IN delay -> Block event timer -> Lok event timer -> zero |
+//When a value is zero, then the next value is checked.\\
+If a value greater than zero, then this value is used and the series is ended.\\
+A **enter2in** event is evaluated as 2 events first an **enter** and then an **in**.//\\
+ \\
+==== Fine Tuning of stopping point ====
+Rocrail revision 1573 or higher allows for fine tuning of the stopping point.\\
+{{:blockdialog_1573_en.png|}}\\
+There are two event timers. This allows for asymmetrical stopping in the block when using the **enter2in** event. An example where this option is useful is a station block where the platform is not in the centre of the sensor section. By using this option different event timers and thus different stopping points can be used for trains entering the block from the right and from the left.\\
+For every route the tickbox T2 determines if "Event timer 1" (T2 not ticked) or "Event timer 2" (T2 ticked) is used. The tickbox is only evaluated when the event is an **enter2in**, **enter2pre** or an **in** event. The **in** event, regardless when it comes from a real sensor or when it is generated by the **enter2in** sensor, is delayed by the selected event timer. The value of the event timers is specified in milliseconds.\\
+In the loco properties **[[:loc-details-en|Loc details]]** fine tuning for the selected event timer due to differences in characteristics of different locos is possible.\\
+> **Note:** Contrary to previous revisions, the event timer is not only effective for the **enter2in** event, but also works for a real **in** sensor. \\ When using schedules, if an in delay is specified, this takes preference over the block event timer. Also, when an event timer is specified in the loc properties, this also takes preference over the block event timer, but not over the in delay in a schedule.
+ \\
+=====Free at off=====
+As alternative to [[:block-gen-en#free_previous_block_on_enter|Free previous block on enter]] the Free event can be used in combination with Enter.\\
+====Requirements====
+  * The sensor is of type current sense.
+  * The sensor decoder is debounced. (WIO, CANGC2, GCA50)
+  * All wagon wheels and axis are conductive.
+====Example====
+The Enter sensor is also used as Free sensor but with option "Endpulse".\\
+{{:block:block-free-en.png?800}}\\