Search results
Jump to navigation
Jump to search
- <controlsRoute> – This is the reference to any route the interlocking controls. <controlsCombinedRoute> – This is the reference to any route combination the interlocking6 KB (597 words) - 13:58, 21 August 2021
- from train traffic. There is normally no intention for any train movement inside it. If there are any movable elements released for local operation this will3 KB (476 words) - 19:35, 29 January 2020
- devices, e.g. button panel near a switch. These assets are not available for any normal operation by the interlocking operator. The activation is done from3 KB (452 words) - 05:55, 18 April 2022
- attributes in the element and put the semantics there. Otherwise use the xs:anyAttribute mechanism. The use of this Wrong style prevents certification of5 KB (463 words) - 12:22, 3 November 2023
- – This is the reference to any <systemAsset>, which can be controlled from this <controller>. This will especially cover any system assets, which are only4 KB (460 words) - 05:23, 18 April 2022
- Autoexport from the XML-Schema for element XS:any of railML® version 3.2 Documentation provide an extension point for non-railML elements in foreign506 bytes (4 words) - 17:35, 20 April 2020
- meaning “expect any kind of proceed” at next signal. proceed – This is used for any aspect indicating the allowance to continue running without any speed restrictions8 KB (1,085 words) - 10:48, 10 November 2023
- hotWheelBox – The detector detects any hot axle box of railway vehicles. intrusion – The detector monitors the access doors to any equipment cabinet or room in2 KB (273 words) - 14:47, 24 January 2020
- 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 that shall5 KB (573 words) - 12:09, 28 May 2022
- applies to any command which does not need special attention and has full technical safety by the interlocking. vital - The vital level applies to any command2 KB (255 words) - 15:33, 29 October 2023
- @selfTestToleranceTime – The duration gives the time the self-test needs to run and any outputs from the detector during it shall be tolerated. @selfTestInterval2 KB (218 words) - 19:17, 29 January 2020
- belongs to from operational point of view. <hasCommand> - The reference to any predefined operator command, which can be used with this element. For details3 KB (405 words) - 15:00, 27 May 2022
- specific data. The rollingstock schema provides container for all data about any kind of rail vehicles including locomotives, multiple units, passenger and3 KB (458 words) - 17:20, 29 November 2023
- 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 reset4 KB (406 words) - 17:47, 22 January 2020
- and can be passed by any vehicle. @localOperated - This gives information, whether the derailer is locally operated independent of any <signalBox>. electrical5 KB (484 words) - 12:44, 27 May 2022
- combination with a special route type. <hasSlaveLock> - This is the reference to any dependent lock that can be used once this master lock is released.4 KB (531 words) - 19:18, 29 January 2020
- belongs to from operational point of view. <hasCommand> - The reference to any predefined operator command, which can be used with this element. For details2 KB (204 words) - 14:43, 27 May 2022
- defining the zone is different. <canBeControlledBy> – This is the reference to any controller, i.e. operator/train dispatcher place, which can use the zone for1 KB (151 words) - 19:42, 29 January 2020
- of railML® version 3.2 UML-visualization of IL Documentation reference to any detector and its state inside or outside the work zone required for use Subschema518 bytes (9 words) - 18:49, 19 December 2019
- to any level crossing and its state inside the work zone required for use Subschema interlocking Parents* localOperationArea, workZone Children any (0523 bytes (9 words) - 18:49, 19 December 2019