comment on OETCS API requirements v1.2

[GEVincent]

general: GE platform uses C code and not ADA; To be discussed
we propose API based on the POSIX 2.0 interface layer. Advantages would be that the interface is standard and has its own documentation. Only work would be to clarify which POSIX interface calls will be supported

3.3.1: For the "types" to use: could be important to limit the use to certain types: for example, prevent the use of floating point (safety reason)

3.3.4: "The duration of the CORE board cycle does not have to be constant": the duration of the CORE board cycle for GE platform is constant. To be discussed

4.4.6: "As these data CANNOT be erased by the maintenance team, the Application SW must ensure that their decoding shall not kill the EVC." = what is the exact meaning of this sentence? how to do that?

4.5.2.1: JRU and DMI can also be tested automatically when powered up

4.6.2: is it a vital clock or non vital clock? Don't we need also a non vital clock for maintenance event timestamp or to manage MDI clock?

4.7.2: Is there any odometry algorithm application running outside the application software? On the GEOS board? Is the odometry algorithm potentailly one of the development of the OpenETCS?

4.7.2.2: is TIME-STAMP = T_ODO as defined in SS?

4.8.2.4: "The position of the center of the balise will be provided in the same coordinate system as the MMU distance calculation": is it possible to clarify what is the possible coordinate system?

4.9: GE platform doesn't support Euroloop. Is it part of the OpenETCS ?

4.10: EB_requested, EVC_isolation_is_requested, occupied_cabin: why does the document detail only these TIU and not others from SS034?

4.13: can you confirm that the aplication SW is providing messages as described in SS058. lower layers (SL/STL/Profibus) are services of the Basic SW?

4.14: Euroradio: confirm that the SS037 is implemented in the Basic SW?