Level 2 Intermission

 

As we await the dramatic conclusion of Geza’s Level 2 flight, here’s a brief intermission to keep you all up to date.

Last Minute Internship Opportunity

We have four opportunities for undergraduates to take part in an 8-week paid internship with Far Horizons. This year’s projects include a two-way radio communications system, and software to track the missions in real time while predicting flight paths and landing location. We particularly encourage applications from students with strong skills in electronics, programming, engineering or electronic communication.

The internship runs weekdays June 18-August 9, 35 hours/wk, with a stipend of $3,200. Applicants must have a permanent residence in the Chicago metropolitan area and be US citizens. To apply, send a cover letter, CV/resumé, and list of relevant courses you have completed to:
Human Resources
hr-ISGC@adlerplanetarium.org
Deadline for full consideration is May 20, 2013. Funding for these positions is provided through grants from NASA and the Illinois Space Grant Consortium.

FH at the Maker Faire This Saturday!

Far Horizons will have a booth at this weekend’s Chicago Northside Mini Maker Faire. We’ll be featuring some of the cool opportunities Far Horizons offers to those in the Maker community. We’ll also be trying to razzle dazzle the visitors to the fair with some of the experiments and equipment we use in our stratospheric missions. If you’re in the neighborhood, come by and say Hi. The fair runs from 10-4 on Saturday the 18th at , 3601 North Milwaukee Ave.

Hey Teens and Volunteers! (I’m looking at you ASW alum)

Want to have a cool time hacking for civic change? The Adler is hosting a Civic Hack Day as part of the National Day Of Civic Hacking June 1-2. This 26-hour event will focus on teen involvement in “hacking for change.” If this piques your interest, we’re looking for interested teens and mentors to form a team to come up with and tackle a cool idea with real community results. Anyone who was involved in last year’s hack-a-thon knows how much of a blast the event was. Check out the links for more info. If you’re interested, shoot me an email or leave a comment.

3rd Annual Operation Airlift, Lifted Off

For the third year running, Far Horizons helped support the Air Force Academy High School Operation Airlift competition. Last Saturday nearly 40 students formed teams and competed to design ROV airships to complete challenges and be crowned the winners. If you want to see some of the images of the event check out this link. Thanks to Far Horizons staff and volunteer Roxanne! They were part of over 30 teens, mentors and volunteers who helped make this the best competition so far. Also, teens blogged live about the event here and here throughout the day.

Finally…

For anyone not familiar with the brilliant, smart and science-based web comic XKCD I have one thing to say… Check it out! The reason I mention it today is that the creator, Randall Munroe, also has a spinoff, What If?, where he answers some of the weirdest and most interesting questions from readers with real science. This one titled, “How many model rocket engines would it take to launch a real rocket into space?” particularly struck my interest and I thought I’d share it.

Until next time…

Permanent link to this article: http://farhorizonsproject.com/blog/level-2-intermission/

The Flight of the Viper (part I)

A couple weeks or so ago I ran into Gorman Cook, a member of the Adler’s Sheppard Society and an avid high power rocketry fan. As we chatted about Far Horizons he mentioned ThunderStruck, an upcoming launch event he intended to attend. ThunderStruck, now in its fourth year is a production of the Indiana Rocket club, centered in Purdue. It’s a big event and has a big launch site, featuring an altitude limit of 18,000 feet. That’s the highest limit east of the Mississippi! I have to admit, it got me thinking… Ever since I got my Level 1 certification I’ve been thinking about going for my Level 2. After all, we’ll need Level 2 certification for SPARK. But the launch was 10 days off. Could I get everything together in time?

Tethys

The first step was to get a rocket. We’ve had good luck dealing with Public Missiles Limited in Michigan so that was my first stop. After a bit of browsing I found their “Tethys” kit, a simple but robust rocket that looked approachable in the time allowed. The Tethys is 53″ long and comes with adaptors so it can be flown on 29, 35 and 54mm motors. For my certification flight I’d be wanting to use a J engine which comes in both 35 and 54mm versions so this gave me maximum flexibility. The Tethys also comes with a 36″ parachute. More on that later. Ordering on Friday was easy and the kit arrived on Tuesday morning. Michigan really is just a hop, skip and jump away.

Construction was pretty much straightforward. The new lab is really just an ideal place for doing this sort of work. All the tools at hand and plenty of space. First task was to make sure all the parts fit and that nothing was binding. The nose cone was a bit tight so I filed down one of the fitting rings. Half an hour later  the nose cone was sliding smoothly with just a bit of a tug for the final separation. This is just what is wanted. The rule of thumb is that you ought to be able to hold the rocket up by its nosecone without it slipping, but if you give it a few shakes it ought to fall out. Any tighter and it might  not eject and deploy the parachute. Any looser and it might slip off during aerodynamic deceleration after engine burnout.

motormount

Next step was to assemble the motor mount. The motor mount is essentially to hold the motor straight and firmly, and to allow quick changes of the motor. Usually it consists of a central “phenolic” tube (in this case 54mm in diameter) that holds the motor and a set of spacing rings to center the tube in the rocket body. The adhesive of choice for high power rocketry is always epoxy. I chose a 15 minute setting epoxy to give me a bit of working time, but also to not make me wait too long between bonds.

fins

After the motor mount was in place the next step was to attach the fiberglass fins. Like most high powered rockets, the Tethys has “through the wall” fins. The fins slide through slots in the body tube and butt up against the motor tube with epoxy. To give extra strength the fins are then filleted on the outside of  the body tube. As an extra step I filled the space between the two centering rings, and the rocket and body tube with an expanding foaming epoxy that is designed to take the heat of the rocket engine firing. This provided a very solid bond for the fins and the motor tube. They weren’t going anywhere!

Simply sliding the motor (in its casing) into the motor tube wouldn’t be sufficient. While the friction fit would keep the motor from moving around in normal transport, when the motor is ignited it would provide vastly more thrust and slide around. In particular, the motor tube is not sealed at the forward end. The motors after all come in a variety of lengths and also the ejection charge gases need to expand out and deploy the parachute. What this means though is that unless the rocket motor is well restrained the thrust will push the motor forward and out the front of the motor tube into the rest of the rocket. With flames shooting out the back into the inside of your rocket and pushing through the parachute and nosecone… The result is a complete flaming catastrophe! Even if this doesn’t happen then the ejection charge can result in a backward thrust, throwing the motor out the rear of the rocket to plummet to the ground… Also a bad situation.

motor_retainerThe motor  retention system is the solution to this scenario. Basically this is simply a combination of a design specification for motors and a simple screw-on ring. The specification stipulates that the motor casings all have a “lip” which is wider than the motor mount tube. This prevents the motor from advancing forward into the rocket body further. The screw-on ring then prevents the motor from falling out the back. It is all made of solid aluminum alloy and is probably the sturdiest thing in the rocket.

Attached to the motor tube assembly is the piston, shock cord and parachute. The piston is a closed tube that slides up and down inside the body tube of the rocket. Its job is to protect the parachute from the hot gases of the ejection charge. It is attached at the bottom to the motor tube and from the top to the parachute and nosecone.When the rocket finishes its burn it, after a delay, sets off an ejection charge. The expanding hot gases push the piston upward which in turn pushes the parachute and nosecone out of the body-tube. You can see the piston in the third image in this post.

With the last touch on the piston the rocket was ready to fly! Or was it? For a rocket to be stable the center of pressure (essentially where the drag acts) has to be sufficiently behind the center of gravity. Usually at least 1 body-tube diameter. The center of pressure I calculated with the help of a nifty program I wrote that allows one to estimate the center of pressure depending on the parameters of the rocket. One can also simply read it off the instruction booklet that comes with the kit. The center of gravity is a bit more difficult because while I could measure the center of gravity of the finished rocket, that didn’t include the weight of the rocket motor. And I couldn’t get the rocket motor until I was at the launch site since I didn’t have my level 2 certification yet! The center of gravity without the motor was only just a bit more than a body-tube diameter in front of the center of pressure. It probably would have been ok, but I decided to give myself a bit of insurance. To move the center of gravity up a bit I filled the nose cone with foaming epoxy and used a heavy metal eyebolt to attach the parachute shock cord to the nosecone.

All this took until Friday evening. In my next post I’ll tell what happened at the launch!

Permanent link to this article: http://farhorizonsproject.com/blog/the-flight-of-the-viper-part-i/

Recent Results

Two Flight Reports In One

Flight 56

Catching up with the last two of our stratospheric flights, we performed Far Horizons flights #56 and #57 over the past few weeks. Here’s the rundown of the results…

Final check of ascent control system before launch by the IMSA team

Final check of ascent control system before launch by the IMSA team

On launch #56 on the 2nd of March, we faced some challenges. Temps were low and some late complications with the experiments made issues tough. At least this time the IMSA built ascent control system left the ground (and made it back). We didn’t have the 30mph gusts to contend with and the ballast was reduced to 1kg to make the launch easier. Lou’s cut down mechanism also went up for its first in flight test. We flew two of the newest generation GoPro Hero 3 cameras as well.

The launch went pretty smoothly and we were positioned within a few hundred meters of the landing. Some snow moved in by the landing which prevented us from observing the landing but recovery was a breeze as it dropped just off the side of the main rural road.

Ready for launch

Preparing for launch

The postmortem was not so kind. A failure in the switch of the ascent system prevented the stepper motor driving the valve to open. The payload hit ground with most of its 1kg ballast still in the hopper. The cut down failed to trigger as well. These were all tests of these new systems so design improvements were all expected to be needed.

A snowy retrieval just short of the trees.

A snowy retrieval just short of the trees.

The GoPros offered a new concern. Both cameras stopped recording before expected. The up-pointing camera stopped recording before the burst and the side camera stopped before landing. According to the GoPro folks, the only reason they should stop recording is if the SD card fills or the batteries no longer powered the camera. Both cards were not filled so we can surmise the batteries failed in flight. Not a good sign for our 360 flight where one failure of any of the nine cameras would negate the results of an entire flight.

Also, thanks to Roxanne for the great pictures of the flight.

Flight 57

Things turned out somewhat better for flight #57. We were joined by a newly trained team of 12 Air Force Academy High School students on their first flight. They worked together wonderfully to get us launched almost exactly on schedule. This time the improved cut down mechanism work to perfection. At exactly 12:11 CDT the cut down triggered at approximately 75,000 feet as programed. This was helpful since the retrieval took us southeast of Lafayette, IN. A longer flight would have made retrieval and a reasonable return time for the students difficult.

View of Indiana and a cloud front off to the East. Lafayette, IN is visible on the far right.

View of Indiana and a cloud front off to the East from the March 21 flight. Lafayette, IN is visible on the far right.

The ascent control system had another switch failure unfortunately. Though the mechanism was redesigned for better reliability, the screw that acted as a pin used to trigger the switch loosened and was lost. Upon retrieval we documented a reduction in the amount of ballast in the system. Some data analysis will be needed to see if there was a single ballast dump and whether that had any recorded effect on the ascent speed. Thanks to Jeff’s GPS data logger we have positioning recorded at a rate of 5 Hz or 5 record per second. This should give the IMSA students the precision needed to deduce whether their unit was effective.

New Lab Procedures Coming Soon

Due to the incredible growth of Far Horizons in the past year, we’ve realized the need for improved procedures for collaborative design, documentation and organization. We’re outgrowing our more informal methods. This should help make all your efforts more effective and transferable to other team members. To begin with, as an example, we’ll be working on protocols for versioning software, archives of technologies and designs, timelines for projects, more efficient project teams, and clear documentation of procedures.

As a first trial in that effort Alan wrote up a nice step-by-step guide to using the MicroDAQ atmospheric data logger this past weekend. He also was able to create a database of all our GoPros, their batteries and SD cards so we can begin keeping track of issues with any combinations we fly. Now that we have that, we’re planning on running a cold test this weekend for all our GoPros and batteries. We’ll have dry ice on hand for the experiments.

On a related note, the 2012 ASW volunteers did an admirable job of diagnosing and testing the high speed features of the GoPro Hero 3 camera this weekend. We now have a better confidence in using this feature for future flights and experiments.

Rocket Time Again

We’re planning another Far Horizons field trip up to the Bong Recreational Area west of Racine, WI to launch some high powered rockets on Sunday, April 21st. The launch, hosted by the folks at WOOSH, is a great opportunity to experience some of the most powerful amatuer rocket launches in the region. The plan is for Mark and me to get our Level 1 certifications. Our other Level 1 certified flyers, Geza and Jeff, will have the opportunity to fly if they’d like, although Geza may want to take the opportunity to see if he can get his rocket down from the tree he lodged in back in September ;-) . Jeff may try out some flight electronics. He’s been working on a variety of sensors and experiments including a GPS data logger, pressure sensors for altitude determination and tracking beacons for retrieval.

If anyone is interested in joining the team in the journey up north, there’s a sign up sheet in the lab or you can drop us a comment or email confirming you’d like to come along for this all day event. Deadline to sign up is Monday, April 15th. We’ll try and arrange transportation and I may be able to sweet talk Jeff into setting up the barbeque once again.

 

Permanent link to this article: http://farhorizonsproject.com/blog/recent-results/

Older posts «

%d bloggers like this: