Home » railML newsgroups » railml.infrastructure » etcsTrainCategory (correct source for definition of values for etcsTrainCategory)
etcsTrainCategory [message #1655] Mon, 16 October 2017 11:02 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 40
Registered: March 2016
@etcsTrainCategory [integer] refers to the (integer)value in:
The XSD schema points to v1.9 from 10/07/2012 (should probably be v0.9)
The wiki points to v1.21 from 20/10/2016
The current version is 1.23 (13/9/2017)
http://www.era.europa.eu/Document-Register/Documents/ERA_ERT MS_040001_v1.23.pdf
The value to use is the @NC_TRAIN in Annex A chapter 6.2

Question: Which is the correct version to use? Note that only the last version is available on the ERA site.

But there is another ERA value with the same purpose in TSI OPE Apendix A (ERTMS OPERATIONAL PRINCIPLES AND RULES) Annex B (LIST OF ETCS OPERATIONAL TRAIN CATEGORIES) that list the @ETCS operational train categories. These are not integers, but string values.
http://www.era.europa.eu/Document-Register/Documents/Appendi x_A_version_4.pdf
For all, but on tilting value the NC_Train values translates into the ETCS operational train category over the identical cant deficiency value. The difference between the two value constructs is that the ETCS operational train category is defined based on cant deficiency AND type of brake (P/G) AND type of train (Pas/Tilt Pas/Freight). Where the NC_TRAIN is based on cant deficiency OR type of brake (P/G) OR type of train (Pas/Freight)

For Norwegian speed profiles this translates to:
NO: NC_Train: ETCS operational train category:
normal 5 PASS3
pluss 6 TILT1
tilt 13 TILT5

Question: Which of the two are correct to use?
I asume NC_Train for railML2.3 as this is the value defined and its an integer (which is the value allowed in the schema).
But for railML3 we should discuss which of the two are more predominant. Or allow to use both?
Re: etcsTrainCategory [message #1698 is a reply to message #1655] Wed, 31 January 2018 19:44 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 7
Registered: February 2017
Junior Member
The documentation restricts the value of etcsTrainCategory to an integer from 0 to 15. In my view that is a misrepresentation of the categories given in the definition of the NC_TRAIN ERTMS variable. The numbers 0 to 15 are neither sufficient to represent the 18 operational train categories in ERTMS nor are they sufficient to identify what kind of train it is. The number 4 would represent three different operational train categories.

To my knowledge, the column "International train category number" in the table in Annex A chapter 6.2 of "Assignment of values to ETCS variables", is not used in any other context, and is only used to enumerate the bits of the NC_TRAIN variable. NC_TRAIN is a 15-bit integer, not an integer between 1 and 15. To quote from the ERTMS SRS definition of NC_TRAIN: "Each bit represents one category. A train can belong to various categories." Let me give three examples, all for a permissible cant deficiency of 80 mm:

* A passenger train: NC_TRAIN = 000 1000 0000 0010 (binary) = 2050 (decimal)
* A freight train braked in "P" position: NC_TRAIN = 000 0010 000 0010 (binary) = 514 (decimal)
* A freight train braked in "G" position: NC_TRAIN = 000 0100 000 0010 (binary) = 1026 (decimal)

I do not know how many bits would be set for higher permissible cant deficiencies. Either just the highest matching category bit is used, or all lower bits are also set. For a passenger train with a permissible cant deficiency of 245 mm the two options would be:

* Only highest: 001 1000 0000 0000
* All: 011 1000 1111 1110

Does anyone in the community know which of these is correct?
Previous Topic: Maximum train current - Proposal for extension of infrastructure scheme in railML 2.4
Next Topic: last open points for speedProfiles in railML 2.2
Goto Forum:

Current Time: Thu Apr 26 05:28:12 CEST 2018