Quote:
|
If you are willing, you can try soldering the wires directly onto the beagleboard. Using a network camera really just defeat your purpose of getting the board. From what Min Soo told me, you guys originally planned on using the Kinect. Remember, the Kinect needs its own 12V power from the cRio, the USB only gives you 5V. Since Beagle Board runs linux, you can give video4linux a try, but it seems as if you had success already without it.
|
We provided the 12V power sources with the adaptor. We also measured the 5v across the pins from the usb. Lights on the Kinect or the usb camera still don't turn on. /dev/video0 does not show up for the usb camera. The strange thing is flashdrives still work.
Something very funky is obviously going on.
We will look into the Kinect( and usb webcams) later, but the ip camera will work perfectly for now.
There was actually 3 reasons why we got the beaglebone.
1. A lot more possibilities, with opencv, full C++ support, etc. We can practically do whatever we wish(and opencv does come with some pretty impressive functions, solvePnp being one of them).
2. We want all this technology to be separate from the drive system. This way, if the code is slow, if the code fails, etc, at least the robot will continue to drive and the driver can manually shoot.
3. We wanted the ability to use usb devices such as usb cameras(much cheaper/ faster), and the Kinect.
2 out of 3 is still pretty good as far as I can see it.