virginia tech1.4 the team must identify all team members attending launch week activities by the...
TRANSCRIPT
-
Virginia TechNASA USLI PDR Presentation
Ishan Arora, Nicholas Corbin, William Dillingham, Valerie Hernley, Joseph Lakkis, Max Reynolds, Angelo Said
11/14/18 - 3:00 PM CST
-
Contents
● Team Overview● Mission Overview ● Launch Vehicle
a. Vehicle Layoutb. Vehicle Specificationsc. Airframe Materialsd. Propulsione. Recoveryf. Electronics Bay
g. Mission Performance Predictionsh. Validity of Analyses
2
-
Contents
● Payloada. Mission Success Criteriab. Design Summaryc. UAV Componentsd. Navigatione. Navigational Beacon Releasef. Retention System
g. Mission Performance Predictions
3
-
Contents
● Requirements Verification Plana. Generalb. Launch Vehiclec. Recoveryd. Payloade. Safety
● Project Managementa. Budgetb. Timelinec. Scrum
● Summary
4
-
Team Overview
5
-
Team Overview
6
-
Mission Overview
7
-
Mission Overview
8
Mission Statement:
“Our booster will reach apogee at 4,500 feet and separate into two independent
sections, each of which have both a drogue and main recovery parachute. After landing, the booster section will
deploy an autonomous UAV with backup RC that
delivers a navigational beacon to a Future Excursion Area.”
-
0) Launch1) Booster/recovery bay separation2) Main parachute deployment3) Booster and recovery bay touchdown, payload deployment4) Navigational Beacon delivery
9
ConOps
-
0) Launch1) Booster/recovery bay separation2) Main parachute deployment3) Booster and recovery bay touchdown, payload deployment4) Navigational Beacon delivery
10
ConOps
-
0) Launch1) Booster/recovery bay separation2) Main parachute deployment3) Booster and recovery bay touchdown, payload deployment4) Navigational Beacon delivery
11
ConOps
-
0) Launch1) Booster/recovery bay separation2) Main parachute deployment3) Booster and recovery bay touchdown, payload deployment4) Navigational Beacon delivery
12
ConOps
-
0) Launch1) Booster/recovery bay separation2) Main parachute deployment3) Booster and recovery bay touchdown, payload deployment4) Navigational Beacon delivery
13
ConOps
-
Launch Vehicle
14
-
Launch Vehicle: Vehicle Layout
15
Center of Gravity
Center of Pressure
-
Launch Vehicle: Vehicle Layout
16
Center of Gravity
Center of Pressure
-
Launch Vehicle: Vehicle Layout
17
-
Launch Vehicle: Vehicle Layout
18
Center of Gravity
Center of Pressure
-
Launch Vehicle: Vehicle Specifications
19
Vehicle Component Length (inches)
Booster Bay 36.75
Recovery Bay 77.5
Von-Karman Nose Cone 34.5
Boat Tail Transition 5
Total Length 100
CG Location 62.3 inches from tip of nose cone
CP Location 75.8 inches from tip of nose cone
Static Stability Margin 2.15
Thrust-to-weight Ratio 10.04
Rail Exit Velocity 85.6 ft/sec
-
Launch Vehicle: Airframe Materials
20 Fiberglass Carbon Fiber
● Body Tube:○ Carbon Fiber / Soric LRC
Foam Laminate○ Expected wall thickness: 0.14
inches ○ Density: 0.23 oz/in^3○ Matrix Material: FibreGlast
System 2000 Epoxy ○ Peak strength: 3270 lbf
● Fins:○ Fabricated from aircraft grade
birch plywood○ External mounting system for easy
replacement
● Nose Cone:○ COTS Fiberglass Von - Karman
-
● Design Criteria○ Excellent performance in highly compressive
loading scenarios○ Lightweight materials
● Preliminary Airframe Material Selection: Carbon Fiber with sandwich core
○ High stiffness and strength to weight ratio○ Allows for lightest possible construction ○ Application of sandwich core increases stiffness
with minimal use of carbon fiber plys and increased weight
21
Launch Vehicle: Airframe Materials
-
Launch Vehicle: Propulsion
Motor Selection: Aerotech K-1000T Reloadable
Motor Casing: Aerotech RMS-75 2560*
Motor Retention: ● Centering rings ● Boat Tail Transition: Carbon fiber,
Aluminum thrust ring, screw-cap retention system
22
*Looking into borrowing to save money, may use comparable CTI casing (Pro75 3G) with AT Crossloads
-
Launch Vehicle: Propulsion
Constraints:● Mass● Finances
Aerotech produces reliable motors:● Two team members are experienced with
assemblies, RMS reloadable motors ● BATES grains using tubular core allow for linear
thrust curve
23
-
Launch Vehicle: Recovery
Parachutes:● Rocketman Kevlar Skyangle
○ 1 ft for drogue chute○ 5 ft for main chute
Separation Method:● Redundant Altimeters
○ Stratologger SL100○ Adafruit BMP280
● Black Powder○ FFFF black powder○ BP weight determined based on
volume and desired pressure24
-
Launch Vehicle: Electronics Bay
25
1
6
5
423
1. Power for the system is a 6600 mAh Li-Po battery (2200 mAh for Recovery Bay)
2. Arduino Battery Shield3. Arduino Uno microcontroller4. Arduino Ultimate GPS Logger
Shield5. 900 MHz XBee Radio6. Adafruit BMP280
Barometric/Altitude Sensor
-
● Vehicle will maintain stability above 2.0 cal throughout its entire flight duration● Vehicle will be within 100 ft of 4,500 ft target apogee● Commercial altimeters will be used to verify official altitude● Will deliver the payload safely to perform a successful beacon delivery● Vehicle shall not exceed Mach 1
26
Mission Performance Predictions
-
Mission Performance Predictions: Flight
27
Data was reproduced from OpenRocket simulations.
-
● Descent under the main parachutes shall land the rocket sections below 75 lb-ft of energy● Upon landing the vehicle shall be fully recoverable and reusable● No damage shall be incurred to the vehicle or payload systems during flight or landing● Accurately acquire data through the altimeters which are all consistent
28
Mission Performance Predictions: Recovery
-
Mission Performance Predictions: Drift
29
Data was reproduced from OpenRocket simulations.
-
● OpenRocket○ Designed for this specific purpose○ Utilizes a 6-Degree Of Freedom Barrowman method for modeling○ Supported by motor manufacturers within industry○ Allows for customization and modeling of individual components
● MATLAB code ○ Developed based on peer approved research publications○ Takes into account average drag coefficient, surface area, vehicle weight with and without
motor, generalized thrust curve, air density, and launch rail angle
30
Launch Vehicle: Validity of Analyses
-
Payload
31
-
● Mission Success Criteria○ Retained during flight using a fail-safe retention system○ Shall autonomously deploy from the launch vehicle upon signal ○ UAV shall deliver a 1 inch cube (navigational beacon) to FEA
● Team-derived requirements○ Small enough to fit within the 6 inch diameter launch vehicle○ The UAV shall complete the mission using autonomous flight
requiring less than 1 minute of manual input○ Range must be great enough to be able to reach an FEA
regardless of vehicle landing location within the launch site
32
Launch field is about 1 square mile and will contain
multiple FEA targets
Payload: Mission Success Criteria
-
Payload: Design Summary
● Quadcopter● Autonomous (GPS)
and RC navigation enabled● Range: 1.4 miles*● Flight Time: 1.7 minutes● Weight: 0.53 lb● Size: 5.71 x 6.10 x 2.45 (inches)● Cube release mechanism
33* Assuming 7 mph wind
-
34
Payload: UAV Components
-
Payload: Navigation
● Autonomous○ GPS coordinates○ iNav open-source software
● RC Back-up○ Transmitter has switch to activate in
case of autonomous malfunction○ Video with manual control can be used
to fine-tune navigation/delivery
● Ultimate goal of UAV: Deploy a 1 cubic inch navigational beacon to the FEA
35
-
Payload: Navigational Beacon Release
● Video will be used to verify arrival at the FEA
● Transmitter will have auxiliary switch designated to the cube release
● Upon signal, cable cutter will fire and release the cube
36
Cable Cutter
-
Payload: Retention System
The fail-safe retention system provides both vertical and horizontal load support while doubling as a bay to protect the payload during separation, guiding it out when it finally deploys.
Vertical Retention: Guide rods running through holes in the UAV
Horizontal Retention: Cables holding down the UAV are taut until cut by cable cutters
Bulkheads: Plates at the ends protect the payload during separation and from black powder charges
37
-
● Battery Capacity: 1000 mAh● Range: 1 mile despite 20 mph wind● Flight Time: 1.7 minutes● Assumptions:
○ Constant wind speed○ Constant thrust○ CD & A estimated from lit review
38
Theoretical results will be validated by extensive testing to improve performance
predictions
Payload: Mission Performance Predictions
-
Requirements Verification Plan
39
-
40
Section Requirement Verification Method
Verification
1.2 The team will provide and maintain a project plan to include the following items: project milestones, budget and community support, checklists, personnel assignments, STEM engagement events, and risks and mitigations
Inspection All project management documents will be available on the team's shared drive. Each report will contain project management information
1.4 The team must identify all team members attending launch week activities by the Critical Design Review (CDR)
Interviews, Documentation
Team leads will make a list of all individuals attending launch week activities prior to CDR
1.5 The team will engage a minimum of 200 participants in educational, hands-on science, technology, engineering, and mathematics (STEM) activities prior to the submission of the CDR
Documentation ESM Rocketry will turn in the STEM Engagement Activity Report
1.6 The team will establish a social media presence to inform the public about team activities Documentation Team members, and specifically the social media lead, will regularly update the social media sites and website
1.9 In every report, teams will provide a table of contents including major sections and their respective sub-sections
Inspection The editor will verify a table of contents is present in every report
Requirements Verification Plan: General
-
41
Section Requirement Verification Method
Verification
2.1 The vehicle will deliver the payload to an altitude between 4,000 and 5,500 feet above ground level
Inspection Altimeter data
2.3 The vehicle will carry one commercially available, barometric altimeter to record the official altitude
Inspection Use of Stratologger commercially available altimeter
2.4 Each altimeter will be armed by a dedicated mechanical arming switch that is accessible from the exterior of the airframe
Inspection The team plans on using commercially available switches to arm the electronics bay components while the vehicle is on the launch rail
2.5 Each altimeter will have its own dedicated power supply Inspection Altimeters will use 9V batteries
2.6 Each arming switch will be capable of being locked in the ON position for launch
Inspection and Demonstration
Checklist, inspection, and implementation of required devices
2.10 The launch vehicle will be capable of being prepared for flight at the launch site within 2 hours of the time the Federal Aviation Administration flight waiver opens
Demonstration, Design
Will design and have procedure/checklist for assembly, will perform dry-run to practice assembly
Requirements Verification Plan: Launch Vehicle
-
42
Section Requirement Verification Method
Verification
2.11 The launch vehicle will be capable of remaining in launch-ready configuration on the pad for at least 2 hours without losing the functionality of any critical on-board components
Demonstration, Inspection, Test, Design
Testing of electronics system after checklist procedure, will perform power budget calculations
2.17 The launch vehicle will have a minimum static stability margin of 2.0 cals at the point of rail exit
Analysis, Design Calculated through simulation software based on vehicle design
2.18 The launch vehicle will reach a minimum velocity of 52 fps at rail exit Demonstration, Test, Analysis
Calculated using simulation software, developed code, and demonstrated during launch
2.19 All teams will successfully launch and recover a subscale model of their rocket prior to CDR
Demonstration The team is planning on launching a subscale vehicle which will not be high powered
2.20 All teams will complete demonstration flights as outlined in the rulebook Demonstration, Test The team has checked with local TRA chapters to ensure they will be on schedule to launch on time and meet requirements
2.21 An FRR Addendum will be required for any team completing a Payload Demonstration Flight or NASA-required Vehicle Demonstration Re-flight after the submission of the FRR Report
Demonstration, Documentation
The team has checked with a local rocketry organization and will plan to fly its Payload Demonstration Flight before the submission of FRR
Requirements Verification Plan: Launch Vehicle
-
43
Section Requirement Verification Method
Verification
3.1 The launch vehicle will deploy a drogue parachute at apogee and a main parachute is deployed at a lower altitude
Design, Test The team will design the recovery system such that drogue parachutes are deployed at apogee and will use chute releases to deploy the mains at a lower altitude. This system will be tested during both the sub-scale and full-scale launches.
3.1.1 The main parachute shall be deployed no lower than 500 feet Analysis, Test This will be calculated through simulation software based on vehicle design
3.1.2 The apogee event may contain a delay of no more than 2 seconds Test Altimeter data will be analyzed post-test to verify deployment of the drogue chute within 2 seconds of hitting apogee
3.3 At landing, each independent section of the launch vehicle will have a maximum kinetic energy of 75 ft-lbf
Demonstration Hand calculations are used to predict the maximum kinetic energy. This uses parachute data (coefficient of drag) as well as vehicle weight information. This will be verified during post-test analysis once flight data is available.
3.6 The recovery system will contain redundant, commercially available altimeters. The term “altimeters” includes both simple altimeters and more sophisticated flight computers.
Design The vehicle will contain a Stratologger SL100 and an Adafruit BMP280
Requirements Verification Plan: Recovery
-
44
Section Requirement Verification Method
Verification
3.8 Removable shear pins will be used for both the main parachute compartment and the drogue parachute compartment.
Design The recovery system is designed with removable shear pins
3.9 Recovery area will be limited to a 2,500 ft. radius from the launch pads. Design, Analysis The design choice to deploye a drogue first and then a main at lower apogee helps limit drift. Drift calculations were performed with various wind speeds. Even with 20 mph wind, the drift is less than 2000 ft.
3.10 Descent time will be limited to 90 seconds (apogee to touch down). Analysis, Test Hand calculations were used to predict descent time based on parachute size and vehicle weight. This will be verified with altimeter data after the test launches.
3.11 An electronic tracking device will be installed in the launch vehicle and will transmit the position of the tethered vehicle or any independent section to a ground receiver.
Design, Test The electronic bay is designed such that each separate section contains a GPS that can be used for tracking the vehicle. This will be tested both through ground tests and during the flight tests.
Requirements Verification Plan: Recovery
-
45
Section Requirement Verification Method
Verification
4.4.2 The UAV will be powered off until the rocket has landed on the ground and is capable of being powered on remotely after landing
Design, Testing
The team will design a MOSFET circuit, triggered using a radio transmitter, to remotely turn on the UAV after the vehicle has landed. This system will be tested in the lab and during the payload test flight to verify it functions properly.
4.4.3 The UAV will be retained within the vehicle utilizing a fail-safe active retention system
Design, Analysis, Testing
The retention system will be designed to withstand the large forces that could be experienced during flight. Analysis will be performed to estimate the force on the payload during flight. Testing will be performed to verify the payload remains secure under a variety of circumstances.
4.4.4 At landing, and under the supervision of the Remote Deployment Officer, the team will remotely activate a trigger to deploy the UAV from the rocket.
Testing The team will design a MOSFET circuit, triggered using a radio transmitter, to remotely turn on the UAV after the vehicle has landed. This system will be tested in the lab and during the payload test flight to verify it functions properly.
Requirements Verification Plan: Payload
-
46
Section Requirement Verification Method
Verification
4.4.8 Once the UAV has reached the FEA, it will place or drop a simulated navigational beacon on the target area
Test GPS will be used to autonomously navigate to the FEA. The cube release mechanism and GPS navigation will both be tested.
4.4.12 The team will abide by all applicable FAA regulations, including the FAA’s Special Rule for Model Aircraft
Documentation The team will identify all applicable FAA regulations and will read them thoroughly to ensure compliance
4.4.13 Any UAV weighing more than .55 lbs will be registered with the FAA and the registration number marked on the vehicle
Measurement, Documentation
The final weight of the UAV will be measured and proof of registration with the FAA will be provided (if heavier than 0.55 lbs)
Requirements Verification Plan: Payload
-
47
Section Requirement Verification Method
Verification
5.3.2 The safety officer will implement procedures developed by the team for construction, assembly, launch, and recovery activities
Documentation The safety officer will hold all team members accountable to following all procedures related to safety
5.3.4 The safety officer will assist in the writing and development of the team’s hazard analyses, failure modes analyses, and procedures
Inspection The safety officer will help write and will review the hazard and failure modes analyses
5.4 During test flights, teams will abide by the rules and guidance of the local rocketry club’s RSO
Documentation, Inspection
The team will contact the local club's president before attending any launches. The team will abide by all safety rules and will respect the authority of the RSO.
5.5 Teams will abide by all rules set forth by the FAA Documentation The team will identify all applicable FAA regulations and will read them thoroughly to ensure compliance
Requirements Verification Plan: Safety
-
Project Management
48
-
49
● Specific parts chosen● Identified suppliers● Developed funding plan
○ Total: $7,153.77○ Current deficit: $809.19
*The team is currently pursuing corporate sponsors/VSGC Grant to cover the remaining $809.19 deficit.
Project Management: Budget
-
Project Management: Timeline
● Gantt chart○ Long-term goals
● Scrum agile project management○ Taiga.io website○ 2 week sprints ○ Organized into 3 levels:
■ Individual Tasks■ “Epics” big-picture goals■ “User Stories” group tasks into categories
○ Assign tasks to individual team members
50
-
51
Project Plan: Scrum (Epics)
-
52
Project Plan: Scrum (User Stories)
-
53
Project Plan: Scrum (Sprint/Tasks)
-
54
● ConOps designed around payload deployment● Target apogee: 4,500 ft● Vehicle designed around budget and payload constraints● Simulations predict stability and ability to reach target apogee
factoring in wind speeds and launch angles● UAV payload designed to complete mission
○ Autonomous navigation to FEA○ RF control possible for fine-tuned delivery as needed○ Cable cutter used for cube release upon arrival
● Developed funding plan and adopted agile project management
Summary