The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Introduction
Documentation
Syntax
|
|
| Documentation
|
One or more TVD sections as part of the route which can be released in a group in rear of passing train.
|
| Subschema
|
interlocking
|
| Parents*
|
routeReleaseGroupsRear
|
| Children
|
belongsToOperationalPoint (0..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), hasTvdSection (0..*), objectName (0..*)
|
Attributes:
- delay: Duration after which the IL releases the partial route. Starts counting from the moment that all the conditions for release are fulfilled. This delay is engineered in static data. If not defined, the IL releases the group without delay.
If the route has only one route release group then the set of TVD sections in the route is released en bloc with the delay given here. (optional; xs:duration),
- typicalDelay: Duration after which the partial route is typically released. Use this delay for simulation purposes. Starts counting from the moment that the interlocking has received all conditions for the release. E.g. TVD sections in the group have been vacated, timers expired. (optional;
xs:duration),
- elementNumber: element number of the object for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- id: unique identifier (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*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.
|
|
|
| Documentation
|
One or more TVD sections as part of the route which can be released in a group in rear of passing train.
|
| Subschema
|
interlocking
|
| Parents*
|
routeReleaseGroupsRear
|
| Children
|
any (0..*), designator (0..1), hasTvdSection (0..*)
|
Attributes:
- delay: Duration after which the IL releases the partial route. Starts counting from the moment that all the conditions for release are fulfilled. This delay is engineered in static data. If not defined, the IL releases the group without delay.
If the route has only one route release group then the set of TVD sections in the route is released en bloc with the delay given here. (optional; xs:duration),
- typicalDelay: Duration after which the partial route is typically released. Use this delay for simulation purposes. Starts counting from the moment that the interlocking has received all conditions for the release. E.g. TVD sections in the group have been vacated, timers expired. (optional;
xs:duration),
- id: unique identifier (optional;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*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
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
| 🗒️
|
- Partial Route
The elements of a route are automatically released after use by a train. This release can be for the whole route at once or parts of it. The trigger for release is the clearing of TVD sections after sequential occupation. Thus the TVD section are of interest for release groups as all other elements are indirectly included in such groups. If one or more TVD section is released in a group, the characteristics are detailed as partialRoute. However, if the interlocking in general releases each individual TVD section after use the release groups can be omitted.
The instantiation extends the abstract type of partialRoute by some additional elements and attributes.
The abstract class contains
- @delay – Duration after which the interlocking releases the partial route. Starts counting from the moment that all the conditions for release are fulfilled. This delay is engineered in static data. If not defined, the interlocking releases the group without delay. If the route has only one route release group then the set of TVD sections in the route is released en bloc with the delay given here.
- @typicalDelay – Duration after which the partial route is typically released. Use this delay for simulation purposes. Starts counting from the moment that the interlocking has received all conditions for the release. E.g. TVD sections in the group have been vacated, timers expired.
- <hasTvdSection> – The reference to the TVD section contained in the release group. There can be more than one section referred to.
|
|
|
Release groups are typically a list of TVD sections to be released as a unit in rear of the passing train. The TVD sections of one group may cover only a part of a route. These release groups are necessary if several elements within the route are to be released together, i.e. each one is cleared by the passing train. A good example is a pair of coupled switches. They are kept in the route until both of them are cleared.
The route lists each of its release groups in <hasReleaseGroup>. However, this is only a reference to the instantiations of partialRoute for a particular routeReleaseGroup as defined in <knowsPartialRoute>. The release groups are only referenced in the route definition as shown here.
<hasReleaseGroup ref="prt02"/>
<hasReleaseGroup ref="prt03"/>
The related details of the release groups are defined in the known assets.
<routeReleaseGroupRear delay="PT1S" id="prt02" typicalDelay="PT2S">
<designator register="_SimpleRegister" entry="tm_A02T"/>
<hasTvdSection ref="A02T"/>
</routeReleaseGroupRear>
<routeReleaseGroupRear delay="PT10S" id="prt03" typicalDelay="PT7S" >
<designator register="_SimpleRegister" entry="tm_A68W02T"/>
<hasTvdSection ref="A68W02T"/>
</routeReleaseGroupRear>
This extract show the combination of two sections within one release group.
<hasReleaseGroup ref="prt02-03"/>
…
<routeReleaseGroupRear delay="PT1S" id="prt02-03" typicalDelay="PT2S">
<designator register="_SimpleRegister" entry="tm_A02T+A68W02T"/>
<hasTvdSection ref="A02T"/>
<hasTvdSection ref="A68W02T"/>
</routeReleaseGroupRear>
Additional Information
Notes
Open Issues