CAP Checklist Date: May 05, 2004 CAP#915 _ |x| Has the interaction with the load been checked? Yes. The SOP uses realtime loads which bypass the OBC and go straight to ACIS, therefore there is no possibility for command contention within the OBC. We will need to check the onboard load to make sure there are no ACIS commands during this interval. _ |x| Has comm been identified and duration estimated accurately? We require a minimum 2 hr COMM. 2004:136:22:35:00-2004:137:01:25:00 We can start the CAP at 136:23:17:00. This fits our duration requirements. |x| If SCS slots are used, is there SCS slot contention? No. SOP_ACIS_SW_EVHCC3X3_CATL does not use SCS slots. SOP_61010_DEA_HKP uses slots 137 and 185 and there is no contention. _ |x| Does the CAP perform SCS slot cleanup? SOP_61010 performs SCS slot cleanup. _ |x| Does the CAP set the correct format at completion? N/A use FMT 2 throughout. _ |x| What happens if comm is lost during the CAP execution? If the BEP has not been rebooted, then we will have to restart the procedure at the next identified comm, which does not have to be the next possible comm. If the BEP autonomously reboots while in this state, the flight software will revert to version 11 and some of the features in version 31 of the SW will not be available for the upcoming science runs to utilize. _ |x| Does CAP require radmon to be enabled or disabled to be compatible with current load? No. _ |x| What is the worst case scenario for the CAP execution? BEP fails to reboot. We then will reload version 30 of the flight software. Loss of comm before all patches are loaded and verified. We can fail over to the version 11, the EEPROM version if we only get some of the version 31 patches into memory and then lose comm AND the BEP reboots before we can get back to it. - what science can be lost? If we fall to version 11, some enhancements to flight software will be lost until this CAP is executed again. Science can still be performed with version 11 of the flight software. - does action generate significant momentum? No - can safe mode be triggered during the CAP? No _ |x| List (or attach list) of products that are required (loads, scripts, CAPs). Include version number for scripts and CAPs. Command Loads 1R_AU000.cld 1R_RU000.cld 1R_G0050.cld 1R_G0053.cld 1R_G0054.cld 1R_G0055.cld 1R_G0056.cld 1R_WU032.cld ------------ (for SOP_61010_DEA_HKP) 1A_WD000_137.cld 1A_XD000_185.cld Scripts C_SET_FORMAT I_1_SW_EVHCC3X3_CATL SOPs SOP_61055_SW_DUMP SOP_61083_SW_EVHCC3X3B SOP_61010_DEA_HKP SOP_ACIS_SW_EVHCC3X3_CATL _ |x| Are all products certified and do CAP and scripts have version 3.0 or higher? Yes. _ |x| Has OC verified that all required products are available on console? _ |x| Does the CAP require an OBSID change? No _ |x| Who will be on-console and is the CAP being run at a reasonable time? OC/CC and ACIS ops. Yes, CAP is being run at a reasonable time. _ |_| Has CAP been reviewed by FD, FOM, SOT lead and OC or their designee? Comments: None To be attached to the signed CAP. Rev 1.5, 12 Apr 2001, RJB