180 likes | 291 Views
MAVEN PFFSW STATUS 5/01/2012. Operational Status. Interface Documents, Meetings STATIC Specification rev N, 3/29/12 SEP Specification rev C, 2/1/12. SWIA Specification rev H, 3/29/12 DFB-DCB ICD rev E, 1/30/12 (15 th revision, they count 1-10, A-E) MAG PRE-I&T Meeting
E N D
MAVEN PFFSW • STATUS • 5/01/2012
Operational Status Interface Documents, Meetings • STATIC Specification rev N, 3/29/12 • SEP Specification rev C, 2/1/12. • SWIA Specification rev H, 3/29/12 • DFB-DCB ICD rev E, 1/30/12 (15th revision, they count 1-10, A-E) • MAG PRE-I&T Meeting • LPW PRE-I&T Meeting Development • Implemented Limit Monitors • Developed LM database process. Need REAL numbers for limits ! • Enabled Fault Protection and had to Revise Logic • Added New Commands, RTS for LPW to fit in PFDPU operational framework • Revised LPW processing to automatically calculate 16-bit checksums. • Sent MAG team sample science data IV&V • Level 5 Requirements Validation Report Next Up • Run through of Flight I&T of MAG, LPW and SEP on the ETU • Need to get agreement on RTS 0-5 , (Cold and Warm Resets, Safe, Normal, Eng modes) • Working on a packet-level compression specification
Op Load Leveling Allocation of interrupt space to processing (LEFT) and time taken in their interrupt (MAX case). Design goal is 50% or less in the interrupt, usually checked by analysis or simulation. Actual measured MAX case in 1/256ths of a second are shown. Orange shows those >= design goal. (Note: measured on DVF with instrument simulation, not ETU with real instruments). Should have a look at load leveling these ISRs. (All work occurring in one interrupt, nothing in another).
Reqts Issues No details available (TBD) Normal to Reboot to start a new Operational program (DELETED) No details available (TBD)
Reqts Moves Move from HSK to PWR (Complete) Move from STA to FP (Complete)
Reqts Build 3 SWIA Moments SWEA Pitch Angle Dists
Old FP SEP1&2 Doors • IsSEP1Open() • FSW Selects SEP1 Door status and directly reads its status. • IsSEP1Allowed() • If either “SEP1 FOV1” or “SEP1 FOV2” ZoneAlerts, then SEP1 Door is not allowed. • If user Enable is low, SEP1 Door is not allowed. • ManSEP1Door() • If open but not allowed, this routine starts RTS[6], SEP1 Door Closure. • If closed but allowed, this routine starts RTS(11), SEP1 Door Open • Does not matter whether SEP is on/off • Shown as a diagram but may be implemented using tables. • Identical logic used in SEP2
New FP SEP1&2 Doors • IsSEP1Open() • FSW Selects SEP1 Door status and directly reads its status. • IsSEP1Allowed() • If either “SEP1 FOV1” or “SEP1 FOV2” ZoneAlerts, then SEP1 Door is not allowed. • If user Enable is low, SEP1 Door is not allowed. • ManSEP1Door() • If open but not allowed, this routine starts RTS[6], SEP1 Door Closure. • Does not matter whether SEP is on/off • Identical logic used in SEP2
Test Environment GSEOS Status: • Instrument simulation (working for MAG science, but others are housekeeping only) • MAG simulated packet has an incorrect checksum. MAG ETU works fine. • Instrument simulation files for LPW, etc. need work. Need for each Instrument: • Case 1. Typical test pattern • Case 2. Anomaly test pattern (e.g Housekeeping violations) • Case 3. Worst case telemetry rate • Limit checking error messages in GSEOS • No limits are being checked GSEOS Python Test Scripts, Displays (no change from April) • # I&T Test Scripts Ready = 0 • # Engineering APIDs displayed : 10 of 13 • # Science APIDs displayed : 10 of 67 • # Total APIDs generated by Version 2.4 : 80
Charts CHARTS
Margin Chart Finished adding LUTs to EEPROM. None in Flash Calculations performed in Analyses.xls