View Single Post
  #6   Spotlight this post!  
Unread 19-01-2014, 10:26
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Robot Code State starving loops

Sounds like a good approach.

My suspicion is that your vision loop was not able to keep up with the camera. Think of it this way. If processing an image from the camera takes 100ms, then the CPU can keep up with a 5fps camera setting. It may be able to keep up with 9fps. But if the camera is set to 15 or 30 fps, the loop will skip frames and will always have an image it is working on. It will never stop running, and therefore the CPU will be at 100%.

If you look a the rate of the vision loop, it will help you determine your camera settings. The same issue can happen on the dashboard by the way, it is just a different and faster CPU, but vision can bog it down too.

Greg McKaskle
Reply With Quote