Team 1418 Oculus Rift Driver Station Interface Release

[ilandprnce]

This was actually something that I was interested in trying to accomplish after this last year as a student on team 319. ( and I'm actually pretty jealous that you guys beat me too it! )

I'm defiantly going to take a look at this sometime both to see if I can learn anything from it, and because I've been dying to try messing with the rift and FRC together.

Quick question however. If this WERE allowed within FIRST, wouldn't you still run into the issue of surpassing the feild broadcast data limit (2mb/s I believe?) As the rift runs "comfortably" at 75htz?

[CarterFendley]

Originally Posted by ilandprnce

Quick question however. If this WERE allowed within FIRST, wouldn't you still run into the issue of surpassing the feild broadcast data limit (2mb/s I believe?) As the rift runs "comfortably" at 75htz?

This version of our Oculus code does not have it grabbing the robot camera. However our team found compiled binaries for a MJPG streamer that works great with the roboRIO: here. It will depend on what camera you use among other variables but it worked well for us.

[virtuald]

Originally Posted by ilandprnce

Quick question however. If this WERE allowed within FIRST, wouldn't you still run into the issue of surpassing the feild broadcast data limit (2mb/s I believe?) As the rift runs "comfortably" at 75htz?

The camera limit is actually 7Mb/s, and you end up with maybe 5Mb/s available for use with a camera. Despite that the Oculus has a 75Hz update rate, you don't necessarily have to update at that rate. But, it certainly is a limitation. Our thought is that the HUD element of this would be more useful, and that's why we mounted a camera on the Rift directly so the operator would be aware of their surroundings. Because there's no bandwidth limitations, the camera works pretty well and with a little more work could probably be streamed with unnoticeable latency.