[davidthefat]

Originally Posted by Lalaland1125

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.

But there is a bandwidth/latency problem you have to overcome. I mean it is milliseconds of time we are working with here, but you will have to run tests to actually see if offloading calculations will actually save you clock cycles. I might honestly be faster to crunch data on the cRio than to transfer over data to the board, calculate and then send it back. Your number two is valid, from what I see. But considering the short time frame of a match, will you pick up on it quickly enough to go into manual override? Just some potential issue I see. Also, you have a very short time to figure all that out, you need a way to interface with the cRio seamlessly.