Skip to content

D2.7 OETCS API Requirements Version 1.2: Review: Chapt. 4.4 ++ #57

@UweSteinkeFromSiemens

Description

@UweSteinkeFromSiemens
  • 4.4.3.2: PERMANENT_DATA_T is not traceable to "OETCS_API Requirements_appendix_functional_data_dictionary_v1.0.pdf"
  • 4.4.4.4: "If it is the case, the train shall never be able to start again until new software is downloaded to restore a correct content to that Novram." It's unclear, which part of the sw is in charge for this function. Additionally, it is platform / hardware dependant since it requires collaboration with the NVRam store function.
  • 4.6.2.1: "The Application shall never use directly the Basic SW clock." What does this mean practically?
  • 4.7.2.4, first diagram: in a section of the diagram, the term (Distance(maximum) - Distance(nominal)) is decreasing. Is this a practical situation?
  • 4.8.2.4: "As long as the train is stopped over the balise, the telegram will not
    be provided to the application": Therefore, the application SW does not know about this position until the train leaves its position on the balise. Is this practically tolerable?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions