Content → Objects → Switches

• Index | General | Interface | Wiring | Control | Frog | Trackdriver | Usage | Menu

Switch Dialog Interface Tab.

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.

See: Addressing

Alternative to the Bus number supported by:

• BiDiB (String: Username)
• RocNet → Must be set in case CTC is used and the Rocnetnode has a UID-Name.

This is Command Station dependent.; Check the manual for details.

Addressing of accessories is described in the 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.)

Special settings for some Command Stations:

• OM32 RS485
• BiDiB
• DCC++

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:

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

The switch definitions used for the example:

<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" />

To avoid creeping under your layout again and swap wires you can use this flag instead.

• Make sure the Wiring sensors, if used, are set accordingly to the invert state.

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.

Note: This value is also used for servo rotation speed in case of WIO. Range 0…10.

Use the switch time to wait after the actual command to signal the switch as ready.

Those fields are enabled for threeway switches and double crossings for setting up the second motor or coil.

Some systems, like BiDiB, Z21, differentiate between accessory and other command types.
For all other systems this flag has no effect.

Port type selection.
Some decoders, like BiDiB LightControl and RocNetNode, provide different port types on the same local address.

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).

Partial list of CS that will work with multiple switches on the same decoder output

• Virtual, ECoS, DCC++, Loconet, Tams (see echo commands here)

Partial list of CS that will not work with multiple switches on the same decoder output

• Hornby Elite, Zimo

Parameter is used to affect servo bouncing in the SIOpico.

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.