Background and Motivation
In 2022 KOTS had some stability and launch rail velocity problems partially caused by not knowing the weight of rocket components until very close to competition (after the fins had been sized). Another cause was uncovering the lack of thrust at the beginning of the Kismet engine burn which decreased off rail velocity by an alarming amount.
In general, further rocket integration and optimization of flight profile has been identified as an area with good potential for growth in the future. Both to reduce likelihood of integration mishaps as well as to improve overall design consistency and focus effort on high reward projects.
Project Description
This project is to create a cycle where:
Subsystems create design concepts and do design work as before
Subsystems and engine team estimate length, mass and engine performance at specific check-in dates (most likely providing high, low, and predicted values). Note engine team would be creating RSE files at each cycle.
This data is fed into various OpenRocket simulations determining apogee, stability, acceleration (for loads), velocity (off launch rail and throughout flight), and any other flight characteristics of interest.
Load simulations run using acceleration data
Resulting simulations are used to write a short digestible report about the results and the highest value design focuses to be disseminated throughout the team and the team leads.
Subsystems are aware of the rocket as a whole and how any changes impact the overall system.
Cycle repeats until design lock with length and mass estimations becoming more and more precise as design is finalized.
A minimum viable product if time/team cooperation is difficult, is to offer case by case simulations to determine how various design changes already under consideration would affect the rocket. This could also be done at the same time as “cycles” however would not be ideal to do alone as it is likely to miss the larger system.
For sure this will be done for fin sizing as in previous years.
Requirements
Must gather information from all rocket subsystems with reasonable confidence that the data is within some accuracy. To ensure this accuracy the method must be easy to understand for both experienced team members and brand new members.
OpenRocket/RSE simulations must predict how changes to rocket length, weight, and engine performance affect rocket performance.
OpenRocket/RSE simulation process must be streamlined enough to be done regularly.
Loads analysis must be done at each cycle
Reports must be written which are extremely digestible and accurately represent the data. (giving effective actionable information to team members)
Regularly scheduled cycles must be implemented without significant schedule slip
Minimum scope of this project is to analyze design decisions using OpenRocket and RSE file generation to help inform team members about high value changes
Maximum scope of this project is to create a project management tool/system to consistently check in on overall key integration parameters (mass, length, engine performance) and disseminate actionable, easy to understand information to drive design decisions while also considering case by case changes to the design.
Required Documentation (Insert links when created)
Instructions for subsystems to submit mass & length information Instructions for Adding Data to Length & Mass Tracking Spreadsheet
Spreadsheet to track information for each cycle. https://docs.google.com/spreadsheets/d/1poRCKzhNSZfQRoP2KN2xZRwuLLkZauFutRtuNmLCAjw/edit#gid=0
Documentation on overall process (design doc) https://uwaterloo.atlassian.net/wiki/spaces/ROCKETRY/pages/edit-v2/43224662139
Mini reports at each cycle.
Document/s to track OpenRocket and loading analysis simulation outputs.
Cycle 1 what we are simulating: Cycle 1 what are we simulating:
Cycle 1 simulation data:https://docs.google.com/spreadsheets/d/1O7EI6IzpHXXCWCLqXju4nxJKGlHdr366o6npeITfkjM/edit#gid=0
Deliverables Timeline
Startup work: (starting early sept. ending at end of sept.)
Create document/system to track mass and length and collect input from the subsystems (Sept. 18 tentative)
Get feedback on it and improve it. (until end of sept.)
Get input from the subsystems alongside the first length/mass data about what scenarios they would like to see simulated
Cycle 1: Starting 1st week of October Ending end of October
Predicted 1.5 weeks to gather data from subsystems (with enough advance warning). Data due entered into spreadsheet by Oct. 12
Predicted 1 week to run open rocket simulations.
Predicted 1 week to write mini report.
Total 3.5 weeks
Results influence the detailed design
Cycle 2: Starting 1st week of January, ending end of January
Same schedule as above
Results are used to finalize designs for the CDR, finalize fin size
Fin sizing finalized (Last year January 11th)
Cycle 3: Starting last week of March, ending mid April
Should incorporate all final design masses and some fabricated part masses
Same schedule as above
Results are used for final project report
Cycle 4: Once the rocket has been completed
Represents the as-built results with fabricated masses
CDR: Early February
Design Log:
20-13-2022
Conversations in slack about changing datums and datum use in general occurred recently. See slack for more details. The short is that we should reconsider the datums before the next cycle.
Overall the project is going well. Propulsion didn’t quite meet the deadline for input due to busyness but basically everyone else did. Now on to simulations.
Remember to get the lengths of the sections for the deadline.