no way to compare when less than two revisions

Differences

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

@@ Line 1: / Line 1: @@
+=====Interface=====
+[[:english#objects|{{  :objects.png}}]][[:english|{{  :rocrail-logo-35.png}}]]
+[[english|Content]] -> [[english#objects|Objects]] -> **[[switch-en|Switches]]**
+  * [[switch-index-en|Index]] | [[switch-gen-en|General]] |  **[[switch-int-en|Interface]]** | [[switch-wiring-en|Wiring]] | [[switch-ctrl-en|Control]] | [[switch-frog-en|Frog]] | [[switch-td-en|Trackdriver]] | [[switch-usage-en|Usage]] | [[switch-menu-en|Menu]]
+// \\ // \\
+Switch Dialog Interface Tab.\\
+{{:switch-int-en.png?800}}
+ \\
+=====Interface ID=====
+If more than one command station is used, then the command station that is responsible for controlling the switch-decoder is specified in this field. The "Interface identifier" field can remain empty if the object is connected to the first command station (first 'digint' in rocrail.ini) from the list of command stations.
+=====Bus=====
+See: **[[:addressing-en#bus|Addressing]]**
+ \\
+=====UID-Name=====
+Alternative to the Bus number supported by:
+  * BiDiB (String: //Username//)
+  * RocNet -> Must be set in case CTC is used and the Rocnetnode has a __**[[:rocnet:rocnetnode-setup-en#uid-name|UID-Name]]**__.
+ \\
+=====Protocol=====
+This is Command Station dependent.; Check the manual for details. \\
+ \\
+=====Address, Port=====
+Addressing of accessories is described in the __**[[:addressing:accessory-pg-en|Practical Guide]]**__.\\
+If the switch is statically (crossing) or only manually controllable, the address and port can be set to zero. (This switch object must be included in routes which run over it.)\\
+ \\
+=====Parameter, Value=====
+Special settings for some Command Stations:
+  * **[[:dinamo-om32-en|OM32]]** RS485
+  * **[[:bidib-examples-en#example_servo|BiDiB]]**
+  * **[[:dccpp:dccpp-en#options1|DCC++]]**
+ \\
+=====Single Gate=====
+Decouplers, Servos and so on can use the gate parameter because they have only one coil/motor, so one gate pair can serve two of them.\\
+ \\
+Example of two decouples on address 139, port 3:
+<code>
+OSwitch  0519 Switch [dc1] will be set to [straight]
+OVirtual 0179 turnout 0139 3 straight   fada=1108 pada=0555 addr=139 port=3 gate=0 dir=0 action=0
+OSwitch  0519 Switch [dc1] will be set to [turnout]
+OVirtual 0179 turnout 0139 3 turnout    fada=1108 pada=0555 addr=139 port=3 gate=0 dir=0 action=1
+OSwitch  0519 Switch [dc2] will be set to [straight]
+OVirtual 0179 turnout 0139 3 straight   fada=1109 pada=0555 addr=139 port=3 gate=1 dir=1 action=0
+OSwitch  0519 Switch [dc2] will be set to [turnout]
+OVirtual 0179 turnout 0139 3 turnout    fada=1109 pada=0555 addr=139 port=3 gate=1 dir=1 action=1
+</code>
+The switch definitions used for the example:
+<code xml>
+<sw type="decoupler" id="dc1" iid="" addr1="139" port1="3" gate1="0" inv="false" singlegate="true" actdelay="false" delay="0" />
+<sw type="decoupler" id="dc2" iid="" addr1="139" port1="3" gate1="1" inv="false" singlegate="true" actdelay="false" delay="0" />
+</code>
+ \\
+=====Invert=====
+To avoid creeping under your layout again and swap wires you can use this flag instead.\\
+  * Make sure the __**[[switch-wiring-en#sensors|Wiring sensors]]**__, if used, are set accordingly to the invert state.
+ \\
+=====Switch time=====
+:!: Activate this timer in case the motor does not switch itself off!\\
+Some Command Stations allow to define a switch activation time. Check your manual for details.
+The time here is in ms.\\
+| Tip: It is much safer to define coil power off in the decoder instead of relying on a second command which could be missed by the decoder and overheat the coil. |
+**Note:** This value is also used for servo rotation speed in case of WIO. Range 0...10.\\
+====Synchronise====
+Use the switch time to wait after the actual command to signal the switch as ready.\\
+ \\
+=====Second Address pair=====
+Those fields are enabled for threeway switches and double crossings for setting up the second motor or coil.\\
+ \\
+=====Accessory=====
+Some systems, like BiDiB, Z21, differentiate between accessory and other command types.\\
+For all other systems this flag has no effect.\\
+ \\
+=====Type=====
+Port type selection.\\
+Some decoders, like BiDiB LightControl and **[[:rocnet:rocnetnode-en|RocNetNode]]**, provide different port types on the same local address.\\
+ \\
+=====Multiple switches at the same decoder output=====
+The solution examples given earlier for this purpose as actions and / or scripts are no longer needed because several Switch objects in the Track plan can / may be defined with the same address data (address / port).
+<html><!--
+In this case, one switch object in the track plan is assigned to a real decoder address.\\
+The other switch object in the track plan get a virtual address and the Interface ID of the __**[[vcs-en|virtual CS]]**__.\\
+Additionally established actions and action conditions ensure that the switching of the first switch and the second (virtual) switch object will be transmitted in the track plan.\\
+See example: __**[[action-example-de#gleichzeitig_geschaltete_weichen|Gleichzeitig geschaltete Weichen]]**__ **(de)**
+>**Note:**
+>In DCC232 and MCS2 and some hardware CS the accessory commands are reported. Both switch objects get the same address.
+>Then the establishment of actions and the virtual CS is not required. \\
+For **manual** switches you can choose an address of 0 on your default controller. However, if you like to see the switch move on the screen, then you can use the virtual controller. In either case no commands are sent to the controller.
+ \\
+--></html>
+Partial list of CS that will work with multiple switches on the same decoder output
+  * Virtual, ECoS, DCC++, Loconet,  Tams (see echo commands __**[[p50x-tams-en#options|here]]**__)
+Partial list of CS that will **not** work with multiple switches on the same decoder output
+  * Hornby Elite, Zimo
+ \\
+=====Parameter=====
+Parameter is used to affect servo bouncing in the **[[wio:wiopico-en|SIOpico]]**.
+ \\
+=====3W OneServo=====
+Using just one servo for a 3W is very common for car systems.\\
+Setup by setting the Address an Port for both motors the same, and select Type Servo.\\
+|< >|
+^ Position ^ Field ^ Remark ^
+| Right | Param 1 |
+| Straight | Value 1 | If zero the value will be calculated. |
+| Left  | Param 2 |