View Single Post
  #7   Spotlight this post!  
Unread 31-01-2010, 11:53
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: Camera lag solution

If the CPU has too many things to do, a line forms and the CPU deals with things one, or depending on architecture, a few things at a time. Priorities are where you give one task cuts in line. Some tasks are left at the back of the line watching other tasks cut over and over again.

If not used carefully, priorities will mean that some tasks will get starved out and will never get any time on the CPU. In particular, I don't think the dashboard should be higher priority than the development tools or the driver station. There is nothing stopping you from setting your own priorities, and I don't think the system will be dangerous if you play with priorities, but if it acts oddly and won't do what you want, put them back to defaults before deciding things are broken.

In most cases, the best way to deal with an overloaded CPU is to figure out how to do less work or do the work more efficiently. Again, this is very different from setting priorities.

Greg McKaskle