Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specification issues report on subset 26 - 5.6.4.3 #44

Open
Farhangi opened this issue Aug 6, 2013 · 3 comments
Open

Specification issues report on subset 26 - 5.6.4.3 #44

Farhangi opened this issue Aug 6, 2013 · 3 comments

Comments

@Farhangi
Copy link
Contributor

Farhangi commented Aug 6, 2013

Description:

After a defined number of repetitions (see appendix to chapter 3, List of Fixed Value Data), and if no reply is received within the fixed waiting time from the last sending of the mode change report, the ERTMS/ETCS onboard equipment shall terminate the session.

Comment:

The Paragraph 5.6.4.3 describes a degraded situation where no order to terminate the communication session was received from the RBC after a given number of position report sendings. It states that in that case the ERTMS/ETCS onboard equipment shall terminate the session. But there is no information about the state change after this action => should be process end? or remain in the same state?

@ericschellenberg
Copy link

Clarification can be found in ERA_ERTMS_015560 v330:
The session is closed, the message "shunting request failed" is displayed, it is the end of the process (see 11.7.4)
and the shunting button is no more available (level 2/3 and no no session, see 11.2.1/table 33)

@Svitlana-Lukicheva
Copy link

Thank you for clarifications. I found the document, and the references you are talking about, but I still don't understand how can I deduce that the process ends. Should it be deduced from the facts that in the Shunting dialogue sequence the process goes to S0, and that the shunting button is no more available? Or it is stated somewhere explicitly?

@ericschellenberg
Copy link

Yes, as the process goes back to S0 and the shunting button is no more available, we can deduce that the process ends.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants