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.

Markers specified for scheduled stops are only triggered, if the train has to perform a<br />

scheduled stop in this block. If the train stops for another reason, e.g. because the exit<br />

of the block is currently locked, then such marker is not triggered.<br />

If at least one stop marker in a block is specified for scheduled stops, then all other stop<br />

markers in this block, which are not specified for scheduled stops, are only triggered for<br />

unscheduled stops. This applies accordingly to brake markers, too.<br />

This feature can be used to specify different stop points for the same train in the same<br />

block, which depend on, whether the train has to perform a scheduled stop or an unscheduled<br />

stop in this block. A good example is a passenger train, which will sometimes<br />

perform a scheduled stopover in the middle of a certain block, <strong>and</strong> which will<br />

pass this block without scheduled stop otherwise. This can be accomplished by specifying<br />

a stop marker located in the middle of the block for scheduled stops <strong>and</strong> another<br />

stop marker at the location of the block signal for unscheduled stops. A passing train,<br />

that has to perform a scheduled stop in this block, will stop in the middle of this block.<br />

In other cases, when this train does not have to perform a scheduled stop, but must stop<br />

here for any other operational reason, the train will stop at the block signal.<br />

5.9 Block Signals<br />

General<br />

Traffic Blocking is used on real railroads to prevent two trains from running into each<br />

other by dividing the track into sections protected by signals. These signals (here called<br />

block signals) indicate to a train whether it can enter the block which begins beyond the<br />

signal. If the block ahead is occupied the driver of a train approaching the signal protecting<br />

that block sees a red stop light. If the section in front is unoccupied <strong>and</strong> the train<br />

has permission to enter it the driver sees a green signal light. In addition to the signal<br />

for the next block the driver is usually also presented with an advance signal which indicates<br />

the status of the block beyond that which is being entered. If the advance signal<br />

indicates green, it means that the subsequent block is free to be entered; otherwise the<br />

block ahead is occupied <strong>and</strong> the train should proceed into the next block with caution<br />

<strong>and</strong> be prepared to stop at a red light.<br />

When a train is running under control of the Dispatcher, <strong>TrainController</strong> automatically<br />

calculates signal aspects taking into account the availability of blocks <strong>and</strong> routes<br />

in front of the train. These signal aspects are displayed in the block diagrams <strong>and</strong> as<br />

home <strong>and</strong> advance signals in the Train Window (see chapter 3, “Train ”). The signals<br />

indicate, whether the current block may be left <strong>and</strong> how the following block must be<br />

169

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

Saved successfully!

Ooh no, something went wrong!