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

Implemented Requirement SCH2003 #20

Open
2 tasks done
ArielSAdamsNASA opened this issue Nov 29, 2022 · 0 comments
Open
2 tasks done

Implemented Requirement SCH2003 #20

ArielSAdamsNASA opened this issue Nov 29, 2022 · 0 comments

Comments

@ArielSAdamsNASA
Copy link

Checklist (Please check before submitting)

  • I reviewed the Contributing Guide.
  • I performed a cursory search to see if the bug report is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
Requirement SCH2003 is not implemented.

Describe the solution you'd like
SCH shall identify the spacecraft Major Frame Signal as "noisy" when two Major Frame Signals occur consecutively that are separated from the previous Major Frame Signal by less than <PLATFORM_DEFINED, 990> milliseconds (running fast) and/or greater than <PLATFORM_DEFINED, 1010> milliseconds (running slow)

Additional context
Only condition found was: "If we are NOT synchronized to the MET (i.e. - the Minor Frame timer has an acceptable resolution), then the Major Frame signal should only occur in the last slot of the schedule table. If we ARE synchronized to the MET (i.e. - the Minor Frame timer is not as good as we would like), then the Major Frame signal should occur within a window of slots at the end of the table."

Reporter Info
Ariel Adams, MCSG Tech

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

No branches or pull requests

1 participant