38
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + − == [http://wiki.stanfordssi.org/HPR_Background_Information High Power Rocketry]==+ − A high powered rocket is defined as a rocket that weighs more than 1500 grams and contains a motor or motors containing more than 125 grams of propellant and/or rated at more than 160 Newton-seconds of total impulse. There are different classifications for motors and different levels of certification required to use these motors. These rockets fall in the Class 2 Rocketry category as long as their total impulse remains below 41,000 Ns. Class 3 rockets require motors that cannot be bought commercially (and are classified as [[ITAR#Defense articles | ITAR defense articles]]).+ − {|+ − ! Class − ! Rating − ! Total Impulse (N-s) − |- − | − Class 1 (Model Rocketry) − − No certifications required − | A − | 1.26-2.5 − |- − | − − | B − | 2.51-5.00 − |- − | − − | C − | 5.01-10.0 − |- − | − − | D − | 10.01-20.0 − |- − | − − | E − | 20.01-40.0 − |- − | − − | F − | 40.01-80.0 − |- − | − − | G − | 80.01-160 − |- − | − Class 2 (High Power Rocketry) − − L1 − | H − | 160.01-320 − |- − | − − | I − | 320-640 − |- − | − − L2 − | J − | 640-1,280 − |- − | − − | K − | 1,280-2,560 − |- − | − − L3 − | L − | 2,560-5,120 − |- − | − − | M − | 5,120-10,200 − |- − | − − | N − | 10,200-20,500 − |- − | − − | O − | 20,500-41,000 − |} − − − − There is no test required to acquire a Level 1 certification. Just a successful flight and recovery using an L1-class motor is required. − − === Level 2: J, K, L === − − The holder of an L1 certification (not necessarily from the organization they are attempting to obtain L2 certification from) must pass an examination on the subject of advanced rocketry concepts and have a successful flight and recovery using an L2-class motor. − − === Level 3: M, N, O and beyond === − − There are many requirements for an L3 flight. Check the NAR and TRA websites for further information. − − ==[[Project Daedalus]]== − − Daedalus teaches the major design principles of high power rocketry with hands-on experience. Teams design and launch novel rocket concepts iteratively, starting with L1, L2 and finally ending with an L3 rocket that successfully flies the thoroughly tested design. The technology coming out of this project will benefit the Rockets Team’s flagship rocketry project. − − Daedalus is the overarching rockets project for the 2015-2016 year that is divided into 4 subteams as described below. − − === [[Pegasus]] === − − The purpose of Pegasus is to demonstrate the feasibility of using a parafoil recovery system to create a controlled, directed recovery for a high-powered rocket from over 10,000 ft. − − === [[Prometheus]] === − − The purpose of Prometheus is to demonstrate roll control of a payload descent using PID-controlled fins. − − === [[Talos]]/[[Kythera]] === − − Talos is the launch vehicle for Kythera, SSI’s first generation flight computer system which will feature a Raspberry Pi that reads data from sensors and communicates that data to Teensys (Arduino-based microcontroller) in addition to using radios to provide real time GPS, orientation, and video data. − − === [[Charybdis]] === − − The purpose of Charybdis is to demonstrate passive ascent stabilization using canted fins. − − = Expectations = − + Line 142:
Line 21: − + Line 160:
Line 39: − + − Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. L1 and L2 do not require more than 10 hours combined (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.+ − + − − − − Note: For a much more specific documentation check out [https://docs.google.com/document/d/1c3D9EUYV-cxaDAc-bi3u-ufAYVxP0EIeB3hBln9TbUQ/edit# ''''The Process: From PDR to PLAR'''']. The document provides specific guidelines and expectations for each stage of the process. − − As specified in NASA’s engineering design life cycle, multiple design reviews are used to assess the feasibility and practicality of both attempting and accomplishing a particular project. This includes a Preliminary Design Review ([https://docs.google.com/presentation/u/1/d/1DXe1mLi3W9Z8g58muUl7w96wpbG8cZbLAWL8znXPc2M/edit#slide=id.p3 ''PDR example'']) to assess mission goals, risks, and criteria and is followed by a Critical Design Review (CDR). By CDR, a project is expected to have assessed ''specific'' hardware and software configurations for viability, addressed questions raised in the PDR, and considered manufacturing and production of their final product. Both stages include extensive criticism and evaluation by other SSI members and external entities. − − '''The PDR demonstrates that the overall preliminary design meets all requirements with acceptable risk and within the cost and schedule constraints.''' It shows that the correct design options have been selected, interfaces have been identified, and verification methods have been described. Full baseline cost and schedules, as well as all risk assessment, management systems, and metrics, are presented. − − The CDR demonstrates that the maturity of the design is appropriate to support proceeding to full-scale fabrication, assembly, integration, and test and that the technical effort is on track to complete the flight and ground system development and mission operations in order to meet overall performance requirements within the identified cost and schedule constraints. Progress against management plans, budget, and schedule, as well as risk assessment, are presented. '''The CDR is a review of the final design of the launch vehicle and payload system'''. All analyses should be complete and some critical testing should be complete. − − The FRR examines tests, demonstrations, analyses, and audits that determine the overall system (all projects working together) readiness for a safe and successful flight/launch and for subsequent flight operations of the as-built rocket and payload system. '''It ensures that all flight and ground hardware, software, personnel, and procedures are operationally ready.''' − − Immediately prior to launch, SSI will conduct a Launch Readiness Review (LRR). The LRR is performed on-site to verify procedural compliance and compliance with applicable safety codes. Furthermore, please note that launch-site safety officers will also be present to approve and assess your rockets. − After launch, SSI will conduct a Post-Launch Assessment Review (PLAR). The PLAR is an assessment of system in-flight performance. The PLAR will determine if mission success criteria were met, discuss any adverse events, enumerate lessons learned, and describe any recommended changes to the SSI Rockets program.+ Line 273:
Line 138: − + − Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).+ − +
update rockets leadership
{{rocket-sidebar}}
{{rocket-sidebar}}
[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]
[[File:Pegasus1Launch.JPG | right| 250px | thumb | Pegasus 1 off the pad.]]
= Background =
Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are {{Leadership|Rockets=true}} - let us know if you have any questions about the group or about what you are supposed to do.
SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).
The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which is less about rockets and more about logistics.
= Basic Info =
=== Level 1: H, I ===
== Meetings ==
== Meetings ==
The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as worksessions where all of the Rockets Team members are in the same place at once.
The Rockets Team has general meetings every week; during Fall Quarter of 2017-2018, these meetings are held on Mondays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as work sessions where all of the Rockets Team members are in the same place at once.
Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.
Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.
== Previous Knowledge ==
== Previous Knowledge ==
We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.
We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.
Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:
Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:
Introductions to many of these are available on [[So You Want To...]]
Introductions to many of these are available on [[So You Want To...]]
== Time Commitment ==
== Safety Training ==
In order to get access to MC (our room), all members must have completed basic safety training. INSERT DETAILS HERE, IM GOING TO DINNER.
= The Process =
== Time Commitment ==
== Design Reviews ==
Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.
== Budget ==
== Budget ==
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']
== Mission Control ==
== End Station III/ISS ==
ISS can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in End Station III, ISS houses work sessions and project storage. Note: keycard access is required to the building. For specific questions, contact our workspace manager (see our website). Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), the floor of End Station III (known as Dragon), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).
<noinclude>[[Category:Rockets]]</noinclude>
<noinclude>[[Category:Rockets]]</noinclude> [[Category: Rockets Guides]]