Kinect Updates Thread

[Dusk Star]

To connect to cRIO: place pandaboard running linux on robot to interface between the kinect and the cRIO. Program the pandaboard to do all of your image processing, outputing only a x,y and distance value to the cRIO. from other threads it seems like you should get ~30 fps processed this way, depending on how intensive your code is. of course, all power connections have to be done custom.

As an extra option, do not connect the pandaboard to the cRIO, but instead get it approved to communicate with your driver station laptop via wifi, per [R67]

[R67]
Any decorations that involve broadcasting a signal to/from the Robot, such as remote cameras, must be approved by FIRST (via e-mail to frcteams@usfirst.org) prior to the event and tested for communications interference at the venue. Such devices, if reviewed and approved, are excluded from Rule [R55].

If you did this, you could probably just do all the image processing on your driver station laptop, and view the image besides.

[Dusk Star]

Forgot to put R55 in there:

[R55]
One D-Link DAP-1522 is the only permitted device for communicating to and from the Robot during the match. All signals must originate from the Operator Console and be transmitted to the Robot via the official Arena hardware. No other form of wireless communications shall be used to communicate to, from or within the Robot (e.g. radio modems from previous FIRST competitions and Bluetooth devices are not permitted on the Robot during competition).


Teams are encouraged to mount the wireless bridge away from noise generating devices such as the CIM motors. By making the diagnostic lights visible, Arena personnel are in a better position to assist teams.