| Balise group values for IS:functionalType [message #3174] |
Thu, 14 December 2023 15:16  |
Terje Nordal
Messages: 9
Registered: December 2023
|
Junior Member |
|
|
Dear railML experts,
I have just recently gotten access to post on the forum, and as requested by the administrators at railML.org I will start my first post with a brief introduction of myself. In the context of railML I represent Bane NOR (part of the railway administration in Norway), working as one of our technical in-house admins for the NRV tool (delivered to us by TrafIT solutions). I work on developing new functionality in the tool, mainly to help our engineers in their day-to-day work and for the tool to process and export data that let's us work with our signalling system suppliers in the best way possible. Other than that I work as a user of the same tool, doing signalling system design and other project related work in that regard, with 10 years of experience from that field.
Moving on to the reason for posting. Referring to https://wiki3.railml.org/wiki/IS:functionalType for balises, several values are possible. In our signalling design we have tried to map our different balise types. So far we have been able to find mapping for four of these, using the values networkRegistration, sessionEstablishment, sessionTermination and announcementLevelTransition. For the case of a level transition scenario, we have an additional two balise functions that we want to map, making a total of three balise functions for a successful level transition implementation.
Our names for these three balise groups are LTA (Level Transition Announcement), which is the one we have already mapped to announcementLevelTransition, LTC (Level Transition Cancellation) and LTO (Level Transition Order). LTC is located in diverging tracks where the Level Transition shall not take place, between the Level Transition Announcement balise group and the signaling system border. It's function is to cancel the transition to another level, in cases where the announcement has already been received by the train. LTO is located at the signaling system border, ordering the transition to the signaling system on the opposite side of the border. I have attached an image to hopefully explain the scenario and functions.
The question is, are there any values in IS:functionalType meant to handle these LTC and LTO balise groups? I have tried reading the value descriptions, but I could not find a perfect match in these cases.
|
|
|
|
| Re: Balise group values for IS:functionalType [message #3182 is a reply to message #3174] |
Fri, 05 January 2024 13:27  |
christian.rahmig
Messages: 474
Registered: January 2016
|
Senior Member |
|
|
Dear Terje,
welcome to the railML community and Happy New Year!
The question that you raised concerning the mapping of different ETCS balise group types w.r.t. their functional type, is best being answered by the railML ETCS use case working group. Therefore, I will take this request with me and bring it up in the next ETCS use case working group meeting on January 22, 2024.
From the railML schema perspective, it seems to be a minor change to extend the baliseGroup functional type enumeration list with the missing entries, but maybe there are other ideas as well...
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
|
|
|
|
|
|
| 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 |
|
|
|
| Re: Balise group values for IS:functionalType [message #3397 is a reply to message #3378] |
Wed, 20 November 2024 09:54 |
Dominik Looser
Messages: 23
Registered: March 2020
|
Junior Member |
|
|
Dear all,
I have noticed that there is a typo in the new enum-value level2TransisitonOrder. This should be level2TransitionOrder, similar to some other values in that list.
Following the deprecation policy, will this be fixed in railML 3.4 or will this stay the same?
Best regards,
Dominik
|
|
|
|
Members
Search
Help
Login
Home
