| 🗒️
|
There can be various logical devices like <keyLockIL> and <genericDetector>, which provide their state as input to the interlocking. Depending on their use it is also possible to send particular information from the interlocking to the logical device in order to provoke a specific reaction. It is an abstract class extended by the particular instances of it like keyLockIL or genericDetector. The common attributes and elements are:
- @elementNumber - A positive integer number unique within one <signalBox> to index the element in internal lists of engineering data.
- @id - The unique identifier used to reference this element within railML.
- @description – The string element takes a more detailed description of the logic. This is for information of the user only.
- <designator> - A coded name as per a specified register for the asset.
- <assetName> - A name for the asset in a given language.
- <belongsToOperationalPoint> - The reference to an <operationalPoint> this device belongs to from operational point of view.
- <hasCommand> - The reference to any predefined operator command, which can be used with this element. For details refer to <hasOperatorCommand>.
- <hasIndication> - The reference to any predefined indication on HMI, which is used with this element. For details refer to <hasHmiIndication>.
- <takesControlOf> – This is the reference to a movable element which can be controlled with the lock. In case of a detector, it is used as reference to any track asset, which is related to the logical device.
- <hasInterface> – The reference to the physical interface of the logical device to the interlocking. For details refer to <interface>.
- <refersTo> - The reference to the physical device like <keyLockIS> in the infrastructure. This element is optional as some detectors may not have a corresponding element in the infrastructure because they are not located at the track.
The particular instantiation extends the abstract type of logicalDevice by some additional elements and attributes.
There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.
|
|
|