(Imported from old site; original post: Tuesday, February 5, 2013)
So I have escaped the winter snowfall of Kentucky in lieu of California’s weather. I am currently in Ventura California at the Gordon Research Conference in Atmospheric Reentry Physics. Why am I qualified to be here, you ask? Don’t worry. I don’t know, either…
I was invited to present information about the REBR project that my team decided to design. We still didn’t have the project fully defined at the time, so we did as much research as possible, figured out where REBR could be best used (e.g. research universities), guessed at what we thought REBR could be used for in addition to its current capabilities, and defined the project ourselves. We then created a large presentation poster containing these ideas. “Hopefully,” we thought, “Aerospace Corporation will agree that the direction we have chosen is the best direction.” And they did. Well, Dr. Bill (William) Ailor did. But he IS Aerospace Corporation to me, so same thing.
Dr. Ailor was the only one in attendance from Aerospace Corporation (that I found), and after reading the poster and talking it over with me, he gave us the go-ahead to continue the work we started. There have been other people I have had conversations with here that have also agreed, at least to an extent of wanting to see more development of it, and that it has good potential. Including people from the ESA (European Space Agency), DSTL (Defence Science and Technology Laboratory) from the United Kingdom, NASA Langley, and Lockheed Martin. No big deal… Those are in no particular order of awesome, because they are all awesome.
Following is the poster that was presented at the conference about our new design for REBR. We call it, REBR-UPS, which stands for ReEntry Breakup Recorder–Universal Payload System. Beware: it’s 12.5 MB. Keep in mind, the actual size of the poster is very nearly 4 feet wide, and 5.5 feet tall.
(Imported from old site; original post: Tuesday, January 8, 2013)
So, tonight I met with my team about the final choice of project. After discussing it and voting, we all agreed that it would be best to proceed with REBR rather than the CubeSat. The actual design work starts tomorrow. We still don’t have a project fully defined from NASA/Aerospace Corporation (the company that invented REBR), but I’m sure we’ll get that all settled soon. Not much else to say other than I am excited for the year ahead. I hope (know) that we’ll do great things.
(Imported from old site; original post: Wednesday, December 26, 2012)
Because of finals week and finals week preparation, I haven’t had a chance to give any updates, but there is good news on the NASA front: funding has been approved as of December fourth. That means that I will be working on a CubeSat next semester! I actually already anticipated receiving funding as well as UK approval, so I’ve already started building my team. I feel good about my team, and when everything gets in full swing, I’ll give them a proper introduction.
Also, I had a telephone meeting this past Thursday with Dr. Martin from UK, Dr. Ioana Cozmuta from NASA Ames, and Dr. William Ailor from Aerospace Corporation. We discussed the possibility of working on a few different improvements of REBR rather than the CubeSat. I have yet to discuss it with all of my team members, but so far with those I’ve talked to, it seems pretty split on which we should work. Many more questions to be asked, but that’s okay–they’ll be answered in time.
(Imported from old site; original post: Saturday, October 20, 2012)
As discussed in the NASA Project entry, I have been attempting to make my senior design project at UK awesome. And awesome things require awesome amounts of money. So, you have to start early.
Recently, Dr. Alexandre Martin (my old, but young, fluids professor, that I mentioned in the NASA Project entry) and I wrote a proposal to NASA asking for money. I was surprised to receive a letter of support prior to the submission of the proposal from none other than Ioana Cozmuta herself (also discussed in the NASA Project post). To quickly sum up, she was essentially the inspiration for this project. The proposal was just submitted today (with her letter included, of course), and I guess we’ll back some time between a year and six months from now. Yes, in that order.
So I may be exaggerating a bit on the time, but it should be before January of next year (2013). Other proposals will need to be written, of course, to other companies. I certainly do NOT volunteer my company to give massive amounts of money to this effort. Why should I when there are aerospace companies with a much larger budget than mine! That’s a joke. Laugh. A true joke, but a joke, nonetheless. Laugh anyway.
Here’s the proposal if you’d like to look through it. The letter is attached as the last page of the PDF: MARTIN_TP_Project_2012
(Imported from old site; original post: Thursday, September 6, 2012)
It’s funny how an idea you just want to do for fun can evolve into something bigger than you thought, isn’t it? For now, and at least into the somewhat new future, what I am about to discuss will be referred to as my “NASA Project”. It sounds cool that way.
I have my senior design (part 1) project next semester, and I have been planning ahead for a long while now that I don’t want to do the traditional project of “Here. Analyze this bolt. Now print off graphs. Repeat. Try not to kill yourself from the monotony.” I decided that before my first semester here at UK even began! But it wasn’t until this past January or February that I really decided what I wanted to do: space. I wanted to do space. And I phrase it that way because it sounds better than “I want to accomplish a feat in the area of some of the most advanced subject matter in the history of man.”…well, okay, so it doesn’t sound better than that, but at least it’s shorter.
(Note: so I’m not doing this under my company, but dangit, it’s cool, and I’m still doing it, and so I’m gonna post about it!)
I brought this up at one point with my old fluids professor. He’s not old. The class was old. I mean it was taken in a semester prior. Anyway, he took an interest in the project (the specifics of which I will dive into here in a moment). Well, he informed me today, out of the blue, that he will be giving a talk at NASA Ames tomorrow morning, Friday, and he would like for me to prepare some slides about the project so he could discuss it and possibly drum up some support. I was thrilled, to say the least.
The project is about finding an economically-friendly way of testing thermal protection systems (TPS) for new spacecraft. I’m sure you’ve seen the black stuff on the bottom of the space shuttle. That is a type of TPS. Specifically, that TPS is an ablative TPS, which means that it would partially disintegrate during re-entry, helping carry heat away from the vehicle quicker than non-ablative TPS. But that’s not important, just interesting.
NASA has used roughly the same TPS for 50 years on the space shuttles (or rather had used; the space shuttle program has now been retired). Why is this? Legacy. Why fly a billion-dollar spacecraft with a TPS you don’t KNOW will work. You can test new TPS in an arc-jet on the ground all year long, but that doesn’t mean it’s proven itself in flight. I’d be a bit hesitant to put TPS on my extremely expensive spacecraft, too! Newer, better TPS exists already today, but nobody wants to be the first to “see if it really works”. This was all discussed by Ioana Cozmuta (NASA Ames) who conducted a seminar at UK, and this discussion was also the inspiration for this project.
So how do we get around this? By testing the TPS on a relatively inexpensive spacecraft, and form the TPS in a certain geometry where we can extrapolate how it will behave over a variety of different shapes and sizes. Now, forgive the lack of detail in the CAD drawings. I did this in 30 minutes:
Picture 1: RetractedPicture 2: Air Contact
Picture 3: Possible TPS Geometry
I won’t go into too much detail, because many things will probably change after the project gets approved/started…at least it better be an approved project! How can you turn down space? Answer: you can’t.
This is a 3U CubeSat, which means it is basically the size of 3 CubeSats stacked on top of each other. The red part of the picture is TPS that we already know works. The orange is the test-TPS to be evaluated. The yellow is the holders used to secure the TPS to the vehicle. The white is ultrasonic sensors. And the blue is obviously the body of the craft.
There can be a maximum of four (4) test-TPS (orange) on the vehicle, or maybe one can be a control-TPS, or maybe it’s all the same TPS but will all different geometries (and they can all be either ablative or non-ablative TPS, but they must ALL be of ONE of these; no mixing and matching of this detail). Many different possible combinations here. A possible geometry to be used is in Picture 3. It looks simplistic, but it is made in a way to test several different radii and slopes for the air to contact during re-entry. I’m almost positive this will have to be changed, because I came up with that in my head in literally 5-10 seconds, and I don’t have a PhD in fluid dynamics.
No matter the geometry, the test-TPS will be secured to the vehicle with the [yellow] holders. I could go into some overly complicated details about how it must secure properly at all points on the base of the test-TPS else it risks fragmentation and blah blah blah. It’s glue. It sticks. It holds. There is one thing of note about the holders: the surface has been coated with a non-ablative TPS. Why? In the event one of the TPS breaks off from the vehicle, the holder will then make contact with the air, having been shaped in a manner beforehand with the hope of stabilizing the craft during re-entry in the event something like this happens. It obviously needs some heat protection during this, so the non-ablative TPS performs this job.
The ultrasonic sensors are for continual mapping/monitoring of the surface of each test-TPS. This data will be constantly transmitted during re-entry, just in case the vehicle is lost for any reason. The data will also prove useful for observing the effects of re-entry at a specific time during re-entry. This time will correspond to a certain altitude, and knowing how things behave at a certain altitude is actually quite important for physicists. This, in turn, will allow for the validation of numerical models (computational fluid dynamics), and will allow engineers to develop even better TPS! This cycle will continue as more tests are performed with this craft.
During launch and orbit, the vehicle will have the test-TPS tucked away to avoid damage from anything (e.g. debris), as shown in Picture 1. As soon as re-entry begins, the test-TPS is thrusted out to a stationary position via a worm-gear drive, the final position shown in Picture 2. The worm-gear is important, as it keeps the test-TPS at a synchronized distance from the vehicle, else the vehicle runs the risk of toppling–a low risk, but a risk nonetheless. Shortly thereafter, the backside of the craft will be severed, and a special radio cable (not pictured) will unravel itself from the inside of the vehicle, long enough to be sufficiently far enough away from the vehicle to not allow ion interference from the plasma generated due to re-entry.
Data is collected on the ground during flight (this is a LOT more complicated to do than you might think…or so I’ve been told). After a certain altitude is met, the radio cable is cut away from the vehicle, and a parachute (also not pictured) is deployed. At this time, the test-TPS is retracted back into the sides of the vehicle. The parachute should slow the craft down well enough that when it hits water (please please please hit water…70% chance!) the test-TPS is undamaged, and remains in the same state as it was before the parachute was deployed.
A flotation device of some sort, and a GPS will also be present on the craft, as well as various other instruments that measure whatever. Just if we have room/weight to spare, may as well use it. I really couldn’t care less what else is on it, as long as my mission is unhindered and successful.
