Skip to main content

Lil' Joe, T-7 days...

While I'm still working refining the payloads with the folks who will be launching the HALE mission, I thought I'd at least put up a few more facts and pictures about them here in the blog. Of my two payloads, Lil' Joe is perhaps the most ambitious... or riskiest. Looking somewhat like a blue loaf of bread with a tailfin, the goal is to replicate, in a very small (& cheap!) way, the famous leap of Col. Joseph Kittinger from over 100,000'. The NXT will try a much more modest goal: being released from roughly 80,000', it will free-fall for a short period of time (something like 20 seconds to a minute or more - the exact length of time is under discussion) before "reeling out" the tailfin, which then functions (I hope!) as a drogue 'chute to pull the main parachute out of the body. There will be no control from the ground, or even communication, with the payload during this process - either the NXT "does it on it's own", or the Nevada desert gets a new crater lined with blue foam and very small pieces of ABS.

The command and control for Lil' Joe is fairly simple: when it is turned on, the NXT-G program starts writing timestamped 3-axis accelerometer data to a datalog as fast as it can. Every five seconds it checks a "free-fall flag", and if that flag has not been set it erases the data & starts again. This way, the final datalog should contain a few seconds of data from just before the payload is cut free, extending through the free-fall and the parachute deployment beyond... even though the NXT doesn't know in advance when it is being released. A second sequence running in parallel with the first is responsible for detecting free-fall and deploying the parachute after that. It simply hangs in a loop, waiting for at least 0.5 seconds of near free-fall (less than 0.25 G's) acceleration, and once it detects that sets the "free-fall flag", as well as starting a count down for the parachute deployment. At the moment of deployment this sequence pauses datalogging briefly, runs the motor to unwind the tether & deploy the parachute, and then resumes datalogging (datalogging is paused because a poorly-timed write to the flash memory can mess up the internal clock and motor control, disasterous if the motor in question is releasing your only parachute).

Just how fast and how far Lil' Joe will fall is poorly known: a 20 second free-fall with no friction at all can produce a velocity of 440 mph after a fall of more than a vertical mile. But even with as thin as the air is up there, there will be some friction, & as the payload plummets deeper in the atmosphere and the atmosphere gets thicker aerodynamic effects will limit it more and more. So it's really an unknown right now. The good news is that with the size of the payload bottom and the size of the parachute (24"), it looks like parachute deceleration might be reasonable at under 10 G's for a couple of seconds... but that means the heavy portions of the payload (batteries) need to be very firmly cradled by the parachute lines directly. The team at the University of Nevada at Reno are working with me on perhaps adding some things to the payload (such as a convection baffle for after the tailfin comes off, and perhaps stronger webbing).

There are more pictures of Lil' Joe up in my Brickshelf gallery:

HALE Photos on Brickshelf

As well as a short YouTube video of Lil' Joe. This is really aimed at explaining to the launch team how it is unpacked and packed, but it also shows (near the end of the video) what the internal mechanism does during free-fall. Hopefully this wasn't the last time I ever get to video it :).

Lil' Joe preparation on YouTube



--
Brian Davis

Popular posts from this blog

MINDSTORMS Retires!

2023 is the 25th Anniversary of the MINDSTORMS brand. For 25 years, MINDSTORMS has educated and inspired a generation of robot builders, both children and adults. Unfortunately, the LEGO Group decided to end the line on December 2022. Many ROBOTMAK3RS have been passionately involved with the development of MINDSTORMS through the MUP and MCP programs. Even with the newest Robot Inventor line, several ROBOTMAK3RS were invited to submit additional bonus models that were included in the official app. Regardless of the retirement of a major LEGO robotics product line, ROBOTMAK3RS continue to MAKE-SHARE-INSPIRE using all LEGO robotics platforms available to us. Here is the official statement from LEGO. Since its launch in September 1998, LEGO MINDSTORMS has been one of the core ‘Build & Code’ experiences in the company’s portfolio, carrying with it significant brand equity and becoming a stand-out experience for the early days of consumer robotics and leading to current Build & Code

Celebrating MINDSTORMS with a Remix Part 1

In honor of the 25th Anniversary of MINDSTORMS, we asked ROBOTMAK3RS to combine a LEGO set of their choice with a MINDSTORMS set. Here is what these five ROBOTMAK3RS came up with.  MINDSTORMS Chess Assistant by Arvind Seshan Overview: When you are new to chess, it can be a challenge to remember which pieces go where. Now, you can use machine learning and LEGO MINDSTORMS Robot Inventor to build a tool to help you learn where all the chess pieces go on the chess board. Sets used: LEGO® Iconic Chess Set (40174) and MINDSTORMS Robot Inventor (51515) Review: I really like how the chess set base can store all the pieces underneath and that the board neatly splits in half for handy storage. The chess pieces themselves are very sturdy and well built. My only criticism is the building of the box itself. It was quite difficult to see what pieces to use and since the entire box is made mostly of thin plates, it took a lot of time and patience. I would have liked the storage area to be sliding dra

Celebrating 25 Years of MINDSTORMS

In celebration of the 25th Anniversary of MINDSTORMS, we take a trip through history. Please also visit ROBOTMAK3RS Community every week as we highlight different projects all through 2023 in celebration of the anniversary. Some of the early history is based on the content shared by  Coder Shah  in our  MINDSTORMS EV3 Community Group . Some of the text and links may have been edited from his original posts for consistency and clarity.  1984 - Kjeld Kirk Kristiansen watched a TV program called "Talking Turtle," where MIT professor Seymour Papert demonstrated how children could control robot "turtles" using LOGO, a programming language he developed. 1988 - The collaboration between MIT and LEGO resulted in LEGO TC Logo in 1988, which allowed students to control LEGO models using computer commands. The video shows Papert demonstrating TC Logo. 1990 - LEGO TC Logo was hampered since the robots you built had to be tethered to a personal computer. LEGO and MIT