Quote:
|
they don't actually mandate you keep the VxWorks software on the cRIO
|
Actually, it is required. You can do whatever you want for the offseason, but for FIRST events, the FPGA image and communications code on the cRIO are essentially agents of the FMS, ensuring that the robot is controllable by the field.
As for the dashboard, all of the camera users are using the cgi requests to the camera. There is a bmp, a jpg, and an mjpg that you can use. The default dashboard goes through the cRIO, but if you move the camera, your laptop can directly talk to the camera.
If you'd rather use the laptop to learn about image processing, that sounds like a fine initial approach. But it would be a good idea to learn how to use other people's libraries, like NIVision -- Color conversions, color thresholds, blob measurements, all in there. Additionally, when you find things that aren't in there, the libraries can be extended. Deciding that you have to do everything over again, in the language you choose can be a tough requirement on any project. But if you are making progress and helping the team build a better robot, power to you, let me know if you have any questions.
Greg McKaskle