Download - Freiwald Software

!
X
sible to take into account the point where the contact is activated or the point where the
contact is deactivated. In this way it is for example possible to avoid premature release
of routes in cases when long trains pass a route and only momentary contacts are used.
This option works only for trains under control of the Dispatcher and it relies on correct
specification of the length of each train.
Virtual Contacts can be combined with Virtual Occupancy Indication, too. The Memory
is namely also available for Virtual Contacts. In this way a Virtual Contact will be
turned on when a train reaches a certain point on the layout. And the Virtual Contact
will stay turned on, until the last car of the train has passed this point.
Please note the difference between Virtual Contacts and Virtual Occupancy Indication.
A Virtual Contact marks a certain point on your model railroad, i.e. a Virtual
Contact is turned on, when a train is assumed to arrive at a certain point. Virtual
Occupancy Indication is used to turn a certain real or Virtual Contact off
when a train has passed a certain point completely.
204
13.4 Controlling the traffic flow in Schedules
Limiting the Reservation of Blocks and Routes in certain Schedules
For each block and each route in a schedule it is possible to specify a condition. This is
a condition, which must be valid when a block or route is about to be reserved during a
running schedule. As long as the condition does not apply it is not possible to reserve
the block or route. How conditions work is outlined in section 12.2, “Protection and
Locking with Conditions”.
This feature provides additional control. It is for example possible to specify, that a certain
block may only be reserved, if a certain on/off switch is toggled off. Turning off or
on this switch you can intervene into the traffic flow at any time and lock or release the
affected block.
Such conditions can be specified on a global or a per-schedule base. Global conditions
are specified as part of the properties of blocks or routes as outlined in section 12.2,
“Protection and Locking with Conditions”. They are valid for all schedules, that use
these blocks or routes.
Conditions can also be specified on a per-schedule base, while editing the diagram of a
schedule. Conditions specified in this way apply only when this schedule is being exe-