Review of OETCS API Requirements - appendix - Application Layer v1.0

[ericschellenberg]

Refers to #47:
We have reviewed the document and we have the following comments:

3
It would be useful to have a summary list of DMI packets

3
This application layer seems to be at very low level. It means that a lot of DMI functionalities will have to be implemented in the Application SW (OpenETCS), most of requirements in ERA_ERTMS_015560 have to be taken into account in OpenETCS SW.

3
Due to this low level application layer, the description of the packets/variables is not sufficient. A complete specification of the packets usage with the expected behaviour of the corresponding DMI is requested.

3.3
Packets for management of text messages seems to be redundant:
Packet 78 = 02 : delete text message
Packet 66 = 09: display text message
Packet 77 = 50: ack text
Packet 79 = 56: stack full
In order to clarify/simplify the data exchanged, it should be possible to use only one improved set of packets (indicating if the text is related to EVC, track or STM)

4
JRU interface should be limited to the JRU messages defined in subset-027 v300.
Time information is provided by the Time Interface of API and status provided by Tests interface.

5.2.2
Packet 0:
V_TIU_TILTING_STATE_FILTERED and V_TIU_TILTING_STATE are not used by ETCS.
V_TIU_VIGIL_ACTION_STATE_FILTERED, V_TIU_VIGIL_DISABLE_STATE_FILTERED, V_TIU_VIGIL_ACTION_STATE and V_TIU_VIGIL_DISABLE_STATE are not used by ETCS.
Information about status of special brakes (regenerative brakes, magnetic shoe brakes, eddy current brakes, ...), passive shunting, pneumatic brake pressure, Type of train data entry are missing (see subset-034)

5.2.2
Packet 1 and 2: text from TIU is out of ETCS scope

5.2.2
Packet 3 is not necessary if braking model is part of the configuration interface.

5.2.2
Packet 6 and 12 are not necessary if test and status of components are part of Tests interface.

5.2.2
Packet 7 and 8: what is the purpose of these packets?

5.2.2
Packet 13: what is the purpose of this packet?

5.2.3
Packet 0:
CCPU_VIGIL_DISABLE_ORDER is not used by ETCS

5.2.3
Packet 3 and 4: what is the purpose of these packets?

5.2.3
Packet 6: is this packet used for odometer recalibration? If yes, it should be part of MMU interface.

5.2.3
Packet 7,8 and 9: what is the purpose of these packets?

5.2.3
There is no packet for Change of allowed current consumption