TrainController Gold and Silver - Freiwald Software

tions depending on the currently executed schedule. Many other useful applications
can be easily accomplished, too. See page 167.
41. It is possible to specify differing brake and stop markers for scheduled stops and
for unscheduled stops in the same block. This can be used, for example, to let the
same train perform scheduled stops in the middle of a platform and perform unscheduled
stops near the block signal at the end of the block, for example. See page
168.
42. It is possible to assign indicators to turnouts for occupancy indication of all routes,
that are using the concerning turnouts. See page 286.
43. It is possible to specify a separate set of schedule rules for AutoTrain runs. These
schedule rules work in the same way as schedule rules for regular schedules. They
can be changed outside edit mode, however, and each change affects all Auto-
Train runs, which are initiated later.
44. Specific rules for AutoTrain can prevent blocks or routes, that are occupied, reserved
by other trains, locked to the according direction of travel or locked by an
unfulfilled condition, from being included in the path search.
45. AutoTrain can be called by operations of other objects. It is in particular possible
to trigger AutoTrain by start and destination keys; even from external control panels.
This allows for automatic train runs on point to point connections without the
need to create schedules in advance. See page 193.
46. Individual schedule rules can be applied to all schedules on request.
47. Specific schedule rules prevent schedules from reserving occupied routes and
blocks without the need to specify extra conditions for the blocks or routes. In other
versions of TrainController it is only possible to prevent trains from running
into such blocks or routes. To prevent reservation,
too, it is necessary there to spe-
cify appropriate conditions.
48. An additional smart mode can be optionally applied as a rule to the release of
routes in schedules: in this mode passed routes with own occupancy indication are
released, when they are no longer reported as occupied. Routes without own occupancy
indication are released, when the train reaches a stop marker of a subsequent
block. In this way the smart mode automatically selects the release policy, which is
optimal for the particular route.
49. Routes, that were already activated prior to reservation by a schedule, are optionally
deactivated automatically upon termination of the schedule, if desired. In other
versions of TrainController such routes remain always activated and must be
turned off explicitly. This is controlled by a new schedule rule.
50. A schedule rule keeps routes and blocks, that could not be released during the normal
run of the schedule, reserved upon termination of the schedule, if desired.
These blocks or routes are automatically released later, when this is possible. In
other versions of TrainController all routes and blocks requested by a schedule
and different from the current block of the train are always released upon termination
of the schedule.
17