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

Interpretation of Indentifier of On-Board Connection Test Application #61

Open
pasetti opened this issue Jul 24, 2017 · 1 comment
Open
Assignees
Labels

Comments

@pasetti
Copy link
Contributor

pasetti commented Jul 24, 2017

According to clause 6.17.4.2c-1, each instruction to perform an on-board connection test shall contain the identifier of the application process that connection test is requested. How exactly should we understand the term "identifier of the application process"? Is there an assumption that the connection test can only be done with another PUS application and hence the argument of the TC(17,3) must be the APID of that application? Or is the intention that the argument of the TC(17,3) is just a generic identifier of the target application of the connection test?

@pasetti pasetti self-assigned this Jul 24, 2017
@Rockenbauer
Copy link

The argument of the TC(17,3) is just a generic identifier. It is the ID that is specified as CR_FW_HOST_APP_ID in the CrFwUserConstants.h because the APID includes also the PCAT.

@pasetti pasetti added the PUS label Jan 4, 2018
@pasetti pasetti changed the title PUS: Interpretation of Indentifier of On-Board Connection Test Application Interpretation of Indentifier of On-Board Connection Test Application Jan 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants