Quote:
Originally Posted by nickcvet89
We are getting the same type of response, actually our code doesn't even do anything with camera tracking enabled. cRIO CPU usage shows 100% on DS. Once we use a disable diagram in our teleop tracking, everything works fine. I was wondering if we should put the tracking code from teleop to periodic tasks.
|
Okay, first of all - you should NEVER run something as resource-intensive as vision processing inside Teleop.vi. Teleop tries to run every time the robot gets a new packet of info from the driver station, and if something is still running when a new packet is received then you get all kinds of problems. You should move your code to Periodic Tasks.vi at a minimum, or move your vision processing into your Dashboard code.
Regarding the original post - where in your code are you running your vision processing? Even if you have your vision code running in Periodic Tasks, you still may get enough lag to make the cRIO give out on you. Many teams (including us) opt to run vision code on our Driver Station PC so that we don't use up so much processing power on the cRIO.