IL:hasTVDresetStrategy

From railML 3 Wiki
Revision as of 17:47, 22 January 2020 by Documentation (talk | contribs) ({{examples}}: Einrückungen)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:hasTVDresetStrategy of railML® version 3.2
Documentation Classification of TVD section reset strategies
Subschema interlocking
Parents* usesTypes
Children any (0..*), designator (0..*)
Attributes:
  • resetStrategy: The classification of the reset strategy. (obligatory; xs:string)
Possible values:
  • unconditionalReset
  • sweepRunWithoutConfirmation
  • sweepRunWithConfirmation
  • procedure
  • conditionalReset,

  • id: unique identifier (optional; 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}\})
*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:hasTVDresetStrategy of railML® version 3.1
Documentation Classification of TVD section reset strategies
Subschema interlocking
Parents* usesTypes
Children any (0..*), designator (0..1)
Attributes:
  • resetStrategy: The classification of the reset strategy. (obligatory; xs:string)
Possible values:
  • unconditionalReset
  • sweepRunWithoutConfirmation
  • sweepRunWithConfirmation
  • procedure
  • conditionalReset,

  • 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}\})
*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.

Semantics

Best Practice / Examples

Railway tracks are divided in logical sections by technical means for detecting the vacancy of the related section. The typical technologies are track circuits or axle counter. They deliver mainly the status information vacant, occupied or failed. In case of a failure the particular sections needs to be reset, i.e. declared clear of any railway vehicle. The individual IM have various strategies for such a reset. In consequence the interlocking can attribute a particular TVD section with the necessary commands. The functional details are specific of the equipment manufacture and not needed here. Thus, a generic classification shall be sufficient. The list of TVD reset strategies in <hasTVDresetStrategy> allows the following possibilities:

  • unconditionalReset – The section will be reset on command without any conditions, i.e. after the reset command was accepted by the interlocking system the TVD section is set to clear/vacant status.
  • conditionalReset – The section will only be reset, if some conditions are fulfilled. In case of several variants one can include the condition information in the <designator> of the reset strategy. Such conditions can be that the TVD section must be failed or the last counting action of delimiting detection points was “in”.
  • sweeprunWithoutConfirmation – Especially for axle counter sections a sweep run (de: Bügelfahrt) can be requested. Although the TVD section reset takes place, with receipt of the operator command to the axle counter unit the interlocking keeps it logically failed until a correct occupation and clearance sequence from a passing train is notified from the axle counter. In this case the section is reset immediately without any further operator action.
  • sweeprunWithConfirmation – Here a sweep run is also requested. However, after the notification of the correct occupation and clearance sequence the operator needs to confirm the result by command before the section is reset within the interlocking.
  • procedure – This is a placeholder for any other procedure to reset a TVD section.


The definition here in <hasTVDresetStrategy> is rather straight forward, as one would give an @id and possibly a <designator> related to the used value from genericResetStrategyList.

<hasTVDresetStrategy id="rst_uc" resetStrategy="unconditionalReset">
        <designator register="_SimpleRegister" entry="unconditional reset"/> 
</hasTVDresetStrategy> 
<hasTVDresetStrategy id="rst_cd" resetStrategy="conditionalReset">
        <designator register="_SimpleRegister" entry="conditional reset"/> 
</hasTVDresetStrategy> 
<hasTVDresetStrategy id="rst_swr_noconf" resetStrategy="sweepRunWithoutConfirmation">
        <designator register="_SimpleRegister" entry="sweeprun without confirmation"/> 
</hasTVDresetStrategy> 
<hasTVDresetStrategy id="rst_swr_conf" resetStrategy="sweepRunWithConfirmation">
        <designator register="_SimpleRegister" entry="sweeprun with confirmation"/> 
</hasTVDresetStrategy>

Additional Information

Notes

Open Issues