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.

X<br />

According to the above the following recommendations apply:<br />

• Specify the particular triggers assigned to the various aspects of the same signal in a<br />

way, that no two different non-empty triggers become valid at the same time. Make<br />

use of the NOT-option (see page 250) to exclude the triggers of other signal aspects<br />

from a particular trigger.<br />

• Leave the trigger of exactly one signal aspect empty, if possible. This is the “else”<br />

case <strong>and</strong> specifies the signal aspect in all cases, where no trigger of another signal<br />

aspect applies.<br />

• To extend the simplified signaling system, which was introduced in section 5.8, <strong>and</strong><br />

which is based on a 1 to 1 mapping of the internally calculated block signal aspects,<br />

with your own rules, you can apply these internally calculated aspects to triggers<br />

<strong>and</strong> conditions of signals (<strong>and</strong> other elements), too, <strong>and</strong> combine them with the status<br />

of other elements.<br />

Macros are used to operate other elements.<br />

14.7 Macros<br />

They are very similar to push buttons in the switchboard (see section 2.5, “Signals <strong>and</strong><br />

Accessories”). Like push buttons they are also able to perform operations (see section<br />

14.4, “Operations”). Unlike push buttons they are not placed in a switchboard. Instead<br />

macros are for example used in the operations called by other elements (see section<br />

14.4, “Operations”), executed in schedules (see section 5.11, “Schedules”), executed in<br />

timetables (see section 16, “ Timetables”) or assigned to engines as part of their functions<br />

(see section 3.6, “Headlights, Steam <strong>and</strong> Whistle”).<br />

In this way, macros are invisible <strong>and</strong> work in the background of the program.<br />

Engine functions assigned to macros can only be executed, if the macro is executed in<br />

the context of an engine. This is the case, if the macro is assigned to another engine<br />

function (in this way engine functions can be triggered indirectly by other engine functions),<br />

or if the macro is assigned to a schedule. If the macro is not executed in the context<br />

of an engine (e.g. by a timetable), then all engine functions contained in the macro<br />

are ignored.<br />

263

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

Saved successfully!

Ooh no, something went wrong!