The P-POD Payload Planner's Guide

More documents

Recommendations

Info

P-POD Payload Planner’s Guide: Revision B – 5/15/00 8 of 19 3.6.4. Physical Effects The CubeSat operations cannot interfere with the normal operations of the P-POD2 structure or components. 4. CUBESAT OPERATIONAL REQUIREMENTS This section of the document outlines the operational requirements for each CubeSat. These requirements are necessary in order to ensure that no one CubeSat is a threat to any other within the same launch tube, or a threat to the mission as a whole. Because CubeSat deployment is the sole mission of P-POD, the highest level of importance is given to the CubeSat missions themselves. In this section, operational requirements are divided into three areas: 4.1. Pre-deployment operations: This sections covers preflight planning and testing to ensure that all CubeSats are flight-worthy and ready for integration into the deployer. 4.2. Deployment operations: The focus in this section is on the state in which the CubeSats must operate when contained within the deployer, and the methods allowed to activate the CubeSats upon deployment from P-POD2. 4.3. Post-deployment operations: this section covers methods of communication between the CubeSat and ground station. 4.1. Pre-Deployment Requirements 4.1.1. Testing Plans Each CubeSat design team must submit a plan and detailed procedure for the following validation tests: Vibration, Thermal-Vacuum, Electromagnetic Interference, and Integration. All test plans must be in accordance with the requirements set forth in Section 3 of this document. All results must be submitted to the P-POD team for review, and should be contained in a formal report. The CubeSat design teams shall perform all tests independently, and a member of the P- POD team will be available to aid of consult during each procedure. For the integration test, a joint team shall ensure proper interface between CubeSat and the deployer. In addition to pre-flight testing, each CubeSat team must provide a detailed list for preand post-launch checkout. This plan must indicate that the CubeSat is ready for the mission, and all internal systems are operating nominally. Once the CubeSat is deployed, the post-launch procedures shall be carried out to confirm that the CubeSat is able to begin its mission.
P-POD Payload Planner’s Guide: Revision B – 5/15/00 9 of 19 4.1.2. Operations Guide The CubeSat design team must submit a formal operations guide to the P-POD team in order to outline the primary mission and identify the functions of the CubeSat’s payload. This guide should also document the CubeSat’s compliance with all of the requirements set forth in this document. Expected behavior of the CubeSat during the entire mission (Pre-deployment, deployment, post-deployment) shall also be documented within this guide. Uplink and downlink frequencies shall also be clearly documented to avoid communications error with the other CubeSats on the mission. All communications with the CubeSats are left to the CubeSat design teams. P-POD shall not provide any communication with any of the CubeSats prior, during, or after they are deployed. However, the deployer will relay launch information back to the ground station, which will verify if the CubeSats were properly deployed from the system. 4.1.3. Physical Constraints This section of the document outlines the method in which all CubeSats are loaded into the deployer to achieve proper dormancy in each satellite. A detailed procedure must be submitted to the P-POD design team, prior to launch, that will explain the proper loading procedure for each CubeSat in order to ensure that all power is turned off when loaded into the deployer. As stated in Section 3, all CubeSat operations (electromagnetic, electrical, etc.) must be suspended until the CubeSat is clear of the launch tube during deployment. 4.2. Deployment Requirements Because no single CubeSat’s mission is seen as more important than any other during the mission, no CubeSat design team shall be given the choice of deployment times or vectors. All CubeSat design teams must agree that their mission may begin at any time, and should be ready to begin their mission within the defined launch window. Because each P-POD tube will contain up to three CubeSats, the CubeSat design teams must coordinate with one another concerning which tubes they will mount into. The P-POD design team will assign tubes and have the ultimate decision if any conflicts arise. CubeSats may only begin their missions upon exiting the deployment tube. No CubeSat may self-actuate until clear of the deployer. Also, no exterior components of the CubeSats, such as antennas or other devices, are allowed to contact the deployment tube. See CubeSat Specifications, Appendix A for details. 4.3. Post Deployment Requirements Once free of the deployer, the CubeSat should activate and begin communication with its ground station. At this time no ground station has been established for CubeSat communication, and we will supply all interested parties this information as soon as it becomes available.
Page 1 and 2: The P-POD Payload Planner’s Guide
Page 3 and 4: P-POD Payload Planner’s Guide: Re
Page 7: P-POD Payload Planner’s Guide: Re
Page 19: P-POD Payload Planner’s Guide: Re

The P-POD Payload Planner's Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?