diff options
| author | orwell96 <orwell@bleipb.de> | 2019-01-15 21:09:48 +0100 |
|---|---|---|
| committer | orwell96 <orwell@bleipb.de> | 2019-01-15 21:09:48 +0100 |
| commit | 8a33e7b93803803ca84e1cbc8f4bfac8a8c4c409 (patch) | |
| tree | 724965983fd74d92fd9a85025b94041acf07aa58 /assets/interlocking.html.LyXconv/interlocking.html | |
| parent | 08649b84a0f4541c716a815bba7dd0a53daf93af (diff) | |
| download | advtrains-8a33e7b93803803ca84e1cbc8f4bfac8a8c4c409.tar.gz advtrains-8a33e7b93803803ca84e1cbc8f4bfac8a8c4c409.tar.bz2 advtrains-8a33e7b93803803ca84e1cbc8f4bfac8a8c4c409.zip | |
Update interlocking manual
Diffstat (limited to 'assets/interlocking.html.LyXconv/interlocking.html')
| -rw-r--r-- | assets/interlocking.html.LyXconv/interlocking.html | 409 |
1 files changed, 288 insertions, 121 deletions
diff --git a/assets/interlocking.html.LyXconv/interlocking.html b/assets/interlocking.html.LyXconv/interlocking.html index f215fa1..f50d158 100644 --- a/assets/interlocking.html.LyXconv/interlocking.html +++ b/assets/interlocking.html.LyXconv/interlocking.html @@ -277,11 +277,13 @@ class="ecsx-1200">Interlocking</span> class="ecsx-1200">patterns</span> <a id="Q1-1-0"></a> -<!--l. 213--><p class="noindent" >This section is supposed to show some examples on how you should set up track sections on certain track configurations. -<!--l. 216--><p class="noindent" > +<!--l. 213--><p class="noindent" >Have a look at the following images. They show you how you can set up sections so that reasonable train moves are +possible. +<!--l. 216--><p class="noindent" >You should settle on a naming scheme for your sections. This way, you can determine the source of an issue faster +<!--l. 219--><p class="noindent" > <a id="x1-31r3"></a> - <!--l. 216--><p class="noindent" ><span + <!--l. 219--><p class="noindent" ><span class="ecsx-1200">3</span> <span class="ecsx-1200">Signals</span> <span @@ -290,19 +292,19 @@ class="ecsx-1200">and</span> class="ecsx-1200">routes</span> <a id="Q1-1-0"></a> -<!--l. 218--><p class="noindent" >Signals are appliances that can give instructions to trains. That can be the permission to proceed, a speed restriction, or other +<!--l. 221--><p class="noindent" >Signals are appliances that can give instructions to trains. That can be the permission to proceed, a speed restriction, or other information. -<!--l. 221--><p class="noindent" >There are 2 types of signals: +<!--l. 224--><p class="noindent" >There are 2 types of signals: <ul class="itemize1"> <li class="itemize">Static signals always display the same information to the train. This can be a speed restriction (or the end of one), a disallowal to proceed as shunt move or similar things. In most cases, these are signs. </li> - <li class="itemize">Variable signals are what most people would call a “signal”. Its function is to inform trains about whether and at which + <li class="itemize">Dynamic signals are what most people would call a “signal”. Its function is to inform trains about whether and at which speed they can proceed into the next section safely.</li></ul> -<!--l. 231--><p class="noindent" > +<!--l. 234--><p class="noindent" > <a id="x1-32r1"></a> - <!--l. 231--><p class="noindent" ><span + <!--l. 234--><p class="noindent" ><span class="ecsx-1200">3.1</span> <span class="ecsx-1200">Signal</span> <span @@ -311,12 +313,12 @@ class="ecsx-1200">Influence</span> class="ecsx-1200">Point</span> <a id="Q1-1-0"></a> -<!--l. 233--><p class="noindent" >Every signal is associated to a track on which the instruction should be followed. Signals are usually placed right next to the track on the +<!--l. 236--><p class="noindent" >Every signal is associated to a track on which the instruction should be followed. Signals are usually placed right next to the track on the right side. Human observers do know then that the signal belongs to the track left of it, however, train safety systems (like the one in advtrains) can not. -<!--l. 239--><p class="noindent" >This is the reason why a so-called “influence point” needs to be assigned to any signal that should actually give instructions to trains, +<!--l. 242--><p class="noindent" >This is the reason why a so-called “influence point” needs to be assigned to any signal that should actually give instructions to trains, should the driver (if even there is one) fail to recognize the instructions. -<!--l. 244--><p class="noindent" >Depending on the signal and the mod that adds the signal, there are different ways to configure this. Signals integrated into advtrains +<!--l. 247--><p class="noindent" >Depending on the signal and the mod that adds the signal, there are different ways to configure this. Signals integrated into advtrains behave as follows: <ul class="itemize1"> <li class="itemize">Static signals and all red-green light signals from core advtrains that are not assigned to a TCB can be configured by @@ -324,37 +326,74 @@ behave as follows: </li> <li class="itemize">All signals that are assigned to a TCB can be configured by first right-clicking them, then selecting “Influence Point” in the signalling formspec.</li></ul> -<!--l. 255--><p class="noindent" >The small formspec that opens allows you to set and later view or clear the Influence Point. To set the influence point, click the “Set” +<!--l. 258--><p class="noindent" >The small formspec that opens allows you to set and later view or clear the Influence Point. To set the influence point, click the “Set” button, face towards the signal and punch a rail about 2m in front of the signal. A small marker will be shown, indicating success. To cancel setting an influence point, punch anything other. (note that then the influence point remains unset, regardless of its previous state) -<!--l. 263--><p class="noindent" >The advtrains-internal train safety system ensures that the train always obeys any restrictions imposed by signals, if (and only if) the +<!--l. 266--><p class="noindent" >The advtrains-internal train safety system ensures that the train always obeys any restrictions imposed by signals, if (and only if) the influence point is set properly. -<!--l. 267--><p class="noindent" > +<!--l. 270--><p class="noindent" > <a id="x1-33r2"></a> - <!--l. 267--><p class="noindent" ><span + <!--l. 270--><p class="noindent" ><span class="ecsx-1200">3.2</span> <span -class="ecsx-1200">Main</span> - <span -class="ecsx-1200">and</span> - <span -class="ecsx-1200">Shunt</span> +class="ecsx-1200">Signal</span> <span -class="ecsx-1200">signals</span> +class="ecsx-1200">Aspects</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 +<!--l. 272--><p class="noindent" >While static signals are mainly used for speed restrictions, the interesting ones are variable signals. Of course, you can always control any variable signal by traditional means (mesecons, digiline, right-click) if the signal allows it, but that misses the point of this interlocking system. -<!--l. 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 +<!--l. 277--><p class="noindent" >A signal aspect is a piece of information that a signal shows to the train driver. It contains information about whether and at what speed +the driver may proceed at the signal. +<!--l. 281--><p class="noindent" >Every signal, both static and dynamic ones, imposes a certain aspect to trains passing the signal. For static signals, this is always the +same aspect, such as “Proceed at speed of 8” or “Shunt moves may not pass”. Dynamic signals, however, can display multiple different +aspects. The default for them is always as restrictive as possible, mostly “Halt!”. +<!--l. 288--><p class="noindent" >You should know that both static and dynamic signals use exactly the same properties for signal aspects. There is no difference in the +meaning of the aspect definitions. +<!--l. 292--><p class="noindent" >In the following sections, we will talk about main signals. By this, we mean a variable signal that can display both a “Danger” aspect (trains are not allowed to proceed) and at least one “Proceed” aspect (train may proceed as train/shunt move, with optional speed restriction), which act as an “entry signal” for one or multiple routes. -<!--l. 281--><p class="noindent" > +<!--l. 299--><p class="noindent" > <a id="x1-34r3"></a> - <!--l. 281--><p class="noindent" ><span + <!--l. 299--><p class="noindent" ><span class="ecsx-1200">3.3</span> <span +class="ecsx-1200">Train</span> + <span +class="ecsx-1200">moves</span> + <span +class="ecsx-1200">and</span> + <span +class="ecsx-1200">Shunt</span> + <span +class="ecsx-1200">Moves</span> +<a + id="Q1-1-0"></a> + <ul class="itemize1"> + <li class="itemize">A “Train move” is a train that is running, going to run on or coming from a main line between stations, passing through + or stopping at a station. Train moves can expect that there are no obstacles on the route and they can proceed at the + maximum permitted speed of the line. This is the regular operation mode for trains. Shunt signals have no meaning for + train moves. + </li> + <li class="itemize">A “Shunt move” is a train that moves within a station and/or is coupling or decoupling wagons or engines. A shunt move + may never leave a station except into a siding. Also, shunt moves may drive at a maximum speed of 6 speed units, because + it is usually not ensured that the path is free of obstacles. (however, advtrains ensures that every route is free of railway + vehicles, even shunt routes)</li></ul> +<!--l. 314--><p class="noindent" >There are also 2 general types of signals: Main signals and Shunt signals. While main signals have a meaning for all types of trains, Shunt +signals only have to be followed by shunt moves. Usually, Shunt signals that are on a train move route are set to a Proceed aspect as +well. +<!--l. 320--><p class="noindent" >When a train reverses, its mode automatically changes to “shunt move” until it passes a main signal that shows “Proceed as +train move”, which is usually designated by a green light. From this point on, it can accelerate to maximum permitted +speed. +<!--l. 325--><p class="noindent" >Some main signals, like the ones from the Ks signals mod included by default, can also display “Proceed as shunt move”, which is +designated by 2 white lights along with the red light. Once a train passes this signal, it becomes a shunt move. +<!--l. 330--><p class="noindent" > +<a + id="x1-35r4"></a> + <!--l. 330--><p class="noindent" ><span +class="ecsx-1200">3.4</span> <span class="ecsx-1200">The</span> <span class="ecsx-1200">concept</span> @@ -364,44 +403,44 @@ class="ecsx-1200">of</span> class="ecsx-1200">routes</span> <a id="Q1-1-0"></a> -<!--l. 283--><p class="noindent" >A so-called route is a locked path between two main signals, which locks all turnouts in the correct position. Its purpose is to offer a train +<!--l. 332--><p class="noindent" >A so-called route is a locked path between two main signals, which locks all turnouts in the correct position. Its purpose is to offer a train a path on which it can safely proceed without interfering with any other train. A route always incorporates and locks one to multiple track sections, starting with the one that lies directly behind the “entry” signal. -<!--l. 290--><p class="noindent" >Example: Imagine a station with 2 platforms on a single track running line. We are looking at signal A. You probably want trains coming +<!--l. 339--><p class="noindent" >Example: Imagine a station with 2 platforms on a single track running line. We are looking at signal A. You probably want trains coming from the right to go into platform 1 or into platform 2, so you need to program 2 routes. -<!--l. 295--><p class="noindent" ><img +<!--l. 344--><p class="noindent" ><img src="6_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex1.png" alt="PIC" > -<!--l. 297--><p class="noindent" >This leads us to the most important aspect of route programming: Routes always start at a signal (A) and end at a signal facing in the +<!--l. 346--><p class="noindent" >This leads us to the most important aspect of route programming: Routes always start at a signal (A) and end at a signal facing in the <span class="ecbx-1000">same direction </span>(D and E), not at an opposite-facing signal (B and C). There are only few exceptions, we’ll cover this later. -<!--l. 302--><p class="noindent" >When you set a route to make a train proceed on it, the interlocking system ensures that: +<!--l. 351--><p class="noindent" >When you set a route to make a train proceed on it, the interlocking system ensures that: <ul class="itemize1"> <li class="itemize">There are no rail vehicles on the route </li> <li class="itemize">All turnouts are set to the correct position and it is impossible to move them </li> <li class="itemize">No other routes can be set that would in any way conflict with this route</li></ul> -<!--l. 311--><p class="noindent" >For this to work, you need to specify all track sections the train will pass along, as well as the positions of all turnouts that need to be +<!--l. 360--><p class="noindent" >For this to work, you need to specify all track sections the train will pass along, as well as the positions of all turnouts that need to be locked. Those are not only the turnouts that lay directly on the train’s route, but also some turnouts on adjacent tracks, the so-called flank protection. -<!--l. 317--><p class="noindent" >The purpose of flank protection is to prevent runaway trains and/or wagons to pass into a route. This is achieved by setting nearby +<!--l. 366--><p class="noindent" >The purpose of flank protection is to prevent runaway trains and/or wagons to pass into a route. This is achieved by setting nearby turnouts to a position that points “away” from the route. Example: -<!--l. 321--><p class="noindent" ><img +<!--l. 370--><p class="noindent" ><img src="7_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex2.png" alt="PIC" > -<!--l. 323--><p class="noindent" >The upper turnout, of course, needs to be locked in straight (normal) position, while the lower one is not relevant for the route itself. But +<!--l. 372--><p class="noindent" >The upper turnout, of course, needs to be locked in straight (normal) position, while the lower one is not relevant for the route itself. But what if the lower turnout was set to the diverging (reverse) position and the driver of another train approaching signal B fails to see the red light? This train would crash into the first one. To minimise danger, that other train would need to be routed towards signal D. -<!--l. 330--><p class="noindent" >There are, of course, situations, where both positions of a turnout would conflict with a route equally. In those situations, there’s nothing +<!--l. 379--><p class="noindent" >There are, of course, situations, where both positions of a turnout would conflict with a route equally. In those situations, there’s nothing you can do and no flank lock needs to be set. -<!--l. 334--><p class="noindent" > +<!--l. 383--><p class="noindent" > <a - id="x1-35r4"></a> - <!--l. 334--><p class="noindent" ><span -class="ecsx-1200">3.4</span> <span + id="x1-36r5"></a> + <!--l. 383--><p class="noindent" ><span +class="ecsx-1200">3.5</span> <span class="ecsx-1200">Assigning</span> <span class="ecsx-1200">main</span> @@ -413,90 +452,85 @@ class="ecsx-1200">to</span> class="ecsx-1200">TCBs</span> <a id="Q1-1-0"></a> -<!--l. 336--><p class="noindent" >Main signals in the advtrains interlocking system are positioned - like in real life - at the border of track sections, because routes also start +<!--l. 385--><p class="noindent" >Main signals in the advtrains interlocking system are positioned - like in real life - at the border of track sections, because routes also start and end there. For advtrains to know from which signal which routes can be set, you need to assign the signal to a TCB. -<!--l. 341--><p class="noindent" >To do this, perform the following steps: +<!--l. 390--><p class="noindent" >To do this, perform the following steps: <ol class="enumerate1" > <li - class="enumerate" id="x1-37x1">If not already happened, set up a TCB (you don’t need to, but are advised to, configure track sections there) + class="enumerate" id="x1-38x1">If not already happened, set up a TCB (you don’t need to, but are advised to, configure track sections there) </li> <li - class="enumerate" id="x1-39x2">Place the signal a few meters in front of the TCB, so that trains stopping at the signal do never pass the TCB + class="enumerate" id="x1-40x2">Place the signal a few meters in front of the TCB, so that trains stopping at the signal do never pass the TCB </li> <li - class="enumerate" id="x1-41x3">Locate the side of the TCB which points in the direction that trains will proceed past the signal, as shown in the figure + class="enumerate" id="x1-42x3">Locate the side of the TCB which points in the direction that trains will proceed past the signal, as shown in the figure below. </li> <li - class="enumerate" id="x1-43x4">Right-click the TCB, and click “Assign a signal” on this side. + class="enumerate" id="x1-44x4">Right-click the TCB, and click “Assign a signal” on this side. </li> <li - class="enumerate" id="x1-45x5">Punch the signal.</li></ol> -<!--l. 352--><p class="noindent" ><img + class="enumerate" id="x1-46x5">Punch the signal.</li></ol> +<!--l. 401--><p class="noindent" ><img src="8_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_assign_signal.png" alt="PIC" > -<!--l. 354--><p class="noindent" >If you haven’t set an influence point for the signal yet, the influence point formspec automatically opens. -<!--l. 357--><p class="noindent" >You can assign a signal to each side of a TCB. This is, for example, useful when creating block sections on a bi-directional main running +<!--l. 403--><p class="noindent" >If you haven’t set an influence point for the signal yet, the influence point formspec automatically opens. +<!--l. 406--><p class="noindent" >You can assign a signal to each side of a TCB. This is, for example, useful when creating block sections on a bi-directional main running line. -<!--l. 361--><p class="noindent" >Only main signals can ever be assigned to TCBs, because static ones can either not display “Danger” or do not permit to proceed at +<!--l. 410--><p class="noindent" >Only main signals can ever be assigned to TCBs, because static ones can either not display “Danger” or do not permit to proceed at all. -<!--l. 365--><p class="noindent" > +<!--l. 414--><p class="noindent" > <a - id="x1-46r5"></a> - <!--l. 365--><p class="noindent" ><span -class="ecsx-1200">3.5</span> <span + id="x1-47r6"></a> + <!--l. 414--><p class="noindent" ><span +class="ecsx-1200">3.6</span> <span class="ecsx-1200">Shunt</span> <span class="ecsx-1200">routes</span> <a id="Q1-1-0"></a> -<!--l. 368--><p class="noindent" ><span +<!--l. 417--><p class="noindent" ><span class="ecbx-1000">The information in this section is subject to future change because of safety issues!</span> -<!--l. 370--><p class="noindent" >Operating railways is not all about driving trains around. Coupling, decoupling and moving single engines, wagons or groups of wagons +<!--l. 419--><p class="noindent" >Operating railways is not all about driving trains around. Coupling, decoupling and moving single engines, wagons or groups of wagons across a station, called shunting, also plays an important role. -<!--l. 374--><p class="noindent" >Remember what we said about routes: There must be no rail vehicles on the route. So what if you have some goods wagons +<!--l. 423--><p class="noindent" >Remember what we said about routes: There must be no rail vehicles on the route. So what if you have some goods wagons ready on a siding, and want to couple an engine to it? You can not set a regular route into the siding, because it is occupied. -<!--l. 379--><p class="noindent" >The solution is to program a second route into the siding, but with the difference that it already ends at the rear-facing signal of it, so it +<!--l. 428--><p class="noindent" >The solution is to program a second route into the siding, but with the difference that it already ends at the rear-facing signal of it, so it doesn’t include the siding section itself: -<!--l. 383--><p class="noindent" ><img +<!--l. 432--><p class="noindent" ><img src="9_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_route_ex3.png" alt="PIC" > -<!--l. 385--><p class="noindent" >The Sht2 route then needs to show a shunt aspect, which instructs the driver to proceed slowly and watch out for vehicles on the route. -To show a “free” aspect here would be wrong, because that would mean that the track is free until the next main signal, which it is clearly -not. -<!--l. 393--><p class="noindent" ><span -class="ecti-1000">Note that advtrains_interlocking currently does not allow to set individual aspects for routes, this is a feature still to be implemented</span> -<span -class="ecti-1000">soon.</span> -<!--l. 395--><p class="noindent" >Shunt routes like this are, so far, the only exception to the “Routes should end at a signal facing the same direction” +<!--l. 434--><p class="noindent" >The Sht2 route then needs to show a shunt aspect, which instructs the driver to proceed slowly and watch out for vehicles on the route. +See later on for how to set this up. +<!--l. 438--><p class="noindent" >Shunt routes like this are, so far, the only exception to the “Routes should end at a signal facing the same direction” rule. -<!--l. 398--><p class="noindent" > +<!--l. 441--><p class="noindent" > <a - id="x1-47r6"></a> - <!--l. 398--><p class="noindent" ><span -class="ecsx-1200">3.6</span> <span + id="x1-48r7"></a> + <!--l. 441--><p class="noindent" ><span +class="ecsx-1200">3.7</span> <span class="ecsx-1200">Route</span> <span class="ecsx-1200">Release</span> <a id="Q1-1-0"></a> -<!--l. 400--><p class="noindent" >In early real-life interlocking systems, routes either had to be cancelled by the signalman after the train had passed the route, or there was +<!--l. 443--><p class="noindent" >In early real-life interlocking systems, routes either had to be cancelled by the signalman after the train had passed the route, or there was a single release contact at the end of the route. However, as interlocking systems evolved and the position of trains is now roughly known by the track sections, portions of the route can be freed as soon as the train has left the corresponding section. -<!--l. 407--><p class="noindent" >AdvTrains has chosen a modern approach to route releasing. Each turnout lock is associated to a track section belonging to the route’s +<!--l. 450--><p class="noindent" >AdvTrains has chosen a modern approach to route releasing. Each turnout lock is associated to a track section belonging to the route’s path. Once the train leaves this section, all assigned locks are also freed. -<!--l. 411--><p class="noindent" >Please note that reversing a train outside of stations is not only discouraged, but also very dangerous, because even +<!--l. 454--><p class="noindent" >Please note that reversing a train outside of stations is not only discouraged, but also very dangerous, because even real-world interlocking system do not expect this. There is a clear, human-sense rule that you should never reverse the driving direction of a train while on a main line or on a turnout. Else, you can be considered a terrorist. (quote from professional!) -<!--l. 418--><p class="noindent" > +<!--l. 461--><p class="noindent" > <a - id="x1-48r7"></a> - <!--l. 418--><p class="noindent" ><span -class="ecsx-1200">3.7</span> <span + id="x1-49r8"></a> + <!--l. 461--><p class="noindent" ><span +class="ecsx-1200">3.8</span> <span class="ecsx-1200">Programming</span> <span class="ecsx-1200">a</span> @@ -504,13 +538,13 @@ class="ecsx-1200">a</span> class="ecsx-1200">route</span> <a id="Q1-1-0"></a> -<!--l. 420--><p class="noindent" >The route programming procedure is quite straightforward if you’ve read the previous sections and understood how routes should be +<!--l. 463--><p class="noindent" >The route programming procedure is quite straightforward if you’ve read the previous sections and understood how routes should be set. -<!--l. 423--><p class="noindent" >Routes always start at a main signal. You must have assigned the signal to a TCB, as described earlier. -<!--l. 426--><p class="noindent" >When you right-click the main signal, it no longer changes its aspect. Instead, a formspec pops up, showing you an (empty) list of routes +<!--l. 466--><p class="noindent" >Routes always start at a main signal. You must have assigned the signal to a TCB, as described earlier. +<!--l. 469--><p class="noindent" >When you right-click the main signal, it no longer changes its aspect. Instead, a formspec pops up, showing you an (empty) list of routes with the possibility to set them or to create new routes. Click the “Create new route” button to start programming a new route. -<!--l. 431--><p class="noindent" >The form closes, and an arrow is displayed on the TCB. You are now in “Route Programming” mode, programming the first track section +<!--l. 474--><p class="noindent" >The form closes, and an arrow is displayed on the TCB. You are now in “Route Programming” mode, programming the first track section of the route. Now: <ul class="itemize1"> <li class="itemize">Put any turnouts you need to lock in the correct position (e.g. by right-clicking them). This includes flank protection. @@ -521,11 +555,11 @@ of the route. Now: </li> <li class="itemize">When you’ve locked all turnouts in the current section, go to and punch the TCB that is the border to the next track section the train proceeds into.</li></ul> -<!--l. 444--><p class="noindent" >Depending on the situation, you are now offered some possibilities to proceed: +<!--l. 487--><p class="noindent" >Depending on the situation, you are now offered some possibilities to proceed: <ul class="itemize1"> <li class="itemize">Click the “Advance to next section” button if your route consists of more sections with turnouts to lock, and you need to continue programming. Follow the above steps to set locks for the next section.</li></ul> -<!--l. 451--><p class="noindent" >Once you’ve clicked the “Advance” button, the lock markers change to a red lock symbol, telling they can’t be changed anymore. Repeat +<!--l. 494--><p class="noindent" >Once you’ve clicked the “Advance” button, the lock markers change to a red lock symbol, telling they can’t be changed anymore. Repeat the above procedure until you are ready to complete the programming procedure: <ul class="itemize1"> <li class="itemize">Click the “Finish route HERE” button when you’ve set up the locks for the last track section of the route and punched the @@ -534,12 +568,8 @@ the above procedure until you are ready to complete the programming procedure: <li class="itemize">The “Finish route at end of NEXT section” button (third button) is an useful quickhand to make the route proceed one more section. Using this button is equivalent to first clicking the “Advance” button, then flying to the end of the next track section and finishing the route there. You can not (officially) set turnout locks in the final section using this method.</li></ul> -<!--l. 467--><p class="noindent" >A few hints: +<!--l. 510--><p class="noindent" >A few hints: <ul class="itemize1"> - <li class="itemize">If one turnout should be locked by more than one section, set the lock only in the <span -class="ectt-1000">last </span>of those sections. Locking the same - turnout in multiple sections of a single route results in undefined behavior! - </li> <li class="itemize">If you accidentally advanced the route wrongly, you can use the “Step back one section” button to undo this. </li> <li class="itemize">If you want to stop programming the entire route without saving it, use the “Cancel route programming” button. @@ -552,10 +582,64 @@ class="ectt-1000">last </span>of those sections. Locking the same </li> <li class="itemize">The third button does NOT work on sections with more than 2 exits, because the system won’t be able to determine the final TCB of the route then.</li></ul> -<!--l. 488--><p class="noindent" > +<!--l. 527--><p class="noindent" > +<a + id="x1-50r9"></a> + <!--l. 527--><p class="noindent" ><span +class="ecsx-1200">3.9</span> <span +class="ecsx-1200">Route</span> + <span +class="ecsx-1200">information</span> + <span +class="ecsx-1200">screen</span> +<a + id="Q1-1-0"></a> +<!--l. 529--><p class="noindent" ><img +src="10_home_moritz_Home_Projekte_Minetest_minetest_____lyx_img_Bildschirmfoto_2019-01-15_19-28-09.png" alt="PIC" +> +<!--l. 531--><p class="noindent" >This is the screen that appears when you click “Edit Route”. It lets you change the route name and delete the route. Also, it shows a +summary of the route and its elements. +<!--l. 535--><p class="noindent" >The route summary lists information per track section on the route, so the line starting with “1” is the first section of the +route. +<!--l. 538--><p class="noindent" >The ARS rule list and its purpose is explained later. +<!--l. 540--><p class="noindent" > +<a + id="x1-51r10"></a> + <!--l. 540--><p class="noindent" ><span +class="ecsx-1200">3.10</span> <span +class="ecsx-1200">Specifying</span> + <span +class="ecsx-1200">signal</span> + <span +class="ecsx-1200">aspects</span> +<a + id="Q1-1-0"></a> +<!--l. 542--><p class="noindent" >By default, newly programmed routes show an aspect that comes closest to “Proceed at maximum speed”. However, it can be desirable to +change this behavior, like when the route passes a diverging turnout, the train should be signalled to drive slower, or the route is a shunt +route and therefore only “Shunting allowed” should be shown. +<!--l. 548--><p class="noindent" >This is the purpose of the “Change Aspect” button in the route info screen. +<!--l. 551--><p class="noindent" >Signal aspects in advtrains consist of 4 sections: main (Information for train moves), dst (Distant signal information, not implemented +yet), shunt (Information for shunt moves) and info (additional information, currently not in use). + <ul class="itemize1"> + <li class="itemize">Train may proceed as train move at maximum speed: “main: free, speed -1” + </li> + <li class="itemize">Train may proceed as train move at speed of 8: “main: free, speed 8” + </li> + <li class="itemize">Train may proceed as shunt move: “shunt: free”</li></ul> +<!--l. 562--><p class="noindent" >There’s a field in the “shunt” part of signal aspects that is not displayed in the GUI, but is of potential interest to developers of signal +addons: shunt.proceed_as_main. + <ul class="itemize1"> + <li class="itemize">A train move can always become a shunt move by passing a signal that shows “Halt for train moves, shunting permitted” + </li> + <li class="itemize">A shunt move can only pass a signal saying “Proceed as train move, shunting not permitted” when proceed_as_main is + true.</li></ul> +<!--l. 571--><p class="noindent" >The property is used by the Limit Of Shunt sign, where proceed_as_main is set to false. Shunt moves have to stop in front of it, while +train moves are signalled “Proceed”. Regular main signals that show “green” have the field set to true, so that all trains can pass +it. +<!--l. 577--><p class="noindent" > <a - id="x1-49r4"></a> - <!--l. 488--><p class="noindent" ><span + id="x1-52r4"></a> + <!--l. 577--><p class="noindent" ><span class="ecsx-1200">4</span> <span class="ecsx-1200">Interlocking</span> <span @@ -564,16 +648,16 @@ class="ecsx-1200">system</span> class="ecsx-1200">operation</span> <a id="Q1-1-0"></a> -<!--l. 490--><p class="noindent" >Setting up the interlocking for a portion of a railway network requires some time, experience and planning, but once done, there’s not +<!--l. 579--><p class="noindent" >Setting up the interlocking for a portion of a railway network requires some time, experience and planning, but once done, there’s not much to do anymore to make trains run on your, now safer, railway. This section covers some useful practices to route trains across your network. -<!--l. 495--><p class="noindent" >At the moment, routes can either be set by clicking the signal or via LuaATC, or by using the “Remote Routesetting” +<!--l. 584--><p class="noindent" >At the moment, routes can either be set by clicking the signal or via LuaATC, or by using the “Remote Routesetting” button from the Onboard Computer. It is planned to control this via a “signal box” view based on the currently broken itrainmap. -<!--l. 500--><p class="noindent" > +<!--l. 589--><p class="noindent" > <a - id="x1-50r1"></a> - <!--l. 500--><p class="noindent" ><span + id="x1-53r1"></a> + <!--l. 589--><p class="noindent" ><span class="ecsx-1200">4.1</span> <span class="ecsx-1200">Train</span> <span @@ -582,18 +666,17 @@ class="ecsx-1200">Safety</span> class="ecsx-1200">System</span> <a id="Q1-1-0"></a> -<!--l. 502--><p class="noindent" >The Train Safety System, called “LZB” in the code (from the german term Linienzugbeeinflussung, although this is a completely different +<!--l. 591--><p class="noindent" >The Train Safety System, called “LZB” in the code (from the german term Linienzugbeeinflussung, although this is a completely different system), ensures that trains obey any restrictions imposed by signals when influence points are set. This way, it is not possible to pass signals at danger or to bypass speed restrictions. -<!--l. 508--><p class="noindent" >It is possible to overrun red signals, if a route is cancelled while a train is approaching. Real interlocking systems use a mechanism called +<!--l. 597--><p class="noindent" >It is possible to overrun red signals, if a route is cancelled while a train is approaching. Real interlocking systems use a mechanism called Approach locking for this, however, as of now, there’s no similar system in this mod. If a red signal is overrun, the train brakes using emergency brake (“BB”) and can not be moved any further. You should then examine the situation and drive the train backwards out of the section. -<!--l. 516--><p class="noindent" >As of now, changing the driving direction of a train always clears any imposed speed restrictions. -<!--l. 519--><p class="noindent" > +<!--l. 605--><p class="noindent" > <a - id="x1-51r2"></a> - <!--l. 519--><p class="noindent" ><span + id="x1-54r2"></a> + <!--l. 605--><p class="noindent" ><span class="ecsx-1200">4.2</span> <span class="ecsx-1200">Simple</span> <span @@ -606,57 +689,141 @@ class="ecsx-1200">and</span> class="ecsx-1200">cancelling</span> <a id="Q1-1-0"></a> -<!--l. 521--><p class="noindent" >To set a route, simply right-click the signal, select a route and click “set route”. If there are no conflicts, the signal turns green and the +<!--l. 607--><p class="noindent" >To set a route, simply right-click the signal, select a route and click “set route”. If there are no conflicts, the signal turns green and the train is allowed to proceed. -<!--l. 525--><p class="noindent" >It may be possible that the route can not be set, because one or more other routes conflict with the current one, or a section is blocked. In +<!--l. 611--><p class="noindent" >It may be possible that the route can not be set, because one or more other routes conflict with the current one, or a section is blocked. In this case, the signal stays red, and the conflicting item is shown in the formspec. As soon as the conflict is resolved (by cancellation or release of the conflicting route, or the section becoming free), the requested route will be set and the signal turns green. -<!--l. 532--><p class="noindent" >If a route is either requested or set, it can be cancelled from the signalling formspec. This means that all turnouts and sections are +<!--l. 618--><p class="noindent" >If a route is either requested or set, it can be cancelled from the signalling formspec. This means that all turnouts and sections are released, and the signal reverts back to red. This of course only works when the train has not passed the signal yet. There is no mechanism for Approach Locking. -<!--l. 538--><p class="noindent" > +<!--l. 624--><p class="noindent" > <a - id="x1-52r3"></a> - <!--l. 538--><p class="noindent" ><span + id="x1-55r3"></a> + <!--l. 624--><p class="noindent" ><span class="ecsx-1200">4.3</span> <span class="ecsx-1200">Automatic</span> <span class="ecsx-1200">Working</span> <a id="Q1-1-0"></a> -<!--l. 540--><p class="noindent" >Block signals on main running lines usually only have a single route to set, the one proceeding along the main line. Their purpose is only +<!--l. 626--><p class="noindent" >Block signals on main running lines usually only have a single route to set, the one proceeding along the main line. Their purpose is only to show whether there are trains in the next section. So, it would be convenient if this only route would set itself again after a train passed. -<!--l. 546--><p class="noindent" >This is what Automatic Working is for. Set a route, click “Enable Automatic Working”, and as soon as a train passes, the route is +<!--l. 632--><p class="noindent" >This is what Automatic Working is for. Set a route, click “Enable Automatic Working”, and as soon as a train passes, the route is automatically re-set. -<!--l. 550--><p class="noindent" >This function is nearly identical to SimSig automatic signals. It can also be useful on a line with high traffic, when there’s a +<!--l. 636--><p class="noindent" >This function is nearly identical to SimSig automatic signals. It can also be useful on a line with high traffic, when there’s a low-frequented access to a siding. You’d enable automatic working for the main route and cancel it only when you need a train to go into the siding. -<!--l. 555--><p class="noindent" > +<!--l. 641--><p class="noindent" > +<a + id="x1-56r4"></a> + <!--l. 641--><p class="noindent" ><span +class="ecsx-1200">4.4</span> <span +class="ecsx-1200">Automatic</span> + <span +class="ecsx-1200">Route</span> + <span +class="ecsx-1200">Setting</span> + <span +class="ecsx-1200">(ARS)</span> +<a + id="Q1-1-0"></a> +<!--l. 643--><p class="noindent" >As interlocking systems evolved, the goal always was to offload work from the human to the system, automating things. Modern +interlocking systems can automatically set routes based on a pre-programmed routing table for each particular train. Since one +outstanding feature of Advtrains is it’s high degree of automation, it has a similar system to automatically set routes for a train +depending on certain parameters. +<!--l. 650--><p class="noindent" >Every train in Advtrains has 2 internal properties that can be set through the Onboard Computer of every engine in the train, the “Line” +and the “Routing Code” + <ul class="itemize1"> + <li class="itemize">The “Line” property is supposed to distinguish trains of multiple lines that share a track. + </li> + <li class="itemize">The “Routing Code” property is supposed to tell the target of a train or which route it should take to reach the target</li></ul> +<!--l. 659--><p class="noindent" >Examples: +<!--l. 661--><p class="noindent" ><img +src="11_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex1.png" alt="PIC" +> +<!--l. 663--><p class="noindent" >Both lines share the section between Blackbirdshire and Parktown. To divert them again, they can save their line number in the “Line” +field. +<!--l. 667--><p class="noindent" ><img +src="12_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_arslin_ex2.png" alt="PIC" +> +<!--l. 669--><p class="noindent" >Some trains should go to B, some to C, the direction can be set with a routing code. +<!--l. 672--><p class="noindent" >One single routing code should not contain spaces. You can set multiple routing codes by just separating them with spaces in the +Routing Code field. So, “Stn Ori” would be matched by ARS rules either containing “Stn” or “Ori”. This does not work for +lines. +<!--l. 677--><p class="noindent" > +<a + id="x1-57r1"></a> + <!--l. 677--><p class="noindent" ><span +class="ecsx-1000">4.4.1</span> <span +class="ecsx-1000">Writing</span> + <span +class="ecsx-1000">ARS</span> + <span +class="ecsx-1000">Rules</span> +<a + id="Q1-1-0"></a> +<!--l. 679--><p class="noindent" >Every route of every signal can be given a set of ARS rules. A single ARS rule can either match a line or a routing code (combinations, +e.g. and’s, are not yet supported). The first rule in the first route that matches any of the properties of the train is selected, and that +route is set for the train. +<!--l. 685--><p class="noindent" ><img +src="13_home_moritz_Home_Projekte_Minetest_minetest_mods_advtrains_assets_lyx_img_ars_ex1.png" alt="PIC" +> +<!--l. 687--><p class="noindent" >You can add an asterisk (“*”) to the ARS rules of one route. That route then becomes the default route. +<!--l. 690--><p class="noindent" >If no explicit ARS rule matches the train, then the default route is chosen and set. If there is no default route, nothing happens and the +signal remains red. +<!--l. 694--><p class="noindent" > <a - id="x1-53r5"></a> - <!--l. 555--><p class="noindent" ><span + id="x1-58r2"></a> + <!--l. 694--><p class="noindent" ><span +class="ecsx-1000">4.4.2</span> <span +class="ecsx-1000">Using</span> + <span +class="ecsx-1000">ARS</span> +<a + id="Q1-1-0"></a> +<!--l. 696--><p class="noindent" >In contrast to Automatic working, where the route is re-set immediately after the train passed, ARS sets the route only when the train +approaches the signal, e.g. is just about to start braking in front of it. +<!--l. 700--><p class="noindent" >At any place where one of the following things take place, you should use the ARS system in favor of Automatic Working: + <ul class="itemize1"> + <li class="itemize">A main line diverts into 2 or more lines: Using ARS, you can direct the trains along the line where they should go + </li> + <li class="itemize">Two or more main lines join into one: You cannot use automatic working here, because all routes are tried to be set at the + same time and it is a matter of luck which one “wins”. In a bad situation, you have a train coming from A, but it cannot + proceed because Signal B has won the “route race” into the shared section, even if there’s no train coming from B. Using + ARS, by just specifying the “default route” by a *, the inward route is only set when a train approaches. + </li> + <li class="itemize">Complex intersections, which are probably a combination of the above two + </li> + <li class="itemize">sometimes-used branching tracks on which only certain trains (with certain routing code or line) should head off, like the + entrance to a factory where only one specific goods train should drive in.</li></ul> +<!--l. 718--><p class="noindent" >In the route overview, you can see some information on the ARS settings: All routes that have ARS rules are highlighted red, the “default +route” is highlighted green. +<!--l. 722--><p class="noindent" >ARS does not affect signals which already have a route set, and signals which are operating under “Automatic Working”. +<!--l. 725--><p class="noindent" > +<a + id="x1-59r5"></a> + <!--l. 725--><p class="noindent" ><span class="ecsx-1200">5</span> <span class="ecsx-1200">Final</span> <span class="ecsx-1200">notes</span> <a id="Q1-1-0"></a> -<!--l. 557--><p class="noindent" >The interlocking system is mainly finished, though there are still some plans and ideas. They include: +<!--l. 727--><p class="noindent" >The interlocking system is mainly finished, though there are still some plans and ideas. They include: <ul class="itemize1"> <li class="itemize">Signalbox panels, as revival of itrainmap </li> - <li class="itemize">Individual signal aspects for routes - </li> <li class="itemize">Distant signals </li> <li class="itemize">On-Train head-up display for oncoming signals (they have something like this in Czech Republic, I forgot how it’s called.)</li></ul> -<!--l. 566--><p class="noindent" >Apart from this, there’s the large oncoming project of a new timetable-based train automation system, but this will take some time to +<!--l. 735--><p class="noindent" >Apart from this, there’s the large oncoming project of a new timetable-based train automation system, but this will take some time to evolve and is out of the scope of this document. -<!--l. 570--><p class="noindent" >If you have any suggestions, corrections, improvements, criticism or cute kittens and stuff, you can always contact me by various means +<!--l. 739--><p class="noindent" >If you have any suggestions, corrections, improvements, criticism or cute kittens and stuff, you can always contact me by various means (Forum PM, E-Mail (orwell@bleipb.de), Linuxworks server chat a.s.o.). Have fun! -<!--l. 575--><p class="noindent" >- orwell +<!--l. 744--><p class="noindent" >- orwell </body></html> |