Home » railML newsgroups » railml.interlocking » Release triggers for routes in railML 3.2
Release triggers for routes in railML 3.2 [message #3175] Thu, 14 December 2023 16:25 Go to previous message
Terje Nordal is currently offline  Terje Nordal
Messages: 9
Registered: December 2023
Junior Member
Hello railML experts,

When modeling routes in railML 3.2, Bane NOR need the ability to define a trigger point for route release, typically a train detector that, when passed by the train, triggers the release of a train route. Up until recently we have used IL:routeReleaseGroupRear to model this, but have since found the description "One or more TVD sections as part of the route which can be released in a group in rear of passing train.". Since it refers to the release of TVD sections, and not routes, we think it does not fit our needs perfectly. We have also not found any other way to model it in railML 3.2. Is there something we have missed, which could be used to model it? Alternatively, are there/should there be plans to add this to railML 3.3?

For context, see the attached image where the route from MB 1 to MB 2 is released at the passing of train detector between TVD section 2 and 3, ie. when TVD section 2 is vacant.

As an addition: A similar trigger exists in railML 2.4nor; @releaseTriggerRef. Part of the description on this is "The trigger position used for releasing the complete route (and thus its overlap) while the train still occupies a track section(s) on the route.". Apart from the part of also releasing the overlap, which would not happen in our ERTMS system, this is exactly what we are trying to model.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Reuse IL:SignalBox for Object controllers
Next Topic: New area types for railML 3.3
Goto Forum:
  


Current Time: Thu Jul 25 08:01:55 CEST 2024