Update manual again
orwell96
parent
11fe530e18
commit
85d752df6b
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Binary file not shown.
|
After Width: | Height: | Size: 9.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.5 KiB |
File diff suppressed because it is too large
Load Diff
|
Before Width: | Height: | Size: 9.2 KiB After Width: | Height: | Size: 9.2 KiB |
File diff suppressed because it is too large
Load Diff
|
Before Width: | Height: | Size: 115 KiB After Width: | Height: | Size: 115 KiB |
File diff suppressed because it is too large
Load Diff
|
|
@ -0,0 +1,24 @@
|
|||
\expandafter\ifx\csname doTocEntry\endcsname\relax \expandafter\endinput\fi
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {1}Introduction}}{3}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2}Setting up track sections}}{3}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.1}Track Circuit Breaks}}{4}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2}Long track sections, crossings and other edge cases}}{5}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.1}Very long track sections}}{5}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.2}Rail crosses}}{5}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.3}Deleting and re-adding single TCBs to a section}}{6}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.4}Dissolving sections}}{6}\relax
|
||||
\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
|
||||
\par
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
\expandafter\ifx\csname doTocEntry\endcsname\relax \expandafter\endinput\fi
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {1}Introduction}}{3}\relax
|
||||
\doTocEntry\tocsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2}Setting up track sections}}{3}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.1}Track Circuit Breaks}}{4}\relax
|
||||
\doTocEntry\tocsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2}Long track sections, crossings and other edge cases}}{5}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.1}Very long track sections}}{5}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.2}Rail crosses}}{5}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.3}Deleting and re-adding single TCBs to a section}}{6}\relax
|
||||
\doTocEntry\tocsubsubsection{}{\csname a:TocLink\endcsname{1}{Q1-1-0}{}{\numberline {2.2.4}Dissolving sections}}{6}\relax
|
||||
\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
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
\relax
|
||||
\ifx\rEfLiNK\UnDef\gdef \rEfLiNK#1#2{#2}\fi
|
||||
\babel@aux{english}{}
|
||||
\newlabel{subsec:Long-track-sections,}{{\rEfLiNK{x1-17r2}{2.2}}{\rEfLiNK{x1-17r2}{5}}}
|
||||
Binary file not shown.
|
|
@ -277,7 +277,7 @@ class="ecsx-1200">Interlocking</span>
|
|||
class="ecsx-1200">patterns</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 213--><p class="noindent" >This section shows some examples on how you should set up track sections on certain track configurations.
|
||||
<!--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" >
|
||||
<a
|
||||
id="x1-31r3"></a>
|
||||
|
|
@ -290,51 +290,71 @@ class="ecsx-1200">and</span>
|
|||
class="ecsx-1200">routes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 218--><p class="noindent" >The purpose of signals is to inform trains about whether they can proceed into the next section safely. Making a section of track safe to
|
||||
pass for a train, turnouts need to be set to the correct position and no other train should be allowed to cross or share parts of the route
|
||||
with this train.
|
||||
<!--l. 224--><p class="noindent" >
|
||||
<!--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
|
||||
information.
|
||||
<!--l. 221--><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
|
||||
speed they can proceed into the next section safely.</li></ul>
|
||||
<!--l. 231--><p class="noindent" >
|
||||
<a
|
||||
id="x1-32r1"></a>
|
||||
<!--l. 224--><p class="noindent" ><span
|
||||
<!--l. 231--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.1</span> <span
|
||||
class="ecsx-1200">Assigning</span>
|
||||
class="ecsx-1200">Signal</span>
|
||||
<span
|
||||
class="ecsx-1200">Signals</span>
|
||||
class="ecsx-1200">Influence</span>
|
||||
<span
|
||||
class="ecsx-1200">to</span>
|
||||
<span
|
||||
class="ecsx-1200">TCBs</span>
|
||||
class="ecsx-1200">Point</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 226--><p class="noindent" >Signals in the advtrains interlocking system are positioned - like in real life - at the border of track sections.
|
||||
<!--l. 229--><p class="noindent" >When you set up a signal, do the following steps:
|
||||
<ol class="enumerate1" >
|
||||
<li
|
||||
class="enumerate" id="x1-34x1">If not already happened, set up a TCB (you don’t need to, but are advised to, configure track sections there)
|
||||
<!--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
|
||||
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,
|
||||
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
|
||||
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
|
||||
holding the “Sneak” key and then right-clicking the signal
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-36x2">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-38x3">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-40x4">Right-click the TCB, and click “Assign a signal” on this side.
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-42x5">Punch the signal.</li></ol>
|
||||
<!--l. 240--><p class="noindent" ><img
|
||||
src="6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png" alt="PIC"
|
||||
>
|
||||
<!--l. 242--><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. 246--><p class="noindent" >
|
||||
<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”
|
||||
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
|
||||
influence point is set properly.
|
||||
<!--l. 267--><p class="noindent" >
|
||||
<a
|
||||
id="x1-43r2"></a>
|
||||
<!--l. 246--><p class="noindent" ><span
|
||||
id="x1-33r2"></a>
|
||||
<!--l. 267--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.2</span> <span
|
||||
class="ecsx-1200">Main</span>
|
||||
<span
|
||||
class="ecsx-1200">and</span>
|
||||
<span
|
||||
class="ecsx-1200">Shunt</span>
|
||||
<span
|
||||
class="ecsx-1200">signals</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" >
|
||||
<a
|
||||
id="x1-34r3"></a>
|
||||
<!--l. 281--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.3</span> <span
|
||||
class="ecsx-1200">The</span>
|
||||
<span
|
||||
class="ecsx-1200">concept</span>
|
||||
|
|
@ -344,87 +364,139 @@ class="ecsx-1200">of</span>
|
|||
class="ecsx-1200">routes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 248--><p class="noindent" >A so-called route is a locked path between two signals, which locks all turnouts in the correct position.
|
||||
<!--l. 251--><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. 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
|
||||
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
|
||||
from the right to go into platform 1 or into platform 2, so you need to program 2 routes.
|
||||
<!--l. 256--><p class="noindent" ><img
|
||||
src="7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png" alt="PIC"
|
||||
<!--l. 295--><p class="noindent" ><img
|
||||
src="6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png" alt="PIC"
|
||||
>
|
||||
<!--l. 258--><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. 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
|
||||
<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. 263--><p class="noindent" >When you set a route to make a train proceed on it, the interlocking system ensures that:
|
||||
<!--l. 302--><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. 272--><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. 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
|
||||
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. 278--><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. 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
|
||||
turnouts to a position that points “away” from the route. Example:
|
||||
<!--l. 282--><p class="noindent" ><img
|
||||
src="8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png" alt="PIC"
|
||||
<!--l. 321--><p class="noindent" ><img
|
||||
src="7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png" alt="PIC"
|
||||
>
|
||||
<!--l. 284--><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. 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
|
||||
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. 291--><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. 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
|
||||
you can do and no flank lock needs to be set.
|
||||
<!--l. 295--><p class="noindent" >
|
||||
<!--l. 334--><p class="noindent" >
|
||||
<a
|
||||
id="x1-44r3"></a>
|
||||
<!--l. 295--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.3</span> <span
|
||||
id="x1-35r4"></a>
|
||||
<!--l. 334--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.4</span> <span
|
||||
class="ecsx-1200">Assigning</span>
|
||||
<span
|
||||
class="ecsx-1200">main</span>
|
||||
<span
|
||||
class="ecsx-1200">signals</span>
|
||||
<span
|
||||
class="ecsx-1200">to</span>
|
||||
<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
|
||||
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:
|
||||
<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)
|
||||
</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
|
||||
</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
|
||||
below.
|
||||
</li>
|
||||
<li
|
||||
class="enumerate" id="x1-43x4">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
|
||||
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
|
||||
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
|
||||
all.
|
||||
<!--l. 365--><p class="noindent" >
|
||||
<a
|
||||
id="x1-46r5"></a>
|
||||
<!--l. 365--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.5</span> <span
|
||||
class="ecsx-1200">Shunt</span>
|
||||
<span
|
||||
class="ecsx-1200">routes</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 297--><p class="noindent" >Operating railways is not all about driving trains around. Coupling, decoupling and moving single engines, wagons or groups of wagons
|
||||
<!--l. 368--><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
|
||||
across a station, called shunting, also plays an important role.
|
||||
<!--l. 301--><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. 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
|
||||
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. 306--><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. 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
|
||||
doesn’t include the siding section itself:
|
||||
<!--l. 310--><p class="noindent" ><img
|
||||
<!--l. 383--><p class="noindent" ><img
|
||||
src="9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png" alt="PIC"
|
||||
>
|
||||
<!--l. 312--><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.
|
||||
<!--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. 320--><p class="noindent" ><span
|
||||
<!--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. 322--><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. 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”
|
||||
rule.
|
||||
<!--l. 325--><p class="noindent" >
|
||||
<!--l. 398--><p class="noindent" >
|
||||
<a
|
||||
id="x1-45r4"></a>
|
||||
<!--l. 325--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.4</span> <span
|
||||
id="x1-47r6"></a>
|
||||
<!--l. 398--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.6</span> <span
|
||||
class="ecsx-1200">Route</span>
|
||||
<span
|
||||
class="ecsx-1200">Release</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 327--><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. 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
|
||||
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. 334--><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. 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
|
||||
path. Once the train leaves this section, all assigned locks are also freed.
|
||||
<!--l. 338--><p class="noindent" >
|
||||
<!--l. 411--><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" >
|
||||
<a
|
||||
id="x1-46r5"></a>
|
||||
<!--l. 338--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.5</span> <span
|
||||
id="x1-48r7"></a>
|
||||
<!--l. 418--><p class="noindent" ><span
|
||||
class="ecsx-1200">3.7</span> <span
|
||||
class="ecsx-1200">Programming</span>
|
||||
<span
|
||||
class="ecsx-1200">a</span>
|
||||
|
|
@ -432,13 +504,13 @@ class="ecsx-1200">a</span>
|
|||
class="ecsx-1200">route</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 340--><p class="noindent" >The route programming procedure is quite straightforward if you’ve read the previous sections and understood how routes should be
|
||||
<!--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
|
||||
set.
|
||||
<!--l. 343--><p class="noindent" >Routes always start at a signal. You must have assigned the signal to a TCB, as described earlier.
|
||||
<!--l. 346--><p class="noindent" >When you right-click the 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
|
||||
<!--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
|
||||
with the possibility to set them or to create new routes. Click the “Create new route” button to start programming a new
|
||||
route.
|
||||
<!--l. 351--><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. 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
|
||||
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.
|
||||
|
|
@ -449,11 +521,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. 364--><p class="noindent" >Depending on the situation, you are now offered some possibilities to proceed:
|
||||
<!--l. 444--><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. 371--><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. 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
|
||||
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
|
||||
|
|
@ -462,7 +534,7 @@ 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. 387--><p class="noindent" >A few hints:
|
||||
<!--l. 467--><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
|
||||
|
|
@ -480,10 +552,10 @@ 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. 408--><p class="noindent" >
|
||||
<!--l. 488--><p class="noindent" >
|
||||
<a
|
||||
id="x1-47r4"></a>
|
||||
<!--l. 408--><p class="noindent" ><span
|
||||
id="x1-49r4"></a>
|
||||
<!--l. 488--><p class="noindent" ><span
|
||||
class="ecsx-1200">4</span> <span
|
||||
class="ecsx-1200">Interlocking</span>
|
||||
<span
|
||||
|
|
@ -492,16 +564,37 @@ class="ecsx-1200">system</span>
|
|||
class="ecsx-1200">operation</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 410--><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. 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
|
||||
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. 415--><p class="noindent" >At the moment, routes can only be set by clicking the signal or via LuaATC, except if you use automatic working. It is planned to control
|
||||
this via the onboard computer and via a “signal box” view based on the currently broken itrainmap.
|
||||
<!--l. 420--><p class="noindent" >
|
||||
<!--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”
|
||||
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" >
|
||||
<a
|
||||
id="x1-48r1"></a>
|
||||
<!--l. 420--><p class="noindent" ><span
|
||||
id="x1-50r1"></a>
|
||||
<!--l. 500--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.1</span> <span
|
||||
class="ecsx-1200">Train</span>
|
||||
<span
|
||||
class="ecsx-1200">Safety</span>
|
||||
<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
|
||||
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
|
||||
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" >
|
||||
<a
|
||||
id="x1-51r2"></a>
|
||||
<!--l. 519--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.2</span> <span
|
||||
class="ecsx-1200">Simple</span>
|
||||
<span
|
||||
class="ecsx-1200">route</span>
|
||||
|
|
@ -513,47 +606,45 @@ class="ecsx-1200">and</span>
|
|||
class="ecsx-1200">cancelling</span>
|
||||
<a
|
||||
id="Q1-1-0"></a>
|
||||
<!--l. 422--><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. 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
|
||||
train is allowed to proceed.
|
||||
<!--l. 426--><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. 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
|
||||
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. 433--><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. 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
|
||||
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. 439--><p class="noindent" >
|
||||
<!--l. 538--><p class="noindent" >
|
||||
<a
|
||||
id="x1-49r2"></a>
|
||||
<!--l. 439--><p class="noindent" ><span
|
||||
class="ecsx-1200">4.2</span> <span
|
||||
id="x1-52r3"></a>
|
||||
<!--l. 538--><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. 441--><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. 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
|
||||
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. 447--><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. 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
|
||||
automatically re-set.
|
||||
<!--l. 451--><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. 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
|
||||
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. 456--><p class="noindent" >
|
||||
<!--l. 555--><p class="noindent" >
|
||||
<a
|
||||
id="x1-50r5"></a>
|
||||
<!--l. 456--><p class="noindent" ><span
|
||||
id="x1-53r5"></a>
|
||||
<!--l. 555--><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. 458--><p class="noindent" >The interlocking system is mainly finished, though there are still some plans and ideas. They include:
|
||||
<!--l. 557--><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">Setting routes from inside a train (via onboard computer)
|
||||
</li>
|
||||
<li class="itemize">Signalbox panels, as revival of itrainmap
|
||||
</li>
|
||||
<li class="itemize">Individual signal aspects for routes
|
||||
|
|
@ -561,11 +652,11 @@ class="ecsx-1200">notes</span>
|
|||
<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. 468--><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. 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
|
||||
evolve and is out of the scope of this document.
|
||||
<!--l. 472--><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. 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
|
||||
(Forum PM, E-Mail (orwell@bleipb.de), Linuxworks server chat a.s.o.). Have fun!
|
||||
<!--l. 477--><p class="noindent" >- orwell
|
||||
<!--l. 575--><p class="noindent" >- orwell
|
||||
</body></html>
|
||||
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -0,0 +1,180 @@
|
|||
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;
|
||||
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;
|
||||
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;
|
||||
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
|
||||
Css: p.noindent { text-indent: 0em }
|
||||
Css: td p.noindent { text-indent: 0em; margin-top:0em; }
|
||||
Css: p.nopar { text-indent: 0em; }
|
||||
Css: p.indent{ text-indent: 1.5em }
|
||||
Css: @media print {div.crosslinks {visibility:hidden;}}
|
||||
Css: a img { border-top: 0; border-left: 0; border-right: 0; }
|
||||
Font_Css("4"): .small-caps{font-variant: small-caps; }
|
||||
Font_Css("10"): .htf-cmbx {font-weight: bold; font-style:normal;}
|
||||
Font_Css("12"): .htf-calligraphy {font-family:cursive}
|
||||
Font_Css("14"): .htf-italic {font-style: italic;}
|
||||
Font_Css("16"): .htf-bold {font-weight: bold;}
|
||||
Font_Css("12"): .htf-calligraphy-bold {font-family:cursive ; font-weight: bold; }
|
||||
Css: center { margin-top:1em; margin-bottom:1em; }
|
||||
Css: td center { margin-top:0em; margin-bottom:0em; }
|
||||
Css: .Canvas { position:relative; }
|
||||
Css: img.math{vertical-align:middle;}
|
||||
Css: li p.indent { text-indent: 0em }
|
||||
Css: li p:first-child{ margin-top:0em; }
|
||||
Css: li p:last-child, li div:last-child { margin-bottom:0.5em; }
|
||||
Css: li p~ul:last-child, li p~ol:last-child{ margin-bottom:0.5em; }
|
||||
Css: .enumerate1 {list-style-type:decimal;}
|
||||
Css: .enumerate2 {list-style-type:lower-alpha;}
|
||||
Css: .enumerate3 {list-style-type:lower-roman;}
|
||||
Css: .enumerate4 {list-style-type:upper-alpha;}
|
||||
Css: div.newtheorem { margin-bottom: 2em; margin-top: 2em;}
|
||||
Css: .obeylines-h,.obeylines-v {white-space: nowrap; }
|
||||
Css: div.obeylines-v p { margin-top:0; margin-bottom:0; }
|
||||
Css: .overline{ text-decoration:overline; }
|
||||
Css: .overline img{ border-top: 1px solid black; }
|
||||
Css: td.displaylines {text-align:center; white-space:nowrap;}
|
||||
Css: .centerline {text-align:center;}
|
||||
Css: .rightline {text-align:right;}
|
||||
Css: div.verbatim {font-family: monospace; white-space: nowrap; text-align:left; clear:both; }
|
||||
Css: .fbox {padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
|
||||
Css: div.fbox {display:table}
|
||||
Css: div.center div.fbox {text-align:center; clear:both; padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
|
||||
Css: div.minipage{width:100%;}
|
||||
Css: div.center, div.center div.center {text-align: center; margin-left:1em; margin-right:1em;}
|
||||
Css: div.center div {text-align: left;}
|
||||
Css: div.flushright, div.flushright div.flushright {text-align: right;}
|
||||
Css: div.flushright div {text-align: left;}
|
||||
Css: div.flushleft {text-align: left;}
|
||||
Css: .underline{ text-decoration:underline; }
|
||||
Css: .underline img{ border-bottom: 1px solid black; margin-bottom:1pt; }
|
||||
Css: .framebox-c, .framebox-l, .framebox-r { padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
|
||||
Css: .framebox-c {text-align:center;}
|
||||
Css: .framebox-l {text-align:left;}
|
||||
Css: .framebox-r {text-align:right;}
|
||||
Css: span.thank-mark{ vertical-align: super }
|
||||
Css: span.footnote-mark sup.textsuperscript, span.footnote-mark a sup.textsuperscript{ font-size:80%; }
|
||||
Css: div.tabular, div.center div.tabular {text-align: center; margin-top:0.5em; margin-bottom:0.5em; }
|
||||
Css: table.tabular td p{margin-top:0em;}
|
||||
Css: table.tabular {margin-left: auto; margin-right: auto;}
|
||||
Css: td p:first-child{ margin-top:0em; }
|
||||
Css: td p:last-child{ margin-bottom:0em; }
|
||||
Css: div.td00{ margin-left:0pt; margin-right:0pt; }
|
||||
Css: div.td01{ margin-left:0pt; margin-right:5pt; }
|
||||
Css: div.td10{ margin-left:5pt; margin-right:0pt; }
|
||||
Css: div.td11{ margin-left:5pt; margin-right:5pt; }
|
||||
Css: table[rules] {border-left:solid black 0.4pt; border-right:solid black 0.4pt; }
|
||||
Css: td.td00{ padding-left:0pt; padding-right:0pt; }
|
||||
Css: td.td01{ padding-left:0pt; padding-right:5pt; }
|
||||
Css: td.td10{ padding-left:5pt; padding-right:0pt; }
|
||||
Css: td.td11{ padding-left:5pt; padding-right:5pt; }
|
||||
Css: table[rules] {border-left:solid black 0.4pt; border-right:solid black 0.4pt; }
|
||||
Css: .hline hr, .cline hr{ height : 1px; margin:0px; }
|
||||
Css: .tabbing-right {text-align:right;}
|
||||
Css: span.TEX {letter-spacing: -0.125em; }
|
||||
Css: span.TEX span.E{ position:relative;top:0.5ex;left:-0.0417em;}
|
||||
Css: a span.TEX span.E {text-decoration: none; }
|
||||
Css: span.LATEX span.A{ position:relative; top:-0.5ex; left:-0.4em; font-size:85%;}
|
||||
Css: span.LATEX span.TEX{ position:relative; left: -0.4em; }
|
||||
Css: div.float, div.figure {margin-left: auto; margin-right: auto;}
|
||||
Css: div.float img {text-align:center;}
|
||||
Css: div.figure img {text-align:center;}
|
||||
Css: .marginpar {width:20%; float:right; text-align:left; margin-left:auto; margin-top:0.5em; font-size:85%; text-decoration:underline;}
|
||||
Css: .marginpar p{margin-top:0.4em; margin-bottom:0.4em;}
|
||||
Css: table.equation {width:100%;}
|
||||
Css: .equation td{text-align:center; }
|
||||
Css: td.equation { margin-top:1em; margin-bottom:1em; }
|
||||
Css: td.equation-label { width:5%; text-align:center; }
|
||||
Css: td.eqnarray4 { width:5%; white-space: normal; }
|
||||
Css: td.eqnarray2 { width:5%; }
|
||||
Css: table.eqnarray-star, table.eqnarray {width:100%;}
|
||||
Css: div.eqnarray{text-align:center;}
|
||||
Css: div.array {text-align:center;}
|
||||
Css: div.pmatrix {text-align:center;}
|
||||
Css: table.pmatrix {width:100%;}
|
||||
Css: span.pmatrix img{vertical-align:middle;}
|
||||
Css: div.pmatrix {text-align:center;}
|
||||
Css: table.pmatrix {width:100%;}
|
||||
Css: span.bar-css {text-decoration:overline;}
|
||||
Css: img.cdots{vertical-align:middle;}
|
||||
Css: .figure img.graphics {margin-left:10%;}
|
||||
File: 0_home_moritz_Home_Projekte_Minetest_minetest_m___s_assets_lyx_img_screenshot_20180830_142551.png
|
||||
File: 1_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-26-35.png
|
||||
File: 2_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-32-48.png
|
||||
File: 3_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-27-25.png
|
||||
File: 4_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-28-32.png
|
||||
File: 5_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-25.png
|
||||
File: 6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png
|
||||
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
|
||||
--- characters ---
|
||||
Font("ecrm","1000","10","100")
|
||||
Font("ecsx","1728","17","100")
|
||||
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")
|
||||
|
|
@ -0,0 +1,528 @@
|
|||
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
|
||||
entering extended mode
|
||||
restricted \write18 enabled.
|
||||
%&-line parsing enabled.
|
||||
**\makeatletter\def\HCode{\futurelet\HCode\HChar}\def\HChar{\ifx"\HCode\def\HCo
|
||||
de"##1"{\Link##1}\expandafter\HCode\else\expandafter\Link\fi}\def\Link#1.a.b.c.
|
||||
{\g@addto@macro\@documentclasshook{\RequirePackage[#1,html]{tex4ht}}\let\HCode\
|
||||
documentstyle\def\documentstyle{\let\documentstyle\HCode\expandafter\def\csname
|
||||
tex4ht\endcsname{#1,html}\def\HCode####1{\documentstyle[tex4ht,}\@ifnextchar[{
|
||||
\HCode}{\documentstyle[tex4ht]}}}\makeatother\HCode .a.b.c.\input interlocking
|
||||
.tex
|
||||
(./interlocking.tex
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/paper/paper.cls
|
||||
Document Class: paper 2008/05/30 1.0l LaTeX document class (wm).
|
||||
\hours=\count79
|
||||
\minutes=\count80
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
|
||||
File: size10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
|
||||
)
|
||||
\beforetitlespace=\skip41
|
||||
\c@part=\count81
|
||||
\c@section=\count82
|
||||
\c@subsection=\count83
|
||||
\c@subsubsection=\count84
|
||||
\c@paragraph=\count85
|
||||
\c@subparagraph=\count86
|
||||
\exampleindent=\skip42
|
||||
\c@figure=\count87
|
||||
\c@table=\count88
|
||||
\abovecaptionskip=\skip43
|
||||
\belowcaptionskip=\skip44
|
||||
\bibindent=\dimen102
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/tex4ht.sty
|
||||
version 2018-02-11-15:01
|
||||
Package: tex4ht
|
||||
--------------------------------------
|
||||
--- Note --- for _ at preamble, use the command line option `early_'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for ^ at preamble, use the command line option `early^'
|
||||
--------------------------------------
|
||||
\tmp:toks=\toks14
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/usepackage.4ht) (/usr/share
|
||||
/texlive/texmf-dist/tex/latex/base/fontenc.sty
|
||||
Package: fontenc 2017/04/05 v2.0i Standard LaTeX package
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
|
||||
File: t1enc.def 2017/04/05 v2.0i Standard LaTeX file
|
||||
LaTeX Font Info: Redeclaring font encoding T1 on input line 48.
|
||||
)) (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
|
||||
Package: inputenc 2015/03/17 v1.2c Input encoding file
|
||||
\inpenc@prehook=\toks15
|
||||
\inpenc@posthook=\toks16
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/base/latin9.def
|
||||
File: latin9.def 2015/03/17 v1.2c Input encoding file
|
||||
)) (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
|
||||
Package: geometry 2010/09/12 v5.6 Page Geometry
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
|
||||
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
|
||||
\KV@toks@=\toks17
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty
|
||||
Package: ifpdf 2017/03/15 v3.2 Provides the ifpdf switch
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty
|
||||
Package: ifvtex 2016/05/16 v1.6 Detect VTeX and its facilities (HO)
|
||||
Package ifvtex Info: VTeX not detected.
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
|
||||
Package: ifxetex 2010/09/12 v0.6 Provides ifxetex conditional
|
||||
)
|
||||
\Gm@cnth=\count89
|
||||
\Gm@cntv=\count90
|
||||
\c@Gm@tempcnt=\count91
|
||||
\Gm@bindingoffset=\dimen103
|
||||
\Gm@wd@mp=\dimen104
|
||||
\Gm@odd@mp=\dimen105
|
||||
\Gm@even@mp=\dimen106
|
||||
\Gm@layoutwidth=\dimen107
|
||||
\Gm@layoutheight=\dimen108
|
||||
\Gm@layouthoffset=\dimen109
|
||||
\Gm@layoutvoffset=\dimen110
|
||||
\Gm@dimlist=\toks18
|
||||
) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
|
||||
Package: graphicx 2017/06/01 v1.1a Enhanced LaTeX Graphics (DPC,SPQR)
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
|
||||
Package: graphics 2017/06/25 v1.2c Standard LaTeX Graphics (DPC,SPQR)
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty
|
||||
Package: trig 2016/01/03 v1.10 sin cos tan (DPC)
|
||||
) (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg
|
||||
File: graphics.cfg 2016/06/04 v1.11 sample graphics configuration
|
||||
)
|
||||
Package graphics Info: Driver file: dvips.def on input line 99.
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def
|
||||
File: dvips.def 2017/06/20 v3.1d Graphics/color driver for dvips
|
||||
))
|
||||
\Gin@req@height=\dimen111
|
||||
\Gin@req@width=\dimen112
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
|
||||
Package: babel 2018/02/14 3.18 The Babel package
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def
|
||||
File: switch.def 2018/02/14 3.18 Babel switching mechanism
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
|
||||
Language: english 2017/06/06 v3.3r English support from the babel system
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
|
||||
File: babel.def 2018/02/14 3.18 Babel common definitions
|
||||
\babel@savecnt=\count92
|
||||
\U@D=\dimen113
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
|
||||
\bbl@dirlevel=\count93
|
||||
)
|
||||
\l@british = a dialect from \language\l@english
|
||||
\l@UKenglish = a dialect from \language\l@english
|
||||
\l@canadian = a dialect from \language\l@american
|
||||
\l@australian = a dialect from \language\l@british
|
||||
\l@newzealand = a dialect from \language\l@british
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/tex4ht.4ht
|
||||
version 2017-05-09-09:21
|
||||
--------------------------------------
|
||||
--- Note --- for additional information, use the command line option `info'
|
||||
--------------------------------------
|
||||
::::::::::::::::::::::::::::::::::::::::::
|
||||
TeX4ht info is available in the log file
|
||||
::::::::::::::::::::::::::::::::::::::::::
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/tex4ht.sty
|
||||
version 2018-02-11-15:01
|
||||
--- needs --- tex4ht interlocking ---
|
||||
\tmp:cnt=\count94
|
||||
\openout15 = `interlocking.tmp'.
|
||||
|
||||
(./interlocking.tmp)
|
||||
\tmp:dim=\skip45
|
||||
--------------------------------------
|
||||
--- Note --- for XML code, use the command line option `xml' or `xhtml'
|
||||
--------------------------------------
|
||||
(./interlocking.xref)
|
||||
\:refout=\write3
|
||||
\openout3 = `interlocking.xref'.
|
||||
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
--------------------------------------
|
||||
--- Note --- to remove the <?xml version=...?> processing instruction use the c
|
||||
ommand line option `no-VERSION'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- to remove the DOCTYPE declaration use the command line option `no-
|
||||
DOCTYPE'
|
||||
--------------------------------------
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)
|
||||
--------------------------------------
|
||||
--- Note --- for marking of the base font, use the command line option `fonts+'
|
||||
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for non active _, use the command line option `no_'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for _ of catcode 13, use the command line option `_13'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for non active ^, use the command line option `no^'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for ^ of catcode 13, use the command line option `^13'
|
||||
--------------------------------------
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
--------------------------------------
|
||||
--- Note --- for alternative charset, use the command line option `charset=...'
|
||||
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- to ignore CSS font decoration, use the `NoFonts' command line opti
|
||||
on
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for jpg bitmaps of pictures, use the `jpg' command line option. (C
|
||||
haracter bitmaps are controled only by `g' records of tex4ht.env and `-g' switc
|
||||
hes of tex4ht.c)
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for gif bitmaps of pictures, use the `gif' command line option. (C
|
||||
haracter bitmaps are controled only by `g' records of tex4ht.env and `-g' switc
|
||||
hes of tex4ht.c)
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for content and toc in 2 frames, use the command line option `fram
|
||||
es'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for content, toc, and footnotes in 3 frames, use the command line
|
||||
option `frames-fn'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for file extension name xht, use the command line option `xht'
|
||||
--------------------------------------
|
||||
TeX4ht package options: html
|
||||
--------------------------------------
|
||||
--- Note --- To print a timestamp, use the command line option timestamp
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- to ignore CSS code, use the command line option `-css
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for inline CSS code, use the command line option `css-in'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for pop ups on mouse over, use the command line option `mouseover'
|
||||
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for addressing images in a subdirectory, use the command line opti
|
||||
on `imgdir:.../'
|
||||
--------------------------------------
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)
|
||||
\:tokwrite=\toks19
|
||||
\:tokpage=\toks20
|
||||
--------------------------------------
|
||||
--- Note --- for back links to toc, use the command line option `sections+'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for linear crosslinks of pages, use the command line option `next'
|
||||
|
||||
--------------------------------------
|
||||
\openout15 = `interlocking.4ct'.
|
||||
|
||||
\:tocout=\write4
|
||||
\openout4 = `interlocking.4tc'.
|
||||
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/latex.4ht
|
||||
version 2018-01-12-14:38
|
||||
LaTeX Info: Redefining \_ on input line 168.
|
||||
--------------------------------------
|
||||
--- Note --- for links into captions, instead of float heads, use the command l
|
||||
ine option `refcaption'
|
||||
--------------------------------------
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
--------------------------------------
|
||||
--- Note --- For mini tocs immediately aftter the header use the command line o
|
||||
ption `minitoc<'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for enumerated list elements with valued data, use the command lin
|
||||
e option `enumerate+'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for enumerated list elements li's with value attributes, use the c
|
||||
ommand line option `enumerate-'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for CSS2 code, use the command line option `css2'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for pictorial tabular, use the command line option `pic-tabular'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for bitmap fbox'es, use the command line option `pic-fbox'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for bitmap framebox'es, use the command line option `pic-framebox'
|
||||
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for inline footnotes use command line option `fn-in'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for tracing of latex font commands, use the command line option `f
|
||||
onts'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for width specifications of tabular p entries, use the `p-width' c
|
||||
ommand line option or a configuration similar to \Configure{HColWidth}{\HCode{
|
||||
style="width:\HColWidth"}}
|
||||
--------------------------------------
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
--------------------------------------
|
||||
--- Note --- for pictorial eqnarray, use the command line option `pic-eqnarray'
|
||||
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for pictorial array, use the command line option `pic-array'
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for pictorial $...$ environments, use the command line option `pic
|
||||
-m' (not recommended!!)
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for pictorial $...$ and $$...$$ environments with latex alt, use t
|
||||
he command line option `pic-m+' (not safe!!)
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for pictorial array, use the command line option `pic-array'
|
||||
--------------------------------------
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/fontmath.4ht
|
||||
version 2009-05-21-09:32
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/inputenc.4ht
|
||||
version 2009-05-21-09:32
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/geometry.4ht
|
||||
version 2016-07-01-08:55
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/graphicx.4ht
|
||||
version 2017-10-21-16:16
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/graphics.4ht (/usr/share/t
|
||||
exlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
--------------------------------------
|
||||
--- Note --- if included graphics are of degraded quality, try the command line
|
||||
options `graphics-num' or `graphics-'. The `num' should provide the density of
|
||||
pixels in the bitmaps (e.g., 110).
|
||||
--------------------------------------
|
||||
--------------------------------------
|
||||
--- Note --- for key dimensions try the option `Gin-dim'; for key dimensions wh
|
||||
en bounding box is unavailable try `Gin-dim+'; neither is recommended
|
||||
--------------------------------------
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/dvips.4ht
|
||||
version 2009-05-21-09:32
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/babel.4ht
|
||||
version 2009-05-21-09:32
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/english.4ht
|
||||
version 2009-05-21-09:32
|
||||
(/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4.4ht
|
||||
version 2018-02-21-09:31
|
||||
) (/usr/share/texlive/texmf-dist/tex/generic/tex4ht/html4-math.4ht
|
||||
version 2017-03-30-16:04
|
||||
)) (./interlocking.aux)
|
||||
\openout1 = `interlocking.aux'.
|
||||
|
||||
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 13.
|
||||
LaTeX Font Info: ... okay on input line 13.
|
||||
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 13.
|
||||
LaTeX Font Info: ... okay on input line 13.
|
||||
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 13.
|
||||
LaTeX Font Info: ... okay on input line 13.
|
||||
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 13.
|
||||
LaTeX Font Info: ... okay on input line 13.
|
||||
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 13.
|
||||
LaTeX Font Info: ... okay on input line 13.
|
||||
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 13.
|
||||
LaTeX Font Info: ... okay on input line 13.
|
||||
*geometry* driver: auto-detecting
|
||||
*geometry* detected driver: dvips
|
||||
|
||||
Package geometry Warning: The marginal notes overrun the paper.
|
||||
Add 47.54726pt and more to the right margin.
|
||||
|
||||
*geometry* verbose mode - [ preamble ] result:
|
||||
* driver: dvips
|
||||
* paper: <default>
|
||||
* layout: <same size as paper>
|
||||
* layoutoffset:(h,v)=(0.0pt,0.0pt)
|
||||
* modes:
|
||||
* h-part:(L,W,R)=(28.45274pt, 557.38951pt, 28.45274pt)
|
||||
* v-part:(T,H,B)=(28.45274pt, 738.0645pt, 28.45274pt)
|
||||
* \paperwidth=614.295pt
|
||||
* \paperheight=794.96999pt
|
||||
* \textwidth=557.38951pt
|
||||
* \textheight=738.0645pt
|
||||
* \oddsidemargin=0.0pt
|
||||
* \evensidemargin=0.0pt
|
||||
* \topmargin=-80.81725pt
|
||||
* \headheight=12.0pt
|
||||
* \headsep=25.0pt
|
||||
* \topskip=10.0pt
|
||||
* \footskip=30.0pt
|
||||
* \marginparwidth=65.0pt
|
||||
* \marginparsep=11.0pt
|
||||
* \columnsep=10.0pt
|
||||
* \skip\footins=9.0pt plus 4.0pt minus 2.0pt
|
||||
* \hoffset=0.0pt
|
||||
* \voffset=0.0pt
|
||||
* \mag=1000
|
||||
* \@twocolumnfalse
|
||||
* \@twosidefalse
|
||||
* \@mparswitchfalse
|
||||
* \@reversemarginfalse
|
||||
* (1in=72.27pt=25.4mm, 1cm=28.453pt)
|
||||
|
||||
--- file interlocking.css ---
|
||||
[1
|
||||
|
||||
] [2]
|
||||
LaTeX Font Info: Try loading font information for T1+cmss on input line 18.
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/base/t1cmss.fd
|
||||
File: t1cmss.fd 2014/09/29 v2.5h Standard LaTeX font definitions
|
||||
)
|
||||
LaTeX Font Info: External font `cmex10' loaded for size
|
||||
(Font) <14.4> on input line 18.
|
||||
LaTeX Font Info: External font `cmex10' loaded for size
|
||||
(Font) <7> on input line 18.
|
||||
LaTeX Font Info: Try loading font information for T1+cmtt on input line 18.
|
||||
(/usr/share/texlive/texmf-dist/tex/latex/base/t1cmtt.fd
|
||||
File: t1cmtt.fd 2014/09/29 v2.5h Standard LaTeX font definitions
|
||||
)
|
||||
|
||||
LaTeX Warning: No \author given.
|
||||
|
||||
LaTeX Font Info: External font `cmex10' loaded for size
|
||||
(Font) <5> on input line 61.
|
||||
[3
|
||||
|
||||
]
|
||||
l.88 --- TeX4ht warning --- File `"0_home_moritz_Home_Projekte_Minetest_minetes
|
||||
t_m___s_assets_lyx_img_screenshot_20180830_142551.xbb"' not found ---
|
||||
l.88 --- TeX4ht warning --- Cannot determine size of graphic in "0_home_moritz_
|
||||
Home_Projekte_Minetest_minetest_m___s_assets_lyx_img_screenshot_20180830_142551
|
||||
.xbb" (no BoundingBox) ---
|
||||
l. 88 --- needs --- 0_home_moritz_Home_Projekte_Minetest_minetest_m___s_assets_
|
||||
lyx_img_screenshot_20180830_142551.png ---
|
||||
l.93 --- TeX4ht warning --- File `"1_home_moritz_Home_Projekte_Minetest_minetes
|
||||
t_m____lyx_img_Bildschirmfoto_2018-08-30_14-26-35.xbb"' not found ---
|
||||
l.93 --- TeX4ht warning --- Cannot determine size of graphic in "1_home_moritz_
|
||||
Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-26-35
|
||||
.xbb" (no BoundingBox) ---
|
||||
l. 93 --- needs --- 1_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_
|
||||
Bildschirmfoto_2018-08-30_14-26-35.png ---
|
||||
l.104 --- TeX4ht warning --- File `"2_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_m____lyx_img_Bildschirmfoto_2018-08-30_14-32-48.xbb"' not found ---
|
||||
l.104 --- TeX4ht warning --- Cannot determine size of graphic in "2_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-32-4
|
||||
8.xbb" (no BoundingBox) ---
|
||||
l. 104 --- needs --- 2_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img
|
||||
_Bildschirmfoto_2018-08-30_14-32-48.png ---
|
||||
l.117 --- TeX4ht warning --- File `"3_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_m____lyx_img_Bildschirmfoto_2018-08-30_14-27-25.xbb"' not found ---
|
||||
l.117 --- TeX4ht warning --- Cannot determine size of graphic in "3_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-27-2
|
||||
5.xbb" (no BoundingBox) ---
|
||||
l. 117 --- needs --- 3_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img
|
||||
_Bildschirmfoto_2018-08-30_14-27-25.png ---
|
||||
l.121 --- TeX4ht warning --- File `"4_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_m____lyx_img_Bildschirmfoto_2018-08-30_14-28-32.xbb"' not found ---
|
||||
l.121 --- TeX4ht warning --- Cannot determine size of graphic in "4_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-28-3
|
||||
2.xbb" (no BoundingBox) ---
|
||||
l. 121 --- needs --- 4_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img
|
||||
_Bildschirmfoto_2018-08-30_14-28-32.png ---
|
||||
[4]
|
||||
l.173 --- TeX4ht warning --- File `"5_home_moritz_Home_Projekte_Minetest_minete
|
||||
st_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-25.xbb"' not found ---
|
||||
l.173 --- TeX4ht warning --- Cannot determine size of graphic in "5_home_moritz
|
||||
_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-2
|
||||
5.xbb" (no BoundingBox) ---
|
||||
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
|
||||
st_mods_advtrains_assets_lyx_img_route_ex1.xbb"' not found ---
|
||||
l.295 --- 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
|
||||
ns_assets_lyx_img_route_ex1.png ---
|
||||
l.321 --- 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
|
||||
_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
|
||||
ns_assets_lyx_img_route_ex2.png ---
|
||||
l.352 --- 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
|
||||
_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
|
||||
ns_assets_lyx_img_assign_signal.png ---
|
||||
[8]
|
||||
l.383 --- 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
|
||||
_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
|
||||
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) )
|
||||
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
|
||||
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).
|
||||
Binary file not shown.
|
|
@ -0,0 +1,576 @@
|
|||
\batchmode
|
||||
\makeatletter
|
||||
\def\input@path{{/home/moritz/Home/Projekte/Minetest/minetest/mods/advtrains/assets/}}
|
||||
\makeatother
|
||||
\documentclass[english]{paper}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage[latin9]{inputenc}
|
||||
\usepackage{geometry}
|
||||
\geometry{verbose,tmargin=1cm,bmargin=1cm,lmargin=1cm,rmargin=1cm}
|
||||
\setlength{\parindent}{0bp}
|
||||
\usepackage{graphicx}
|
||||
\usepackage{babel}
|
||||
\begin{document}
|
||||
|
||||
\title{Minetest Mod - Advanced Trains {[}advtrains{]}}
|
||||
|
||||
\title{Interlocking System Guide}
|
||||
\maketitle
|
||||
|
||||
\section{Introduction}
|
||||
|
||||
In real-world railways, a so-called interlocking system is a set of
|
||||
railway signals and trackside equipment. Its purpose is to prevent
|
||||
conflicting train movements which otherwise could result in derailing
|
||||
or colliding trains. If you want more information, just search for
|
||||
``railway interlocking'' on the internet.
|
||||
|
||||
Real-world interlocking systems perform this task by setting routes.
|
||||
A route is a path along a track that a train can safely pass. To set
|
||||
a route for a train, the signalman (the operator of a signal box)
|
||||
has to set switches (turnouts) to the correct position and lock them
|
||||
in order to make a signal for a train show ``Proceed''. In newer
|
||||
systems, this is done automatically by the interlocking system. A
|
||||
route can not be set if switches are locked to a wrong position by
|
||||
another route or if any portion of the route is occupied by a train.
|
||||
|
||||
The interlocking system in this Minetest mod tries to follow real-world
|
||||
interlocking systems as far as applicable. It divides tracks into
|
||||
track sections and implements a route setting mechanism following
|
||||
the same principle.
|
||||
|
||||
However, for the sake of simplicity of implementation and usage, not
|
||||
all concepts of real-world interlocking have been taken over. Especially,
|
||||
there is no mechanism for overlap.
|
||||
|
||||
If you are looking for a place to learn how real-world interlocking
|
||||
systems work, have a look at ``SimSig''. By looking at their simulations,
|
||||
you can obtain experience on how to set up your own interlocking systems
|
||||
in AdvTrains. The SimSig glossary is a good place to look up unknown
|
||||
terms in this document.
|
||||
|
||||
\section{Setting up track sections}
|
||||
|
||||
In the real world, a line of track is divided into so-called track
|
||||
sections, or track circuits. Those systems often can not tell where
|
||||
exactly a train is, but only which track sections it occupies. A route
|
||||
can never be set through an occupied track section.
|
||||
|
||||
A track section often covers:
|
||||
\begin{itemize}
|
||||
\item A section on a main running line, between two signals
|
||||
\item A single turnout
|
||||
\item A rail crossing, or a set of turnouts acting as a double/single slip
|
||||
switch
|
||||
\item A siding
|
||||
\end{itemize}
|
||||
You will find some examples on how to interlock certain patterns later.
|
||||
|
||||
\subsection{Track Circuit Breaks}
|
||||
|
||||
In this mod, you will not directly configure the locations of track
|
||||
sections. Instead, you designate the borders of each track section
|
||||
using a special node, the Track Circuit Break, abbreviated TCB.
|
||||
|
||||
For example, if you want to create a track section for a piece of
|
||||
a main running line, you set up two TCBs at the ends of this track
|
||||
circuit.
|
||||
|
||||
Setting up a TCB works as follows:
|
||||
\begin{enumerate}
|
||||
\item Place a TCB node somewhere near the place where the circuit break
|
||||
is going to be located.
|
||||
\item Right-click the TCB node
|
||||
\item Punch the rail which should act as TCB
|
||||
\end{enumerate}
|
||||
The result should look like this:
|
||||
|
||||
\includegraphics[width=10cm]{0_home_moritz_Home_Projekte_Minetest_minetest_m___s_assets_lyx_img_screenshot_20180830_142551.png}
|
||||
|
||||
Now you have assigned the TCB node to a rail. Right-click the TCB
|
||||
node once again. This will bring up a form which looks as follows:
|
||||
|
||||
\includegraphics[width=10cm]{1_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-26-35.png}
|
||||
|
||||
You see that the form is divided in side A and side B. To designate
|
||||
where each side is, a marker is displayed on the rail. You can always
|
||||
make this marker show up by punching the TCB node, and remove it by
|
||||
punching the marker. Both sides are shown as ``End of interlocking''.
|
||||
This means that there is no track section set up at this place.
|
||||
|
||||
You should repeat this procedure once again a few meters away from
|
||||
the first TCB to create a second TCB on the same track.
|
||||
|
||||
\includegraphics[width=10cm]{2_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-32-48.png}
|
||||
|
||||
Once you have both bordering TCBs set up, you can now create the actual
|
||||
track section. To do this:
|
||||
\begin{enumerate}
|
||||
\item Right-click one of the TCBs
|
||||
\item Locate the correct side (A or B) to create the track section
|
||||
\item Click ``Create interlocked Track Section'' in the formspec on the
|
||||
chosen side.
|
||||
\end{enumerate}
|
||||
Now, the text on the formspec has changed. It shows something like
|
||||
this:
|
||||
|
||||
\includegraphics[width=5cm]{3_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-27-25.png}
|
||||
|
||||
Clicking ``Show Track Section'' brings up another formspec:
|
||||
|
||||
\includegraphics[width=5cm]{4_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-28-32.png}
|
||||
|
||||
On the top, you see a list of all TCBs that border this track section.
|
||||
In your case, there should be two TCBs listed. If there's only one,
|
||||
head over to \ref{subsec:Long-track-sections,}. You should now select
|
||||
a name for the track section, to identify it later.
|
||||
|
||||
The same procedure is applicable when you create a turnout track section,
|
||||
except that you have to set up three or more TCBs.
|
||||
|
||||
The AdvTrains interlocking system allows you to add more TCBs after
|
||||
you have created a track section. This works without problems in most
|
||||
cases. For example, you can easily insert a turnout into an already
|
||||
set-up track section and create another TCB behind it, and AdvTrains
|
||||
will automatically detect the existing track section. Problems arise
|
||||
only if you try to insert a TCB in-between a section, in which case
|
||||
both sides of the TCB will end up assigned to the same section. The
|
||||
code currently does not handle this case properly, so try to avoid
|
||||
this situation by all means. As a last resort, you can always dissolve
|
||||
a faulty track section, as described in the next chapter.
|
||||
|
||||
\subsection{Long track sections, crossings and other edge cases\label{subsec:Long-track-sections,}}
|
||||
|
||||
\subsubsection{Very long track sections}
|
||||
|
||||
If you try to set up a track section that is longer than 1000 nodes,
|
||||
advtrains won't recognize the TCB at the other end because of a safety
|
||||
limit in the traverser function, which is supposed to prevent deadlocks.
|
||||
This case has happened when the Track Section overview screen only
|
||||
shows one TCB in the list. The procedure for this is as follows:
|
||||
\begin{enumerate}
|
||||
\item Go to the second TCB (the one that wasn't recognized). It should show
|
||||
``End of Interlocking'' on the relevant side.
|
||||
\item Click ``Create interlocked track section''. The section created
|
||||
will be different from the one that is already present.
|
||||
\item In the track section overview, click ``Join into other section''
|
||||
\item Go back to the first TCB, bring up the Track Section overview screen
|
||||
of the first track section and click ``Join with ???''
|
||||
\end{enumerate}
|
||||
The other, missing TCB should now appear in the list. If you accidentally
|
||||
started such a joining procedure, click the ``X'' button on the
|
||||
right.
|
||||
|
||||
\subsubsection{Rail crosses}
|
||||
|
||||
Since rail crosses are created by laying tracks across each other
|
||||
without logical connection, there's no way for advtrains to know whether
|
||||
rails cross each other.
|
||||
|
||||
Rail crossings in interlocking systems are always one single track
|
||||
section, which in most cases has 4 TCBs adjacent.
|
||||
|
||||
\includegraphics[width=5cm]{5_home_moritz_Home_Projekte_Minetest_minetest_m____lyx_img_Bildschirmfoto_2018-08-30_14-51-25.png}
|
||||
|
||||
The procedure is quite similar to the one for long sections: First,
|
||||
create two track sections for the branches, and then use the ``Join''
|
||||
function to merge both sections into one.
|
||||
|
||||
\subsubsection{Deleting and re-adding single TCBs to a section}
|
||||
|
||||
In some occasions, for example when you remove a siding or a crossover,
|
||||
it can be necessary to unassign a TCB from a track section. There
|
||||
are multiple ways to do this:
|
||||
\begin{itemize}
|
||||
\item In the TCB form, click the ``Remove from section'' button
|
||||
\item In the track section form, first select the TCB in the list and then
|
||||
click ``Unlink selected TCB''
|
||||
\end{itemize}
|
||||
The result is that the TCB shows ``End of Interlocking'' and the
|
||||
section does not list the TCB as an endpoint anymore.
|
||||
|
||||
The other case is adding a siding or a crossover, in which case one
|
||||
or more TCBs still show ``End of Interlocking'' although they should
|
||||
be part of a section:
|
||||
\begin{itemize}
|
||||
\item Go to another TCB that is registered in the track section and click
|
||||
``Update near TCBs''
|
||||
\item If that did not work, follow the procedure of creating a long track
|
||||
section
|
||||
\end{itemize}
|
||||
|
||||
\subsubsection{Dissolving sections}
|
||||
|
||||
If you made a mistake setting up something and you don't see any other
|
||||
way to fix a misconfigured track section, you can always delete it
|
||||
using the ``Dissolve section'' button. This operation removes the
|
||||
track section and sets all TCBs that previously belonged to the section
|
||||
as ``End of Interlocking''. This will always work and lets you start
|
||||
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.
|
||||
|
||||
\section{Signals and routes}
|
||||
|
||||
Signals are appliances that can give instructions to trains. That
|
||||
can be the permission to proceed, a speed restriction, or other information.
|
||||
|
||||
There are 2 types of signals:
|
||||
\begin{itemize}
|
||||
\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
|
||||
function is to inform trains about whether and at which speed they
|
||||
can proceed into the next section safely.
|
||||
\end{itemize}
|
||||
|
||||
\subsection{Signal Influence Point}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
\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''
|
||||
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
|
||||
formspec.
|
||||
\end{itemize}
|
||||
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)
|
||||
|
||||
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}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\subsection{The concept of routes}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\includegraphics[width=7cm]{6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png}
|
||||
|
||||
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 \textbf{same
|
||||
direction} (D and E), not at an opposite-facing signal (B and C).
|
||||
There are only few exceptions, we'll cover this later.
|
||||
|
||||
When you set a route to make a train proceed on it, the interlocking
|
||||
system ensures that:
|
||||
\begin{itemize}
|
||||
\item There are no rail vehicles on the route
|
||||
\item All turnouts are set to the correct position and it is impossible
|
||||
to move them
|
||||
\item No other routes can be set that would in any way conflict with this
|
||||
route
|
||||
\end{itemize}
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
\includegraphics[width=7cm]{7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\subsection{Assigning main signals to TCBs}
|
||||
|
||||
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.
|
||||
|
||||
To do this, perform the following steps:
|
||||
\begin{enumerate}
|
||||
\item If not already happened, set up a TCB (you don't need to, but are
|
||||
advised to, configure track sections there)
|
||||
\item Place the signal a few meters in front of the TCB, so that trains
|
||||
stopping at the signal do never pass the TCB
|
||||
\item Locate the side of the TCB which points in the direction that trains
|
||||
will proceed past the signal, as shown in the figure below.
|
||||
\item Right-click the TCB, and click ``Assign a signal'' on this side.
|
||||
\item Punch the signal.
|
||||
\end{enumerate}
|
||||
\includegraphics[width=8cm]{8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png}
|
||||
|
||||
If you haven't set an influence point for the signal yet, the influence
|
||||
point formspec automatically opens.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\subsection{Shunt routes}
|
||||
|
||||
\textbf{The information in this section is subject to future change
|
||||
because of safety issues!}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
|
||||
\includegraphics[width=7cm]{9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png}
|
||||
|
||||
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.}
|
||||
|
||||
Shunt routes like this are, so far, the only exception to the ``Routes
|
||||
should end at a signal facing the same direction'' rule.
|
||||
|
||||
\subsection{Route Release}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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!)
|
||||
|
||||
\subsection{Programming a route}
|
||||
|
||||
The route programming procedure is quite straightforward if you've
|
||||
read the previous sections and understood how routes should be set.
|
||||
|
||||
Routes always start at a main signal. You must have assigned the signal
|
||||
to a TCB, as described earlier.
|
||||
|
||||
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.
|
||||
|
||||
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:
|
||||
\begin{itemize}
|
||||
\item Put any turnouts you need to lock in the correct position (e.g. by
|
||||
right-clicking them). This includes flank protection.
|
||||
\item Punch them. This makes a marker with a blue lock symbol appear.
|
||||
\item If you punch a turnout again, or punch the marker, you can remove
|
||||
the lock again.
|
||||
\item 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.
|
||||
\end{itemize}
|
||||
Depending on the situation, you are now offered some possibilities
|
||||
to proceed:
|
||||
\begin{itemize}
|
||||
\item 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.
|
||||
\end{itemize}
|
||||
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:
|
||||
\begin{itemize}
|
||||
\item Click the ``Finish route HERE'' button when you've set up the locks
|
||||
for the last track section of the route and punched the final TCB
|
||||
(the one with the next signal). You will be asked for a route name
|
||||
and your route will be saved.
|
||||
\item 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.
|
||||
\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,
|
||||
use the ``Cancel route programming'' button.
|
||||
\item The third button is especially useful for programming simple block
|
||||
sections on a main running line, since you can stay at the starting
|
||||
signal (punch starting TCB and select third button).
|
||||
\item If a route should end in a dead end, you MUST use the ``Finish in
|
||||
NEXT section'' button, because there is no final TCB that you could
|
||||
punch.
|
||||
\item 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{itemize}
|
||||
|
||||
\section{Interlocking system operation}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\subsection{Train Safety System}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
click ``set route''. If there are no conflicts, the signal turns
|
||||
green and the train is allowed to proceed.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\subsection{Automatic Working}
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
\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.)
|
||||
\end{itemize}
|
||||
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.
|
||||
|
||||
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!
|
||||
|
||||
- orwell
|
||||
\end{document}
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
1179085530 1539633834 /tmp/lyx_tmpdir.rkwTfVUz2649/lyx_tmpbuf0/interlocking.tex
|
||||
3359239522 1492297155 /usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
|
||||
3238294924 1480098821 /usr/share/texlive/texmf-dist/tex/latex/base/size10.clo
|
||||
3164737843 1492297155 /usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def
|
||||
712237411 1480098836 /usr/share/texlive/texmf-dist/tex/latex/paper/paper.cls
|
||||
2377097700 1256929440 /usr/share/texmf/tex/latex/lm/ot1lmr.fd
|
||||
661117479 1256929440 /usr/share/texmf/tex/latex/lm/t1lmr.fd
|
||||
|
|
@ -0,0 +1,56 @@
|
|||
705793250 1535390202 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecbx1000.600pk
|
||||
1687523072 1536659294 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm0900.600pk
|
||||
4048883546 1535390203 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm1000.600pk
|
||||
3344031364 1536659294 /home/moritz/.texlive2017/texmf-var/fonts/pk/ljfour/jknappen/ec/ecss0900.600pk
|
||||
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
|
||||
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
|
||||
982861076 1518644053 /usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
|
||||
2545392670 1518644053 /usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
|
||||
105161961 1518644053 /usr/share/texlive/texmf-dist/tex/generic/babel/switch.def
|
||||
2237033387 1518644053 /usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def
|
||||
340064178 1480098815 /usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty
|
||||
610376126 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/etexcmds.sty
|
||||
1902548649 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
|
||||
1052579112 1490564930 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty
|
||||
437048305 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty
|
||||
960054333 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty
|
||||
409280369 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty
|
||||
871910792 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
|
||||
2567467016 1480098815 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
|
||||
4103748996 1517006633 /usr/share/texlive/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
|
||||
3359239522 1492297155 /usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
|
||||
761296675 1480098821 /usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
|
||||
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
|
||||
2865791710 1515537368 /usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def
|
||||
422786180 1498427532 /usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
|
||||
3371385264 1498427532 /usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
|
||||
4097419011 1480098830 /usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty
|
||||
1051994689 1480098830 /usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty
|
||||
1239917799 1480098833 /usr/share/texlive/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg
|
||||
2869318152 1480098836 /usr/share/texlive/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
|
||||
1966367522 1480098836 /usr/share/texlive/texmf-dist/tex/latex/oberdiek/grfext.sty
|
||||
2259528920 1480098836 /usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty
|
||||
712237411 1480098836 /usr/share/texlive/texmf-dist/tex/latex/paper/paper.cls
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
|
||||
/* css.sty */
|
||||
|
|
@ -0,0 +1,61 @@
|
|||
\:CrossWord{)F1F-}{interlocking.html}{1}%
|
||||
\:CrossWord{)M1x0}{;}{3}%
|
||||
\:CrossWord{)Qx1-2r1}{1}{3}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{3}%
|
||||
\:CrossWord{)Qx1-3r2}{1}{3}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{3}%
|
||||
\:CrossWord{)Qx1-4r1}{1}{4}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{4}%
|
||||
\:CrossWord{)Qx1-6x1}{1}{4}%
|
||||
\:CrossWord{)Qx1-8x2}{1}{4}%
|
||||
\:CrossWord{)Qx1-10x3}{1}{4}%
|
||||
\:CrossWord{)Qx1-12x1}{1}{4}%
|
||||
\:CrossWord{)Qx1-14x2}{1}{4}%
|
||||
\:CrossWord{)Qx1-16x3}{1}{4}%
|
||||
\:CrossWord{)Qx1-17r2}{1}{5}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{5}%
|
||||
\:CrossWord{)Qx1-18r1}{1}{5}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{5}%
|
||||
\:CrossWord{)Qx1-20x1}{1}{5}%
|
||||
\:CrossWord{)Qx1-22x2}{1}{5}%
|
||||
\:CrossWord{)Qx1-24x3}{1}{5}%
|
||||
\:CrossWord{)Qx1-26x4}{1}{5}%
|
||||
\:CrossWord{)Qx1-27r2}{1}{5}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{5}%
|
||||
\:CrossWord{)Qx1-28r3}{1}{5}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{6}%
|
||||
\:CrossWord{)Qx1-29r4}{1}{6}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{6}%
|
||||
\:CrossWord{)Qx1-30r3}{1}{6}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{6}%
|
||||
\:CrossWord{)Qx1-31r3}{1}{6}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{6}%
|
||||
\:CrossWord{)Qx1-32r1}{1}{7}%
|
||||
\: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-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{)QQ1-1-0}{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{)QQ1-1-0}{1}{10}%
|
||||
\:CrossWord{)Qx1-50r1}{1}{11}%
|
||||
\:CrossWord{)QQ1-1-0}{1}{11}%
|
||||
\:CrossWord{)Qx1-51r2}{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{)QQ1-1-0}{1}{12}%
|
||||
|
|
@ -615,8 +615,8 @@ Interlocking patterns
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This section shows some examples on how you should set up track sections
|
||||
on certain track configurations.
|
||||
This section is supposed to show some examples on how you should set up
|
||||
track sections on certain track configurations.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
|
|
@ -624,71 +624,159 @@ Signals and routes
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The purpose of signals is to inform trains about whether they can proceed
|
||||
into the next section safely.
|
||||
Making a section of track safe to pass for a train, turnouts need to be
|
||||
set to the correct position and no other train should be allowed to cross
|
||||
or share parts of the route with this train.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Assigning Signals to TCBs
|
||||
Signals are appliances that can give instructions to trains.
|
||||
That can be the permission to proceed, a speed restriction, or other informatio
|
||||
n.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Signals in the advtrains interlocking system are positioned - like in real
|
||||
life - at the border of track sections.
|
||||
There are 2 types of signals:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
When you set up a signal, do the following steps:
|
||||
\begin_layout 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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
If not already happened, set up a TCB (you don't need to, but are advised
|
||||
to, configure track sections there)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Place the signal a few meters in front of the TCB, so that trains stopping
|
||||
at the signal do never pass the TCB
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Locate the side of the TCB which points in the direction that trains will
|
||||
proceed past the signal, as shown in the figure below.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Right-click the TCB, and click
|
||||
\begin_layout Itemize
|
||||
Variable signals are what most people would call a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Assign a signal
|
||||
signal
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
on this side.
|
||||
.
|
||||
Its function is to inform trains about whether and at which speed they
|
||||
can proceed into the next section safely.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Punch the signal.
|
||||
\begin_layout Subsection
|
||||
Signal Influence Point
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/assign_signal.png
|
||||
width 8cm
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This is the reason why a so-called
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
influence point
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
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:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Static signals and all red-green light signals from core advtrains that
|
||||
are not assigned to a TCB can be configured by holding the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Sneak
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
key and then right-clicking the signal
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
All signals that are assigned to a TCB can be configured by first right-clicking
|
||||
them, then selecting
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Influence Point
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
in the signalling formspec.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The small formspec that opens allows you to set and later view or clear
|
||||
the Influence Point.
|
||||
To set the influence point, click the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Set
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
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)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Main and Shunt signals
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\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
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Danger
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
aspect (trains are not allowed to proceed) and at least one
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
aspect (train may proceed as train/shunt move, with optional speed restriction)
|
||||
, which act as an
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
entry signal
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
for one or multiple routes.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
|
|
@ -696,8 +784,20 @@ The concept of routes
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
A so-called route is a locked path between two signals, which locks all
|
||||
turnouts in the correct position.
|
||||
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
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
entry
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
signal.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
|
@ -794,10 +894,98 @@ There are, of course, situations, where both positions of a turnout would
|
|||
to be set.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Assigning main signals to TCBs
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
To do this, perform the following steps:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
If not already happened, set up a TCB (you don't need to, but are advised
|
||||
to, configure track sections there)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Place the signal a few meters in front of the TCB, so that trains stopping
|
||||
at the signal do never pass the TCB
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Locate the side of the TCB which points in the direction that trains will
|
||||
proceed past the signal, as shown in the figure below.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Right-click the TCB, and click
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Assign a signal
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
on this side.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Punch the signal.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/assign_signal.png
|
||||
width 8cm
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
If you haven't set an influence point for the signal yet, the influence
|
||||
point formspec automatically opens.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Only main signals can ever be assigned to TCBs, because static ones can
|
||||
either not display
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Danger
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
or do not permit to proceed at all.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Shunt routes
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
||||
\series bold
|
||||
The information in this section is subject to future change because of safety
|
||||
issues!
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Operating railways is not all about driving trains around.
|
||||
Coupling, decoupling and moving single engines, wagons or groups of wagons
|
||||
|
|
@ -882,6 +1070,16 @@ AdvTrains has chosen a modern approach to route releasing.
|
|||
Once the train leaves this section, all assigned locks are also freed.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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!)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Programming a route
|
||||
\end_layout
|
||||
|
|
@ -892,12 +1090,12 @@ The route programming procedure is quite straightforward if you've read
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Routes always start at a signal.
|
||||
Routes always start at a main signal.
|
||||
You must have assigned the signal to a TCB, as described earlier.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
When you right-click the signal, it no longer changes its aspect.
|
||||
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
|
||||
|
|
@ -1096,9 +1294,17 @@ Setting up the interlocking for a portion of a railway network requires
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
At the moment, routes can only be set by clicking the signal or via LuaATC,
|
||||
except if you use automatic working.
|
||||
It is planned to control this via the onboard computer and via a
|
||||
At the moment, routes can either be set by clicking the signal or via LuaATC,
|
||||
or by using the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Remote Routesetting
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
button from the Onboard Computer.
|
||||
It is planned to control this via a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1109,6 +1315,49 @@ signal box
|
|||
view based on the currently broken itrainmap.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Train Safety System
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The Train Safety System, called
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
LZB
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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 (
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
BB
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
) and can not be moved any further.
|
||||
You should then examine the situation and drive the train backwards out
|
||||
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
|
||||
|
|
@ -1190,10 +1439,6 @@ The interlocking system is mainly finished, though there are still some
|
|||
They include:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Setting routes from inside a train (via onboard computer)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Signalbox panels, as revival of itrainmap
|
||||
\end_layout
|
||||
|
|
|
|||
|
|
@ -624,71 +624,159 @@ Signals and routes
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The purpose of signals is to inform trains about whether they can proceed
|
||||
into the next section safely.
|
||||
Making a section of track safe to pass for a train, turnouts need to be
|
||||
set to the correct position and no other train should be allowed to cross
|
||||
or share parts of the route with this train.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Assigning Signals to TCBs
|
||||
Signals are appliances that can give instructions to trains.
|
||||
That can be the permission to proceed, a speed restriction, or other informatio
|
||||
n.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Signals in the advtrains interlocking system are positioned - like in real
|
||||
life - at the border of track sections.
|
||||
There are 2 types of signals:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
When you set up a signal, do the following steps:
|
||||
\begin_layout 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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
If not already happened, set up a TCB (you don't need to, but are advised
|
||||
to, configure track sections there)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Place the signal a few meters in front of the TCB, so that trains stopping
|
||||
at the signal do never pass the TCB
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Locate the side of the TCB which points in the direction that trains will
|
||||
proceed past the signal, as shown in the figure below.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Right-click the TCB, and click
|
||||
\begin_layout Itemize
|
||||
Variable signals are what most people would call a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Assign a signal
|
||||
signal
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
on this side.
|
||||
.
|
||||
Its function is to inform trains about whether and at which speed they
|
||||
can proceed into the next section safely.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Punch the signal.
|
||||
\begin_layout Subsection
|
||||
Signal Influence Point
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/assign_signal.png
|
||||
width 8cm
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
This is the reason why a so-called
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
influence point
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
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:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Static signals and all red-green light signals from core advtrains that
|
||||
are not assigned to a TCB can be configured by holding the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Sneak
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
key and then right-clicking the signal
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
All signals that are assigned to a TCB can be configured by first right-clicking
|
||||
them, then selecting
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Influence Point
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
in the signalling formspec.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The small formspec that opens allows you to set and later view or clear
|
||||
the Influence Point.
|
||||
To set the influence point, click the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Set
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
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)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Main and Shunt signals
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\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
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Danger
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
aspect (trains are not allowed to proceed) and at least one
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Proceed
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
aspect (train may proceed as train/shunt move, with optional speed restriction)
|
||||
, which act as an
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
entry signal
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
for one or multiple routes.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
|
|
@ -696,8 +784,20 @@ The concept of routes
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
A so-called route is a locked path between two signals, which locks all
|
||||
turnouts in the correct position.
|
||||
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
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
entry
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
signal.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
|
@ -794,10 +894,98 @@ There are, of course, situations, where both positions of a turnout would
|
|||
to be set.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Assigning main signals to TCBs
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
To do this, perform the following steps:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
If not already happened, set up a TCB (you don't need to, but are advised
|
||||
to, configure track sections there)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Place the signal a few meters in front of the TCB, so that trains stopping
|
||||
at the signal do never pass the TCB
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Locate the side of the TCB which points in the direction that trains will
|
||||
proceed past the signal, as shown in the figure below.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Right-click the TCB, and click
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Assign a signal
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
on this side.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Enumerate
|
||||
Punch the signal.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
\begin_inset Graphics
|
||||
filename lyx_img/assign_signal.png
|
||||
width 8cm
|
||||
|
||||
\end_inset
|
||||
|
||||
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
If you haven't set an influence point for the signal yet, the influence
|
||||
point formspec automatically opens.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Only main signals can ever be assigned to TCBs, because static ones can
|
||||
either not display
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Danger
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
or do not permit to proceed at all.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Shunt routes
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
|
||||
\series bold
|
||||
The information in this section is subject to future change because of safety
|
||||
issues!
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Operating railways is not all about driving trains around.
|
||||
Coupling, decoupling and moving single engines, wagons or groups of wagons
|
||||
|
|
@ -882,6 +1070,16 @@ AdvTrains has chosen a modern approach to route releasing.
|
|||
Once the train leaves this section, all assigned locks are also freed.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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!)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Programming a route
|
||||
\end_layout
|
||||
|
|
@ -892,12 +1090,12 @@ The route programming procedure is quite straightforward if you've read
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
Routes always start at a signal.
|
||||
Routes always start at a main signal.
|
||||
You must have assigned the signal to a TCB, as described earlier.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
When you right-click the signal, it no longer changes its aspect.
|
||||
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
|
||||
|
|
@ -1079,6 +1277,11 @@ Finish in NEXT section
|
|||
button, because there is no final TCB that you could punch.
|
||||
\end_layout
|
||||
|
||||
\begin_layout 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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Section
|
||||
Interlocking system operation
|
||||
\end_layout
|
||||
|
|
@ -1091,9 +1294,17 @@ Setting up the interlocking for a portion of a railway network requires
|
|||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
At the moment, routes can only be set by clicking the signal or via LuaATC,
|
||||
except if you use automatic working.
|
||||
It is planned to control this via the onboard computer and via a
|
||||
At the moment, routes can either be set by clicking the signal or via LuaATC,
|
||||
or by using the
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
Remote Routesetting
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
button from the Onboard Computer.
|
||||
It is planned to control this via a
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1104,6 +1315,49 @@ signal box
|
|||
view based on the currently broken itrainmap.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Subsection
|
||||
Train Safety System
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
The Train Safety System, called
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
LZB
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
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.
|
||||
\end_layout
|
||||
|
||||
\begin_layout Standard
|
||||
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 (
|
||||
\begin_inset Quotes eld
|
||||
\end_inset
|
||||
|
||||
BB
|
||||
\begin_inset Quotes erd
|
||||
\end_inset
|
||||
|
||||
) and can not be moved any further.
|
||||
You should then examine the situation and drive the train backwards out
|
||||
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
|
||||
|
|
@ -1185,10 +1439,6 @@ The interlocking system is mainly finished, though there are still some
|
|||
They include:
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Setting routes from inside a train (via onboard computer)
|
||||
\end_layout
|
||||
|
||||
\begin_layout Itemize
|
||||
Signalbox panels, as revival of itrainmap
|
||||
\end_layout
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 7.5 KiB After Width: | Height: | Size: 9.5 KiB |
Loading…
Reference in New Issue