Quote:
|
Have you been able to access the camera via the RoboRio Webdashboard.
|
Yes we have
Quote:
1) I don't believe GRIP can use the camera if you're also sending that information to the driver station. So if you have robot code opening up the camera, it'll hog it and grip will not be able to see it
2) So if your robot code would normally open webcamX, then your GRIP code should now open webcamX instead
3) My opinion is that running GRIP on the roboRIO is to slow for anything other than learning a little bit about vision processing. If you have the resources to get a Kangaroo PC (~$100) I would highly recommend that instead. Additionally, there are instructions for using a raspberry pi.
3a) some extra context: If I recall, robot code wants to use about 60% of the processor running fairly basic robot code. GRIP also wants about 60% of the processor if you have what I would consider a reasonable quality image for vision processing. In my experience, we couldn't reduce the delay to much less than 2-3 seconds running grip on the roboRIO, even with reducing the quality of the image substantially.
|
Thank you so much for the advice! Would you recommend a Kangaroo PC or a raspberry pi?