Skip to content

Implemented Requirement SCH2003 #20

@ArielSAdamsNASA

Description

@ArielSAdamsNASA

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions