| Re: Balise group values for IS:functionalType [message #3378 is a reply to message #3257] |
Fri, 25 October 2024 23:35   |
Karl-Friedemann Jerosch
Messages: 12
Registered: May 2020
|
Junior Member |
|
|
Dear Terje,
because UNISIG SUBSET-026 does not provide an ETCS packet or ETCS variable to "cancel" a level transition order,
the railML scheme should also not provide a special value "levelTransitionCancellation" for railML/infrastructure/functionalInfrastructure/baliseGroups/ functionalType/@value.
In ETCS, a level transition transmitted to a train can only be overwritten by a new level transition.
Following this principle, instead of "LevelTransitionCancellation",
please check the ETCS level which shall be valid for the train after passing the LTC-balise group and
use the corresponding value of baliseGroup functionalType in railML.
For example:
- If there is a level NTC area after the LTC-balise group (means tracks equipped with a national ATP system like Ebicab), then use @value="levelNtcTransitionOrder".
- If there is a level 2 area after the LTC-balise group (means tracks equipped with ETCS level 2 installations), then use @value="level2TransitionOrder".
best regards
Karl
[Updated on: Fri, 25 October 2024 23:39] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
