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.

indicated as occupied when the train reaches “Southtown” release of “Main Line East”<br />

is further delayed until the occupancy indication of “Main Line East” is turned off.<br />

In detail the following rules apply:<br />

• A block is assumed to be reached, when the train reaches a stop indicator assigned<br />

to this block.<br />

• An occupied block or route is not released. (An exception of this rule is outlined below.)<br />

• A block or route is not released until the train has reached a block behind of this<br />

block/route.<br />

• When a train reaches a block all non-occupied blocks/routes located before this<br />

block, but not located behind another occupied <strong>and</strong> reserved block/route, are released.<br />

If, for example, “Main Line East” in Diagram 118 is still reserved <strong>and</strong> occupied<br />

when the train reaches “Main Line West”, then the used block of “Southtown”<br />

is not released, regardless whether it is occupied or not. If both, “Main Line East”<br />

<strong>and</strong> the related block in “Southtown”, are unoccupied when the train reaches “Main<br />

Line West”, then both blocks are released.<br />

• When the train reaches the destination position of the current schedule, i.e. the stop<br />

indicator in a destination block of this schedule, then all blocks <strong>and</strong> routes apart<br />

from this last block are released, regardless whether they are currently occupied or<br />

not.<br />

184<br />

Preset Block Signals <strong>and</strong> Speed Limits<br />

As outlined in section 5.9, “Block Signals” <strong>TrainController</strong> automatically calculates<br />

signal aspects for all trains running under control of the Dispatcher. These signal aspects<br />

take into account the availability of blocks <strong>and</strong> routes ahead of the train. If the<br />

train must not enter a block, then the signal of the previous block is set to “red”. If the<br />

train can enter the block, then the signal is usually set to “green”. It is additionally possible,<br />

however, to cause <strong>TrainController</strong> to display “yellow” instead of “green”, if<br />

desired.<br />

For this purpose it is possible to select an individual signal aspect (yellow or green) for<br />

each block or each route in a schedule. Dependent on this setting <strong>TrainController</strong><br />

will automatically apply the selected color to the calculated block signal, if the train<br />

may proceed.<br />

These signal settings are specified at the level of blocks <strong>and</strong> routes in a schedule. That<br />

means: the same block or route may have differing signal settings in different schedules.

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

Saved successfully!

Ooh no, something went wrong!