1 / 3

Command Verification

Command Verification. CEV - command verification (performed on server - Verifier) Uplink Verification (based on reports from Ground Station) Execution Verification (multiple stages) to verify command was received on board and executed correctly Two Types:

byron
Download Presentation

Command Verification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Command Verification • CEV - command verification (performed on server - Verifier) • Uplink Verification (based on reports from Ground Station) • Execution Verification (multiple stages) to verify command was received on board and executed correctly • Two Types: • Report packets from S/C (PUS service 1) • Database defined check, telemetry parameters with expected values • Validity of telemetry parameters used for verification is accounted for. • Also drives status consistency checking • Verification dynamics: UNKNOWN/ FAILED/ PASSED/ UNVERIFIED/ AFFECTED/ UNCERTAIN PASSED/ UNCERTAIN FAILED PENDING/ PASSED/ FAILED/ SUPERSEDED Release time (execution time of TT) UNKNOWN UNVERIFIED PASSED/ PENDING IDLE Execution Duration (DB: CVS_START field) Verification Delay (Window of Uncertainty TC Spacon variable) Sampling Interval (DB: CVS_INTERVAL field) Manual consolidation if UNKNOWN Or AFFECTED Verification window

  2. There are 3 Uplink Verification stages: • Ground Station Reception (1st stage) • Ground Station Uplink (Radiation/Transfer) (2nd stage) • On-Board Reception (CLCW based) (3rd stage) • There are 4 Execution Verification stages: • Application Acceptance • Start of Execution • Execution Progress (multiple steps – SCOS-2000 supports 0 – 9) • Completion of Execution • The possible states a stage can take: • Idle: Window not yet open • Pending: Window not open • Passed: TM successfully shows stage as successful • Failed: TM shows stage has failed (only for report based) • Unknown: No TM arrived to verify the stage after window closes • Superseded: A new command’s window uses same TM parameters and overlaps • Affected: A new command’s window uses same TM parameters but windows do not overlap • Unverified:Consolidated by user if previously Unknown or Affected, or if 3rd stage AD number has been reset/ or re-used • Timed-out:UV stage not received G/S response (only applies to UV) • Uncertain Passed:TM arrived shows stage passed but after window has closed • Uncertain Failed:TM arrived shows stage failed but after window has closed • Assumed: Only applicable to 3rd stage if not yet passed but subsequent stages have passed. • Disabled: Time-tagged command disabled at Execution (To be taken back from Rosetta) • Deleted: Time-tagged commands removed from on-board before execution

  3. Verification states explained Sampling period (CVS_INTERVAL) Uncertainty window (TC SPACON) Execution duration (CVS_START) Late ….. PENDING IDLE PASSED Timely TM “true” Release of TT TC End of execution duration FAILED Timely TM “false” Consolidated by user UNVERIFIED SUPERSEDED Overlapping TC for same TM Consolidated by user TIMED OUT 3rd stage UV only AFFECTED TC for same TM DISABLED Disabled at execution UNCERTAIN PASSED DELETED Removed by TC Late TM “true” UNCERTAIN FAILED UNKNOWN No TM at close of sampling window Late TM “false” ASSUMED Passed later verification stage

More Related