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.

!<br />

!<br />

!<br />

The rule to release preceding blocks <strong>and</strong> routes of a certain schedule at the stop indicator<br />

of subsequent blocks should be turned off only, if the routes contained in this schedule<br />

are equipped with an own occupancy indication. Furthermore the tail of each train<br />

should be able to trigger the sensors used for occupancy indication of the routes. Usually<br />

this requires, that the trailing cars of affected trains are lighted or the wheel sets of<br />

these cars are conductive.<br />

Occupancy indication of routes can also be used to detect cars lost in a turnout area or<br />

to prevent routes from being prematurely released, when a long train is completely filling<br />

the subsequent block, but the tail of the train is still located on the route. In this case<br />

the route is not released, even if this long train has reached the stop indicator of this<br />

block (exception: the block is the destination block of a schedule, in which case all<br />

routes contained in this schedule may be released).<br />

Schedule Watchdog <strong>and</strong> Limited Aberration Protection<br />

With a specific schedule rule it is possible to specify a schedule watchdog. This is the<br />

maximum time period between activation of two indicators. If no indicator is triggered<br />

within the specified period of time <strong>and</strong> the train is set to run at non zero speed, then it is<br />

assumed, that the train got stuck. In such cases a warning is displayed in the message<br />

window <strong>and</strong> an error indication is raised in the train list.<br />

It is furthermore possible to activate a limited aberration protection for each schedule. If<br />

the train under control of this schedule is detected by train tracking in block, which<br />

does not belong to the schedule, then the train is stopped immediately, a warning is displayed<br />

in the message window <strong>and</strong> an error indication is raised in the train list. Such<br />

condition can occur, for example, if a turnout contained in the schedule does not work<br />

correctly <strong>and</strong> the train is directed to a wrong block.<br />

The limited aberration protection can detect certain, but not all possible conditions,<br />

where trains run into wrong blocks. In particular it usually cannot protect<br />

the train against collision, if the wrong block is already reserved by another train.<br />

Aberration protection should not be misunderstood as collision protection <strong>and</strong> it<br />

does not rid you from arranging for reliably working hardware.<br />

Track Cleaning Trains<br />

With a specific schedule rule it is possible to specify, that always that path is selected,<br />

that contains routes or blocks, which have been visited by the train under control of this<br />

schedule the longest time ago (“oldest” block or routes).<br />

289

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

Saved successfully!

Ooh no, something went wrong!