24.01.2013 Views

TrainController Gold and Silver - Freiwald Software

TrainController Gold and Silver - Freiwald Software

TrainController Gold and Silver - Freiwald Software

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

X<br />

!<br />

X<br />

282<br />

Virtual Occupancy Indication<br />

If an indicator is associated with a momentary contact then this contact can be upgraded<br />

with the memory of the indicator to a virtual occupancy sensor (see section 14.2, “The<br />

Memory of Indicators”). If this is done the indicator stays on after activation of the contact<br />

until the complete train has passed the point where the contact is located. It is possible<br />

to take into account the point where the contact is activated or the point where the<br />

contact is deactivated. In this way it is for example possible to avoid premature release<br />

of routes in cases when long trains pass a route <strong>and</strong> only momentary contacts are used.<br />

This option works only for trains under control of the Dispatcher <strong>and</strong> it relies on correct<br />

specification of the length of each train.<br />

Virtual Contacts can be combined with Virtual Occupancy Indication, too. The Memory<br />

is namely also available for Virtual Contacts. In this way a Virtual Contact will be<br />

turned on when a train reaches a certain point on the layout. And the Virtual Contact<br />

will stay turned on, until the last car of the train has passed this point.<br />

Please note the difference between Virtual Contacts <strong>and</strong> Virtual Occupancy Indication.<br />

A Virtual Contact marks a certain point on your model railroad, i.e. a Virtual<br />

Contact is turned on, when a train is assumed to arrive at a certain point. Virtual<br />

Occupancy Indication is used to turn a certain real or Virtual Contact off<br />

when a train has passed a certain point completely.<br />

15.3 Controlling the traffic flow in Schedules<br />

Limiting the Reservation of Blocks <strong>and</strong> Routes in certain Schedules<br />

For each block <strong>and</strong> each route in a schedule it is possible to specify a condition. This is<br />

a condition, which must be valid when a block or route is about to be reserved during a<br />

running schedule. As long as the condition does not apply it is not possible to reserve<br />

the block or route. How conditions work is outlined in section 14.3, “Protection <strong>and</strong><br />

Locking with Conditions”.<br />

This feature provides additional control. It is for example possible to specify, that a certain<br />

block may only be reserved, if a certain on/off switch is toggled off. Turning off or<br />

on this switch you can intervene into the traffic flow at any time <strong>and</strong> lock or release the<br />

affected block.<br />

Such conditions can be specified on a global or a per-schedule base. Global conditions<br />

are specified as part of the properties of blocks or routes as outlined in section 14.3,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!