Template:LogicalDevices: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
No edit summary
No edit summary
Line 1: Line 1:
{{note|There can be various logical devices like {{tag|IL|keyLockIL}} and {{tag|IL|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 {{doc|IL|keyLockIL}} or {{doc|IL|genericDetector}}. The common attributes and elements are:
{{note|There can be various logical devices like {{tag|IL|keyLockIL}} and {{tag|IL|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 {{doc|IL|keyLockIL}} or {{doc|IL|genericDetector}}. The common attributes and elements are:
*{{@|description}} – The string element takes a more detailed description of the logic. This is for information of the user only.
*{{@|description}} – The string element takes a more detailed description of the logic. This is for information of the user only.
*{{tag|IL|takesControlOf}}{{doc|IL| }}– 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.
*{{tag|IL|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.
*{{tag|IL|hasInterface}}– The reference to the physical interface of the logical device to the interlocking.
*{{tag|IL|hasInterface}} – The reference to the physical interface of the logical device to the interlocking.
*{{tag|IL|refersTo}}- The reference to the physical device like {{tag|IS|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.<br>The particular instantiation extends the abstract type of '''logicalDevice''' by some additional elements and attributes.<br>There are further logical devices conceivable that {{lila|are not yet implemented}}: tunnel gates, bascule bridges or water barriers.}}
*{{tag|IL|refersTo}} - The reference to the physical device like {{tag|IS|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.<br>The particular instantiation extends the abstract type of '''logicalDevice''' by some additional elements and attributes.<br>There are further logical devices conceivable. Currently the {{tag|IL|movableBridge}} is implemented using this abstract class.}}

Revision as of 14:56, 27 May 2022

🗒️ 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:
  • @description – The string element takes a more detailed description of the logic. This is for information of the user only.
  • <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.
  • <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.