Home » railML newsgroups » railml.interlocking » Release triggers for routes in railML 3.2
Re: Release triggers for routes in railML 3.2 [message #3176 is a reply to message #3175] Mon, 18 December 2023 07:11 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 89
Registered: March 2016
Dear Terje,

the intention for modelling route release is probably not so obvious but based on philosophy of conventional interlockings.

1) IL:routeReleaseGroupRear
Here the information is put for releasing parts of the running path of the route before the release trigger is reached. Especially some legacy interlockings do route release not per each element when the train passed it but using kind of intermediate triggers to release a defined group of elements at once.

2) final route release
To model the release trigger for overlap and final route release the IL:overlap element is intended. There are cases in conventional interlockings where routes do not have a physical overlap. But even then the overlap (with length 0) is modelled having all the information for route release.
The IL:overlap element is available in IL:routeExit and in IL:destinationPoint.

Best regards,
Joerg v. Lingen - Interlocking Coordinator
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: Sat Jul 13 07:51:24 CEST 2024