Skip to main content Skip to navigation
Washington State University Aerospace Club

Direction for Spaceport America Cup 2019

Noah Thompson, Rocket Team Lead

Matthew Dickson, Control System Electronics Lead

Current Air Brake Design Prototype 

INTRODUCTION

In order to align objectives with the current aerospace industry and establish WSU as a contender on the world intercollegiate rocketry stage, the aerospace club is developing custom simulations and control systems for complex aerodynamic surfaces. The team’s initial design for submission to Spaceport America Cup 2019 included two payloads: a Doppler effect based velocity measurement and an egg. The club has now replaced the doppler payload with an active air brake. The original payloads were auxiliary to the primary goal of the submission, which was to serve as a test platform for the future development of aforementioned control systems. This lead to resources being removed from the original goal of the rocket. In late January the decision was made to remove the placeholder payloads, instead pursuing a simple active braking surface directly. Given a time of only five weeks to produce a functioning prototype for test launch, the group determined that use of an airbrake on this year’s rocket would only be during ascent. The P.I.D. and simulation platform developed for this system will directly apply to later, more ambitious endeavors. With the use of such control surfaces, the club can obtain a level of trajectory control unattainable through other means.

INITIAL DESIGN

This system was considered to contain primarily only an electrical and mechanical system. The physical structure of the rocket increase (an inherent requirement of the technology’s function). The mechanical components selected also were evaluated on their relative response time, as fast adjustments will need to be made during flight. Lastly, each proposed design’s significance with regard to the current state of astronautical engineering was considered as well. The proposed designs are illustrated in Figure 1.

Figure 1. Considered Air-Brake Design

A weighted case study was performed, comparing each design on the criteria of mechanical simplicity, electrical simplicity, drag capabilities (ability to significantly effect overall drag), Cost, Response, and Engineering Significance (how impressive is it?). Simplicity was weighted heavily due to the time constraints. This study is summarized in the Table 1.

Table 1 – Qualitative trade study of air brake designs.

Air Brake Trade Study
Criteria Weighting #1 #2 #3 #5
Mech. Simplicity 0.3 8 5 6 9
Electr. Simplicity 0.3 7 7 6 9
Drag Ability 0.1 10 10 2 2
Cost 0.1 3 4 4 7
Response Speed 0.1 9 4 8 10
Relevance 0.1 8 6 2 2
TOTALS 7.5 6 5.8 8.1

Ultimately design five, the rotating fin section brake scored the highest in the trade study for its simplicity. However, due to its very low hypothesized drag ability, more in depth analysis of the design was performed.

Two SolidWorks flow studies of design five, one with holes open and one with holes closed, was performed. The total force against flow only increased 3N (from 230N to 233N). These preliminary findings suggest that such a drag modification device might not be significant enough for our purposes. The more traditional air brake was chosen.

Figure 2. Rough conceptual model of design #5, ring air brake

The air brake will be designed to be so electrically and mechanically simple as possible. Almost all internal structures related to it are designed to be cut in two dimensions using a water jet (or a laser cutter for the wooden test rocket components), thus minimizing manufacturing cost and time to production. The mechanism is designed such that a single linear actuator or large servo could engage all brakes by pushing on a single platform.

 

Figure 3. Base model of design #1, unoptimized, configured for test rocket. Left shown closed, right shown open

 

Final design and optimization for test rocket will occur from February 15th to 22nd, in tandem with test rocket primary structures fabrication and implementation of control schemes on stationary test bed.

 

The test rocket will have the centering rings cut from sheet metal, the center platform and linkages 3D printed with solid infill, and the fin supports will be wooden. On the spaceport model, the entirety of the structure will likely be either composite or metal, with the center structure being the only machined component.

 

POSSIBLE CONTROL METHODS

The design shown in this document is mostly conceptual (not yet having been optimized). The model shown is designed for a test rocket, flying to an apogee of only 100ft and meeting FAR 101 regulations. This rocket is intended for repeated launch on private land outside pullman, clear of restricted airspace. The data collected in this set of launches will be used to compare four primary frameworks for airbrake control, and two logical methods for approaching onboard data processing. The team’s goal is to minimize the amount of time necessary to run one computational cycle while maximizing altitude control accuracy. These combinations are listed below. Test rocket systems will be run off of a Teensy 3.6.

 

Frameworks:

“Bang-Bang” ControllerSystem has binary states. In the case of the airbrake, if overshoot is detected the brake will extend fully.

 

P-ControllerSystem state depends on error. The larger the error, the stronger the corrective action.

 

PI-ControllerSystem state depends on error and duration of error. The larger the error, the stronger the corrective action. In addition, if the error is too small for corrective action but is sustained, proportional corrective action will take place.

 

PID-ControllerSystem state depends on error, duration of error, and change in error. The larger the error, the stronger the corrective action. Small but sustained error will also result in a proportional corrective action. In addition, corrective action will be taken proportional to the current change in error.

 

Logical Methods:

Acceleration to AccelerationThe movement of the air brake is determined only by a direction and proximity to desired acceleration. The control system operates only based on acceleration response to movement, without prior knowledge of expected drag.

 

Acceleration to Brake PositionDesired brake position is determined as a function of needed acceleration to reach apogee. This function is created using the linear interpolation of a two dimensional coefficient of drag matrix. This dataset is generated in terms of velocity and brake position, but reparametrized in terms of average acceleration at a point.

 

 

BUDGET & TIMELINE

There is very little time to accomplish this goal, and so a strict timeline will be adhered to.

A test rocket will begin launching the weekend of March 9th, weather allowing. Design of the test rocket concludes on February 16th, with construction beginning that same weekend. The base code for the test rocket will be completed prior to the end of February. Ordering of materials for spaceport rocket fabrication will be completed upon approval, with construction beginning as soon as they arrive. The club’s updated layup technique sacrifices a small amount of weight and strength in exchange for dramatically faster turnaround and low rejection rate as compared to previous years. All rocket body tubes (and extras) should be completed within a week of construction beginning.

The full rocket will be completed in time for full scale test launch in late April, the weekend before finals. If less than three club members can be found to attend this launch, it will be postponed until late May.

4 Switches Buck boost converter

Design and Justification

The buck-boost circuit that was used during the alpha prototype was the most simplistic topology involving just one-switch in the buck-boost converter. Based on a published paper by the Department of Electrical and Electronics Engineering SSN College of Engineering [1], the one switch steps up/steps down the converter that we uses has a relatively high voltage and current stress on components overtime compare to the buck or boost converter. By using different topologies with more than 1 transistor, the efficiency of the converter could be significantly increased to over 90%. Oculus has chose a new 4-switches mode selection buck-boost converter (figure 1).

Figure 1. 4 switches buck boost converter

 

Due to having 3 extra transistors, the circuit requires a more complicated controller compare to the previous design. The circuit operates on 3 different modes with 4 different switching states (Figure 2).

Figure 2. Switching states of the Buck boost converter

Oculus has developed a controller that could be used to control the circuit. The mode selection circuit is a state machine that would detect the output voltage, and decide which operation mode the circuit will run on by comparing it with the reference voltage (22.5V).

Figure 3. The control system

 

Figure 4. Selection mode

Figure 5 & 6. PID control

Result

The new design buck-boost converter has shown a lot of promising results, between the first submission on March 1st to current date, Oculus has managed to have some significant progress. The problem with the control circuit earlier has been fixed and now it’s working and capable of producing clear signals (figure 7).

Figure 7. Buck mode, boost mode, and buck-boost mode control signals

The reference voltage was set to be at 22.5V (typical voltage for 6s battery system). Although the circuit itself has yet to be able to produce a clean and reliable waveform, it indicates the circuit work exactly how it was designed to be (figure 8). Based on the reading, the most logical reason for such signal has to be from out of tune PID control. Oculus believe once the PID has been tune up to match the circuit, the signal should be clean up and a stable output voltage will be produced

 

Figure 8. Output signal.

 

Figure 9 shows our model for the entire power system of the drone

 

UPDATE: Saturday Mar 16, 2019 . 4:08pm

 

Based on the signals (figure below), I have pinpoint where the bug might be. For some unknown reason, the PID control stopped working during the boost mode. I have some suspicious why this is happening and have a plan to tackle this. Right now I’m using 1 PID for everything, there is a possibility I have to build a dedicated control for each mode. Before I do anything, I would need to go back to my drawing board and recheck my  TF calculations.

UPDATE: Monday Mar 18, 2019 . 10:14pm

A PID control was replaced by a PI control. I rechecked my math (figure 11) and was able to determine the correct duty cycle and managed to clean up the signal noise. However I have yet to determine the cause of the bug shown in 2 figures below. I have determined it must be within the PI control itself

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 10a. Output signal on 3/16/19 & 3/18/19

Figure 11. Circuit analysis

UPDATE: Monday Mar 26, 2019 . 1:03 am:

One week has passed since the last update, the main culprit has been finally identified. After recheck and confirm my math and logic, it has been clear to me the problem must lie with Simulink itself. Having a PID control within multiple blocks has proved to be hard for Simulink to process, and thus fail to produce the intended signals. After multiple different design configurations, I have nailed down the one that would work with my model. Figure 12 below shows the control signals as intended and figure 13 shows the voltage output

Figure 12. Control signals

Figure 13. Output signal

Despite having a lot of noise and being very unstable, the signal has indicated that the output voltage hovers around 22.5V (Reference voltage). There are still a lot of work ahead to clear up the signal, but so far the output voltage looks very promising

Figure 14. New PI controller