After debating a couple of different designs including the use of cell phones we settled on using an actual GPS chip and transmitting APRS data back to our recovery team (and more importantly to APRS repeaters in the area as we found out). Also included was a buzzer for alerting the recovery team which was a handy feature. The build team consisted of Harold, Erik, and Ken with programming help from Travis. All of whom did a great job.

Launch day was Sunday August 29th and we all met at the Lab to assemble. The recovery team consisted of Ethan, Erik, Ken, Mike, and myself. Later we’d be joined by Michael W. who was letting us use his field to launch. Launch prep went smoothly with lots of double/triple/quadruple checking of “is the camera on?”.

We let go at 10:58 AM EST and anxiously awaited the first transmission form the balloon aloft. It was an agonizing 60 seconds. We all sat around watching our baby float off into the clouds until it was nearly out of sight and then began the frantic packing of gear into cars to start the chase. Sadly Mike parted ways with the rest of the group here as he had to get back to the Lab to prepare for the 757 CCC meetup that afternoon. Michael W. decided to join us and brought along baby Ridley who’d been enjoying (except for the loud noises of the helium tank as we filled the balloon) the launch prep from the porch.

Tracking the balloon felt a bit like being a storm chaser. We were receiving live data from the balloon for the first 16,000 ft. and tracking it via aprs.fi after that calling between vehicles with status updates on our walkies. For a while we managed to get ahead of the balloon and stopped for lunch but after higher altitude winds got ahold of it we were racing to keep up.

After peaking at over 103,000 ft. we confirmed the balloon burst and was on the way down after a few consecutive readings of decreasing altitude and pulled over to try to get a fix on its eventual resting place. Sadly we realized we were nearly 30 minutes away from where it was headed. The last transmission we received was at 3,000 ft. and (when reception permitted) we were getting quite a few text messages and twitter inquires as the the balloons status from those following along at home. The situation didn’t look too good as the area under the last reported location was heavily wooded. The balloon’s camera also documented this for us quite well…

The car’s GPS, having been given the last known coordinates of the balloon, told us to “navigate off road” into a soybean field and the woods behind it but we decided against it and pushed on looking for at least a decent place to pull off the road. Luckily there was a fire lane just down the road that served quite nicely.

While we were there Ethan pulled out an old scanner we’d brought along and tuned into the station on which the balloon was broadcasting. After a few second we heard a screech of data that made us all quite excited. The balloon was a live and we could hear it! We adjusted the input to the laptop and managed to get coordinates off the last message. With updated coordinates we set off on foot down the fire road². The handheld GPS was telling us that it was basically directly down the road; sadly this was too good to be true. The balloon appeared to be 500-700 ft. off the road into the woods and, somewhat discouragingly, 96 ft. above sea level. Off we went exploring.

The first trek didn’t yield anything other than a debate over if we’d head the buzzer or not. We retreated to the fire road to try to make a call to Harold in an attempt to get confirmation on what we were hearing. While there wegot another GPS fix on the location with the handheld which wasn’t getting great reception in the woods. The group had mixed feelings about what we were hearing but decided with some encouragement from Ken to make another attempt. We headed back into the woods and kept looking in treetops hoping to catch a glimpse of the bright pink parachute. Strangely i did find a pink party balloon lying in the woods along the way.

I happened to not be looking at treetops when i caught a glimpse of pink in the trees. All i could see was a swatch of pink and nothing else but i couldn’t really think of anything else that it could be. I called to Erik and Ken to get eyes on it as well so we didn’t lose it when trying to get through the underbrush and then we headed on. What awaited us was both exciting and a bit daunting — the balloon was hanging about 20-30 ft. up in a tree.

Ken and Erik grabbed some large branches and began trying to catch the parachute lines with them so we could pull it down. We managed with not too much effort and soon had payload, parachute, and balloon remnants in our hands. We rushed back through the woods and began our trip back to the car to try and get the pictures off of the card. At this point i realized that the payload was still taking pictures! The buzzer appeared to have died but everything else was still working. Again, amazing job by the build team!

Once in the car Ethan pried open the payload container and pulled the SD card from a quite hot digital camera. We let it cool for a bit and then feasted on the fruits of our labor. Some truly amazing shots from our first attempt at high-altitude ballooning.

The project was a great success and a lot of fun. Thanks to Workshop 88 for coming up with the idea that motivated us to participate and best of luck to all of our fellow hackerspaces competing.

For more information on the project be sure to check out 757labs.org for blog posts as well as the 757 Labs Flickr Pool for some great photos.

[1] I guess we probably could have done without it landing in a forest in North Carolina but it only added about 30-45 minutes to the recovery time.

[2] Which incidentally was also an access road for a local hunting club…

Due to this strange love of arcades i’ve always wanted my own multicade cabinet (because i just don’t have the room or the desire to be that guy who has a full arcade in his house). I’ve had an X-Arcade stick for a while and it’s fun for playing “reproductions” on the PC but it’s just not the same if you’re not standing in front of a massive wooden cabinet flailing away at a joystick.

This weekend was a big arcade auction down in NC and a few friends were taking a truck down in hopes of bringing back some pinball games. On a whim i asked them to be on the lookout for a nice cabinet in good condition with a working monitor and enough buttons to play something a little more modern than Ms. Pac-Man (not that i have anything against Ms. Pac-Man, which is a game i have many fond memories over). Luck would have it that they ended up bringing back a Tekken Tag cabinet for me! But sadly no pinball machines.

Inspecting the cabinet it seems to work fine though Ethan (757 Labs‘s local arcade repair wizard) suggests a re-capping of the monitor just to clear things up a bit as he’s has luck with that approach in the past. After Matt D. and Ethan played a quick game of Tekken (Matt coming out the victor) we got to taking things apart and figuring out what we had to work with.

The board is a Namco System 12 which was the same board used in Soul Calibur and Mr. Driller both awesome games i hope to find as swap-ins for this cabinet. Since the System 12 is a JAMMA board i’ve already ordered a J-PAC and I-PAC² to hook a PC up to the cabinet. The next step will, hopefully, be the hardest part: waiting for parts to arrive.

When i was a kid i absolutely loved getting my first pocket knife. It was given to me by my granddad and i’ve still got it, somewhere, amidst all the other pocket knives i’ve collected since. To this day I carry a pocket knife or multi-tool just about everywhere i go (insert TSA gripes here) because they’re simply so damn useful. So when i saw Gever Tulley’s TED Talk on dangerous things for kids in which he suggests all children should be given a pocket knife i was interested.

Tulley also suggested in his talk that children be allowed to take things apart and learn how they work which was another of my favourite hobbies as a kid. My father would always bring home broken computer equipment and i would disassemble it and, rarely, put it back together again. Part of me thinks this is what lead to my love of computers and tinkering.

Looks like Tulley’s book Fifty Dangerous Things has finally been released and if it’s anything like his TED talk it should be excellent. Will definitely be picking up a copy myself.

Maybe i’m just spoiled by the MacBook Pro’s touchpad but i really miss being able to 4-finger swipe to open Exposé. Granted fitting four fingers on a Magic Mouse would be a bit of a pain but i still feel like more could have been done with the mouse.

On the plus side the right-click functionality doesn’t feel as awkward to me as the Mighty Mouse did, however i find myself trying to two-finger click for right-click sometimes as thought it were a touchpad. An option for middle-click would be really nice (three-finger click?) as i’m getting tired of seeing the “open in new tab” context menu in Safari.

All-in-all a decent product and so far i’m not writhing in pain from RSI as i expected i would be with all the gesturing.

More recently the NYC Resistor hackers have been working on an 8′ Lite Brite. It’s not net-enabled, but that’d take the fun out of it.

Any other super-sized toys i’ve missed? Wonder what’ll be next.

In the early days of OS X the Energy Saver preferences looked a little different – users could set a time to wait before putting drives to sleep.

Thankfully after some digging i realized it could all be set through the pmset command. The man page has everything you need but for the lazy here’s the gist for disk sleep timing. pmset takes a flag to determine which power profile you’re changing: wall-charger (-a), battery (-b), UPS (-u) or all profiles (-a). Next simply pass it the disksleep argument and a number in minutes.

Set all power profiles to sleep the disks after 15 minutes instead of the typical 10:

sudo pmset -a disksleep 15


Setting the time to 0 will disable disk sleep altogether for that power profile.

One interesting thing to note is i originally stumbled onto this on a rather old article that suggested using the spindown argument instead of disksleep as the man page now suggests (as of 10.4). Using spindown does not cause pmset to complain though it appears to disable disk sleep altogether.

Stumbled across this depiction of the 20 Largest Bankruptcies in the history of the world. I love how cheerful the graphic is in comparison to the depressing truth it is displaying. All in all a great little bit of info viz.

To the random internet stranger who, through coho, i apparently demanded the “internet sex” from, hats off to you my friend.