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.

• In cases, where a specific block or route will always be passed with the same signal<br />

indication, it is much more convenient to preselect the indication once for all schedules<br />

in the properties of the block or route.<br />

• The possibility to preselect a signal on the level of turnouts is useful, if specific turnouts<br />

will always be passed with the same signal indication. It is much more convenient<br />

to preselect this indication once for all routes <strong>and</strong> schedules, which use this<br />

turnout, in the properties of the turnout, rather than being forced, to repeat the same<br />

selection in all affected routes or schedules.<br />

• The possibility to specify differing signal indications for the particular positions of a<br />

turnout is useful, if the indication of the calculated signal will depend on the turnout<br />

position.<br />

• The signal indication preselected for a block, route or turnout is also applied to<br />

trains run by AutoTrain. In other versions of <strong>TrainController</strong> the signal indication<br />

for trains run by AutoTrain is always green in all blocks or routes <strong>and</strong><br />

cannot be changed.<br />

As outlined earlier there is a close connection between calculated block signals <strong>and</strong><br />

speed limits. The allowed speed of a train depends on the currently valid signal indication<br />

(green or yellow). While other versions of <strong>TrainController</strong> only allow to specify<br />

speed limits on the level of blocks, <strong>TrainController</strong> <strong>Gold</strong> allows to specify speed<br />

limits also on the level of schedules, routes <strong>and</strong> even turnout positions. The hierarchy of<br />

the various settings is similar to that of the signal settings described above. To calculate<br />

the speed limit for a certain route or block in a schedule, <strong>TrainController</strong> <strong>Gold</strong> at<br />

first determines the speed limit specified for this block or route in the settings of the<br />

schedule. Additionally the speed limit preset in the properties of the block or route is<br />

determined, too. In the case of a route the speed limits for the according positions of all<br />

turnouts contained in this route are determined, too. The final speed limit results from<br />

the minimum of all determined limits. If no speed limit is specified for a certain object<br />

in this chain, then the settings of this object do not affect the resulting speed limit.<br />

The possibility to preset speed limits on the level of routes or turnouts provides the<br />

same advantages as listed above. Especially it is possible with <strong>TrainController</strong><br />

<strong>Gold</strong> to propagate speed limits valid for a certain position of a turnout to all affected<br />

schedules <strong>and</strong> also to trains run by AutoTrain.<br />

186<br />

Temporary Speed Limits<br />

A temporary speed limit can be accomplished by executing a specific train operation,<br />

e.g. by a marker in a block. Temporary speed limits can be applied for trains running<br />

under control of a schedule, AutoTrain or interlocking.

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

Saved successfully!

Ooh no, something went wrong!