Poste de Contrôle et de Régulation

From TrainzOnline
(Difference between revisions)
Jump to: navigation, search
(Created page with "===Postes de Contrôle et Régulation=== Version anglaise : Enhanced Interlocking Towers thumb ...")
 
(Postes de Contrôle et Régulation)
Line 1: Line 1:
 
===Postes de Contrôle et Régulation===
 
===Postes de Contrôle et Régulation===
[[Enhanced Interlocking Towers|Version anglaise : Enhanced Interlocking Towers]]
+
[[Enhanced Interlocking Tower|Version anglaise : Enhanced Interlocking Tower]]
 
[[File:Help-eit-assets-img01.png | left | thumb ]]
 
[[File:Help-eit-assets-img01.png | left | thumb ]]
  
Line 25: Line 25:
 
::* niveau de deboggage : Cette option à destination des développeurs permet de choisir entre l'absence de toute log et un logging plus complet.<br>
 
::* niveau de deboggage : Cette option à destination des développeurs permet de choisir entre l'absence de toute log et un logging plus complet.<br>
 
::* Les Postes de Contrôle Régulation permette via l'utilisation d'un composant additionnel adéquat eit pathtrigger d'ajuster à la baisse ou à la hausse  la distance avant déclenchement d'un nouvel itinéraire.
 
::* Les Postes de Contrôle Régulation permette via l'utilisation d'un composant additionnel adéquat eit pathtrigger d'ajuster à la baisse ou à la hausse  la distance avant déclenchement d'un nouvel itinéraire.
 +
 +
=== Poste de Contrôle et de Régulation : Comment les utiliser ? ===
 +
 +
Pour utiliser un Poste de Contrôle et de Régulation, vous devez placer sur votre carte un objet Poste de Contrôle et Régulation comme le PCR - Poste de Contrôle Régulation TRC3 invisible <kuid2:61392:8101:76>. D'autres créateurs ont mise à disposition sur la DLS d'autres objets de type Poste de Contrôle Régulation ou Interlocking Tower. En fait tout objet de type "scenery" peut être transformé en un objet Poste de Contrôle Régulation par ajout de la configuation adéquate dans son fichier de configuration.
 +
 +
'''Liste au 18/02/2021 de tous les Postes de Contrôle Régulation disponible sur la DLS :'''
 +
 +
PCR - Poste de Contrôle Régulation TRC3 invisible  <kuid2:61392:8101:47> by pguy
 +
 +
ITE SB Nameable 1  <kuid:182010:100397> by peterwhite
 +
 +
ITE SB Nameable 2  <kuid:182010:100403> by peterwhite
 +
 +
ITE SB Nameable 3  <kuid:182010:100410> by peterwhite
 +
 +
ITE SB Nameable 5  <kuid:182010:100401> by peterwhite
 +
 +
ITE SB Nameable 6  <kuid:182010:100407> by peterwhite
 +
 +
ITE SB Nameable 7  <kuid:182010:100402> by peterwhite
 +
 +
ITE SB Nameable 8  <kuid:182010:100398> by peterwhite
 +
 +
ITE SB Nameable 9  <kuid:182010:100408> by peterwhite
 +
 +
ITE SB Nameable 10  <kuid:182010:100411> by peterwhite
 +
 +
 +
Après avoir placé sur votre carte le poste de contrôle régulation que vous voulez utiliser, vous n'avez plus qu'à éditer les propriétés de l'objet en cliquant dessus pour ouvrir la fenêtre standard d'édition des propriétés du Poste de Contrôle Régulation. Pour cet objet, l'ensemble des options à configurer sera dans le paneau supérieur de la fenêtre des propriétés.
 +
 +
 +
==== Edition d'un Poste de Contrôle Régulation : les options disponibles dans la fenêtre d'édition ====
 +
 +
[[File:Help-edit-pcr.png | 768px | none ]]
 +
 +
 +
Les options disponibles dans le paneau supérieur sont :
 +
 +
:* '''tower display yellow disc option :'''
 +
::by clicking on the link on the right, you can either choose display yellow disc enabled or disabled
 +
 +
:* '''tower path requery option :'''
 +
::this option is on how to process AI trains with schedule blocked. It can either be '''try requery path on schedule blocked''' or '''do not requery path on schedule blocked'''. With requery path option active, when an AI train has its schedule blocked, the enhanced IT will try to release unused paths (paths owned but not entered)  to enable some other paths to be activated. The unused paths released are requeued for later activation. This standard processing done in standard IT may help to find a solution to some AI schedule blocked, but may have some side effects as some activated path may be cancelled before being later reactivated. If you do not want this behavior, just change the option to do not requery path on schedule blocked and no processing will be done when an AI train has its schedule blocked.
 +
 +
:* '''tower dynamic ownership option (available since release 47 march 2018) :'''
 +
::this option is on how the tower will take ownership of all its paths objects (entry signal, exit signal, other signals, junctions, crossings, ...). Entry signals are always owned by the tower for all the session duration whatever the option choosen. With static ownership, it is the same for all paths objects for which ownership will also be taken for all the session duration. With dynamic ownership, path object ownership is taken only on path activation and will be released when the path returns to path not set state. With dynamic ownership, a path object belonging to one or several paths currently not activated is no longer owned by the tower and can be used by other components for manual operation. This may be usefull for sidings where you can have the junctions unlocked available for manual operations when no paths using this junction are active.
 +
 +
:* '''tower trc compatible mode :'''
 +
::when this option is active, crossings conformant to trc system specification will not be managed by interlocking tower. Trc crossing objects will be skipped with no tower ownership and will remain managed by the trc system. if the option is inactive, interlocking tower will manage all the crossings along its path.
 +
 +
:* '''tower debug level :'''
 +
::tower debug level option is an option available that help session developper to understand interlocking tower problems. Interlocking tower have an integrated debugging facility by default disabled. By selecting only log debug information or log and print debugging information, you will activate the debugging facility which may help to understand some conflicting or deadlock problems using interlocking tower.
 +
 +
at the bottom of the header area, you will find a link '''Restore default options''' that enables to reset all the current enhanced options to the default values defined by the enhanced tower asset content creator.
 +
 +
==== Editing enhanced Interlocking tower path : options available in the path editor window ====
 +
 +
[[File:Help-eit-assets-img03.png  | 768px | none ]]
 +
 +
 +
The available options in the header at the path level are :
 +
 +
:* '''Path clear method to use :'''
 +
::you can here select the path clear method to be used between '''Clear on cancel (when a path is either complete or cancelled)''' , '''Clear on drive (following train progress along the path)''' and '''Clear after last junction (when the train leaves the last junction along the path)'''. Clear on cancel is the standard IT clear method that can still be selected. Clear on cancel will release path objects locks when the owning train leaves the path object. With clear on drive, the path will still be cleared and cancelled only when the train will leaves the exit signal, but path objects are unlocked as soon as the train has left them and are made available for other conflicting paths to be activated earlier. Clear after last junction will clear and cancel the path as soon as the owning train has left the last junction along the path and will not wait for the train to reach and leave the exit signal. Clear on last junction may be an interesting option for path leading to an and of track with a buffer. You can use the buffer as the exit signal, and though the owning train will never leave the buffer exit signal, the path will be cleared as soon as the train will have left the last junction along the path.
 +
 +
:* '''Path track circuit blocks mode :'''
 +
::this option can either be '''no tcb processing''' , '''process only tcb for exit signal''' or '''process all tcbs along path'''. With process only tcb for exit signal, before activation, the path will look if its exit signal is embedded in some track circuit block, and if it is the case will check that the track circuit block is not occupied and not locked. If it is not the case, path activation will be delayed until the previous conditions are met. When the exit tcb is unoccupied and unlocked, path will be activated but will also lock the tcb name while the path is active. Doing so enables to guarantee that a path is activated only when a tcb embedding the exit signal is not occupied and locking its name enables to prevent other paths to activate while the initial path is active even if there are no common paths objects between the paths. Exit signal tcb are very usefull for terminal station platforms, for through station platforms and for unique track between two several passing places. As several interlocking tower paths from distinct towers can have their exit signal embedded in the same tcb, this facility also enables to do some interlocking between paths form distinct towers. Using the process all tcbs option along path enables to do the same processing for all the tcbs embedding some path objects and not only for the exit signal tcb.
 +
 +
:* '''Path clear option for owned junctions :'''
 +
::this option enable to either restore the junction initial direction (default used by standard it)  or to do not restore junctions initial direction when a path is cleared. This option is available mainly for prototypical behavior as sometimes it is not very prototypical to have a junction having its initial direction restored because a path has been cleared followed by rechanging the direction due to another path being activated. With this option you avoid successive inadequate direction changes for junctions.
 +
 +
:* '''Exclusive sets membership :'''
 +
::exclusive sets membership is an option that has been designed to help protect a crossing of tracks without the need to add some invisible junctions using these junctions as external object reference. When you add an exclusive set name in this field, the path will only be activated if no other paths in any tower with also the same exclusive set name is active. Paths sharing the same exclusive set name cannot be simultaneously active and this works inside the same tower as inside any tower on your route. To protect a crossing of track, you need only to give a unique name to this crossing of track and reference this name as an exclusive set name in all your paths using this crossing of tracks. It is much more easy to use than using invisible junctions with external references in paths.
 +
::You can enter in this field either only one name or several names separated by a comma. Exclusive set name A will be displayed in the field as A. Exclusive set names A , B will be displayed as an exclusive set names list [A,B]. What is important is that you can enter either one name or several names separated by commas. When several names have been listed, the path belongs to all the exclusive set names and will check that no paths active are referencing any of these names before activating the path. This feature is very usefull to protect crossing tracks, and also slips and double-slips.
 +
 +
At the bottom of the header, you have also two links available : the '''restore default options''' link will restore all the default values for the enhanced options for the current path. The '''make current path options default options''' will change the default options in the current tower to be the current path options. Using these options link, it is quite easy to retrieve some path options and to propagate them to some other paths.
 +
 +
===== And now below a few tips on how to use some of the enhanced options =====
 +
 +
::TIP001 - [[Enhanced Interlocking Tower Tip 001 | How to protect paths using crossing, slips, double slips ]]
 +
 +
===== How to ajust the default distance for automatic path selection =====
 +
 +
By default, automatic path selection is called when an incoming train approaches an entry signal at about 0.5 mile. But since version 60 available from DLS in 02/2019, you can adjust (increase or decrease) this default distance by using specific path trigger object ( <kuid2:61392:8121:1> ). When you place a path trigger object, automatic path selection will be called when the incoming train reaches the last path trigger object before the entry signal (the train needs to have the track already set in the correct direction to go to the entry signal). If the path trigger is reached before the standard 0.5 mile distance, automatic path selection will be done with an increased distance from the entry signal. If when the train arrives at the standard distance, the system find there is a path trigger between the train and the entry signal, automatic path selection will be delayed until the train reaches the path trigger, and automatic path selection will be done at a reduced distance from the entry signal. Path trigger works only with EIT and not at all with standard ITs.
 +
 +
===== How to activate easily a path for a train using ITSetPath family driver commands =====
 +
 +
An easy method to activate a path for a train is to use one of the three driver commands ITSetPath (<kuid:61392:8111>) , ITSetPathAndWaitNotRed (<kuid:61392:8112>) or ITSetPathAndWaitActive ( <kuid:61392:8113>). These three driver commands enable the user to choose the interlocking tower and the path to request for the current driver when the driver command is executed. ITSetPath will only request the path activation and will immediately terminates, giving control to the next driver command in the train schedule. ITSetPathAndWaitNotRed will also request the path activation, but will wait until the path has been activated and the entry signal is not red before terminating and giving control to the next command. ITSetPathAndWaitActive will request the path activation and will wait for the path being active but will terminates giving control to the next command even if entry signal is still red. This last command may be usefull to set a path to drive and couple to another consist just after the entry signal.
 +
 +
==== Creating your own enhanced Interlocking tower asset : What are the modifications needed in your asset config.txt file  ====
 +
 +
Like for standard interlocking tower, any scenery asset can be transformed in an enhanced interlocking tower asset by making a few modifications to the config file.
 +
 +
You will find below as an example, taken from the config.txt file for the enhanced trc3 invisible interlocking tower, all the lines you need to have in your own asset config.txt so that your asset becomes an enhanced interlocking tower. Other lines like your asset kuid number, description, username, ... should remain unchanged.
 +
 +
'''List of lines needing to be present for a scenery asset to become an enhanced interlocking tower asset (in SP2 or later) :'''
 +
 +
  <nowiki>
 +
trainz-build                            4.5
 +
kind                                    "interlocking-tower"
 +
script                                  "dummyinterlockingtower.gs"
 +
class                                  "DummyInterlockingTower"
 +
category-class                          "IT"
 +
 +
extensions
 +
{
 +
  generic-61392
 +
  {
 +
    assetid                            "enhancedinterlockingtower"
 +
   
 +
    eitoptions
 +
    {
 +
      displayyellowdisc                0
 +
      pathrequeryonscheduledblocked    1
 +
      trcsupport                        1
 +
      debuglevel                        0
 +
      clearmethod                      1
 +
      checktcb                          1
 +
      resetjunctions                    1
 +
      edityellowdisc                    2
 +
      editpathrequery                  2
 +
      edittrcsupport                    2
 +
      editdebuglevel                    2
 +
      editclearmethod                  2
 +
      editchecktcb                      2
 +
      editresetjunctions                2
 +
      editexclusivesets                2
 +
    }
 +
   
 +
    colors-61392
 +
    {
 +
      cunselect                        "bbf5bb"
 +
      cselect                          "f5bbbb"
 +
      clink                            "ffffff"
 +
      cnrm                              "c0c0c0"
 +
      cwhite                            "ffffff"
 +
      calert                            "ff0000"
 +
    }
 +
  }
 +
}
 +
 +
script-include-table
 +
{
 +
  commondata                            <kuid:61392:4050>
 +
  esvlib                                <kuid:61392:4052>
 +
  eitlib                                <kuid:61392:8190>
 +
  trcitlib                              <kuid:61392:8191>
 +
}
 +
 +
kuid-table
 +
{
 +
  sessvar                              <kuid:-3:10197>
 +
  sessvars                              <kuid:-3:10197>
 +
  commondata                            <kuid2:61392:4050:51>
 +
  esvlib                                <kuid2:61392:4052:4>
 +
  eitlib                                <kuid2:61392:8190:47>
 +
  trcitlib                              <kuid:61392:8191>
 +
  0                                    <kuid:61392:4050>
 +
  1                                    <kuid:61392:8190>
 +
  2                                    <kuid:61392:4052>
 +
}
 +
  </nowiki>
 +
 +
Just only a few comments on some of these mandatory lines in config.txt file :
 +
 +
The trainz-build tag needs to be at least 4.5 for any interlocking tower in SP2 or later. The kind tag should always be "interlocking-tower". The script and class should be "dummyinterlockingtower.gs" and "DummyinterlockingTower" and should respect the case for the class tag. And the category-class tag should be "IT". These tags are mandatory and should not be changed.
 +
 +
In the extensions part, default values for enhanced options are defined and may be changed if you wish to change the default values in your enhanced interlocking tower asset.
 +
 +
displayyellowdisctag is 0 for yellow disc disabled or 1 for yellow disc enabled.
 +
 +
pathrequeryonscheduleblocked should be 0 to disable requery and 1 to enable requery when an ai train has its schedule blocked.
 +
 +
trcsupport should be 1 to support trc system and 0 if not.
 +
 +
debug level should be 0 for no debugging, 1 for log only debugging message and 2 for log and print debugging messages
 +
 +
clear method should be 1 to clear on cancel, 2 for clear on drive, and 101 for clear after last junction. Other values may lead to unexpected results.
 +
 +
checktcb should be 0 for no tcb processing, 1 for process only exit tcb, 2 for process all tcbs along path.
 +
 +
reset junctions should be 0 to avoid reseting junctions direction when a path is cleared and 1 to reset junctions when a path is cleared.
 +
 +
and that's all for default values settings. The following tags will define if an enhanced option is not visible (0), displayed only (1), or displayed and editable (2).
 +
the tags edityellowdisc, editpathrequery, edittrcsupport, editdebuglevel, editclearmethod, editchecktcb, editresetjunctions, editexclusivesets can be set to one of these values (0, 1, 2) to make the enhanced option not visible, displayed in read-only mode, or displayed and editable.
 +
By configuring these extensions tags, an enhanced interlocking tower content creator can choose the default values for an option, and decide if it can be viewed or not, and if the end user can change the default values. For example, if trcsupport is set to 1 and edittrcsupport is set to 0, the tower will have the trc support option enabled, but not displayed and so not updatable by the end user. Using these tags the asset content creator can enforce any of the enhanced options value.
 +
 +
the other tags cunselect, cselect, clink, cnrm, cwhite, calert defines the colors to be used in the interface. You should not normally alter these values, but if you don't like the colors scheme used, you may alter these values to change the colors used in the interface. The string values defined for each tag are only the RGB hexadecimal values for the color to be used for this category of information.
 +
 +
and the last containers script-include-table and kuid-table should be left unchanged for the enhanced interlocking tower to work correctly.

Revision as of 00:00, 19 February 2021

Contents

Postes de Contrôle et Régulation

Version anglaise : Enhanced Interlocking Tower

Help-eit-assets-img01.png


Les Postes de Contrôle et Régulation sont des composants tiers scriptés, qui étendent la notion d'Interlocking Tower au standard N3V avec des fonctionnalités supplémentaires intéressantes. Ceci se fait en rajoutant des pré traitements avant d'appeler les scripts standards N3V et aussi des post traitements. Cette méthode permet de vous proposer des composants compatibles avec les "Interlocking Towers" et supportant des fonctionnalités supplémentaires avancées.

Parmi ces fonctionnalités ajoutées, on trouvera entre autres :

au niveau itinéraire :
  • un itinéraire accepte que son signal de sortie soit aussi un signal d'entrée au sein d'un autre poste de contrôle régulation
  • un itinéraire ne sera enclenché que si il n'y a aucun convoi actuellement présent sur le parcours de l'itinéraire. Si ce n'est pas cas, l'enclenchement sera différé tant qu'il restera un convoi sur le parcours de l'itinéraire.
  • un itinéraire peut être annulé en utilisant une commande conducteur adéquate ou en utilisant la règle de gestion des Postes de Contrôle et Régulation. Pour éviter tout risque de déraillements en cas d'annulation les aiguilles en recouvrement sous un convoi ne seront pas restaurées dans leur direction originelle.
  • un itinéraire peut utiliser différentes méthodes de libération d'un itinéraire. La libération sur fin d'itinéraire ou annulation est la méthode traditionelle utilisée avec les interlocking towers. La libération progressive au fur et à mesure de l'avancement du train permet de libérer les objets pour une autre utilisation avant la libération finale de l'itinéraire. La libération après la dernière aiguille permet de libérer l'itinéraire dés que le train a quité la dernière aiguille.
  • un itinéraire peut optionnellement vérifier la présente d'un TCB (track circuit block) autour du signal de sortie et vérifier si le TCB est occupé ou non. Les TCB sont utiles pour protéger une voie unique ou les voies le long des quais d'une gare voyageur.
  • un itinéraire peut choisir de restaurer ou non ses aiguilles dans leur direction initiale après passage du train.
  • un itinéraire peut optionnellement être membre d'un ensemble exclusif. Dans ce cas, l'enclenchement de l'itinéraire sera différé tant un autre itinéraire fera réfèrence au même ensemble exxclusif.
au niveau du poste de contrôle et régulation :
  • Il est possible d'afficher ou non le symbole disque jaune utilisé par N3V.
  • Il est possible de choisir un mode de possession staatique ou dynamique. Avec le mode statique tous les objets de l'itinéraire sont possédés par le poste de contrôle commande pour toute la session. En mode dynamique, seul le signal d'entrée est possédé pour toute la durée de la session ; les autres signaux et objets le long de l'itinéraire seront pris en possession uniquement pendant la durée où l'itinéraire est enclenché.
  • compatibilité trc : il est possible de choisir au niveau du poste de contrôle régulation si l'on gère les passages à nuveau TRC au niveau de la règle TRC ou au niveau du poste.
  • niveau de deboggage : Cette option à destination des développeurs permet de choisir entre l'absence de toute log et un logging plus complet.
  • Les Postes de Contrôle Régulation permette via l'utilisation d'un composant additionnel adéquat eit pathtrigger d'ajuster à la baisse ou à la hausse la distance avant déclenchement d'un nouvel itinéraire.

Poste de Contrôle et de Régulation : Comment les utiliser ?

Pour utiliser un Poste de Contrôle et de Régulation, vous devez placer sur votre carte un objet Poste de Contrôle et Régulation comme le PCR - Poste de Contrôle Régulation TRC3 invisible <kuid2:61392:8101:76>. D'autres créateurs ont mise à disposition sur la DLS d'autres objets de type Poste de Contrôle Régulation ou Interlocking Tower. En fait tout objet de type "scenery" peut être transformé en un objet Poste de Contrôle Régulation par ajout de la configuation adéquate dans son fichier de configuration.

Liste au 18/02/2021 de tous les Postes de Contrôle Régulation disponible sur la DLS :

PCR - Poste de Contrôle Régulation TRC3 invisible <kuid2:61392:8101:47> by pguy

ITE SB Nameable 1 <kuid:182010:100397> by peterwhite

ITE SB Nameable 2 <kuid:182010:100403> by peterwhite

ITE SB Nameable 3 <kuid:182010:100410> by peterwhite

ITE SB Nameable 5 <kuid:182010:100401> by peterwhite

ITE SB Nameable 6 <kuid:182010:100407> by peterwhite

ITE SB Nameable 7 <kuid:182010:100402> by peterwhite

ITE SB Nameable 8 <kuid:182010:100398> by peterwhite

ITE SB Nameable 9 <kuid:182010:100408> by peterwhite

ITE SB Nameable 10 <kuid:182010:100411> by peterwhite


Après avoir placé sur votre carte le poste de contrôle régulation que vous voulez utiliser, vous n'avez plus qu'à éditer les propriétés de l'objet en cliquant dessus pour ouvrir la fenêtre standard d'édition des propriétés du Poste de Contrôle Régulation. Pour cet objet, l'ensemble des options à configurer sera dans le paneau supérieur de la fenêtre des propriétés.


Edition d'un Poste de Contrôle Régulation : les options disponibles dans la fenêtre d'édition


Les options disponibles dans le paneau supérieur sont :

  • tower display yellow disc option :
by clicking on the link on the right, you can either choose display yellow disc enabled or disabled
  • tower path requery option :
this option is on how to process AI trains with schedule blocked. It can either be try requery path on schedule blocked or do not requery path on schedule blocked. With requery path option active, when an AI train has its schedule blocked, the enhanced IT will try to release unused paths (paths owned but not entered) to enable some other paths to be activated. The unused paths released are requeued for later activation. This standard processing done in standard IT may help to find a solution to some AI schedule blocked, but may have some side effects as some activated path may be cancelled before being later reactivated. If you do not want this behavior, just change the option to do not requery path on schedule blocked and no processing will be done when an AI train has its schedule blocked.
  • tower dynamic ownership option (available since release 47 march 2018) :
this option is on how the tower will take ownership of all its paths objects (entry signal, exit signal, other signals, junctions, crossings, ...). Entry signals are always owned by the tower for all the session duration whatever the option choosen. With static ownership, it is the same for all paths objects for which ownership will also be taken for all the session duration. With dynamic ownership, path object ownership is taken only on path activation and will be released when the path returns to path not set state. With dynamic ownership, a path object belonging to one or several paths currently not activated is no longer owned by the tower and can be used by other components for manual operation. This may be usefull for sidings where you can have the junctions unlocked available for manual operations when no paths using this junction are active.
  • tower trc compatible mode :
when this option is active, crossings conformant to trc system specification will not be managed by interlocking tower. Trc crossing objects will be skipped with no tower ownership and will remain managed by the trc system. if the option is inactive, interlocking tower will manage all the crossings along its path.
  • tower debug level :
tower debug level option is an option available that help session developper to understand interlocking tower problems. Interlocking tower have an integrated debugging facility by default disabled. By selecting only log debug information or log and print debugging information, you will activate the debugging facility which may help to understand some conflicting or deadlock problems using interlocking tower.

at the bottom of the header area, you will find a link Restore default options that enables to reset all the current enhanced options to the default values defined by the enhanced tower asset content creator.

Editing enhanced Interlocking tower path : options available in the path editor window

Help-eit-assets-img03.png


The available options in the header at the path level are :

  • Path clear method to use :
you can here select the path clear method to be used between Clear on cancel (when a path is either complete or cancelled) , Clear on drive (following train progress along the path) and Clear after last junction (when the train leaves the last junction along the path). Clear on cancel is the standard IT clear method that can still be selected. Clear on cancel will release path objects locks when the owning train leaves the path object. With clear on drive, the path will still be cleared and cancelled only when the train will leaves the exit signal, but path objects are unlocked as soon as the train has left them and are made available for other conflicting paths to be activated earlier. Clear after last junction will clear and cancel the path as soon as the owning train has left the last junction along the path and will not wait for the train to reach and leave the exit signal. Clear on last junction may be an interesting option for path leading to an and of track with a buffer. You can use the buffer as the exit signal, and though the owning train will never leave the buffer exit signal, the path will be cleared as soon as the train will have left the last junction along the path.
  • Path track circuit blocks mode :
this option can either be no tcb processing , process only tcb for exit signal or process all tcbs along path. With process only tcb for exit signal, before activation, the path will look if its exit signal is embedded in some track circuit block, and if it is the case will check that the track circuit block is not occupied and not locked. If it is not the case, path activation will be delayed until the previous conditions are met. When the exit tcb is unoccupied and unlocked, path will be activated but will also lock the tcb name while the path is active. Doing so enables to guarantee that a path is activated only when a tcb embedding the exit signal is not occupied and locking its name enables to prevent other paths to activate while the initial path is active even if there are no common paths objects between the paths. Exit signal tcb are very usefull for terminal station platforms, for through station platforms and for unique track between two several passing places. As several interlocking tower paths from distinct towers can have their exit signal embedded in the same tcb, this facility also enables to do some interlocking between paths form distinct towers. Using the process all tcbs option along path enables to do the same processing for all the tcbs embedding some path objects and not only for the exit signal tcb.
  • Path clear option for owned junctions :
this option enable to either restore the junction initial direction (default used by standard it) or to do not restore junctions initial direction when a path is cleared. This option is available mainly for prototypical behavior as sometimes it is not very prototypical to have a junction having its initial direction restored because a path has been cleared followed by rechanging the direction due to another path being activated. With this option you avoid successive inadequate direction changes for junctions.
  • Exclusive sets membership :
exclusive sets membership is an option that has been designed to help protect a crossing of tracks without the need to add some invisible junctions using these junctions as external object reference. When you add an exclusive set name in this field, the path will only be activated if no other paths in any tower with also the same exclusive set name is active. Paths sharing the same exclusive set name cannot be simultaneously active and this works inside the same tower as inside any tower on your route. To protect a crossing of track, you need only to give a unique name to this crossing of track and reference this name as an exclusive set name in all your paths using this crossing of tracks. It is much more easy to use than using invisible junctions with external references in paths.
You can enter in this field either only one name or several names separated by a comma. Exclusive set name A will be displayed in the field as A. Exclusive set names A , B will be displayed as an exclusive set names list [A,B]. What is important is that you can enter either one name or several names separated by commas. When several names have been listed, the path belongs to all the exclusive set names and will check that no paths active are referencing any of these names before activating the path. This feature is very usefull to protect crossing tracks, and also slips and double-slips.

At the bottom of the header, you have also two links available : the restore default options link will restore all the default values for the enhanced options for the current path. The make current path options default options will change the default options in the current tower to be the current path options. Using these options link, it is quite easy to retrieve some path options and to propagate them to some other paths.

And now below a few tips on how to use some of the enhanced options
TIP001 - How to protect paths using crossing, slips, double slips
How to ajust the default distance for automatic path selection

By default, automatic path selection is called when an incoming train approaches an entry signal at about 0.5 mile. But since version 60 available from DLS in 02/2019, you can adjust (increase or decrease) this default distance by using specific path trigger object ( <kuid2:61392:8121:1> ). When you place a path trigger object, automatic path selection will be called when the incoming train reaches the last path trigger object before the entry signal (the train needs to have the track already set in the correct direction to go to the entry signal). If the path trigger is reached before the standard 0.5 mile distance, automatic path selection will be done with an increased distance from the entry signal. If when the train arrives at the standard distance, the system find there is a path trigger between the train and the entry signal, automatic path selection will be delayed until the train reaches the path trigger, and automatic path selection will be done at a reduced distance from the entry signal. Path trigger works only with EIT and not at all with standard ITs.

How to activate easily a path for a train using ITSetPath family driver commands

An easy method to activate a path for a train is to use one of the three driver commands ITSetPath (<kuid:61392:8111>) , ITSetPathAndWaitNotRed (<kuid:61392:8112>) or ITSetPathAndWaitActive ( <kuid:61392:8113>). These three driver commands enable the user to choose the interlocking tower and the path to request for the current driver when the driver command is executed. ITSetPath will only request the path activation and will immediately terminates, giving control to the next driver command in the train schedule. ITSetPathAndWaitNotRed will also request the path activation, but will wait until the path has been activated and the entry signal is not red before terminating and giving control to the next command. ITSetPathAndWaitActive will request the path activation and will wait for the path being active but will terminates giving control to the next command even if entry signal is still red. This last command may be usefull to set a path to drive and couple to another consist just after the entry signal.

Creating your own enhanced Interlocking tower asset : What are the modifications needed in your asset config.txt file

Like for standard interlocking tower, any scenery asset can be transformed in an enhanced interlocking tower asset by making a few modifications to the config file.

You will find below as an example, taken from the config.txt file for the enhanced trc3 invisible interlocking tower, all the lines you need to have in your own asset config.txt so that your asset becomes an enhanced interlocking tower. Other lines like your asset kuid number, description, username, ... should remain unchanged.

List of lines needing to be present for a scenery asset to become an enhanced interlocking tower asset (in SP2 or later) :

 
trainz-build                            4.5
kind                                    "interlocking-tower"
script                                  "dummyinterlockingtower.gs"
class                                   "DummyInterlockingTower"
category-class                          "IT"

extensions
{
  generic-61392
  {
    assetid                             "enhancedinterlockingtower"
    
    eitoptions
    {
      displayyellowdisc                 0
      pathrequeryonscheduledblocked     1
      trcsupport                        1
      debuglevel                        0
      clearmethod                       1
      checktcb                          1
      resetjunctions                    1
      edityellowdisc                    2
      editpathrequery                   2
      edittrcsupport                    2
      editdebuglevel                    2
      editclearmethod                   2
      editchecktcb                      2
      editresetjunctions                2
      editexclusivesets                 2
    }
    
    colors-61392
    {
      cunselect                         "bbf5bb"
      cselect                           "f5bbbb"
      clink                             "ffffff"
      cnrm                              "c0c0c0"
      cwhite                            "ffffff"
      calert                            "ff0000"
    }
  }
}

script-include-table
{
  commondata                            <kuid:61392:4050>
  esvlib                                <kuid:61392:4052>
  eitlib                                <kuid:61392:8190>
  trcitlib                              <kuid:61392:8191>
}

kuid-table
{
  sessvar                               <kuid:-3:10197>
  sessvars                              <kuid:-3:10197>
  commondata                            <kuid2:61392:4050:51>
  esvlib                                <kuid2:61392:4052:4>
  eitlib                                <kuid2:61392:8190:47>
  trcitlib                              <kuid:61392:8191>
  0                                     <kuid:61392:4050>
  1                                     <kuid:61392:8190>
  2                                     <kuid:61392:4052>
}
  

Just only a few comments on some of these mandatory lines in config.txt file :

The trainz-build tag needs to be at least 4.5 for any interlocking tower in SP2 or later. The kind tag should always be "interlocking-tower". The script and class should be "dummyinterlockingtower.gs" and "DummyinterlockingTower" and should respect the case for the class tag. And the category-class tag should be "IT". These tags are mandatory and should not be changed.

In the extensions part, default values for enhanced options are defined and may be changed if you wish to change the default values in your enhanced interlocking tower asset.

displayyellowdisctag is 0 for yellow disc disabled or 1 for yellow disc enabled.

pathrequeryonscheduleblocked should be 0 to disable requery and 1 to enable requery when an ai train has its schedule blocked.

trcsupport should be 1 to support trc system and 0 if not.

debug level should be 0 for no debugging, 1 for log only debugging message and 2 for log and print debugging messages

clear method should be 1 to clear on cancel, 2 for clear on drive, and 101 for clear after last junction. Other values may lead to unexpected results.

checktcb should be 0 for no tcb processing, 1 for process only exit tcb, 2 for process all tcbs along path.

reset junctions should be 0 to avoid reseting junctions direction when a path is cleared and 1 to reset junctions when a path is cleared.

and that's all for default values settings. The following tags will define if an enhanced option is not visible (0), displayed only (1), or displayed and editable (2). the tags edityellowdisc, editpathrequery, edittrcsupport, editdebuglevel, editclearmethod, editchecktcb, editresetjunctions, editexclusivesets can be set to one of these values (0, 1, 2) to make the enhanced option not visible, displayed in read-only mode, or displayed and editable. By configuring these extensions tags, an enhanced interlocking tower content creator can choose the default values for an option, and decide if it can be viewed or not, and if the end user can change the default values. For example, if trcsupport is set to 1 and edittrcsupport is set to 0, the tower will have the trc support option enabled, but not displayed and so not updatable by the end user. Using these tags the asset content creator can enforce any of the enhanced options value.

the other tags cunselect, cselect, clink, cnrm, cwhite, calert defines the colors to be used in the interface. You should not normally alter these values, but if you don't like the colors scheme used, you may alter these values to change the colors used in the interface. The string values defined for each tag are only the RGB hexadecimal values for the color to be used for this category of information.

and the last containers script-include-table and kuid-table should be left unchanged for the enhanced interlocking tower to work correctly.

Personal tools