Home » railML newsgroups » railml.interlocking » Release triggers for routes in railML 3.2
Re: Release triggers for routes in railML 3.2 [message #3197 is a reply to message #3189] Tue, 27 February 2024 05:30 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 89
Registered: March 2016
Member
Dear Terje,

thanks for your the description of your rules and background. Let me add
the following:

1) Objects in a train route and its flank protection are
released when related TVP section is passed by the entire
train.
That's the assumed standard behaviour why it does not need extra
definition. Refer https://wiki3.railml.org/wiki/IL:routeReleaseGroupRear.
<routeReleaseGroupRear> is forseen the cases where elements are released
from route as a group by extra command.

2) final route release by train
If route release shall be independent of any associated overlap a route
release trigger can be added to the <routeExit> referring to the trigger
position with mode information (occupation, dispatcher, trainStandstill).

--
Dr.-Ing. Jörg von Lingen - Interlocking scheme coordinator

Report message to a moderator

[Message index]
 
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:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Jul 27 19:16:37 CEST 2024