UAV::Pilot version 0.2 is now up on CPAN. The big change in this one is initilizing the navigation stream and parsing the data. I also whipped up this retro-videogame looking graphical output:
The usability of the nav data is a bit limited at this point, because we need to grab the stream continously in a loop for display while also processing the flight commands. This is where an event system like AnyEvent will come in handy. You can try programming it around AnyEvent (or whatever event system you like) with what’s there right now.
The major work for the v0.3 release will be getting an event loop integrated into the library.
My 370z needs new tires. The tread depth is technically legal, but driving in the rain is scary, and they don’t grip very well under hard launches. They’re also 19-inch wheels, which apparently nobody is selling in the best, most grippy street tires right now.
Tires might seem like the most boring part of the car, but they’re the only part that touches the ground (well, usually . . . ). They’re also something that tends to get a little bit better every year.
Bridgestone Potenza RE-11’s were my first choice. I had them on my RX-8, and they were great. Problem is, they’re slowly introducing the RE-11A’s and pulling the older RE-11’s from sale. Which would be all well and good if they actually had RE-11A’s in 19-inch sizes. The originals are going or gone in 19-inches, and the new ones haven’t been introduced there yet.
Then there are BFGoodrich g-Force Rivals, and the Dunlop Direzza ZII’s. The Rivals don’t seem to come in 19-inch sizes yet, and while the Direzza’s do, they’re not in the widths I want.
Bridgestone Potenza S-04s are a step down from all the above, but they are in the right size.
Two or three months from now, I’m sure this will all be worked out, but I can’t wait that long. I have an event coming up and I want sticky tires for it. The question might come down to the S-04’s slightly less sticky compound being made up for with a slightly larger contact patch.
There are parts of the Parrot AR.Drone that are rather underdocumented, and one of those is getting the navigation data. Once you activate the nav data, it doesn’t send the data directly to you. Instead, it sends it to the 184.108.40.206 muticast address.
Which is great and all. That means you can have one person controlling on their laptop and a bunch of other people watching the nav data on their own systems. But it’d be nice if their docs told you this.
There’s also a way to get it to unicast to your address, but they certainly don’t lay that out.
Anyway, the good news is, I can receive the AR.Drone’s nav data now, which is a big milestone for the 0.2 release.
Playing around with WordPress themes. I wanted something akin to my old custom-built blog, with the retro-greenscale console screen look. The Mantra theme looked close to what I wanted, and then I messed around with the CSS a bit. Looks to be good enough for now.
UAV::Pilot is a Perl library for controlling UAVs. It currently works with the Parrot AR.Drone, with plans to expand to others in the future.
The current library supports basic commands, such as takeoff, pitch, roll, yaw, vert speed, and land. All the preprogrammed flight animations are also in place. Navigation data and video are not yet supported–see the ROADMAP file for future plans.
Github repository: https://github.com/frezik/UAV-Pilot
Took my 370Z autocrossing at the Columbus 151 Speedway on 4/28. YouTube vids available.