turntable-en
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | turntable-en [2022/04/24 05:04] (current) – [Bridge Occupancy] rainerk | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Turntable====== | ||
+ | [[: | ||
+ | |||
+ | [[english|Content]] -> [[english# | ||
+ | * [[turntable-index-en|Index]] | [[turntable-gen-en|General]] | [[turntable-int-en|Interface]] | [[turntable-tracks-en|Tracks]] | [[turntable-setup-en|Setup]] | [[traverser-setup-en|Traverser setup]] | ||
+ | \\ | ||
+ | {{ draaischijf.jpg}}\\ | ||
+ | |||
+ | =====Sensors===== | ||
+ | To provide Rocrail with events you must add some sensors to the turntable. | ||
+ | On most turntable you can add without much affort those sensors: [[turntable_locdec_en]] | ||
+ | In the worst case you can use reed schwitches in combination with magnets. But any how it is up to you to find the best solution for your turntable. | ||
+ | |||
+ | ====Bridge Position==== | ||
+ | Needed for displaying and auto mode. | ||
+ | |||
+ | ====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, but its only at one rail necessary. (One side of the Bridge track). Alternatively, | ||
+ | For the triggering and assignment of the events see: __**[[turntable-int-en# | ||
+ | |||
+ | |< >| | ||
+ | | {{turntable-2-sections.jpg}} | | ||
+ | | 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. | ||