Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

T Th he e P P- -P PO OD D P Pa ay yl lo oa ad d P Pl la an nn ne er r’ ’s s G G

T Th he e P P- -P PO OD D P Pa ay yl lo oa ad d P Pl la an nn ne er r’ ’s s G Gu ui id de e Revision C – June 5, 2000 Author: Ryan Connolly P-POD Payload Planner’s Guide: Revision B – 5/15/00 2 of 19 1. INTRODUCTION The Space Development, Manufacturing & Integration (SDMI) Team is positioning Cal Poly, San Luis Obispo to be at the center of small satellite development. Working with Stanford’s Space Systems Development Laboratory (SSDL), the goal is to produce a standardized platform for small orbital experiments. Known as CubeSats, these tiny space vehicles are classified as PicoSatellites, meaning that the entire satellite weighs less then one kilogram. The 10-centimeter cubes are designed to house small experiments that otherwise would be cost-prohibitive to flight validate. Universities, alongside industrial and governmental interests, will be able to place their own CubeSats into orbit using our standardized deployment system. Cal Poly’s own satellite, PolySat, will be one of the first of these new CubeSats. The SDMI is leading the way in the development of this deployment system known as the P-POD (Poly Picosatellite Orbital Deployer). The two versions of the deployer will mount to various launch vehicles, including the Delta II and the Minotaur. The maiden voyage for P-POD1 and P-POD2, along with PolySat is tentatively scheduled for Late Summer 2001. The total number of CubeSats launched is yet unknown, but the manifest could reach upwards of fifteen CubeSats on the maiden voyage. Cal Poly will oversee CubeSat development worldwide, and shall orchestrate all launching services with the launch providers. The integration design team is responsible for overseeing all incoming CubeSats, and verifying that they meet the design requirements set forth in the P-POD Payload Planner’s Guide, which will be available to all interested parties. This ambitious interdisciplinary project, with students from all engineering majors and even several non-engineering majors, embodies the Cal Poly ‘Learn by Doing’ credo in every respect. The purpose of the Payload Planner’s Guide is to define clearly and carefully all CubeSat design requirements and all requirements for their interface with the deployer. This document is divided into the following sections: 1. Introduction 2. CubeSat Deployer Description 3. CubeSat Physical and Electrical Requirements 4. CubeSat Operational Requirements 5. Delivery Deadlines and Pricing Please refer to the SDMI website for more information regarding the project: http://www.calpoly.edu/~aero/polysat P-POD Payload Planner’s Guide: Revision B – 5/15/00 3 of 19 2. PICOSATELLITE DEPLOYER DESCRIPTION This section of the document shall provide an overview of the CubeSat environment while onboard the deployer. The CubeSat provider shall be briefed on the following criteria required for integration into the deployer: 2.1 Deployer System Overview 2.2 CubeSat Containment and Deployer Interface 2.3 CubeSat Launch Environment 2.4 P-POD Orbital Environment Please refer to Section 3 for explicit CubeSat requirements. 2.1 Deployer System Overview The P-POD System has two distinct release platforms, each with a unique deployer that has different requirements on the CubeSats themselves. 2.1.1. Platform #1: P-POD1 With this configuration, the deployment system requires less design refinement for the CubeSats. The published specification tolerances for the CubeSat, as well as the outer mounting surface area provide for easier manufacturing of the CubeSats. The ultimate aim of this system is to provide deployment services to clients with limited manufacturing capabilities, such as universities and high schools, since the P-POD1 can accept a wider variation in CubeSat design. The mounting configuration for P-POD1 has three CubeSats per “POD,” with each CubeSat located by their corners via a series of mounting blocks. The three CubeSats sit next to one another on a base that slides vertically on roller slides, and two doors, which remain closed and locked until deployment, confine the entire base. Two Compression Springs provide the launching force, and the doors are opened via a cam system that ensures that the doors are fully opened when the base reaches its maximum height. Figure 2.1. P-POD1 Concept Model. (Left: Doors Open Right: Doors Closed) Note: As of the publishing date of this document, the P-POD1 is still under design review. Anticipated release of all design documentation is Winter 2000. No further mention of the P-POD1 design shall take place in this edition of the Payload Planner’s Guide. P-POD Payload Planner’s Guide: Revision B – 5/15/00 4 of 19 2.2. Platform #2: P-POD2 This configuration of the deployment system, which is in the final design phase, represents the method of deployment for all customers. CubeSats aimed for deployment in P-POD2 must meet tighter tolerances and stricter design requirements, therefore limiting clients to those with highly accurate manufacturing capabilities. The deployment device consists of a series of machined aluminum tubes, with each tube composing one unit, or “pod.” Each pod is modular and can be assembled in a variety of configurations with other pods to accommodate many launch vehicle requirements. A single spring handles the deployment force, and a hinged spring-loaded door at one end of the tube restrains the CubeSats. A non-explosive actuator releases the door. Three CubeSats shall be positioned in each P-POD2 unit, with a 6.5 mm “clearance” distance from all six sides of the CubeSats. This clearance distance allows for mounting of any external features (solar panels, antennas, etc.) that extend above the CubeSat surface. Four 7mm standoffs shall be included (on two opposing sides) in the structure of each CubeSat in order to achieve proper spacing between each satellite within the launch tube. Detailed drawings of the deployer and CubeSat form factors can be found in Appendix A. Figure 2.2. Artist’s conception of P-POD2 Deployment Device P-POD Payload Planner’s Guide: Revision B – 5/15/00 5 of 19 2.2.1. CubeSat Containment and Deployer Interface The CubeSats, when loading within the deployer, shall be constrained by the rail system of the tube, as well as secondary loading washers pressing them against the secured door. The rail design prevents jamming of the CubeSats during deployment, but requires tight tolerances on the outside dimensions of the CubeSats. The designated rail contact surfaces on each CubeSat must have a smooth surface finish, as detailed in the CubeSat requirements drawings in Appendix A. When loaded into the deployer, all CubeSat power must be completely off, and the CubeSats may only be powered on once clear of the tube. To accomplish this, kill- switches (microswitches) must be mounted to the exterior of each CubeSat (in designated areas stipulated on the requirements drawings) to turn off all power when compressed. Also, the microswitches must be flush with the CubeSat surface when compressed. In addition to the kill-switches, a “remove before flight” pin must be furnished in the location stipulated on the CubeSat requirements drawings. This provides a universal method to ensure all CubeSats remain dormant during loading into the deployer. Additionally, an optional USB data port may be provided on the CubeSats in the location shown on the specification drawings. Access to the port will be provided on the deployer tube, such that final access to the CubeSat is available after integration to the deployer. 2.2.2. CubeSat Launch Environment The CubeSats shall be launched with an exit velocity between 0.5 and 1 foot per second. The CubeSats shall have a small relative velocity and will remain close to one another for a relatively long time. No intentional spin is imparted to the CubeSat during launch. 2.2.3. P-POD Orbital Environment The P-POD2 system may be launched aboard the OSP Space Launch Vehicle, and hard- mounted to the JAWSAT satellite as its primary payload. The details of the orbit and launch altitude are not yet known. Additional launch possibilities may arise, and any changes shall be published immediately. The launch vector of the CubeSats with respect to Earth and launch vehicle will be unknown at the time of deployment, and all clients must accept this factor at time of CubeSat installation into the Deployer. P-POD2 shall experience the space vacuum and radiation dosage of a typical low-earth orbit environment. Predicted temperatures range from -40°C to 80°C, and large temperature fluctuations are possible. There will be no thermal control within P-POD2, so all CubeSats must be able to withstand these environmental fluctuations. P-POD Payload Planner’s Guide: Revision B – 5/15/00 6 of 19 3. CUBESAT PHYSICAL AND ELECTRICAL REQUIREMENTS This section of the document shall provide the physical (overall shape, size, weight) and electrical requirements for the CubeSats traveling aboard the P-POD2 system. The supplier testing criteria for the CubeSats is also outlined in this section, and should be used by CubeSat designers to design, construct, and test the satellites before delivery to Cal Poly. Any CubeSat that meets all of the requirements and passes all of the required tests shall be considered flight worthy by the P-POD team. Note: Once the design of P-POD1 is complete, requirements shall also be set forth for flight aboard that system as well. 3.1. Dimensions The CubeSat shall conform to the shape and size specified in the CubeSat specification drawings in Appendix A. 3.2. Mass Properties The uploads/Ingenierie_Lourd/ planners-guide.pdf