Tuesday, August 26, 2008

More Thank Yous

As you might guess from our on going "Thank You" posts that we have been accepting donations to help pay with the team effort. It's a nontrivial amount of money to do testing. As you may have noted, we have a donation button - hint, hint - but we also have a Cafe Press Store. If you have a desire for some team paraphernalia and want to help the team with our enormous testing bill, by all means, check it out!

That said, we wish to thank Theodore Baird and Karen Davis for their contributions towards helping us reach our goals. Thank you both of you.

Monday, August 25, 2008

A Spin off Idea, son of the LLC Team Summit

We are back from the LLC Team Summit. Our blogging has been a little behind schedule. We're going to try to get caught up. Life's been a little complicated. That said, we have to agree with the X Prize Foundation that the event was definitely a success, even if we would have worded it a bit different. There were some brilliant people there and we found their designs absolutely fascinating. There were things we never thought of. One team, a new one under wraps still, really impressed us. We hope that the team makes it to the launch pad this year.

We, ourselves, are rushing as fast as we can to get our ducks in a row. It's going to be a harrowing journey, no matter what, but we came away with something from the summit that really needs to be brought to a larger audience. Perhaps our blog might be a vehicle (ha! we kill ourselves...errrmmm...bad choice of words) to see if that idea might gain soem traction. We have already bounced this off our FAA contact and we'll see if it gets anywhere.

That idea is what we light heartedly calling the "So You Want to Build a Rocket" conference. The suggestion that we made was that the the FAA would present the requirements for their paperwork and the reasoning behind that paperwork. We think that this should be the the opening conference for the next Lunar Lander Challenge, a required conference, that would preceed registration as to give teams an idea of what they are getting into and why.

This would greatly improve what the teams for the LLC - or any other group that wants to build rockets without much prior experience - generate and reduce the time that the FAA would need to hand hold each and every group that comes to them. It would also help the X Prize Foundation as well.

Just a thought.

Wednesday, August 20, 2008

Flight Safety Zones

From Inner Most to Outer Most:

Safety Clear Zone (domes on the launch and landing pads): Where the team works without any other personnel within that zone while the rocket is grounded.

Soft Abort Zone (inner most yellow polygon): This is where the rocket has the pilot override and try to get it to teh landing pad mnually.

Hard Abort Zone (inner most blue polygon): This is where the Primary Dead Man's Switch is triggered because it has deviated from the planned flight path in such a manner as to be dangerous.

Operating Area (outer most yellow polygon): This is the area large enough to contain all the potential debris from the instanteous impact point analysis.

Flight Hazard Zone (out most blue polygon): The outer bubble for safety based on FAA regulations.

There's a lot of detail we are leaving out, okay a massive amount, but this ought to give you some eye candy and some insight into what and why the paperwork is so hefty to fly even a bitty rocket like our own.

Monday, August 18, 2008

More Thank Yous

1. Robert Baird
2, Thomas Langley

Thank you, gentlemen!

Briefing Holloman: Instantaneous Impact Point

As a team, we have been preparing for briefings we have to give at Holloman AFB on Tuesday and Wednesday. We're excited and a little daunted by the task. There will be teams there that have been doing this for a few years. There will be people from Holloman and FAA that are experts in this and want to make sure we're not crazy as a loon with a rocket pack.

One of the single most important aspects of this presentation is that of safety. How are our procedures on the ground going to be? If your rocket goes nuts, what will happen? How will we react? This is actually probably as important as anything else, if not more so, than what you do for the rest of the project. We're not going to run through the whole of what we did to prepare for this, but we would like to talk about the instantaneous impact point.

The instantaneous impact point (IIP) is the spot where the rocket will crash land based on the position and trajectory of the vehicle when things go wrong. This is really crucial to know at any given time during a rocket's flight because that will dictate where the public and uninvolved should be cleared from and what property may be damaged. IIP is actually more important to track than the position of the vehicle since what the rocket may damage is of more concern to the flight safety folks than the rocket itself.

We of Team Phoenicia, with the advise of some friends that work in the flight safety business for a test range, did a quick analysis of The Wind at Dawn. It turned out that the back of envelope calculations we had done for an estimate for our safety zones fit pretty closely to our first order model. With the help of our graphics powerhouse friend up in the cold, cold north, we produced a video for the presentation.

There are a few things to note about this. One, it's not a perfect representation. It's a first order model and therefore needs some fine tuning. Second, you ought to realize that the higher you go, the greater the radius is when the rocket loses its marbles and crashes - if it does at all! Our job is to make sure this is unnecessary. However, the flight folks, Holloman and FAA, really need this. We'll, of course, give them the numbers too if they ask, but we'll wait and see.

IIP: know it or no flying.

More another time. There's a plane to catch!

Wednesday, August 13, 2008

Mountains of Paperwork

One of the things we keep going on about is the amount of paperwork that needs to be done. It really is enormous. There are two sets of paperwork that any team that wishes to compete need to be aware of. The first is that of the X Prize Foundation's and the second is the FAA. Neither is nontrivial. However, the latter is emphatetically the heftier of the two.

The X Prize Foundation's requirements are not too bad. They require the team to register, make some presentations, and keep them up to date each month on the team's progress. Our registration came in at approximately 24 pages. The presentations are approximately twice that in PDF form. The monthly updates are about two pages in length. Again, still nontrivial.

Other the other hand, there's the FAA requirements. oy. They require a burn time waiver, a tethered flight waiver, and a permit for flying your vehicle. These overlap, but they are not the same. The example permit application that the FAA places up on their webpage is 75 pages long and omitts some big "attached documents." Ours came out to be 92 pages long. The burn time waiver comes out to be around fifteen pages. The tethered waiver, which we haven't yet submitted, is around ten pages so far and growing, but we're holding off on submitting this as yet.

This has all been generated since the X Prize Foundation said go in mid June...and based on what we have been told there will be some revisions and growth needed in the FAA application. We don't have a dedicated paper generator and it has been causing us some problems as far as resource contention. It has impacted our testing and coding. As a consequence, we will be pushed to the limits in order to make our deadlines. Sleep is not an option. At least until the papers have been served.

That is why we are strongly recommending any participating teams in the future have a dedicated writer/paper generator/human printer. This person is someone that needs to be more than jsut a technical writer. This must be a person that grasps everything that will be covered in the writing. This person also has to have very good people skills as well: they have to interact with the FAA, XPF, and the whole team seamlessly and flawlessly. Making enemies of any of the above causes the cart to lose its wheels, folks.

Switching gears, we have some more thank yous to put out. These go out to the following people:

1. Andrew Gray
2. Pascal le Rudulier
3. Rachael Moore

That's a wrap for today and we hope you will join us again soon.

Monday, August 11, 2008

Monday Update

First up, there has been a a little more publicity for the team. Will Baird's, the Team Leader, has a day job that has taken note of his participation in the Lunar Lander Challenge and, with the successful completion of the LLC, the Google Lunar X Prize. No, he wasn't interviewed.

We keep getting a lot of questions about the information on the team page. Specifically about the thrust of our rocket. Everyone else as far as the team 's profiles go on the 'matchup' tool have a thrust to weight ratio that is at least one. Why don't The Wind at Dawn? There's a good reason. It's not because have a typo in our page. It is not because we don't have a clue about what we are designing. Rather it is because the information we provided is the ignition thrust, not the maximum thrust at full throttle. That's about a third more than what's listed. Just a small clarification there.

Our FAA application is progressing and its now in the hands of the engineers there. We have hopes we'll make it in time, but that Tethered Flight ruling has thrown more than a few wrenches into our plans. Paperwork really does eat a lot of our time.

That wraps it up for today! Happy Monday!

Sunday, August 10, 2008

A Little More of The Wind at Dawn

This is a frame from the previous Travel Cam video. You can see the relation to the drawing in the post below.

Saturday, August 9, 2008

The Wind at Dawn Drawing

This is a very simplified version of The Wind at Dawn. It was put together from the CAD drawings we did and then 'cleaned' so that it would actually look like something instead of billions of holes and micro details. Note, there are missing details: no wiring or plumbing for example. There are other omissions as well, but it works for what it was intended for. We thought we would share it as a way of showing what we have been up to.

Friday, August 8, 2008

A Bit of Progress and Some Quick Thank You's

Our post today is going to be a little bit short and not as interesting. The team is working on coding up the last of the data acquisition that is needed for The Wind at Dawn and finishing out the paperwork for the FAA. We need to write up a quick report for the X Prize Foundation and get that to them ASAP too. There's a briefing at Holloman we're prepping for as well. Like we said, get someone on your team for the paperwork alone. Make sure they like it!

The actual fun part of our entry happens in a couple weeks.

Now we'd like to have a quick moment to do some thank yous to those that have donated to the team. We already have mentioned our main sponsors already. However, we've had several people outright donate money without so much as a thank you. We're rectifying that now. A big thank you goes out to:

1. Amanda Northrop
2. Ola Nordhus
3. Marilee Layman
4. Carlos Yu
5. Micheal Hellwig
6. Julia Heathcote (and her Ethical Husband)
7. Suzanne & Greg Lee

More to come!

Thursday, August 7, 2008

The Wind at Dawn Flight Simulations

When we set out to enter the Lunar Lander Challenge, we had to do a lot of work to design The Wind at Dawn. There was a whole month spent working out some of the really basic equations and then translating them into some simulations of the flight based on changing mass, throttling, thrust profiles, wind, and several other factors. It was interesting work because it was all tied together. If you consume propellant, the amount of thrust needed to flight at a given height decreases which causes throttling changes which changes the amount of propellant that is to be used. etc. In the end, we had a series of numbers for given time frame snapshots. These were heights, lateral displacements, throttling requirements, thrust, etc. We took these to the ever talented Scott E of Coherent Lighthouse and his nice little IRIX cluster. He did a crazy bang up job and produced the following visualizations of the event.

The first visualization is if you had a 'travel camera' that was back about 3m or so that would allow you to focus on the vehicle as it lifted off and keep altitudal pace with it. Unfortunately, the viz machines choked part way through and we had a deadline, so the video is incomplete. Since the flight isn't really that interesting from this POV, we asked if he'd just give us what he had.

The second visualization is from the point of view of an observer 250m away from the flight path of The Wind at Dawn. This video shows the whole flight.

Let's say that we strongly recommend the work of Scott Elyard. He's a hard worker, able to get work done on short notice, and a good guy all around.

Wednesday, August 6, 2008

We are LIVE!

Welcome to Team Phoenicia's blog!

We're dusting everything off for our fun and games PR wise. Multiple people have probably paid call on our oh-so-quiet blog. It's not because we wanted to be quiet. it is merely because we had to. There are some rules with regards publicity and announcements by the X Prize Foundation. This is merely so that everyone is coordinated with regards to the talking heads, etc.

So what are we doing?

We are attempting to aim for the Google Lunar X Prize.

Hold the phone/block on that socket! You are announced by the X Prize Foundation as participating in the Lunar Lander Challenge NOT the Google Lunar X Prize.

That's right! We're working on the LLC as a demonstration phase for our backers. The LLC vehicle, The Wind at Dawn, is not a direct prototype for the GLXP landing stage. It is, however, a step in that direction. We are only entering into the Second Level of the LLC where our lander must fly for 180 seconds and put down on a lunar simulant landing pad.

Once we have completed our demonstration here for our backers, we will be moving on to register for the GLXP.

Who are we?

We are a team of techno types from mostly government lab/test range day jobs.

The Team Leader, William Baird, works in the supercomputing field. Wes Pickens works in specialized antenna development. Brandon Rohrer works in advanced human-robotics interfacing, namely prosthetics. Shane Thomas works in programming for a test range. Lyudmila Baird is a former government accountant and currently a student. That's a little vague, but we're very well known in our respective fields. This isn't wholly inclusive of everyone in Team Phoenicia for the GLXP effort. It is inclusive of everyone in the LLC effort.

Who are your backers?

This is a bit of a pitch and thank you to the companies that are backing us.

First up is Wind River. These guys have provided us with software and persuasive support in a big, big way. They really have been there for us. They're software is top notch and their people have been very, very responsive.

Secondly we have Ansoft. Their help has been invaluable. Their software is the big hammer of RF/Microwave design.

Finally, of our public backers, we do not want to leave out Emachineshop. Without their expertise and support, we would not have been able to build The Wind at Dawn.

We hope to announce a handful more backers very, very soon.

So where are you now?

We are a little behind schedule, but our design is complete. Our parts are on order and will arrive very shortly. We are planning on doing our first test fires of the prototype engine shortly. Our software is humming along. We have done simulations and plenty of analyses. If anything, we'd have to say we've done more paperwork in support of licenses and participation than we've needed to do rocket science. (o.O)

Our recommendation for any team in the future is that they have a person dedicated to just doing the paperwork. We are not kidding about that at all.

We will try to have an update daily.