[NotInControl]

Originally Posted by fb39ca4

Being able to use H.264 instead of motion JPEG would help that a lot, but our team has not figured out how to get that working with the Axis camera.

Depending on the camera you are using there will be an H.264 stream link that can be enabled via the web interface. If you use a USB camera next year, there are a number of h.264 compatible USB cameras that have linux drivers. Ultimately it depends on what processing library you use for H.264 to be useful to you. Lowering your image resolution will also reduce bandwidth over the FMS network.

Originally Posted by yash101

Hopefully it supports some sort of MJPEG because I don't know for sure if OpenCV supports H. 264. Hopefully they can bump up the bandwidth to at least 16Mbps next year because that will reduce lag by a lot.

Open CV does support H.264, you need to compile ffmpeg with H.264 encoding support. Directions for adding h.264 support to ffmpeg can be found on the ffmpeg website.

Originally Posted by yash101

What type of Linux does the new cRIO run? Is it completely based off NI or is it based off an Operating System like Debian?

The RoboRio (which is what I assume you mean by cRIO) runs a custom made linux distro. The difference is that the OS on the Robo RIO is a Real-time operating system with hard time slicing for deterministic results. More information of NI Linux Real-time can be found on the NI website. I am not sure it is correct to say that it is based off one type of linux or another. What I can say truthfully is that it is a linux real-time operating system with a full linux shell and provides opkg for package management. NI can elaborate more on the development of the OS.

Originally Posted by yash101

Another funny question that I have is that I am wondering if it would be possible for the cRIO to compile code on itself? That would be a nice finishing touch. My vision coprocessor checks code differences and compiles the code on bootup

Yes this is possible as long as you choose to shell into the device and have a compiler installed. But it will be extrmely slow when compared to a desktop or laptop. Speed in compliation, and using a full up IDE (not over x window) is usually the reason for cross-compilation which is what the WPILib Plugins do. They allow you to develop, build, and compile code on your windows machine for an Arm based target and transfer the resulting binary over to the RoboRio. Remember the RoboRio is running a dual-core are at 667Hz and limited memory, compared to the gigaHz of your laptop/pc with gigs of ram, really is no comparison.