Update interlocking manual
This commit is contained in:
orwell96
parent
08649b84a0
commit
8a33e7b938
Binary file not shown.
|
After Width: | Height: | Size: 534 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 170 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 906 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 132 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
|
|
@ -10,15 +10,21 @@
|
|||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.3}Interlocking patterns}}{6}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3}Signals and routes}}{6}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.1}Signal Influence Point}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.2}Main and Shunt signals}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.3}The concept of routes}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.4}Assigning main signals to TCBs}}{8}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.5}Shunt routes}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.6}Route Release}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.7}Programming a route}}{9}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4}Interlocking system operation}}{10}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.1}Train Safety System}}{11}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.2}Simple route setting and cancelling}}{11}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.3}Automatic Working}}{11}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {5}Final notes}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.2}Signal Aspects}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.3}Train moves and Shunt Moves}}{8}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.4}The concept of routes}}{8}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.5}Assigning main signals to TCBs}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.6}Shunt routes}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.7}Route Release}}{10}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.8}Programming a route}}{10}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.9}Route information screen}}{11}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.10}Specifying signal aspects}}{11}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4}Interlocking system operation}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.1}Train Safety System}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.2}Simple route setting and cancelling}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.3}Automatic Working}}{13}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.4}Automatic Route Setting (ARS)}}{13}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.4.1}Writing ARS Rules}}{13}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.4.2}Using ARS}}{14}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {5}Final notes}}{14}\relax
|
||||
\par
|
||||
|
|
|
|||
|
|
@ -10,14 +10,20 @@
|
|||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.3}Interlocking patterns}}{6}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3}Signals and routes}}{6}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.1}Signal Influence Point}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.2}Main and Shunt signals}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.3}The concept of routes}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.4}Assigning main signals to TCBs}}{8}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.5}Shunt routes}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.6}Route Release}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.7}Programming a route}}{9}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4}Interlocking system operation}}{10}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.1}Train Safety System}}{11}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.2}Simple route setting and cancelling}}{11}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.3}Automatic Working}}{11}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {5}Final notes}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.2}Signal Aspects}}{7}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.3}Train moves and Shunt Moves}}{8}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.4}The concept of routes}}{8}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.5}Assigning main signals to TCBs}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.6}Shunt routes}}{9}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.7}Route Release}}{10}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.8}Programming a route}}{10}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.9}Route information screen}}{11}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {3.10}Specifying signal aspects}}{11}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4}Interlocking system operation}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.1}Train Safety System}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.2}Simple route setting and cancelling}}{12}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.3}Automatic Working}}{13}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.4}Automatic Route Setting (ARS)}}{13}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.4.1}Writing ARS Rules}}{13}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {4.4.2}Using ARS}}{14}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {5}Final notes}}{14}\relax
|
||||
|
|
|
|||
|
|
@ -6,8 +6,6 @@
|
|||
.ecsx-1728{ font-weight: bold;}
|
||||
.ecsx-1728{ font-weight: bold;}
|
||||
.ecsx-1728{ font-weight: bold;}
|
||||
.ecsx-1728{ font-weight: bold;}
|
||||
.ecsx-1728{ font-weight: bold;}
|
||||
.ecst-1440{font-size:140%;}
|
||||
.ecsx-1200{font-size:120%; font-weight: bold;}
|
||||
.ecsx-1200{ font-weight: bold;}
|
||||
|
|
@ -15,10 +13,6 @@
|
|||
.ecsx-1200{ font-weight: bold;}
|
||||
.ecsx-1200{ font-weight: bold;}
|
||||
.ecsx-1200{ font-weight: bold;}
|
||||
.ecsx-1200{ font-weight: bold;}
|
||||
.ecsx-1200{ font-weight: bold;}
|
||||
.ecsx-1000{ font-weight: bold;}
|
||||
.ecsx-1000{ font-weight: bold;}
|
||||
.ecsx-1000{ font-weight: bold;}
|
||||
.ecsx-1000{ font-weight: bold;}
|
||||
.ecsx-1000{ font-weight: bold;}
|
||||
|
|
@ -31,24 +25,6 @@
|
|||
.ecbx-1000{ font-weight: bold;}
|
||||
.ecbx-1000{ font-weight: bold;}
|
||||
.ecbx-1000{ font-weight: bold;}
|
||||
.ecbx-1000{ font-weight: bold;}
|
||||
.ecbx-1000{ font-weight: bold;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ecti-1000{ font-style: italic;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
.ectt-1000{ font-family: monospace;}
|
||||
p.noindent { text-indent: 0em }
|
||||
td p.noindent { text-indent: 0em; margin-top:0em; }
|
||||
p.nopar { text-indent: 0em; }
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -277,11 +277,13 @@ class="ecsx-1200">Interlocking</span>
|
|||
class="ecsx-1200">patterns</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 213--><p class="noindent" >This section is supposed to show some examples on how you should set up track sections on certain track configurations.
|
||||
<!--l. 216--><p class="noindent" >
|
||||
<!--l. 213--><p class="noindent" >Have a look at the following images. They show you how you can set up sections so that reasonable train moves are
|
||||
possible.
|
||||
<!--l. 216--><p class="noindent" >You should settle on a naming scheme for your sections. This way, you can determine the source of an issue faster
|
||||
<!--l. 219--><p class="noindent" >
|
||||
<a
|
||||
id="x1-31r3"></a>
|
||||
<!--l. 216--><p class="noindent" ><span
|
||||
<!--l. 219--><p class="noindent" ><span
|
||||
class="ecsx-1200">3</span> <span
|
||||
class="ecsx-1200">Signals</span>
|
||||
<span
|
||||
|
|
@ -290,19 +292,19 @@ class="ecsx-1200">and</span>
|
|||
class="ecsx-1200">routes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 218--><p class="noindent" >Signals are appliances that can give instructions to trains. That can be the permission to proceed, a speed restriction, or other
|
||||
<!--l. 221--><p class="noindent" >Signals are appliances that can give instructions to trains. That can be the permission to proceed, a speed restriction, or other
|
||||
information.
|
||||
<!--l. 221--><p class="noindent" >There are 2 types of signals:
|
||||
<!--l. 224--><p class="noindent" >There are 2 types of signals:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Static signals always display the same information to the train. This can be a speed restriction (or the end of one), a
|
||||
disallowal to proceed as shunt move or similar things. In most cases, these are signs.
|
||||
</li>
|
||||
<li class="itemize">Variable signals are what most people would call a “signal”. Its function is to inform trains about whether and at which
|
||||
<li class="itemize">Dynamic signals are what most people would call a “signal”. Its function is to inform trains about whether and at which
|
||||
speed they can proceed into the next section safely.</li></ul>
|
||||
<!--l. 231--><p class="noindent" >
|
||||
<!--l. 234--><p class="noindent" >
|
||||
<a
|
||||
id="x1-32r1"></a>
|
||||
<!--l. 231--><p class="noindent" ><span
|
||||
<!--l. 234--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.1</span> <span
|
||||
class="ecsx-1200">Signal</span>
|
||||
<span
|
||||
|
|
@ -311,12 +313,12 @@ class="ecsx-1200">Influence</span>
|
|||
class="ecsx-1200">Point</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 233--><p class="noindent" >Every signal is associated to a track on which the instruction should be followed. Signals are usually placed right next to the track on the
|
||||
<!--l. 236--><p class="noindent" >Every signal is associated to a track on which the instruction should be followed. Signals are usually placed right next to the track on the
|
||||
right side. Human observers do know then that the signal belongs to the track left of it, however, train safety systems (like the one in
|
||||
advtrains) can not.
|
||||
<!--l. 239--><p class="noindent" >This is the reason why a so-called “influence point” needs to be assigned to any signal that should actually give instructions to trains,
|
||||
<!--l. 242--><p class="noindent" >This is the reason why a so-called “influence point” needs to be assigned to any signal that should actually give instructions to trains,
|
||||
should the driver (if even there is one) fail to recognize the instructions.
|
||||
<!--l. 244--><p class="noindent" >Depending on the signal and the mod that adds the signal, there are different ways to configure this. Signals integrated into advtrains
|
||||
<!--l. 247--><p class="noindent" >Depending on the signal and the mod that adds the signal, there are different ways to configure this. Signals integrated into advtrains
|
||||
behave as follows:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Static signals and all red-green light signals from core advtrains that are not assigned to a TCB can be configured by
|
||||
|
|
@ -324,37 +326,74 @@ behave as follows:
|
|||
</li>
|
||||
<li class="itemize">All signals that are assigned to a TCB can be configured by first right-clicking them, then selecting “Influence Point” in
|
||||
the signalling formspec.</li></ul>
|
||||
<!--l. 255--><p class="noindent" >The small formspec that opens allows you to set and later view or clear the Influence Point. To set the influence point, click the “Set”
|
||||
<!--l. 258--><p class="noindent" >The small formspec that opens allows you to set and later view or clear the Influence Point. To set the influence point, click the “Set”
|
||||
button, face towards the signal and punch a rail about 2m in front of the signal. A small marker will be shown, indicating success. To
|
||||
cancel setting an influence point, punch anything other. (note that then the influence point remains unset, regardless of its previous
|
||||
state)
|
||||
<!--l. 263--><p class="noindent" >The advtrains-internal train safety system ensures that the train always obeys any restrictions imposed by signals, if (and only if) the
|
||||
<!--l. 266--><p class="noindent" >The advtrains-internal train safety system ensures that the train always obeys any restrictions imposed by signals, if (and only if) the
|
||||
influence point is set properly.
|
||||
<!--l. 267--><p class="noindent" >
|
||||
<!--l. 270--><p class="noindent" >
|
||||
<a
|
||||
id="x1-33r2"></a>
|
||||
<!--l. 267--><p class="noindent" ><span
|
||||
<!--l. 270--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.2</span> <span
|
||||
class="ecsx-1200">Main</span>
|
||||
class="ecsx-1200">Signal</span>
|
||||
<span
|
||||
class="ecsx-1200">Aspects</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 272--><p class="noindent" >While static signals are mainly used for speed restrictions, the interesting ones are variable signals. Of course, you can always control any
|
||||
variable signal by traditional means (mesecons, digiline, right-click) if the signal allows it, but that misses the point of this interlocking
|
||||
system.
|
||||
<!--l. 277--><p class="noindent" >A signal aspect is a piece of information that a signal shows to the train driver. It contains information about whether and at what speed
|
||||
the driver may proceed at the signal.
|
||||
<!--l. 281--><p class="noindent" >Every signal, both static and dynamic ones, imposes a certain aspect to trains passing the signal. For static signals, this is always the
|
||||
same aspect, such as “Proceed at speed of 8” or “Shunt moves may not pass”. Dynamic signals, however, can display multiple different
|
||||
aspects. The default for them is always as restrictive as possible, mostly “Halt!”.
|
||||
<!--l. 288--><p class="noindent" >You should know that both static and dynamic signals use exactly the same properties for signal aspects. There is no difference in the
|
||||
meaning of the aspect definitions.
|
||||
<!--l. 292--><p class="noindent" >In the following sections, we will talk about main signals. By this, we mean a variable signal that can display both a “Danger” aspect
|
||||
(trains are not allowed to proceed) and at least one “Proceed” aspect (train may proceed as train/shunt move, with optional speed
|
||||
restriction), which act as an “entry signal” for one or multiple routes.
|
||||
<!--l. 299--><p class="noindent" >
|
||||
<a
|
||||
id="x1-34r3"></a>
|
||||
<!--l. 299--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.3</span> <span
|
||||
class="ecsx-1200">Train</span>
|
||||
<span
|
||||
class="ecsx-1200">moves</span>
|
||||
<span
|
||||
class="ecsx-1200">and</span>
|
||||
<span
|
||||
class="ecsx-1200">Shunt</span>
|
||||
<span
|
||||
class="ecsx-1200">signals</span>
|
||||
class="ecsx-1200">Moves</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 269--><p class="noindent" >While static signals are mainly used for speed restrictions, the interesting ones are variable signals. Of course, you can always control any
|
||||
variable signal by traditional means (mesecons, digiline, right-click) if the signal allows it, but that misses the point of this interlocking
|
||||
system.
|
||||
<!--l. 274--><p class="noindent" >In the following sections, we will talk about main signals. By this, we mean a variable signal that can display both a “Danger” aspect
|
||||
(trains are not allowed to proceed) and at least one “Proceed” aspect (train may proceed as train/shunt move, with optional speed
|
||||
restriction), which act as an “entry signal” for one or multiple routes.
|
||||
<!--l. 281--><p class="noindent" >
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">A “Train move” is a train that is running, going to run on or coming from a main line between stations, passing through
|
||||
or stopping at a station. Train moves can expect that there are no obstacles on the route and they can proceed at the
|
||||
maximum permitted speed of the line. This is the regular operation mode for trains. Shunt signals have no meaning for
|
||||
train moves.
|
||||
</li>
|
||||
<li class="itemize">A “Shunt move” is a train that moves within a station and/or is coupling or decoupling wagons or engines. A shunt move
|
||||
may never leave a station except into a siding. Also, shunt moves may drive at a maximum speed of 6 speed units, because
|
||||
it is usually not ensured that the path is free of obstacles. (however, advtrains ensures that every route is free of railway
|
||||
vehicles, even shunt routes)</li></ul>
|
||||
<!--l. 314--><p class="noindent" >There are also 2 general types of signals: Main signals and Shunt signals. While main signals have a meaning for all types of trains, Shunt
|
||||
signals only have to be followed by shunt moves. Usually, Shunt signals that are on a train move route are set to a Proceed aspect as
|
||||
well.
|
||||
<!--l. 320--><p class="noindent" >When a train reverses, its mode automatically changes to “shunt move” until it passes a main signal that shows “Proceed as
|
||||
train move”, which is usually designated by a green light. From this point on, it can accelerate to maximum permitted
|
||||
speed.
|
||||
<!--l. 325--><p class="noindent" >Some main signals, like the ones from the Ks signals mod included by default, can also display “Proceed as shunt move”, which is
|
||||
designated by 2 white lights along with the red light. Once a train passes this signal, it becomes a shunt move.
|
||||
<!--l. 330--><p class="noindent" >
|
||||
<a
|
||||
id="x1-34r3"></a>
|
||||
<!--l. 281--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.3</span> <span
|
||||
id="x1-35r4"></a>
|
||||
<!--l. 330--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.4</span> <span
|
||||
class="ecsx-1200">The</span>
|
||||
<span
|
||||
class="ecsx-1200">concept</span>
|
||||
|
|
@ -364,44 +403,44 @@ class="ecsx-1200">of</span>
|
|||
class="ecsx-1200">routes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 283--><p class="noindent" >A so-called route is a locked path between two main signals, which locks all turnouts in the correct position. Its purpose is to offer a train
|
||||
<!--l. 332--><p class="noindent" >A so-called route is a locked path between two main signals, which locks all turnouts in the correct position. Its purpose is to offer a train
|
||||
a path on which it can safely proceed without interfering with any other train. A route always incorporates and locks one to multiple
|
||||
track sections, starting with the one that lies directly behind the “entry” signal.
|
||||
<!--l. 290--><p class="noindent" >Example: Imagine a station with 2 platforms on a single track running line. We are looking at signal A. You probably want trains coming
|
||||
<!--l. 339--><p class="noindent" >Example: Imagine a station with 2 platforms on a single track running line. We are looking at signal A. You probably want trains coming
|
||||
from the right to go into platform 1 or into platform 2, so you need to program 2 routes.
|
||||
<!--l. 295--><p class="noindent" ><img
|
||||
<!--l. 344--><p class="noindent" ><img
|
||||
src="6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png" alt="PIC"
|
||||
>
|
||||
<!--l. 297--><p class="noindent" >This leads us to the most important aspect of route programming: Routes always start at a signal (A) and end at a signal facing in the
|
||||
<!--l. 346--><p class="noindent" >This leads us to the most important aspect of route programming: Routes always start at a signal (A) and end at a signal facing in the
|
||||
<span
|
||||
class="ecbx-1000">same direction </span>(D and E), not at an opposite-facing signal (B and C). There are only few exceptions, we’ll cover this
|
||||
later.
|
||||
<!--l. 302--><p class="noindent" >When you set a route to make a train proceed on it, the interlocking system ensures that:
|
||||
<!--l. 351--><p class="noindent" >When you set a route to make a train proceed on it, the interlocking system ensures that:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">There are no rail vehicles on the route
|
||||
</li>
|
||||
<li class="itemize">All turnouts are set to the correct position and it is impossible to move them
|
||||
</li>
|
||||
<li class="itemize">No other routes can be set that would in any way conflict with this route</li></ul>
|
||||
<!--l. 311--><p class="noindent" >For this to work, you need to specify all track sections the train will pass along, as well as the positions of all turnouts that need to be
|
||||
<!--l. 360--><p class="noindent" >For this to work, you need to specify all track sections the train will pass along, as well as the positions of all turnouts that need to be
|
||||
locked. Those are not only the turnouts that lay directly on the train’s route, but also some turnouts on adjacent tracks, the so-called
|
||||
flank protection.
|
||||
<!--l. 317--><p class="noindent" >The purpose of flank protection is to prevent runaway trains and/or wagons to pass into a route. This is achieved by setting nearby
|
||||
<!--l. 366--><p class="noindent" >The purpose of flank protection is to prevent runaway trains and/or wagons to pass into a route. This is achieved by setting nearby
|
||||
turnouts to a position that points “away” from the route. Example:
|
||||
<!--l. 321--><p class="noindent" ><img
|
||||
<!--l. 370--><p class="noindent" ><img
|
||||
src="7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png" alt="PIC"
|
||||
>
|
||||
<!--l. 323--><p class="noindent" >The upper turnout, of course, needs to be locked in straight (normal) position, while the lower one is not relevant for the route itself. But
|
||||
<!--l. 372--><p class="noindent" >The upper turnout, of course, needs to be locked in straight (normal) position, while the lower one is not relevant for the route itself. But
|
||||
what if the lower turnout was set to the diverging (reverse) position and the driver of another train approaching signal B fails to see the
|
||||
red light? This train would crash into the first one. To minimise danger, that other train would need to be routed towards signal
|
||||
D.
|
||||
<!--l. 330--><p class="noindent" >There are, of course, situations, where both positions of a turnout would conflict with a route equally. In those situations, there’s nothing
|
||||
<!--l. 379--><p class="noindent" >There are, of course, situations, where both positions of a turnout would conflict with a route equally. In those situations, there’s nothing
|
||||
you can do and no flank lock needs to be set.
|
||||
<!--l. 334--><p class="noindent" >
|
||||
<!--l. 383--><p class="noindent" >
|
||||
<a
|
||||
id="x1-35r4"></a>
|
||||
<!--l. 334--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.4</span> <span
|
||||
id="x1-36r5"></a>
|
||||
<!--l. 383--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.5</span> <span
|
||||
class="ecsx-1200">Assigning</span>
|
||||
<span
|
||||
class="ecsx-1200">main</span>
|
||||
|
|
@ -413,90 +452,85 @@ class="ecsx-1200">to</span>
|
|||
class="ecsx-1200">TCBs</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 336--><p class="noindent" >Main signals in the advtrains interlocking system are positioned - like in real life - at the border of track sections, because routes also start
|
||||
<!--l. 385--><p class="noindent" >Main signals in the advtrains interlocking system are positioned - like in real life - at the border of track sections, because routes also start
|
||||
and end there. For advtrains to know from which signal which routes can be set, you need to assign the signal to a
|
||||
TCB.
|
||||
<!--l. 341--><p class="noindent" >To do this, perform the following steps:
|
||||
<!--l. 390--><p class="noindent" >To do this, perform the following steps:
|
||||
<ol class="enumerate1" >
|
||||
<li
|
||||
class="enumerate" id="x1-37x1">If not already happened, set up a TCB (you don’t need to, but are advised to, configure track sections there)
|
||||
class="enumerate" id="x1-38x1">If not already happened, set up a TCB (you don’t need to, but are advised to, configure track sections there)
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-39x2">Place the signal a few meters in front of the TCB, so that trains stopping at the signal do never pass the TCB
|
||||
class="enumerate" id="x1-40x2">Place the signal a few meters in front of the TCB, so that trains stopping at the signal do never pass the TCB
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-41x3">Locate the side of the TCB which points in the direction that trains will proceed past the signal, as shown in the figure
|
||||
class="enumerate" id="x1-42x3">Locate the side of the TCB which points in the direction that trains will proceed past the signal, as shown in the figure
|
||||
below.
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-43x4">Right-click the TCB, and click “Assign a signal” on this side.
|
||||
class="enumerate" id="x1-44x4">Right-click the TCB, and click “Assign a signal” on this side.
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-45x5">Punch the signal.</li></ol>
|
||||
<!--l. 352--><p class="noindent" ><img
|
||||
class="enumerate" id="x1-46x5">Punch the signal.</li></ol>
|
||||
<!--l. 401--><p class="noindent" ><img
|
||||
src="8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png" alt="PIC"
|
||||
>
|
||||
<!--l. 354--><p class="noindent" >If you haven’t set an influence point for the signal yet, the influence point formspec automatically opens.
|
||||
<!--l. 357--><p class="noindent" >You can assign a signal to each side of a TCB. This is, for example, useful when creating block sections on a bi-directional main running
|
||||
<!--l. 403--><p class="noindent" >If you haven’t set an influence point for the signal yet, the influence point formspec automatically opens.
|
||||
<!--l. 406--><p class="noindent" >You can assign a signal to each side of a TCB. This is, for example, useful when creating block sections on a bi-directional main running
|
||||
line.
|
||||
<!--l. 361--><p class="noindent" >Only main signals can ever be assigned to TCBs, because static ones can either not display “Danger” or do not permit to proceed at
|
||||
<!--l. 410--><p class="noindent" >Only main signals can ever be assigned to TCBs, because static ones can either not display “Danger” or do not permit to proceed at
|
||||
all.
|
||||
<!--l. 365--><p class="noindent" >
|
||||
<!--l. 414--><p class="noindent" >
|
||||
<a
|
||||
id="x1-46r5"></a>
|
||||
<!--l. 365--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.5</span> <span
|
||||
id="x1-47r6"></a>
|
||||
<!--l. 414--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.6</span> <span
|
||||
class="ecsx-1200">Shunt</span>
|
||||
<span
|
||||
class="ecsx-1200">routes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 368--><p class="noindent" ><span
|
||||
<!--l. 417--><p class="noindent" ><span
|
||||
class="ecbx-1000">The information in this section is subject to future change because of safety issues!</span>
|
||||
<!--l. 370--><p class="noindent" >Operating railways is not all about driving trains around. Coupling, decoupling and moving single engines, wagons or groups of wagons
|
||||
<!--l. 419--><p class="noindent" >Operating railways is not all about driving trains around. Coupling, decoupling and moving single engines, wagons or groups of wagons
|
||||
across a station, called shunting, also plays an important role.
|
||||
<!--l. 374--><p class="noindent" >Remember what we said about routes: There must be no rail vehicles on the route. So what if you have some goods wagons
|
||||
<!--l. 423--><p class="noindent" >Remember what we said about routes: There must be no rail vehicles on the route. So what if you have some goods wagons
|
||||
ready on a siding, and want to couple an engine to it? You can not set a regular route into the siding, because it is
|
||||
occupied.
|
||||
<!--l. 379--><p class="noindent" >The solution is to program a second route into the siding, but with the difference that it already ends at the rear-facing signal of it, so it
|
||||
<!--l. 428--><p class="noindent" >The solution is to program a second route into the siding, but with the difference that it already ends at the rear-facing signal of it, so it
|
||||
doesn’t include the siding section itself:
|
||||
<!--l. 383--><p class="noindent" ><img
|
||||
<!--l. 432--><p class="noindent" ><img
|
||||
src="9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png" alt="PIC"
|
||||
>
|
||||
<!--l. 385--><p class="noindent" >The Sht2 route then needs to show a shunt aspect, which instructs the driver to proceed slowly and watch out for vehicles on the route.
|
||||
To show a “free” aspect here would be wrong, because that would mean that the track is free until the next main signal, which it is clearly
|
||||
not.
|
||||
<!--l. 393--><p class="noindent" ><span
|
||||
class="ecti-1000">Note that advtrains_interlocking currently does not allow to set individual aspects for routes, this is a feature still to be implemented</span>
|
||||
<span
|
||||
class="ecti-1000">soon.</span>
|
||||
<!--l. 395--><p class="noindent" >Shunt routes like this are, so far, the only exception to the “Routes should end at a signal facing the same direction”
|
||||
<!--l. 434--><p class="noindent" >The Sht2 route then needs to show a shunt aspect, which instructs the driver to proceed slowly and watch out for vehicles on the route.
|
||||
See later on for how to set this up.
|
||||
<!--l. 438--><p class="noindent" >Shunt routes like this are, so far, the only exception to the “Routes should end at a signal facing the same direction”
|
||||
rule.
|
||||
<!--l. 398--><p class="noindent" >
|
||||
<!--l. 441--><p class="noindent" >
|
||||
<a
|
||||
id="x1-47r6"></a>
|
||||
<!--l. 398--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.6</span> <span
|
||||
id="x1-48r7"></a>
|
||||
<!--l. 441--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.7</span> <span
|
||||
class="ecsx-1200">Route</span>
|
||||
<span
|
||||
class="ecsx-1200">Release</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 400--><p class="noindent" >In early real-life interlocking systems, routes either had to be cancelled by the signalman after the train had passed the route, or there was
|
||||
<!--l. 443--><p class="noindent" >In early real-life interlocking systems, routes either had to be cancelled by the signalman after the train had passed the route, or there was
|
||||
a single release contact at the end of the route. However, as interlocking systems evolved and the position of trains is now
|
||||
roughly known by the track sections, portions of the route can be freed as soon as the train has left the corresponding
|
||||
section.
|
||||
<!--l. 407--><p class="noindent" >AdvTrains has chosen a modern approach to route releasing. Each turnout lock is associated to a track section belonging to the route’s
|
||||
<!--l. 450--><p class="noindent" >AdvTrains has chosen a modern approach to route releasing. Each turnout lock is associated to a track section belonging to the route’s
|
||||
path. Once the train leaves this section, all assigned locks are also freed.
|
||||
<!--l. 411--><p class="noindent" >Please note that reversing a train outside of stations is not only discouraged, but also very dangerous, because even
|
||||
<!--l. 454--><p class="noindent" >Please note that reversing a train outside of stations is not only discouraged, but also very dangerous, because even
|
||||
real-world interlocking system do not expect this. There is a clear, human-sense rule that you should never reverse the
|
||||
driving direction of a train while on a main line or on a turnout. Else, you can be considered a terrorist. (quote from
|
||||
professional!)
|
||||
<!--l. 418--><p class="noindent" >
|
||||
<!--l. 461--><p class="noindent" >
|
||||
<a
|
||||
id="x1-48r7"></a>
|
||||
<!--l. 418--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.7</span> <span
|
||||
id="x1-49r8"></a>
|
||||
<!--l. 461--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.8</span> <span
|
||||
class="ecsx-1200">Programming</span>
|
||||
<span
|
||||
class="ecsx-1200">a</span>
|
||||
|
|
@ -504,13 +538,13 @@ class="ecsx-1200">a</span>
|
|||
class="ecsx-1200">route</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 420--><p class="noindent" >The route programming procedure is quite straightforward if you’ve read the previous sections and understood how routes should be
|
||||
<!--l. 463--><p class="noindent" >The route programming procedure is quite straightforward if you’ve read the previous sections and understood how routes should be
|
||||
set.
|
||||
<!--l. 423--><p class="noindent" >Routes always start at a main signal. You must have assigned the signal to a TCB, as described earlier.
|
||||
<!--l. 426--><p class="noindent" >When you right-click the main signal, it no longer changes its aspect. Instead, a formspec pops up, showing you an (empty) list of routes
|
||||
<!--l. 466--><p class="noindent" >Routes always start at a main signal. You must have assigned the signal to a TCB, as described earlier.
|
||||
<!--l. 469--><p class="noindent" >When you right-click the main signal, it no longer changes its aspect. Instead, a formspec pops up, showing you an (empty) list of routes
|
||||
with the possibility to set them or to create new routes. Click the “Create new route” button to start programming a new
|
||||
route.
|
||||
<!--l. 431--><p class="noindent" >The form closes, and an arrow is displayed on the TCB. You are now in “Route Programming” mode, programming the first track section
|
||||
<!--l. 474--><p class="noindent" >The form closes, and an arrow is displayed on the TCB. You are now in “Route Programming” mode, programming the first track section
|
||||
of the route. Now:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Put any turnouts you need to lock in the correct position (e.g. by right-clicking them). This includes flank protection.
|
||||
|
|
@ -521,11 +555,11 @@ of the route. Now:
|
|||
</li>
|
||||
<li class="itemize">When you’ve locked all turnouts in the current section, go to and punch the TCB that is the border to the next track
|
||||
section the train proceeds into.</li></ul>
|
||||
<!--l. 444--><p class="noindent" >Depending on the situation, you are now offered some possibilities to proceed:
|
||||
<!--l. 487--><p class="noindent" >Depending on the situation, you are now offered some possibilities to proceed:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Click the “Advance to next section” button if your route consists of more sections with turnouts to lock, and you need to
|
||||
continue programming. Follow the above steps to set locks for the next section.</li></ul>
|
||||
<!--l. 451--><p class="noindent" >Once you’ve clicked the “Advance” button, the lock markers change to a red lock symbol, telling they can’t be changed anymore. Repeat
|
||||
<!--l. 494--><p class="noindent" >Once you’ve clicked the “Advance” button, the lock markers change to a red lock symbol, telling they can’t be changed anymore. Repeat
|
||||
the above procedure until you are ready to complete the programming procedure:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Click the “Finish route HERE” button when you’ve set up the locks for the last track section of the route and punched the
|
||||
|
|
@ -534,12 +568,8 @@ the above procedure until you are ready to complete the programming procedure:
|
|||
<li class="itemize">The “Finish route at end of NEXT section” button (third button) is an useful quickhand to make the route proceed one
|
||||
more section. Using this button is equivalent to first clicking the “Advance” button, then flying to the end of the next track
|
||||
section and finishing the route there. You can not (officially) set turnout locks in the final section using this method.</li></ul>
|
||||
<!--l. 467--><p class="noindent" >A few hints:
|
||||
<!--l. 510--><p class="noindent" >A few hints:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">If one turnout should be locked by more than one section, set the lock only in the <span
|
||||
class="ectt-1000">last </span>of those sections. Locking the same
|
||||
turnout in multiple sections of a single route results in undefined behavior!
|
||||
</li>
|
||||
<li class="itemize">If you accidentally advanced the route wrongly, you can use the “Step back one section” button to undo this.
|
||||
</li>
|
||||
<li class="itemize">If you want to stop programming the entire route without saving it, use the “Cancel route programming” button.
|
||||
|
|
@ -552,10 +582,64 @@ class="ectt-1000">last </span>of those sections. Locking the same
|
|||
</li>
|
||||
<li class="itemize">The third button does NOT work on sections with more than 2 exits, because the system won’t be able to determine the
|
||||
final TCB of the route then.</li></ul>
|
||||
<!--l. 488--><p class="noindent" >
|
||||
<!--l. 527--><p class="noindent" >
|
||||
<a
|
||||
id="x1-49r4"></a>
|
||||
<!--l. 488--><p class="noindent" ><span
|
||||
id="x1-50r9"></a>
|
||||
<!--l. 527--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.9</span> <span
|
||||
class="ecsx-1200">Route</span>
|
||||
<span
|
||||
class="ecsx-1200">information</span>
|
||||
<span
|
||||
class="ecsx-1200">screen</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 529--><p class="noindent" ><img
|
||||
src="10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.png" alt="PIC"
|
||||
>
|
||||
<!--l. 531--><p class="noindent" >This is the screen that appears when you click “Edit Route”. It lets you change the route name and delete the route. Also, it shows a
|
||||
summary of the route and its elements.
|
||||
<!--l. 535--><p class="noindent" >The route summary lists information per track section on the route, so the line starting with “1” is the first section of the
|
||||
route.
|
||||
<!--l. 538--><p class="noindent" >The ARS rule list and its purpose is explained later.
|
||||
<!--l. 540--><p class="noindent" >
|
||||
<a
|
||||
id="x1-51r10"></a>
|
||||
<!--l. 540--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.10</span> <span
|
||||
class="ecsx-1200">Specifying</span>
|
||||
<span
|
||||
class="ecsx-1200">signal</span>
|
||||
<span
|
||||
class="ecsx-1200">aspects</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 542--><p class="noindent" >By default, newly programmed routes show an aspect that comes closest to “Proceed at maximum speed”. However, it can be desirable to
|
||||
change this behavior, like when the route passes a diverging turnout, the train should be signalled to drive slower, or the route is a shunt
|
||||
route and therefore only “Shunting allowed” should be shown.
|
||||
<!--l. 548--><p class="noindent" >This is the purpose of the “Change Aspect” button in the route info screen.
|
||||
<!--l. 551--><p class="noindent" >Signal aspects in advtrains consist of 4 sections: main (Information for train moves), dst (Distant signal information, not implemented
|
||||
yet), shunt (Information for shunt moves) and info (additional information, currently not in use).
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Train may proceed as train move at maximum speed: “main: free, speed -1”
|
||||
</li>
|
||||
<li class="itemize">Train may proceed as train move at speed of 8: “main: free, speed 8”
|
||||
</li>
|
||||
<li class="itemize">Train may proceed as shunt move: “shunt: free”</li></ul>
|
||||
<!--l. 562--><p class="noindent" >There’s a field in the “shunt” part of signal aspects that is not displayed in the GUI, but is of potential interest to developers of signal
|
||||
addons: shunt.proceed_as_main.
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">A train move can always become a shunt move by passing a signal that shows “Halt for train moves, shunting permitted”
|
||||
</li>
|
||||
<li class="itemize">A shunt move can only pass a signal saying “Proceed as train move, shunting not permitted” when proceed_as_main is
|
||||
true.</li></ul>
|
||||
<!--l. 571--><p class="noindent" >The property is used by the Limit Of Shunt sign, where proceed_as_main is set to false. Shunt moves have to stop in front of it, while
|
||||
train moves are signalled “Proceed”. Regular main signals that show “green” have the field set to true, so that all trains can pass
|
||||
it.
|
||||
<!--l. 577--><p class="noindent" >
|
||||
<a
|
||||
id="x1-52r4"></a>
|
||||
<!--l. 577--><p class="noindent" ><span
|
||||
class="ecsx-1200">4</span> <span
|
||||
class="ecsx-1200">Interlocking</span>
|
||||
<span
|
||||
|
|
@ -564,16 +648,16 @@ class="ecsx-1200">system</span>
|
|||
class="ecsx-1200">operation</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 490--><p class="noindent" >Setting up the interlocking for a portion of a railway network requires some time, experience and planning, but once done, there’s not
|
||||
<!--l. 579--><p class="noindent" >Setting up the interlocking for a portion of a railway network requires some time, experience and planning, but once done, there’s not
|
||||
much to do anymore to make trains run on your, now safer, railway. This section covers some useful practices to route trains across your
|
||||
network.
|
||||
<!--l. 495--><p class="noindent" >At the moment, routes can either be set by clicking the signal or via LuaATC, or by using the “Remote Routesetting”
|
||||
<!--l. 584--><p class="noindent" >At the moment, routes can either be set by clicking the signal or via LuaATC, or by using the “Remote Routesetting”
|
||||
button from the Onboard Computer. It is planned to control this via a “signal box” view based on the currently broken
|
||||
itrainmap.
|
||||
<!--l. 500--><p class="noindent" >
|
||||
<!--l. 589--><p class="noindent" >
|
||||
<a
|
||||
id="x1-50r1"></a>
|
||||
<!--l. 500--><p class="noindent" ><span
|
||||
id="x1-53r1"></a>
|
||||
<!--l. 589--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.1</span> <span
|
||||
class="ecsx-1200">Train</span>
|
||||
<span
|
||||
|
|
@ -582,18 +666,17 @@ class="ecsx-1200">Safety</span>
|
|||
class="ecsx-1200">System</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 502--><p class="noindent" >The Train Safety System, called “LZB” in the code (from the german term Linienzugbeeinflussung, although this is a completely different
|
||||
<!--l. 591--><p class="noindent" >The Train Safety System, called “LZB” in the code (from the german term Linienzugbeeinflussung, although this is a completely different
|
||||
system), ensures that trains obey any restrictions imposed by signals when influence points are set. This way, it is not possible to pass
|
||||
signals at danger or to bypass speed restrictions.
|
||||
<!--l. 508--><p class="noindent" >It is possible to overrun red signals, if a route is cancelled while a train is approaching. Real interlocking systems use a mechanism called
|
||||
<!--l. 597--><p class="noindent" >It is possible to overrun red signals, if a route is cancelled while a train is approaching. Real interlocking systems use a mechanism called
|
||||
Approach locking for this, however, as of now, there’s no similar system in this mod. If a red signal is overrun, the train brakes using
|
||||
emergency brake (“BB”) and can not be moved any further. You should then examine the situation and drive the train backwards out of
|
||||
the section.
|
||||
<!--l. 516--><p class="noindent" >As of now, changing the driving direction of a train always clears any imposed speed restrictions.
|
||||
<!--l. 519--><p class="noindent" >
|
||||
<!--l. 605--><p class="noindent" >
|
||||
<a
|
||||
id="x1-51r2"></a>
|
||||
<!--l. 519--><p class="noindent" ><span
|
||||
id="x1-54r2"></a>
|
||||
<!--l. 605--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.2</span> <span
|
||||
class="ecsx-1200">Simple</span>
|
||||
<span
|
||||
|
|
@ -606,57 +689,141 @@ class="ecsx-1200">and</span>
|
|||
class="ecsx-1200">cancelling</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 521--><p class="noindent" >To set a route, simply right-click the signal, select a route and click “set route”. If there are no conflicts, the signal turns green and the
|
||||
<!--l. 607--><p class="noindent" >To set a route, simply right-click the signal, select a route and click “set route”. If there are no conflicts, the signal turns green and the
|
||||
train is allowed to proceed.
|
||||
<!--l. 525--><p class="noindent" >It may be possible that the route can not be set, because one or more other routes conflict with the current one, or a section is blocked. In
|
||||
<!--l. 611--><p class="noindent" >It may be possible that the route can not be set, because one or more other routes conflict with the current one, or a section is blocked. In
|
||||
this case, the signal stays red, and the conflicting item is shown in the formspec. As soon as the conflict is resolved (by cancellation
|
||||
or release of the conflicting route, or the section becoming free), the requested route will be set and the signal turns
|
||||
green.
|
||||
<!--l. 532--><p class="noindent" >If a route is either requested or set, it can be cancelled from the signalling formspec. This means that all turnouts and sections are
|
||||
<!--l. 618--><p class="noindent" >If a route is either requested or set, it can be cancelled from the signalling formspec. This means that all turnouts and sections are
|
||||
released, and the signal reverts back to red. This of course only works when the train has not passed the signal yet. There is no
|
||||
mechanism for Approach Locking.
|
||||
<!--l. 538--><p class="noindent" >
|
||||
<!--l. 624--><p class="noindent" >
|
||||
<a
|
||||
id="x1-52r3"></a>
|
||||
<!--l. 538--><p class="noindent" ><span
|
||||
id="x1-55r3"></a>
|
||||
<!--l. 624--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.3</span> <span
|
||||
class="ecsx-1200">Automatic</span>
|
||||
<span
|
||||
class="ecsx-1200">Working</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 540--><p class="noindent" >Block signals on main running lines usually only have a single route to set, the one proceeding along the main line. Their purpose is only
|
||||
<!--l. 626--><p class="noindent" >Block signals on main running lines usually only have a single route to set, the one proceeding along the main line. Their purpose is only
|
||||
to show whether there are trains in the next section. So, it would be convenient if this only route would set itself again after a train
|
||||
passed.
|
||||
<!--l. 546--><p class="noindent" >This is what Automatic Working is for. Set a route, click “Enable Automatic Working”, and as soon as a train passes, the route is
|
||||
<!--l. 632--><p class="noindent" >This is what Automatic Working is for. Set a route, click “Enable Automatic Working”, and as soon as a train passes, the route is
|
||||
automatically re-set.
|
||||
<!--l. 550--><p class="noindent" >This function is nearly identical to SimSig automatic signals. It can also be useful on a line with high traffic, when there’s a
|
||||
<!--l. 636--><p class="noindent" >This function is nearly identical to SimSig automatic signals. It can also be useful on a line with high traffic, when there’s a
|
||||
low-frequented access to a siding. You’d enable automatic working for the main route and cancel it only when you need a train to go into
|
||||
the siding.
|
||||
<!--l. 555--><p class="noindent" >
|
||||
<!--l. 641--><p class="noindent" >
|
||||
<a
|
||||
id="x1-53r5"></a>
|
||||
<!--l. 555--><p class="noindent" ><span
|
||||
id="x1-56r4"></a>
|
||||
<!--l. 641--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.4</span> <span
|
||||
class="ecsx-1200">Automatic</span>
|
||||
<span
|
||||
class="ecsx-1200">Route</span>
|
||||
<span
|
||||
class="ecsx-1200">Setting</span>
|
||||
<span
|
||||
class="ecsx-1200">(ARS)</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 643--><p class="noindent" >As interlocking systems evolved, the goal always was to offload work from the human to the system, automating things. Modern
|
||||
interlocking systems can automatically set routes based on a pre-programmed routing table for each particular train. Since one
|
||||
outstanding feature of Advtrains is it’s high degree of automation, it has a similar system to automatically set routes for a train
|
||||
depending on certain parameters.
|
||||
<!--l. 650--><p class="noindent" >Every train in Advtrains has 2 internal properties that can be set through the Onboard Computer of every engine in the train, the “Line”
|
||||
and the “Routing Code”
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">The “Line” property is supposed to distinguish trains of multiple lines that share a track.
|
||||
</li>
|
||||
<li class="itemize">The “Routing Code” property is supposed to tell the target of a train or which route it should take to reach the target</li></ul>
|
||||
<!--l. 659--><p class="noindent" >Examples:
|
||||
<!--l. 661--><p class="noindent" ><img
|
||||
src="11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.png" alt="PIC"
|
||||
>
|
||||
<!--l. 663--><p class="noindent" >Both lines share the section between Blackbirdshire and Parktown. To divert them again, they can save their line number in the “Line”
|
||||
field.
|
||||
<!--l. 667--><p class="noindent" ><img
|
||||
src="12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.png" alt="PIC"
|
||||
>
|
||||
<!--l. 669--><p class="noindent" >Some trains should go to B, some to C, the direction can be set with a routing code.
|
||||
<!--l. 672--><p class="noindent" >One single routing code should not contain spaces. You can set multiple routing codes by just separating them with spaces in the
|
||||
Routing Code field. So, “Stn Ori” would be matched by ARS rules either containing “Stn” or “Ori”. This does not work for
|
||||
lines.
|
||||
<!--l. 677--><p class="noindent" >
|
||||
<a
|
||||
id="x1-57r1"></a>
|
||||
<!--l. 677--><p class="noindent" ><span
|
||||
class="ecsx-1000">4.4.1</span> <span
|
||||
class="ecsx-1000">Writing</span>
|
||||
<span
|
||||
class="ecsx-1000">ARS</span>
|
||||
<span
|
||||
class="ecsx-1000">Rules</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 679--><p class="noindent" >Every route of every signal can be given a set of ARS rules. A single ARS rule can either match a line or a routing code (combinations,
|
||||
e.g. and’s, are not yet supported). The first rule in the first route that matches any of the properties of the train is selected, and that
|
||||
route is set for the train.
|
||||
<!--l. 685--><p class="noindent" ><img
|
||||
src="13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.png" alt="PIC"
|
||||
>
|
||||
<!--l. 687--><p class="noindent" >You can add an asterisk (“*”) to the ARS rules of one route. That route then becomes the default route.
|
||||
<!--l. 690--><p class="noindent" >If no explicit ARS rule matches the train, then the default route is chosen and set. If there is no default route, nothing happens and the
|
||||
signal remains red.
|
||||
<!--l. 694--><p class="noindent" >
|
||||
<a
|
||||
id="x1-58r2"></a>
|
||||
<!--l. 694--><p class="noindent" ><span
|
||||
class="ecsx-1000">4.4.2</span> <span
|
||||
class="ecsx-1000">Using</span>
|
||||
<span
|
||||
class="ecsx-1000">ARS</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 696--><p class="noindent" >In contrast to Automatic working, where the route is re-set immediately after the train passed, ARS sets the route only when the train
|
||||
approaches the signal, e.g. is just about to start braking in front of it.
|
||||
<!--l. 700--><p class="noindent" >At any place where one of the following things take place, you should use the ARS system in favor of Automatic Working:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">A main line diverts into 2 or more lines: Using ARS, you can direct the trains along the line where they should go
|
||||
</li>
|
||||
<li class="itemize">Two or more main lines join into one: You cannot use automatic working here, because all routes are tried to be set at the
|
||||
same time and it is a matter of luck which one “wins”. In a bad situation, you have a train coming from A, but it cannot
|
||||
proceed because Signal B has won the “route race” into the shared section, even if there’s no train coming from B. Using
|
||||
ARS, by just specifying the “default route” by a *, the inward route is only set when a train approaches.
|
||||
</li>
|
||||
<li class="itemize">Complex intersections, which are probably a combination of the above two
|
||||
</li>
|
||||
<li class="itemize">sometimes-used branching tracks on which only certain trains (with certain routing code or line) should head off, like the
|
||||
entrance to a factory where only one specific goods train should drive in.</li></ul>
|
||||
<!--l. 718--><p class="noindent" >In the route overview, you can see some information on the ARS settings: All routes that have ARS rules are highlighted red, the “default
|
||||
route” is highlighted green.
|
||||
<!--l. 722--><p class="noindent" >ARS does not affect signals which already have a route set, and signals which are operating under “Automatic Working”.
|
||||
<!--l. 725--><p class="noindent" >
|
||||
<a
|
||||
id="x1-59r5"></a>
|
||||
<!--l. 725--><p class="noindent" ><span
|
||||
class="ecsx-1200">5</span> <span
|
||||
class="ecsx-1200">Final</span>
|
||||
<span
|
||||
class="ecsx-1200">notes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 557--><p class="noindent" >The interlocking system is mainly finished, though there are still some plans and ideas. They include:
|
||||
<!--l. 727--><p class="noindent" >The interlocking system is mainly finished, though there are still some plans and ideas. They include:
|
||||
<ul class="itemize1">
|
||||
<li class="itemize">Signalbox panels, as revival of itrainmap
|
||||
</li>
|
||||
<li class="itemize">Individual signal aspects for routes
|
||||
</li>
|
||||
<li class="itemize">Distant signals
|
||||
</li>
|
||||
<li class="itemize">On-Train head-up display for oncoming signals (they have something like this in Czech Republic, I forgot how it’s called.)</li></ul>
|
||||
<!--l. 566--><p class="noindent" >Apart from this, there’s the large oncoming project of a new timetable-based train automation system, but this will take some time to
|
||||
<!--l. 735--><p class="noindent" >Apart from this, there’s the large oncoming project of a new timetable-based train automation system, but this will take some time to
|
||||
evolve and is out of the scope of this document.
|
||||
<!--l. 570--><p class="noindent" >If you have any suggestions, corrections, improvements, criticism or cute kittens and stuff, you can always contact me by various means
|
||||
<!--l. 739--><p class="noindent" >If you have any suggestions, corrections, improvements, criticism or cute kittens and stuff, you can always contact me by various means
|
||||
(Forum PM, E-Mail (orwell@bleipb.de), Linuxworks server chat a.s.o.). Have fun!
|
||||
<!--l. 575--><p class="noindent" >- orwell
|
||||
<!--l. 744--><p class="noindent" >- orwell
|
||||
</body></html>
|
||||
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -46,22 +46,6 @@ htfcss: ecss font-family: sans-serif;
|
|||
htfcss: ecff font-family: fantasy;
|
||||
htfcss: ecti font-style: italic;
|
||||
htfcss: ectt font-family: monospace;
|
||||
htfcss: ecbx font-weight: bold;
|
||||
htfcss: ecsx font-weight: bold;
|
||||
htfcss: ecbi font-weight: bold; font-style: italic;
|
||||
htfcss: ecit font-style: italic; font-family: monospace;
|
||||
htfcss: ecss font-family: sans-serif;
|
||||
htfcss: ecff font-family: fantasy;
|
||||
htfcss: ecti font-style: italic;
|
||||
htfcss: ectt font-family: monospace;
|
||||
htfcss: ecbx font-weight: bold;
|
||||
htfcss: ecsx font-weight: bold;
|
||||
htfcss: ecbi font-weight: bold; font-style: italic;
|
||||
htfcss: ecit font-style: italic; font-family: monospace;
|
||||
htfcss: ecss font-family: sans-serif;
|
||||
htfcss: ecff font-family: fantasy;
|
||||
htfcss: ecti font-style: italic;
|
||||
htfcss: ectt font-family: monospace;
|
||||
File: interlocking.html
|
||||
File: interlocking.css
|
||||
File: interlocking.tmp
|
||||
|
|
@ -169,6 +153,10 @@ File: 6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_im
|
|||
File: 7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png
|
||||
File: 8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png
|
||||
File: 9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png
|
||||
File: 10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.png
|
||||
File: 11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.png
|
||||
File: 12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.png
|
||||
File: 13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.png
|
||||
--- characters ---
|
||||
Font("ecrm","1000","10","100")
|
||||
Font("ecsx","1728","17","100")
|
||||
|
|
@ -176,5 +164,3 @@ Font("ecst","1440","14","100")
|
|||
Font("ecsx","1200","12","100")
|
||||
Font("ecsx","1000","10","100")
|
||||
Font("ecbx","1000","10","100")
|
||||
Font("ecti","1000","10","100")
|
||||
Font("ectt","1000","10","100")
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=latex 2018.8.26) 15 OCT 2018 22:04
|
||||
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) (preloaded format=latex 2018.10.18) 15 JAN 2019 21:06
|
||||
entering extended mode
|
||||
restricted \write18 enabled.
|
||||
%&-line parsing enabled.
|
||||
|
|
@ -483,46 +483,73 @@ _Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-2
|
|||
l. 173 --- needs --- 5_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img
|
||||
_Bildschirmfoto_2018-08-30_14-51-25.png ---
|
||||
[5] [6] [7]
|
||||
l.295 --- TeX4ht warning --- File `"6_home_moritz_Home_Projekte_Minetest_minete
|
||||
l.344 --- TeX4ht warning --- File `"6_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_mods_advtrains_assets_lyx_img_route_ex1.xbb"' not found ---
|
||||
l.295 --- TeX4ht warning --- Cannot determine size of graphic in "6_home_moritz
|
||||
l.344 --- TeX4ht warning --- Cannot determine size of graphic in "6_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.xbb" (
|
||||
no BoundingBox) ---
|
||||
l. 295 --- needs --- 6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
l. 344 --- needs --- 6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
ns_assets_lyx_img_route_ex1.png ---
|
||||
l.321 --- TeX4ht warning --- File `"7_home_moritz_Home_Projekte_Minetest_minete
|
||||
[8]
|
||||
l.370 --- TeX4ht warning --- File `"7_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_mods_advtrains_assets_lyx_img_route_ex2.xbb"' not found ---
|
||||
l.321 --- TeX4ht warning --- Cannot determine size of graphic in "7_home_moritz
|
||||
l.370 --- TeX4ht warning --- Cannot determine size of graphic in "7_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.xbb" (
|
||||
no BoundingBox) ---
|
||||
l. 321 --- needs --- 7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
l. 370 --- needs --- 7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
ns_assets_lyx_img_route_ex2.png ---
|
||||
l.352 --- TeX4ht warning --- File `"8_home_moritz_Home_Projekte_Minetest_minete
|
||||
l.401 --- TeX4ht warning --- File `"8_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_mods_advtrains_assets_lyx_img_assign_signal.xbb"' not found ---
|
||||
l.352 --- TeX4ht warning --- Cannot determine size of graphic in "8_home_moritz
|
||||
l.401 --- TeX4ht warning --- Cannot determine size of graphic in "8_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.xb
|
||||
b" (no BoundingBox) ---
|
||||
l. 352 --- needs --- 8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
l. 401 --- needs --- 8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
ns_assets_lyx_img_assign_signal.png ---
|
||||
[8]
|
||||
l.383 --- TeX4ht warning --- File `"9_home_moritz_Home_Projekte_Minetest_minete
|
||||
l.432 --- TeX4ht warning --- File `"9_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_mods_advtrains_assets_lyx_img_route_ex3.xbb"' not found ---
|
||||
l.383 --- TeX4ht warning --- Cannot determine size of graphic in "9_home_moritz
|
||||
l.432 --- TeX4ht warning --- Cannot determine size of graphic in "9_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.xbb" (
|
||||
no BoundingBox) ---
|
||||
l. 383 --- needs --- 9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
l. 432 --- needs --- 9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrai
|
||||
ns_assets_lyx_img_route_ex3.png ---
|
||||
[9]
|
||||
LaTeX Font Info: Font shape `T1/cmtt/bx/n' in size <10> not available
|
||||
(Font) Font shape `T1/cmtt/m/n' tried instead on input line 470.
|
||||
[10] [11] [12] (./interlocking.aux) )
|
||||
[9] [10]
|
||||
l.529 --- TeX4ht warning --- File `"10_home_moritz_Home_Projekte_Minetest_minet
|
||||
est_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.xbb"' not found ---
|
||||
l.529 --- TeX4ht warning --- Cannot determine size of graphic in "10_home_morit
|
||||
z_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-0
|
||||
9.xbb" (no BoundingBox) ---
|
||||
l. 529 --- needs --- 10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img
|
||||
_Bildschirmfoto_2019-01-15_19-28-09.png ---
|
||||
[11] [12]
|
||||
l.661 --- TeX4ht warning --- File `"11_home_moritz_Home_Projekte_Minetest_minet
|
||||
est_mods_advtrains_assets_lyx_img_arslin_ex1.xbb"' not found ---
|
||||
l.661 --- TeX4ht warning --- Cannot determine size of graphic in "11_home_morit
|
||||
z_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.xbb"
|
||||
(no BoundingBox) ---
|
||||
l. 661 --- needs --- 11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtra
|
||||
ins_assets_lyx_img_arslin_ex1.png ---
|
||||
l.667 --- TeX4ht warning --- File `"12_home_moritz_Home_Projekte_Minetest_minet
|
||||
est_mods_advtrains_assets_lyx_img_arslin_ex2.xbb"' not found ---
|
||||
l.667 --- TeX4ht warning --- Cannot determine size of graphic in "12_home_morit
|
||||
z_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.xbb"
|
||||
(no BoundingBox) ---
|
||||
l. 667 --- needs --- 12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtra
|
||||
ins_assets_lyx_img_arslin_ex2.png ---
|
||||
l.685 --- TeX4ht warning --- File `"13_home_moritz_Home_Projekte_Minetest_minet
|
||||
est_mods_advtrains_assets_lyx_img_ars_ex1.xbb"' not found ---
|
||||
l.685 --- TeX4ht warning --- Cannot determine size of graphic in "13_home_morit
|
||||
z_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.xbb" (n
|
||||
o BoundingBox) ---
|
||||
l. 685 --- needs --- 13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtra
|
||||
ins_assets_lyx_img_ars_ex1.png ---
|
||||
[13] [14] (./interlocking.aux) )
|
||||
Here is how much of TeX's memory you used:
|
||||
5165 strings out of 494848
|
||||
63469 string characters out of 6179106
|
||||
253312 words of memory out of 5000000
|
||||
8381 multiletter control sequences out of 15000+600000
|
||||
15892 words of font info for 33 fonts, out of 8000000 for 9000
|
||||
5182 strings out of 494848
|
||||
65027 string characters out of 6179105
|
||||
253348 words of memory out of 5000000
|
||||
8396 multiletter control sequences out of 15000+600000
|
||||
14893 words of font info for 31 fonts, out of 8000000 for 9000
|
||||
59 hyphenation exceptions out of 8191
|
||||
28i,6n,29p,763b,465s stack positions out of 5000i,500n,10000p,200000b,80000s
|
||||
|
||||
Output written on interlocking.dvi (12 pages, 52488 bytes).
|
||||
Output written on interlocking.dvi (14 pages, 65604 bytes).
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -210,8 +210,11 @@ over new with setting up track sections.
|
|||
|
||||
\subsection{Interlocking patterns}
|
||||
|
||||
This section is supposed to show some examples on how you should set
|
||||
up track sections on certain track configurations.
|
||||
Have a look at the following images. They show you how you can set
|
||||
up sections so that reasonable train moves are possible.
|
||||
|
||||
You should settle on a naming scheme for your sections. This way,
|
||||
you can determine the source of an issue faster
|
||||
|
||||
\section{Signals and routes}
|
||||
|
||||
|
|
@ -223,7 +226,7 @@ There are 2 types of signals:
|
|||
\item Static signals always display the same information to the train. This
|
||||
can be a speed restriction (or the end of one), a disallowal to proceed
|
||||
as shunt move or similar things. In most cases, these are signs.
|
||||
\item Variable signals are what most people would call a ``signal''. Its
|
||||
\item Dynamic signals are what most people would call a ``signal''. Its
|
||||
function is to inform trains about whether and at which speed they
|
||||
can proceed into the next section safely.
|
||||
\end{itemize}
|
||||
|
|
@ -246,7 +249,7 @@ different ways to configure this. Signals integrated into advtrains
|
|||
behave as follows:
|
||||
\begin{itemize}
|
||||
\item Static signals and all red-green light signals from core advtrains
|
||||
that are not assigned to a TCB can be configured by holding the ``Sneak''
|
||||
that are not assigned to a TCB can be configured by holding the ``Use''
|
||||
key and then right-clicking the signal
|
||||
\item All signals that are assigned to a TCB can be configured by first
|
||||
right-clicking them, then selecting ``Influence Point'' in the signalling
|
||||
|
|
@ -264,13 +267,28 @@ The advtrains-internal train safety system ensures that the train
|
|||
always obeys any restrictions imposed by signals, if (and only if)
|
||||
the influence point is set properly.
|
||||
|
||||
\subsection{Main and Shunt signals}
|
||||
\subsection{Signal Aspects}
|
||||
|
||||
While static signals are mainly used for speed restrictions, the interesting
|
||||
ones are variable signals. Of course, you can always control any variable
|
||||
signal by traditional means (mesecons, digiline, right-click) if the
|
||||
signal allows it, but that misses the point of this interlocking system.
|
||||
|
||||
A signal aspect is a piece of information that a signal shows to the
|
||||
train driver. It contains information about whether and at what speed
|
||||
the driver may proceed at the signal.
|
||||
|
||||
Every signal, both static and dynamic ones, imposes a certain aspect
|
||||
to trains passing the signal. For static signals, this is always the
|
||||
same aspect, such as ``Proceed at speed of 8'' or ``Shunt moves
|
||||
may not pass''. Dynamic signals, however, can display multiple different
|
||||
aspects. The default for them is always as restrictive as possible,
|
||||
mostly ``Halt!''.
|
||||
|
||||
You should know that both static and dynamic signals use exactly the
|
||||
same properties for signal aspects. There is no difference in the
|
||||
meaning of the aspect definitions.
|
||||
|
||||
In the following sections, we will talk about main signals. By this,
|
||||
we mean a variable signal that can display both a ``Danger'' aspect
|
||||
(trains are not allowed to proceed) and at least one ``Proceed''
|
||||
|
|
@ -278,6 +296,37 @@ aspect (train may proceed as train/shunt move, with optional speed
|
|||
restriction), which act as an ``entry signal'' for one or multiple
|
||||
routes.
|
||||
|
||||
\subsection{Train moves and Shunt Moves}
|
||||
\begin{itemize}
|
||||
\item A ``Train move'' is a train that is running, going to run on or
|
||||
coming from a main line between stations, passing through or stopping
|
||||
at a station. Train moves can expect that there are no obstacles on
|
||||
the route and they can proceed at the maximum permitted speed of the
|
||||
line. This is the regular operation mode for trains. Shunt signals
|
||||
have no meaning for train moves.
|
||||
\item A ``Shunt move'' is a train that moves within a station and/or is
|
||||
coupling or decoupling wagons or engines. A shunt move may never leave
|
||||
a station except into a siding. Also, shunt moves may drive at a maximum
|
||||
speed of 6 speed units, because it is usually not ensured that the
|
||||
path is free of obstacles. (however, advtrains ensures that every
|
||||
route is free of railway vehicles, even shunt routes)
|
||||
\end{itemize}
|
||||
There are also 2 general types of signals: Main signals and Shunt
|
||||
signals. While main signals have a meaning for all types of trains,
|
||||
Shunt signals only have to be followed by shunt moves. Usually, Shunt
|
||||
signals that are on a train move route are set to a Proceed aspect
|
||||
as well.
|
||||
|
||||
When a train reverses, its mode automatically changes to ``shunt
|
||||
move'' until it passes a main signal that shows ``Proceed as train
|
||||
move'', which is usually designated by a green light. From this point
|
||||
on, it can accelerate to maximum permitted speed.
|
||||
|
||||
Some main signals, like the ones from the Ks signals mod included
|
||||
by default, can also display ``Proceed as shunt move'', which is
|
||||
designated by 2 white lights along with the red light. Once a train
|
||||
passes this signal, it becomes a shunt move.
|
||||
|
||||
\subsection{The concept of routes}
|
||||
|
||||
A so-called route is a locked path between two main signals, which
|
||||
|
|
@ -384,13 +433,7 @@ so it doesn't include the siding section itself:
|
|||
|
||||
The Sht2 route then needs to show a shunt aspect, which instructs
|
||||
the driver to proceed slowly and watch out for vehicles on the route.
|
||||
To show a ``free'' aspect here would be wrong, because that would
|
||||
mean that the track is free until the next main signal, which it is
|
||||
clearly not.
|
||||
|
||||
\textit{Note that advtrains\_interlocking currently does not allow
|
||||
to set individual aspects for routes, this is a feature still to be
|
||||
implemented soon.}
|
||||
See later on for how to set this up.
|
||||
|
||||
Shunt routes like this are, so far, the only exception to the ``Routes
|
||||
should end at a signal facing the same direction'' rule.
|
||||
|
|
@ -466,10 +509,6 @@ final section using this method.
|
|||
\end{itemize}
|
||||
A few hints:
|
||||
\begin{itemize}
|
||||
\item If one turnout should be locked by more than one section, set the
|
||||
lock only in the \texttt{\textbf{last}} of those sections. Locking
|
||||
the same turnout in multiple sections of a single route results in
|
||||
undefined behavior!
|
||||
\item If you accidentally advanced the route wrongly, you can use the ``Step
|
||||
back one section'' button to undo this.
|
||||
\item If you want to stop programming the entire route without saving it,
|
||||
|
|
@ -485,6 +524,56 @@ because the system won't be able to determine the final TCB of the
|
|||
route then.
|
||||
\end{itemize}
|
||||
|
||||
\subsection{Route information screen}
|
||||
|
||||
\includegraphics[width=10cm]{10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.png}
|
||||
|
||||
This is the screen that appears when you click ``Edit Route''. It
|
||||
lets you change the route name and delete the route. Also, it shows
|
||||
a summary of the route and its elements.
|
||||
|
||||
The route summary lists information per track section on the route,
|
||||
so the line starting with ``1'' is the first section of the route.
|
||||
|
||||
The ARS rule list and its purpose is explained later.
|
||||
|
||||
\subsection{Specifying signal aspects}
|
||||
|
||||
By default, newly programmed routes show an aspect that comes closest
|
||||
to ``Proceed at maximum speed''. However, it can be desirable to
|
||||
change this behavior, like when the route passes a diverging turnout,
|
||||
the train should be signalled to drive slower, or the route is a shunt
|
||||
route and therefore only ``Shunting allowed'' should be shown.
|
||||
|
||||
This is the purpose of the ``Change Aspect'' button in the route
|
||||
info screen.
|
||||
|
||||
Signal aspects in advtrains consist of 4 sections: main (Information
|
||||
for train moves), dst (Distant signal information, not implemented
|
||||
yet), shunt (Information for shunt moves) and info (additional information,
|
||||
currently not in use).
|
||||
\begin{itemize}
|
||||
\item Train may proceed as train move at maximum speed: ``main: free, speed
|
||||
-1''
|
||||
\item Train may proceed as train move at speed of 8: ``main: free, speed
|
||||
8''
|
||||
\item Train may proceed as shunt move: ``shunt: free''
|
||||
\end{itemize}
|
||||
There's a field in the ``shunt'' part of signal aspects that is
|
||||
not displayed in the GUI, but is of potential interest to developers
|
||||
of signal addons: shunt.proceed\_as\_main.
|
||||
\begin{itemize}
|
||||
\item A train move can always become a shunt move by passing a signal that
|
||||
shows ``Halt for train moves, shunting permitted''
|
||||
\item A shunt move can only pass a signal saying ``Proceed as train move,
|
||||
shunting not permitted'' when proceed\_as\_main is true.
|
||||
\end{itemize}
|
||||
The property is used by the Limit Of Shunt sign, where proceed\_as\_main
|
||||
is set to false. Shunt moves have to stop in front of it, while train
|
||||
moves are signalled ``Proceed''. Regular main signals that show
|
||||
``green'' have the field set to true, so that all trains can pass
|
||||
it.
|
||||
|
||||
\section{Interlocking system operation}
|
||||
|
||||
Setting up the interlocking for a portion of a railway network requires
|
||||
|
|
@ -513,9 +602,6 @@ emergency brake (``BB'') and can not be moved any further. You should
|
|||
then examine the situation and drive the train backwards out of the
|
||||
section.
|
||||
|
||||
As of now, changing the driving direction of a train always clears
|
||||
any imposed speed restrictions.
|
||||
|
||||
\subsection{Simple route setting and cancelling}
|
||||
|
||||
To set a route, simply right-click the signal, select a route and
|
||||
|
|
@ -552,13 +638,96 @@ can also be useful on a line with high traffic, when there's a low-frequented
|
|||
access to a siding. You'd enable automatic working for the main route
|
||||
and cancel it only when you need a train to go into the siding.
|
||||
|
||||
\subsection{Automatic Route Setting (ARS)}
|
||||
|
||||
As interlocking systems evolved, the goal always was to offload work
|
||||
from the human to the system, automating things. Modern interlocking
|
||||
systems can automatically set routes based on a pre-programmed routing
|
||||
table for each particular train. Since one outstanding feature of
|
||||
Advtrains is it's high degree of automation, it has a similar system
|
||||
to automatically set routes for a train depending on certain parameters.
|
||||
|
||||
Every train in Advtrains has 2 internal properties that can be set
|
||||
through the Onboard Computer of every engine in the train, the ``Line''
|
||||
and the ``Routing Code''
|
||||
\begin{itemize}
|
||||
\item The ``Line'' property is supposed to distinguish trains of multiple
|
||||
lines that share a track.
|
||||
\item The ``Routing Code'' property is supposed to tell the target of
|
||||
a train or which route it should take to reach the target
|
||||
\end{itemize}
|
||||
Examples:
|
||||
|
||||
\includegraphics{11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.png}
|
||||
|
||||
Both lines share the section between Blackbirdshire and Parktown.
|
||||
To divert them again, they can save their line number in the ``Line''
|
||||
field.
|
||||
|
||||
\includegraphics{12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.png}
|
||||
|
||||
Some trains should go to B, some to C, the direction can be set with
|
||||
a routing code.
|
||||
|
||||
One single routing code should not contain spaces. You can set multiple
|
||||
routing codes by just separating them with spaces in the Routing Code
|
||||
field. So, ``Stn Ori'' would be matched by ARS rules either containing
|
||||
``Stn'' or ``Ori''. This does not work for lines.
|
||||
|
||||
\subsubsection{Writing ARS Rules}
|
||||
|
||||
Every route of every signal can be given a set of ARS rules. A single
|
||||
ARS rule can either match a line or a routing code (combinations,
|
||||
e.g. and's, are not yet supported). The first rule in the first route
|
||||
that matches any of the properties of the train is selected, and that
|
||||
route is set for the train.
|
||||
|
||||
\includegraphics{13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.png}
|
||||
|
||||
You can add an asterisk (``{*}'') to the ARS rules of one route.
|
||||
That route then becomes the default route.
|
||||
|
||||
If no explicit ARS rule matches the train, then the default route
|
||||
is chosen and set. If there is no default route, nothing happens and
|
||||
the signal remains red.
|
||||
|
||||
\subsubsection{Using ARS}
|
||||
|
||||
In contrast to Automatic working, where the route is re-set immediately
|
||||
after the train passed, ARS sets the route only when the train approaches
|
||||
the signal, e.g. is just about to start braking in front of it.
|
||||
|
||||
At any place where one of the following things take place, you should
|
||||
use the ARS system in favor of Automatic Working:
|
||||
\begin{itemize}
|
||||
\item A main line diverts into 2 or more lines: Using ARS, you can direct
|
||||
the trains along the line where they should go
|
||||
\item Two or more main lines join into one: You cannot use automatic working
|
||||
here, because all routes are tried to be set at the same time and
|
||||
it is a matter of luck which one ``wins''. In a bad situation, you
|
||||
have a train coming from A, but it cannot proceed because Signal B
|
||||
has won the ``route race'' into the shared section, even if there's
|
||||
no train coming from B. Using ARS, by just specifying the ``default
|
||||
route'' by a {*}, the inward route is only set when a train approaches.
|
||||
\item Complex intersections, which are probably a combination of the above
|
||||
two
|
||||
\item sometimes-used branching tracks on which only certain trains (with
|
||||
certain routing code or line) should head off, like the entrance to
|
||||
a factory where only one specific goods train should drive in.
|
||||
\end{itemize}
|
||||
In the route overview, you can see some information on the ARS settings:
|
||||
All routes that have ARS rules are highlighted red, the ``default
|
||||
route'' is highlighted green.
|
||||
|
||||
ARS does not affect signals which already have a route set, and signals
|
||||
which are operating under ``Automatic Working''.
|
||||
|
||||
\section{Final notes}
|
||||
|
||||
The interlocking system is mainly finished, though there are still
|
||||
some plans and ideas. They include:
|
||||
\begin{itemize}
|
||||
\item Signalbox panels, as revival of itrainmap
|
||||
\item Individual signal aspects for routes
|
||||
\item Distant signals
|
||||
\item On-Train head-up display for oncoming signals (they have something
|
||||
like this in Czech Republic, I forgot how it's called.)
|
||||
|
|
|
|||
|
|
@ -5,19 +5,21 @@
|
|||
3448209989 1536659293 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecsx1000.600pk
|
||||
1128057700 1536659294 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecsx1200.600pk
|
||||
3518449051 1536659295 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecsx1728.600pk
|
||||
4257729402 1536952949 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecti1000.600pk
|
||||
771831286 1536952949 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ectt1000.600pk
|
||||
2083572688 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/0_home_moritz_Home_Projekte_Minetest_minetest_m___s_assets_lyx_img_screenshot_20180830_142551.png
|
||||
3163851185 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/1_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-26-35.png
|
||||
3946952010 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/2_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-32-48.png
|
||||
1282794055 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/3_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-27-25.png
|
||||
2081046434 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/4_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-28-32.png
|
||||
437805775 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/5_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-25.png
|
||||
1859874562 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png
|
||||
2936847921 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png
|
||||
4200189852 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png
|
||||
674084759 0 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png
|
||||
3607079205 1539633848 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/interlocking.tex
|
||||
2083572688 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/0_home_moritz_Home_Projekte_Minetest_minetest_m___s_assets_lyx_img_screenshot_20180830_142551.png
|
||||
1551666653 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.png
|
||||
2968881962 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.png
|
||||
953715842 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.png
|
||||
873631604 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.png
|
||||
3163851185 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/1_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-26-35.png
|
||||
3946952010 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/2_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-32-48.png
|
||||
1282794055 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/3_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-27-25.png
|
||||
2081046434 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/4_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-28-32.png
|
||||
437805775 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/5_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-25.png
|
||||
1859874562 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png
|
||||
2936847921 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png
|
||||
4200189852 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png
|
||||
674084759 0 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png
|
||||
2812755771 1547582062 /tmp/lyx_tmpdir.RZQWWIUz3517/lyx_tmpbuf0/interlocking.tex
|
||||
3180002928 1480098733 /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb
|
||||
2483225172 1480098806 /usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
|
||||
1629800494 1496785618 /usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
|
||||
|
|
@ -40,7 +42,6 @@
|
|||
3929707912 1480098821 /usr/share/texlive/texmf-dist/tex/latex/base/latin9.def
|
||||
3238294924 1480098821 /usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
|
||||
380232544 1480098821 /usr/share/texlive/texmf-dist/tex/latex/base/t1cmss.fd
|
||||
3252814856 1480098821 /usr/share/texlive/texmf-dist/tex/latex/base/t1cmtt.fd
|
||||
3164737843 1492297155 /usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
|
||||
2603123796 1480098829 /usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
|
||||
1212982396 1480098830 /usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg
|
||||
|
|
|
|||
|
|
@ -34,28 +34,40 @@
|
|||
\:CrossWord{)QQ1-1-0}{1}{7}%
|
||||
\:CrossWord{)Qx1-33r2}{1}{7}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{7}%
|
||||
\:CrossWord{)Qx1-34r3}{1}{7}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{7}%
|
||||
\:CrossWord{)Qx1-34r3}{1}{8}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{8}%
|
||||
\:CrossWord{)Qx1-35r4}{1}{8}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{8}%
|
||||
\:CrossWord{)Qx1-37x1}{1}{8}%
|
||||
\:CrossWord{)Qx1-39x2}{1}{8}%
|
||||
\:CrossWord{)Qx1-41x3}{1}{8}%
|
||||
\:CrossWord{)Qx1-43x4}{1}{8}%
|
||||
\:CrossWord{)Qx1-45x5}{1}{8}%
|
||||
\:CrossWord{)Qx1-46r5}{1}{9}%
|
||||
\:CrossWord{)Qx1-36r5}{1}{9}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{9}%
|
||||
\:CrossWord{)Qx1-38x1}{1}{9}%
|
||||
\:CrossWord{)Qx1-40x2}{1}{9}%
|
||||
\:CrossWord{)Qx1-42x3}{1}{9}%
|
||||
\:CrossWord{)Qx1-44x4}{1}{9}%
|
||||
\:CrossWord{)Qx1-46x5}{1}{9}%
|
||||
\:CrossWord{)Qx1-47r6}{1}{9}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{9}%
|
||||
\:CrossWord{)Qx1-48r7}{1}{9}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{9}%
|
||||
\:CrossWord{)Qx1-49r4}{1}{10}%
|
||||
\:CrossWord{)Qx1-48r7}{1}{10}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{10}%
|
||||
\:CrossWord{)Qx1-50r1}{1}{11}%
|
||||
\:CrossWord{)Qx1-49r8}{1}{10}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{10}%
|
||||
\:CrossWord{)Qx1-50r9}{1}{11}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{11}%
|
||||
\:CrossWord{)Qx1-51r2}{1}{11}%
|
||||
\:CrossWord{)Qx1-51r10}{1}{11}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{11}%
|
||||
\:CrossWord{)Qx1-52r3}{1}{11}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{11}%
|
||||
\:CrossWord{)Qx1-53r5}{1}{11}%
|
||||
\:CrossWord{)Qx1-52r4}{1}{12}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{12}%
|
||||
\:CrossWord{)Qx1-53r1}{1}{12}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{12}%
|
||||
\:CrossWord{)Qx1-54r2}{1}{12}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{12}%
|
||||
\:CrossWord{)Qx1-55r3}{1}{13}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{13}%
|
||||
\:CrossWord{)Qx1-56r4}{1}{13}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{13}%
|
||||
\:CrossWord{)Qx1-57r1}{1}{13}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{13}%
|
||||
\:CrossWord{)Qx1-58r2}{1}{14}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{14}%
|
||||
\:CrossWord{)Qx1-59r5}{1}{14}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{14}%
|
||||
|
|
|
|||
|
|
@ -615,8 +615,14 @@ Interlocking patterns
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This section is supposed to show some examples on how you should set up
|
||||
track sections on certain track configurations.
|
||||
Have a look at the following images.
|
||||
They show you how you can set up sections so that reasonable train moves
|
||||
are possible.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
You should settle on a naming scheme for your sections.
|
||||
This way, you can determine the source of an issue faster
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
|
|
@ -641,7 +647,7 @@ Static signals always display the same information to the train.
|
|||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Variable signals are what most people would call a
|
||||
Dynamic signals are what most people would call a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
|
|
@ -738,7 +744,7 @@ The advtrains-internal train safety system ensures that the train always
|
|||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Main and Shunt signals
|
||||
Signal Aspects
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
|
@ -749,6 +755,51 @@ While static signals are mainly used for speed restrictions, the interesting
|
|||
the point of this interlocking system.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
A signal aspect is a piece of information that a signal shows to the train
|
||||
driver.
|
||||
It contains information about whether and at what speed the driver may
|
||||
proceed at the signal.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every signal, both static and dynamic ones, imposes a certain aspect to
|
||||
trains passing the signal.
|
||||
For static signals, this is always the same aspect, such as
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed at speed of 8
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
or
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Shunt moves may not pass
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
Dynamic signals, however, can display multiple different aspects.
|
||||
The default for them is always as restrictive as possible, mostly
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Halt!
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
You should know that both static and dynamic signals use exactly the same
|
||||
properties for signal aspects.
|
||||
There is no difference in the meaning of the aspect definitions.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
In the following sections, we will talk about main signals.
|
||||
By this, we mean a variable signal that can display both a
|
||||
|
|
@ -779,6 +830,88 @@ entry signal
|
|||
for one or multiple routes.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Train moves and Shunt Moves
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Train move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is a train that is running, going to run on or coming from a main line
|
||||
between stations, passing through or stopping at a station.
|
||||
Train moves can expect that there are no obstacles on the route and they
|
||||
can proceed at the maximum permitted speed of the line.
|
||||
This is the regular operation mode for trains.
|
||||
Shunt signals have no meaning for train moves.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Shunt move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is a train that moves within a station and/or is coupling or decoupling
|
||||
wagons or engines.
|
||||
A shunt move may never leave a station except into a siding.
|
||||
Also, shunt moves may drive at a maximum speed of 6 speed units, because
|
||||
it is usually not ensured that the path is free of obstacles.
|
||||
(however, advtrains ensures that every route is free of railway vehicles,
|
||||
even shunt routes)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
There are also 2 general types of signals: Main signals and Shunt signals.
|
||||
While main signals have a meaning for all types of trains, Shunt signals
|
||||
only have to be followed by shunt moves.
|
||||
Usually, Shunt signals that are on a train move route are set to a Proceed
|
||||
aspect as well.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
When a train reverses, its mode automatically changes to
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
shunt move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
until it passes a main signal that shows
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed as train move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
, which is usually designated by a green light.
|
||||
From this point on, it can accelerate to maximum permitted speed.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Some main signals, like the ones from the Ks signals mod included by default,
|
||||
can also display
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed as shunt move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
, which is designated by 2 white lights along with the red light.
|
||||
Once a train passes this signal, it becomes a shunt move.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
The concept of routes
|
||||
\end_layout
|
||||
|
|
@ -1019,23 +1152,7 @@ The solution is to program a second route into the siding, but with the
|
|||
\begin_layout Standard
|
||||
The Sht2 route then needs to show a shunt aspect, which instructs the driver
|
||||
to proceed slowly and watch out for vehicles on the route.
|
||||
To show a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
free
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
aspect here would be wrong, because that would mean that the track is free
|
||||
until the next main signal, which it is clearly not.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
||||
\shape italic
|
||||
Note that advtrains_interlocking currently does not allow to set individual
|
||||
aspects for routes, this is a feature still to be implemented soon.
|
||||
See later on for how to set this up.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
|
@ -1221,19 +1338,6 @@ Advance
|
|||
A few hints:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
If one turnout should be locked by more than one section, set the lock only
|
||||
in the
|
||||
\family typewriter
|
||||
\series bold
|
||||
last
|
||||
\family default
|
||||
\series default
|
||||
of those sections.
|
||||
Locking the same turnout in multiple sections of a single route results
|
||||
in undefined behavior!
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
If you accidentally advanced the route wrongly, you can use the
|
||||
\begin_inset Quotes eld
|
||||
|
|
@ -1282,6 +1386,196 @@ The third button does NOT work on sections with more than 2 exits, because
|
|||
the system won't be able to determine the final TCB of the route then.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Route information screen
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/Bildschirmfoto_2019-01-15_19-28-09.png
|
||||
width 10cm
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This is the screen that appears when you click
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Edit Route
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
It lets you change the route name and delete the route.
|
||||
Also, it shows a summary of the route and its elements.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The route summary lists information per track section on the route, so the
|
||||
line starting with
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
1
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is the first section of the route.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The ARS rule list and its purpose is explained later.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Specifying signal aspects
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
By default, newly programmed routes show an aspect that comes closest to
|
||||
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed at maximum speed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
However, it can be desirable to change this behavior, like when the route
|
||||
passes a diverging turnout, the train should be signalled to drive slower,
|
||||
or the route is a shunt route and therefore only
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Shunting allowed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
should be shown.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This is the purpose of the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Change Aspect
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
button in the route info screen.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Signal aspects in advtrains consist of 4 sections: main (Information for
|
||||
train moves), dst (Distant signal information, not implemented yet), shunt
|
||||
(Information for shunt moves) and info (additional information, currently
|
||||
not in use).
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Train may proceed as train move at maximum speed:
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
main: free, speed -1
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Train may proceed as train move at speed of 8:
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
main: free, speed 8
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Train may proceed as shunt move:
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
shunt: free
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
There's a field in the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
shunt
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
part of signal aspects that is not displayed in the GUI, but is of potential
|
||||
interest to developers of signal addons: shunt.proceed_as_main.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A train move can always become a shunt move by passing a signal that shows
|
||||
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Halt for train moves, shunting permitted
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A shunt move can only pass a signal saying
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed as train move, shunting not permitted
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
when proceed_as_main is true.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The property is used by the Limit Of Shunt sign, where proceed_as_main is
|
||||
set to false.
|
||||
Shunt moves have to stop in front of it, while train moves are signalled
|
||||
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
Regular main signals that show
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
green
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
have the field set to true, so that all trains can pass it.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Interlocking system operation
|
||||
\end_layout
|
||||
|
|
@ -1353,11 +1647,6 @@ BB
|
|||
of the section.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
As of now, changing the driving direction of a train always clears any imposed
|
||||
speed restrictions.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Simple route setting and cancelling
|
||||
\end_layout
|
||||
|
|
@ -1429,6 +1718,270 @@ d access to a siding.
|
|||
you need a train to go into the siding.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Automatic Route Setting (ARS)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
As interlocking systems evolved, the goal always was to offload work from
|
||||
the human to the system, automating things.
|
||||
Modern interlocking systems can automatically set routes based on a pre-program
|
||||
med routing table for each particular train.
|
||||
Since one outstanding feature of Advtrains is it's high degree of automation,
|
||||
it has a similar system to automatically set routes for a train depending
|
||||
on certain parameters.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every train in Advtrains has 2 internal properties that can be set through
|
||||
the Onboard Computer of every engine in the train, the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Line
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
and the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Routing Code
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
The
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Line
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
property is supposed to distinguish trains of multiple lines that share
|
||||
a track.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
The
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Routing Code
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
property is supposed to tell the target of a train or which route it should
|
||||
take to reach the target
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Examples:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/arslin_ex1.png
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Both lines share the section between Blackbirdshire and Parktown.
|
||||
To divert them again, they can save their line number in the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Line
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
field.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/arslin_ex2.png
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Some trains should go to B, some to C, the direction can be set with a routing
|
||||
code.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
One single routing code should not contain spaces.
|
||||
You can set multiple routing codes by just separating them with spaces
|
||||
in the Routing Code field.
|
||||
So,
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Stn Ori
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
would be matched by ARS rules either containing
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Stn
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
or
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Ori
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
This does not work for lines.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsubsection
|
||||
Writing ARS Rules
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every route of every signal can be given a set of ARS rules.
|
||||
A single ARS rule can either match a line or a routing code (combinations,
|
||||
e.g.
|
||||
and's, are not yet supported).
|
||||
The first rule in the first route that matches any of the properties of
|
||||
the train is selected, and that route is set for the train.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/ars_ex1.png
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
You can add an asterisk (
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
*
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
) to the ARS rules of one route.
|
||||
That route then becomes the default route.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
If no explicit ARS rule matches the train, then the default route is chosen
|
||||
and set.
|
||||
If there is no default route, nothing happens and the signal remains red.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsubsection
|
||||
Using ARS
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
In contrast to Automatic working, where the route is re-set immediately
|
||||
after the train passed, ARS sets the route only when the train approaches
|
||||
the signal, e.g.
|
||||
is just about to start braking in front of it.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
At any place where one of the following things take place, you should use
|
||||
the ARS system in favor of Automatic Working:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A main line diverts into 2 or more lines: Using ARS, you can direct the
|
||||
trains along the line where they should go
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Two or more main lines join into one: You cannot use automatic working here,
|
||||
because all routes are tried to be set at the same time and it is a matter
|
||||
of luck which one
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
wins
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
In a bad situation, you have a train coming from A, but it cannot proceed
|
||||
because Signal B has won the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
route race
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
into the shared section, even if there's no train coming from B.
|
||||
Using ARS, by just specifying the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
default route
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
by a *, the inward route is only set when a train approaches.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Complex intersections, which are probably a combination of the above two
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
sometimes-used branching tracks on which only certain trains (with certain
|
||||
routing code or line) should head off, like the entrance to a factory where
|
||||
only one specific goods train should drive in.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
In the route overview, you can see some information on the ARS settings:
|
||||
All routes that have ARS rules are highlighted red, the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
default route
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is highlighted green.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
ARS does not affect signals which already have a route set, and signals
|
||||
which are operating under
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Automatic Working
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Final notes
|
||||
\end_layout
|
||||
|
|
@ -1443,10 +1996,6 @@ The interlocking system is mainly finished, though there are still some
|
|||
Signalbox panels, as revival of itrainmap
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Individual signal aspects for routes
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Distant signals
|
||||
\end_layout
|
||||
|
|
|
|||
|
|
@ -615,8 +615,14 @@ Interlocking patterns
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This section is supposed to show some examples on how you should set up
|
||||
track sections on certain track configurations.
|
||||
Have a look at the following images.
|
||||
They show you how you can set up sections so that reasonable train moves
|
||||
are possible.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
You should settle on a naming scheme for your sections.
|
||||
This way, you can determine the source of an issue faster
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
|
|
@ -641,7 +647,7 @@ Static signals always display the same information to the train.
|
|||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Variable signals are what most people would call a
|
||||
Dynamic signals are what most people would call a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
|
|
@ -692,7 +698,7 @@ Static signals and all red-green light signals from core advtrains that
|
|||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Sneak
|
||||
Use
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
|
@ -738,7 +744,7 @@ The advtrains-internal train safety system ensures that the train always
|
|||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Main and Shunt signals
|
||||
Signal Aspects
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
|
@ -749,6 +755,51 @@ While static signals are mainly used for speed restrictions, the interesting
|
|||
the point of this interlocking system.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
A signal aspect is a piece of information that a signal shows to the train
|
||||
driver.
|
||||
It contains information about whether and at what speed the driver may
|
||||
proceed at the signal.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every signal, both static and dynamic ones, imposes a certain aspect to
|
||||
trains passing the signal.
|
||||
For static signals, this is always the same aspect, such as
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed at speed of 8
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
or
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Shunt moves may not pass
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
Dynamic signals, however, can display multiple different aspects.
|
||||
The default for them is always as restrictive as possible, mostly
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Halt!
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
You should know that both static and dynamic signals use exactly the same
|
||||
properties for signal aspects.
|
||||
There is no difference in the meaning of the aspect definitions.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
In the following sections, we will talk about main signals.
|
||||
By this, we mean a variable signal that can display both a
|
||||
|
|
@ -779,6 +830,88 @@ entry signal
|
|||
for one or multiple routes.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Train moves and Shunt Moves
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Train move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is a train that is running, going to run on or coming from a main line
|
||||
between stations, passing through or stopping at a station.
|
||||
Train moves can expect that there are no obstacles on the route and they
|
||||
can proceed at the maximum permitted speed of the line.
|
||||
This is the regular operation mode for trains.
|
||||
Shunt signals have no meaning for train moves.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Shunt move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is a train that moves within a station and/or is coupling or decoupling
|
||||
wagons or engines.
|
||||
A shunt move may never leave a station except into a siding.
|
||||
Also, shunt moves may drive at a maximum speed of 6 speed units, because
|
||||
it is usually not ensured that the path is free of obstacles.
|
||||
(however, advtrains ensures that every route is free of railway vehicles,
|
||||
even shunt routes)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
There are also 2 general types of signals: Main signals and Shunt signals.
|
||||
While main signals have a meaning for all types of trains, Shunt signals
|
||||
only have to be followed by shunt moves.
|
||||
Usually, Shunt signals that are on a train move route are set to a Proceed
|
||||
aspect as well.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
When a train reverses, its mode automatically changes to
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
shunt move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
until it passes a main signal that shows
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed as train move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
, which is usually designated by a green light.
|
||||
From this point on, it can accelerate to maximum permitted speed.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Some main signals, like the ones from the Ks signals mod included by default,
|
||||
can also display
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed as shunt move
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
, which is designated by 2 white lights along with the red light.
|
||||
Once a train passes this signal, it becomes a shunt move.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
The concept of routes
|
||||
\end_layout
|
||||
|
|
@ -1019,23 +1152,7 @@ The solution is to program a second route into the siding, but with the
|
|||
\begin_layout Standard
|
||||
The Sht2 route then needs to show a shunt aspect, which instructs the driver
|
||||
to proceed slowly and watch out for vehicles on the route.
|
||||
To show a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
free
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
aspect here would be wrong, because that would mean that the track is free
|
||||
until the next main signal, which it is clearly not.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
||||
\shape italic
|
||||
Note that advtrains_interlocking currently does not allow to set individual
|
||||
aspects for routes, this is a feature still to be implemented soon.
|
||||
See later on for how to set this up.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
|
@ -1221,19 +1338,6 @@ Advance
|
|||
A few hints:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
If one turnout should be locked by more than one section, set the lock only
|
||||
in the
|
||||
\family typewriter
|
||||
\series bold
|
||||
last
|
||||
\family default
|
||||
\series default
|
||||
of those sections.
|
||||
Locking the same turnout in multiple sections of a single route results
|
||||
in undefined behavior!
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
If you accidentally advanced the route wrongly, you can use the
|
||||
\begin_inset Quotes eld
|
||||
|
|
@ -1282,6 +1386,196 @@ The third button does NOT work on sections with more than 2 exits, because
|
|||
the system won't be able to determine the final TCB of the route then.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Route information screen
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/Bildschirmfoto_2019-01-15_19-28-09.png
|
||||
width 10cm
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This is the screen that appears when you click
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Edit Route
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
It lets you change the route name and delete the route.
|
||||
Also, it shows a summary of the route and its elements.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The route summary lists information per track section on the route, so the
|
||||
line starting with
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
1
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is the first section of the route.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The ARS rule list and its purpose is explained later.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Specifying signal aspects
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
By default, newly programmed routes show an aspect that comes closest to
|
||||
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed at maximum speed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
However, it can be desirable to change this behavior, like when the route
|
||||
passes a diverging turnout, the train should be signalled to drive slower,
|
||||
or the route is a shunt route and therefore only
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Shunting allowed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
should be shown.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This is the purpose of the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Change Aspect
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
button in the route info screen.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Signal aspects in advtrains consist of 4 sections: main (Information for
|
||||
train moves), dst (Distant signal information, not implemented yet), shunt
|
||||
(Information for shunt moves) and info (additional information, currently
|
||||
not in use).
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Train may proceed as train move at maximum speed:
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
main: free, speed -1
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Train may proceed as train move at speed of 8:
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
main: free, speed 8
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Train may proceed as shunt move:
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
shunt: free
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
There's a field in the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
shunt
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
part of signal aspects that is not displayed in the GUI, but is of potential
|
||||
interest to developers of signal addons: shunt.proceed_as_main.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A train move can always become a shunt move by passing a signal that shows
|
||||
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Halt for train moves, shunting permitted
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A shunt move can only pass a signal saying
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed as train move, shunting not permitted
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
when proceed_as_main is true.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The property is used by the Limit Of Shunt sign, where proceed_as_main is
|
||||
set to false.
|
||||
Shunt moves have to stop in front of it, while train moves are signalled
|
||||
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
Regular main signals that show
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
green
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
have the field set to true, so that all trains can pass it.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Interlocking system operation
|
||||
\end_layout
|
||||
|
|
@ -1353,11 +1647,6 @@ BB
|
|||
of the section.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
As of now, changing the driving direction of a train always clears any imposed
|
||||
speed restrictions.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Simple route setting and cancelling
|
||||
\end_layout
|
||||
|
|
@ -1429,6 +1718,261 @@ d access to a siding.
|
|||
you need a train to go into the siding.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Automatic Route Setting (ARS)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
As interlocking systems evolved, the goal always was to offload work from
|
||||
the human to the system, automating things.
|
||||
Modern interlocking systems can automatically set routes based on a pre-program
|
||||
med routing table for each particular train.
|
||||
Since one outstanding feature of Advtrains is it's high degree of automation,
|
||||
it has a similar system to automatically set routes for a train depending
|
||||
on certain parameters.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every train in Advtrains has 2 internal properties that can be set through
|
||||
the Onboard Computer of every engine in the train, the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Line
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
and the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Routing Code
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
The
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Line
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
property is supposed to distinguish trains of multiple lines that share
|
||||
a track.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
The
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Routing Code
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
property is supposed to tell the target of a train or which route it should
|
||||
take to reach the target
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Examples:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/arslin_ex1.png
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Both lines share the section between Blackbirdshire and Parktown.
|
||||
To divert them again, they can save their line number in the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Line
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
field.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/arslin_ex2.png
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Some trains should go to B, some to C, the direction can be set with a routing
|
||||
code.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
One single routing code should not contain spaces.
|
||||
You can set multiple routing codes by just separating them with spaces
|
||||
in the Routing Code field.
|
||||
So,
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Stn Ori
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
would be matched by ARS rules either containing
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Stn
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
or
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Ori
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
This does not work for lines.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsubsection
|
||||
Writing ARS Rules
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Every route of every signal can be given a set of ARS rules.
|
||||
A single ARS rule can either match a line or a routing code (combinations,
|
||||
e.g.
|
||||
and's, are not yet supported).
|
||||
The first rule in the first route that matches any of the properties of
|
||||
the train is selected, and that route is set for the train.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
You can add an asterisk (
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
*
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
) to the ARS rules of one route.
|
||||
That route then becomes the default route.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
If no explicit ARS rule matches the train, then the default route is chosen
|
||||
and set.
|
||||
If there is no default route, nothing happens and the signal remains red.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsubsection
|
||||
Using ARS
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
In contrast to Automatic working, where the route is re-set immediately
|
||||
after the train passed, ARS sets the route only when the train approaches
|
||||
the signal, e.g.
|
||||
is just about to start braking in front of it.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
At any place where one of the following things take place, you should use
|
||||
the ARS system in favor of Automatic Working:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
A main line diverts into 2 or more lines: Using ARS, you can direct the
|
||||
trains along the line where they should go
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Two or more main lines join into one: You cannot use automatic working here,
|
||||
because all routes are tried to be set at the same time and it is a matter
|
||||
of luck which one
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
wins
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
In a bad situation, you have a train coming from A, but it cannot proceed
|
||||
because Signal B has won the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
route race
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
into the shared section, even if there's no train coming from B.
|
||||
Using ARS, by just specifying the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
default route
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
by a *, the inward route is only set when a train approaches.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Complex intersections, which are probably a combination of the above two
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
sometimes-used branching tracks on which only certain trains (with certain
|
||||
routing code or line) should head off, like the entrance to a factory where
|
||||
only one specific goods train should drive in.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
In the route overview, you can see some information on the ARS settings:
|
||||
All routes that have ARS rules are highlighted red, the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
default route
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
is highlighted green.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
ARS does not affect signals which already have a route set, and signals
|
||||
which are operating under
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Automatic Working
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Final notes
|
||||
\end_layout
|
||||
|
|
@ -1443,10 +1987,6 @@ The interlocking system is mainly finished, though there are still some
|
|||
Signalbox panels, as revival of itrainmap
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Individual signal aspects for routes
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Distant signals
|
||||
\end_layout
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 132 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.2 KiB |
Loading…
Reference in New Issue