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
  • #498
Closed
Open
Issue created Mar 18, 2022 by IS Coordination@coordination.ISMaintainer

Document the functional balise group types

Description

Enum values need to be documented in UML.

Background

Links

  • Forum discussion
  • Git issues
    • #366 (closed)
    • #498 (closed)
  • Wiki documentation

Proposed solution railML 3.2

attribute <baliseGroup/functionalType> specifies the functional type of a balise group using @value with possible values (extendable list):

  • "announcementLevelTransition" (In relation to this balise group, at least the UNISIG Packet 41 including D_LEVELTR < 32767 will be transmitted to the train (via balise: ETCS L1 or L2 or via radio: ETCS L2 only) for the mileageDirection valid for this function.),
  • "border" (In relation to this balise group, at least the UNISIG Packet 41 including D_LEVELTR = 32767 will be transmitted to the train (via balise: ETCS L1 or L2 or via radio: ETCS L2 only) for the mileageDirection valid for this function.),
  • "handover" (This balise group transmits at least a UNISIG Packet 131 for the mileageDirection valid for this function.),
  • "sessionTermination" (This balise group transmits at least a UNISIG Packet 42 including Q_RBC=0 for the mileageDirection valid for this function.),
  • "signalBaliseGroup" (This balise group is linked physically (in case of ETCS L1) or logical (in case of ETCS Level 2) with a main signal. In relation to this balise group, at least the UNISIG Packets MA (12: ETCS L1 or 15: ETCS L2), 21 and 27 will be transmitted to the train (via balise: ETCS L1 or via radio: ETCS L2) for the mileageDirection valid for this function.),
  • "infillBaliseGroup" (This balise group transmits at least a UNISIG Packet 136 for the mileageDirection valid for this function.),
  • "stopIfInShunting" (This balise group transmits at least a UNISIG Packet 132 including Q_ASPECT=0 for the mileageDirection valid for this function.),
  • "odometryPurposeOnly" (Each balise of this balise group transmits only UNISIG defined ETCS telegram header and UNISIG Packet 255 (End of information) for the mileageDirection valid for this function.),
  • "sessionEstablishment" (This balise group transmits at least a UNISIG Packet 42 including Q_RBC=1 for the mileageDirection valid for this function.),
  • "networkRegistration" (This balise group transmits at least a UNISIG Packet 45 for the mileageDirection valid for this function.)
  • "announcementTemporarySpeedRestriction" (This balise group transmits at least a UNISIG Packet 65 for the mileageDirection valid for this function.),
  • "revocationTemporarySpeedRestriction" (This balise group transmits at least a UNISIG Packet 66 for the mileageDirection valid for this function.)
Edited Mar 22, 2022 by IS Coordination
Assignee
Assign to
Time tracking

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