Slashdot Mirror
Kinect Hacked, Adafruit Bounty Won
scharkalvin writes "Adafruit has announced a winner to their bounty for an open source driver for the MS Kinect. From the article: 'We have verified that it works and have a screenshot from another member in the hacking community (thanks qdot!) who was also able to use the code. Congrats to Hector! He's running all this on a Linux laptop (his code works with OpenGL) and doesn't even have an Xbox!'" We talked about Adafruit's bounty yesterday.
"Using a linux laptop". . Now every geek that has avoided Microsoft and their products like the plaugue will be rushing out and buying Kinect controllers. .
Step One: Create a toy that will entise the Open Source crowd
Step Two: Wait for some one to get it to work on their linux box
Step Three: watch all the geeks and hobyists buy said toy
Step Four: Profit
Hacking is good for business.
. .
The very term Microsoft used, "product tampering", sent chills down my spine. They weren't even talking about replacing aspirin with cyanide, but words like 'tampering' (and implications about getting law enforcement involved) certainly make it sound like that. We're talking about the stuff people themselves actually own. It's astonishing to think that their rhetoric extends so far.
Scientists point out problems, engineers fix them
altslashdot.org: The future of slashdot.
Measure depth. And capture 4-channel audio with spatial location and echo cancellation (unconfirmed but likely). It also moves up and down and has an accelerometer. People are mostly interested in the depth thing, though.
I guess the problem might be replacing Kinect with a different device presenting itself as Kinect to XBox. This way you'd gain unfair advantage in online games - where your fitness, physical condition and body momentum would restrict you normally, you could use, say, a key to deliver lightning fast kicks, or duck to the ground faster than gravitational acceleration would normally let you.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
This guy is on the way to solving the three main problems of personal robotics:
1. Indoor localization (figure out where you are inside)
2. Indoor navigation
3. Table top manipulation
There are already open source software packages for all of these items, but they require very expensive laser scanners (starting at 5K a pop). Most of these lasers only scan one row at a time, which means that for situations where you want 3D, you have to tilt the scanner up and down. This is a hassle and leads to slow scan times, which reduces the responsiveness of the robot.
For indoor localization, what you really want is just a line of points at a fixed height (you could extract one row of Kinect depth pixels) that you can feed to particle filers to figure out position in a mapped space. You might also be able to use opensource SLAM software, wheel encoders, and a Kinect to make 2D and 3D maps of indoor environments.
For indoor navigation, you can use 2D navigation planners to figure out plans through maps, and then use indoor localization to follow the plans. The Kinect can serve as an obstacle detector in addition to the providing data to the localizer. For example, if a person or animal jumps in front of the robot, the Kinect will sense it, and allow the robot to stop instantly and plan a new route. With a tilting laser, the reaction time would be slower, because laser might be in an orientation where it does not see the obstacle.
For table top manipulation, the Kinect can provide a point cloud of the objects on the table. CV software can remove the background (table, wall, etc.) and then detect the objects on the table. Once this is done, motion planners can plan a route for an arm or other manipulator to pick up objects on the table.
Once we have all three of these systems, it should not be all that hard to link them together and start actually doing useful things with robots in our homes. Even just the first two would make it possible useful cleaning and sentry robots.
Responsibility is an addiction
Virtue is a temptation
Community is a cartel
Just think.. your fav porn site can now see just how hard your spanking your monkey, and suggest videos based upon how much you enjoyed previous ones from that genre.
You are entitled to your own opinions, not your own facts.
There is another possible consideration: the producer of the technology.
Primesense created, presumably holds patents on, and did the reference design for, the "Kinect" camera/IR projector range mapping stuff. MS didn't buy them, they just bought/licenced enough of their stuff to produce Kinect hardware.
It is quite possible that Primesense also sells one or more much expensive motion capture solutions/SDKs/whatever based on the same technology; but agreed to give MS a sweet deal, in $/unit terms, because of the number of units expected to sell.
If the Kinect becomes generally useful, with independently produced drivers, anybody will be able to buy an instance of PrimeSense's fancy tech for $150 at any gamestop.
Consider an example from the old days: the first "Airport" cards were actually just rebadged Lucent gear; but with the pins deliberately switched around so that they would be incompatible with a PCMCIA slot. The Lucent branded equivalents were more expensive; but worked with normal PCMCIA slots. Obviously Lucent wasn't taking a loss on the "airport" cards; but they were having it both ways: sell a bunch of units to well-heeled consumers via Apple; but don't cannibalize the deep-pocketed connected enterprise market, thanks to deliberate incompatibility. There could be something similar going on here.
This is a somewhat different thing from what Johnny Lee did, though. Johnny took existing Wiimote driver code and used it to do some very cool things with the data, such as his famous head tracking demonstration. He didn't figure out the actual communications protocol, though (in fact, I did a lot of the early Wiimote reverse engineering hacks too; I guess I have a thing for wacky game controllers!).
Unfortunately for us engineers and low-level hackers, the people actually finding practical algorithms and cool uses for these devices tend to get more attention than the people hacking the low-level details ;). I'm genuinely excited to see what computer vision experts can do with the raw Kinect data, though (I personally can't do much more than apply a cheap heat map to the data like I did in my video).
"If the hacker only released a driver that works without altering the Kinect module in any way, MS can say what they want but they don't have much legal standing."
Why the hell would they have any standing if he did alter it? It belongs to him, not MS!
Hell, he could pull it apart, rewire it, reflash things...
What the hell happened to I bought it, it's mine ?? If I want to use it as a doorstop I will, if I figure out a way to cannibalise a sensor in it for some other purpose, I will. If I want to paint it green and shove it up my arse, I will.
FFS what's wrong with this planet?