Skip to content
New issue

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

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

Already on GitHub? # to your account

Reporting List of Disabled Event Definitions #136

Open
pasetti opened this issue Oct 28, 2018 · 2 comments
Open

Reporting List of Disabled Event Definitions #136

pasetti opened this issue Oct 28, 2018 · 2 comments
Assignees
Labels

Comments

@pasetti
Copy link
Contributor

pasetti commented Oct 28, 2018

Clause 6.5.5.4 (Report the list of disabled event definitions) includes the following sub-clause:

d: For each valid request to report the list of disabled event definitions, the event reporting subservice shall generate a single disabled event definitions list report that includes all related disabled event definition notifications.

In all cases known to me, each application sets a maximum size for a telemetry report. Suppose that the number of disabled events in an application is such that they do not fit within one single (5,8) report. What happens in that case? How can be comply with the requirement of clause 6.5.5.4d?

Note that a similar problem exists for several other commands which trigger the generation of a multi-instruction report.

@pasetti pasetti added the PUS label Oct 28, 2018
@pasetti pasetti self-assigned this Oct 28, 2018
@pasetti
Copy link
Contributor Author

pasetti commented Jan 18, 2019

I have submitted this comment through the ECSS Change Request process on 17 Jan 2019.

@pasetti
Copy link
Contributor Author

pasetti commented Mar 19, 2019

Clause 5.4.11.3.2a implies that requests which imply the generation of a response which exceeds the maximum size of a packet should be rejected. But is this really the intention in the case of the telecommand in question?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant