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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

in a specific format. In particular the diagrams of those schedules were not based on the<br />

main block diagram. These specific schedules were transitionally still supported in<br />

<strong>TrainController</strong> 5 for compatibility reasons. However, it was always recommended<br />

for several years now to convert the old format of these schedules into the new format<br />

introduced with Version 5.<br />

These old-format schedules are not supported anymore. Affected old-format schedules<br />

are deleted during loading of a layout file created with an earlier Version of <strong>TrainController</strong>.<br />

Note once more, that only schedules created with Version 3 or 4 are affected by this<br />

change. Schedules created with <strong>TrainController</strong> 5 are not affected <strong>and</strong> work as before.<br />

End blocks of Schedules<br />

<strong>TrainController</strong> 5 distinguishes between (dead) end blocks <strong>and</strong> destination blocks<br />

of schedules. By enabling a certain rule it is possible to use end blocks as destination<br />

blocks of schedules, too. This is no longer supported for schedules newly created in<br />

<strong>TrainController</strong> 7. For reasons of clarity all desired destination blocks of schedules<br />

are always marked explicitly.<br />

Schedules, that are contained in files created with <strong>TrainController</strong> 5 may continue<br />

using end blocks as destination blocks for the time being. The according rule in the<br />

properties of the schedule should be turned off, however, at the next opportunity <strong>and</strong><br />

the according destination blocks should be marked explicitly.<br />

Yellow Signal <strong>and</strong> Speed restrictions for Routes in Schedules<br />

If the yellow signal was set in <strong>TrainController</strong> 5 in the schedule specific setting of a<br />

route, than the (usually limited) speed was applied, which was specified for the yellow<br />

signal in the properties of the subsequent block.<br />

In <strong>TrainController</strong> 7 the allowed speed is calculated separately for each route or<br />

block in a schedule (see also page 184). In particular the speed limit valid for a route<br />

with a yellow signal in a schedule is no longer derived from the properties of the subsequent<br />

block. In order to accomplish the same behavior as before it is possible to set an<br />

explicit speed limit in the properties of each route (<strong>TrainController</strong> 7 <strong>Gold</strong> only) or<br />

in the schedule specific route settings (<strong>TrainController</strong> 7 <strong>Gold</strong> <strong>and</strong> <strong>Silver</strong>).<br />

331

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

Saved successfully!

Ooh no, something went wrong!