From railML 3 Wiki
Jump to navigation Jump to search




This element does not appear in railML® 3.2 within the IL subschema. It is available only in railML® 3.1. Do not hesitate to contact for further questions.

Autoexport from the XML-Schema for element IL:atpDevice of railML® version 3.1
Documentation not with railML3.1
Subschema interlocking
Parents* atpDevices
Children any (0..*), atpType (1..1), designator (0..1), device (1..1), entrySignal (1..2), exitSignal (1..2)
  • 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}}); compare: Dev:Identities
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.

Changes 3.1→3.2

Removed with version 3.2.


Best Practice / Examples

Systems for Automatic Train Protection (ATP) can be intermittently or continuously. The latter ones are systems like LZB, TVM or ETCS, which comprise a control unit independent of the interlocking. This control unit is steering the track devices of the system. The intermittent systems have devices directly controlled from interlocking module or indirectly via a Lineside Electronic Unit (LEU). Such LEU derives the steering information from the control circuits the interlocking uses for signals or other elements. The principles of ATP devices are shown in the figure below.


  • <atpType> – reference not yet implemented!
  • <atpDevice> – reference not yet implemented!
  • <exitSignal> – reference not yet implemented!
  • <entrySignal> – reference not yet implemented!

Additional Information


This element was deleted in 3.2.

Open Issues