Good hacking night last night. D came over so that we could hack on owen, my little NSLU2 box that's been on the shelf for, oh, a few years. After a few false starts (involving things like having to remember passwords I haven't used since 2005), we threw together a quick LAN off my laptop, got owen on that network, and successfully logged in. We then figured out that trying to configure a bridge between eth0 and ra0 was more trouble than it was worth, so no updating owen straight from the package server for now. I'll need to get the switch set up before I can actually drop owen on the main network, and I don't have the furniture for that right now, but owen clearly still works like a charm and now speaks DHCP, so overall I'll call that a win.

Our eventual goal is to set up pokylinux, as a "just to see if we can, since there's not a pokylinux build for this particular hardware yet" project, which will probably involve doing some compilation on the box itself. That's going to be slightly hilarious; I haven't done a multi-day toolchain build since, oh, 2001 or thereabouts. Good times.

Laterish today I'm going to pop round to the electronics store that also sells RC cars, planes and helicopters to see what my battery options are; I assume it's easier these days to supply 5V/500mA off something rechargeable than it was four years ago. (I need to be gainfully employed before I can actually buy one, as I expect sticker shock, but this is how budgets are made.)

I also dug up the little USB-to-Roomba-serial-interface circuit I was assembling some time back, and found the ostensibly Linux-compatible Bluetooth and 802.11g dongles that have been waiting ever so patiently. Yep, that's right -- after far too long on the shelf, the Evil Robot Vacuum Cleaner Army project is rolling once more.

... woot.com had the Roomba Discovery 4220 SE on special yesterday for $150 plus $5 shipping, so I did a little budget-checking and decided it was time to start establishing my robot vacuum cleaner army. (Ever since the Bluetooth-enabled Roomba cockfight at ETech back in March, I've been thinking it would be cool to get a bunch of Roombas and write flocking and swarming algorithms for them, then bring them to a conference, have them lock onto some poor bastard's Bluetooth cellphone or PDA, and watch while cackling hysterically.)

I could only afford one, but one is enough to start playing around with the Serial Command Interface. I'm pleased that the SCI manual shows a Python code fragment for changing the baud rate, but all the commands are bit-level, power-this-pin-for-this-long/send-this-opcode-and-data-packet instructions. It doesn't appear that anyone's written a higher-level API (at least not in Python, though the Illinois Roomba Lab (!) at UIUC has a C++ one). (And why would I want a Python Roomba API? Because then any Nokia S60 phone becomes my Bluetooth-Roomba-army control platform. I love you, Python interpreter. Muahahaha.)

(Note to self: in that case, do we open up a need for encrypted channels between cellphones and robots? Should I draft an RFC for SRCP, the Secure Roomba Control Protocol? "Man-in-the-middle" takes on a whole new meaning when the attacker is somewhere in the room with you!)

Anyway, one robot vacuum cleaner does not an army make, but it'll be a neat sidekick. I need a naming convention for robot vacuum cleaners!