Autoexport from the XML-Schema for element IL:routeActivationSection of railML® version 3.3 | |
| Description | Description of the route activation, i.e. automatic setting or locking when the route entry is approached. |
| Subschema | interlocking |
| Parents* | |
| Children |
designator (0..*), elementState (0..*), activationSection (1..*) |
Attributes:
| |
| *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element. | |
IL:routeActivationSection
Jump to navigation
Jump to search
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:routeActivationSection of railML® version 3.2 | |
| Description | Description of the route activation, i.e. automatic setting or locking when the route entry is approached. |
| Subschema | interlocking |
| Parents* | |
| Children |
designator (0..*), activationSection (1..*) |
Attributes:
| |
| *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element. | |
Autoexport from the XML-Schema for element IL:routeActivationSection of railML® version 3.1 | |
| Description | Description of the route activation, i.e. automatic setting or locking when the route entry is approached. |
| Subschema | interlocking |
| Parents* | |
| Children |
designator (0..1), activationSection (1..*), any (0..*) |
Attributes:
| |
| *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element. | |
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The children have been changed.
The attributes have been changed.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
The route activation stands for two different scenarios. Commonly, the signalman or control system calls a route, which the interlocking then prepares. The route is activated (=locked) either after a given delay but more generally after an activation section turns occupied. This indicates an approaching train and the route shall not be released without special precautions. In the second scenario the automatic route setting is triggered as defined in route activation, i.e. on occupation of the referred track section the interlocking is triggered to set the related route. Usually the definition of the activation data is independently of the scenario, which it is used for.
A route may refer to a route activation section, which contains:
- @delayForLock – This is the time between the moment the approach section turns from vacant to occupied and the moment the interlocking locks the route.
- @automaticReleaseDelay – This is time between the moment that the route is locked because the approach section turned occupied, and the possible release of the route. This delay for automatic delay would typically be used when an approach train stops in an approach section but fails to enter the route.
- <activationSection> – This is the reference to the TVD section activating the route when this section turns from vacant to occupied. The activation means setting the route or lock it due to the approaching train.
The example shows the route is activated when the section in rear of the route entry is occupied.
<routeActivationSection id="rt_act01" delayForLock="PT2S" automaticReleaseDelay="PT5S">
<designator register="_SimpleRegister" entry="activation Route_68N1_69A"/>
<activationSection ref="A02T"/>
</routeActivationSection>