Search results

– IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page   If you want to reactivate your inactive use case

The block signal is used on open line at the start of a block route. blockInterface - This signal is in most cases a virtual signal used to transfer the actual

value is used in case of any TVD section of the route is also used by the conflicting one. ConflictingHeadProtection – This value is used in case any signal

</relatedDerailerInPosition> </hasPositionRestriction> </switchIL> </switchesIL> <derailersIL> <derailerIL returnsToPreferredPosition="true" id="dr_der01" isKeyLocked="false"

modelled in <levelCrossingIL>. In order to avoid ambiguity with the infrastructure element the related type is called levelCrossingIL in railML interlocking

Current UML visualization A list of use cases for railML's interlocking scheme can be found here Category:Use_case_(IL). Interlocking Concepts — explanations

is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop or just a train detection device when

<hasExitSignal> – This is the reference to a <signalIL> which protects the exit from this TVD section. It shall be used in case @isBerthingTrack is set to true. Within

route lock is only applied when a train is approaching the route. In that case this time is the minimum required before the final route lock can be applied

infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForIL> is not only a collection

in infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForInterlocking>

</relatedDerailerInPosition> </hasPositionRestriction> </switchIL> </switchesIL> <derailersIL> <derailerIL returnsToPreferredPosition="true" id="dr_der01" isKeyLocked="false"

position. In case of switch actuators connected to the crossing for changing its position the attribute @numberOfFrogSwitchActuators shall be used to identify

tunnelGateIL is installed at tunnel portals or within the tunnel to fulfill various purposes. When installed at the portals they are mainly used to control

conflictingHeadProtection: This value is used in case any signal that shall provide flank/head protection to either route is used as route destination for the other

conditions to conclude a train is approaching the level crossing. In first case this happens when the train crosses a detection point, i.e. an insulated

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

<refersTo> – This is the reference to the start element of the route. In most cases this is a signal. Preferable the reference shall be made to the element with

element. @bitNr – This is the order number of the command in the list. In case of transmission as complete bitmask it defines the bit position in the byte

released for removal. The key is a simple mean of authorisation transfer as its use allows the manual operation of a moveable element. The lock with control from