Differences

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

--- turntable-en [2018/11/12 08:56] – external edit 127.0.0.1
+++ turntable-en [2022/04/24 05:04] (current) – [Bridge Occupancy] rainerk
@@ Line 17: / Line 17: @@
 ====Bridge Occupancy====
 For generating the **enter** and **in** event.
-The most common way ist to split up the bridge track into two equals occupancy sections, and you only have to do this with one rail. (one side of the bridge track)
+The most common way ist to split up the bridge track into two equals occupancy sections, but its only at one rail necessary. (One side of the Bridge track). Alternatively, two Point sensors can be used near the ends of the Bridge track.\\
-How the sensors are ordered is not importend: The first event will generate the **enter** event and an **in** if both have got occupied.
+For the triggering and assignment of the events see: __**[[turntable-int-en#bridge_sensors_1_to_4|Turntable: Interface]]**__
-Alternatively you can just use the whole bridge as one section, which will generate an **enter2in** event. In conjunction with the event timer and route velocity you must fine tune this to make sure the locomotive will halt completely on the bridge.
+|< >|
 | {{turntable-2-sections.jpg}} |
-| Only one side the rail is devided in to 2 sections, This Fleischmann 6652 turntable is also converted from K-Rail to Tillig Code 83 and features  6 contacts, but I only need 4. |
+|  Only the rail at one side is divided into 2 sections. \\ This Fleischmann 6652 turntable is also converted from K-Rail \\ to Tillig Code 83 and features 6 contacts, but only 4 are needed.  |