Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 3 railML 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 3railML 3
  • Issues
  • #548
Closed
Open
Issue created Jun 06, 2024 by IS Coordination@coordination.ISMaintainer

Modelling Lineside Electronic Units (ETCS L1)

Background

For including ETCS Level 1 in the railML 3 data model, the need for modelling Lineside Electronic Units (LEU) was discussed. In particular, the following requirements have been collected:

  1. An infrastructure element for the LEU is needed.
  2. A LEU should be able to connect with one or more signals.
  3. A LEU should be able to connect with one or more balise groups.
  4. A LEU should be able to connect with one or more balises.
  5. A LEU should be able to connect with one or more euroloops.
  6. The signal aspects to be evaluated by the LEU should be provided.
  7. For each signal aspect to be evaluated by the LEU, the relevant route should be provided
  • target signal of the movement authority
  • required position of passed switches
  • signals between start and target signal of the route (optional)

Links

  • Forum discussion:
    • Christian Rahmig, 06.06.2024: https://www.railml.org/forum/index.php?t=msg&th=952&start=0&
    • https://www.railml.org/forum/index.php?t=msg&goto=3250&&srch=loop#msg_3250
  • Gitlab tickets:
    • #548
  • Wiki documentation: https://wiki3.railml.org/index.php?title=Dev:Euroloop

Proposed solution railML 3.3

  • Introduce a new functional infrastructure element \\linesideElectronicUnitIS within its container \\linesideElectricUnitsIS.
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToSignal with attribute @ref to link from LEU to signal. linesideElectronicUnitIL shall refer with one element [0..*] to SignalIL/hasLamp [#548 (comment 9679)]
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToBaliseGroup with attribute @ref to link from LEU to balise group.
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToBalise with attribute @ref to link from LEU to (single) balise.
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToEuroloop with attribute @ref to link from LEU to euroloop.
  • Introduce a new interlocking element \\linesideElectronicUnitIL with child element \\refersTo to link \\linesideElectronicUnitIS.
  • Define repeatable child element \\linesideElectronicUnitIL\evaluatesSignalAspect with attribute @ref to link a signal aspect that shall be evaluated by the LEU.
Edited Jan 17, 2025 by CO Onto
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany