View Single Post
  #32   Spotlight this post!  
Unread 27-04-2010, 14:47
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,102
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: Statistics on top 20 teams?

Quote:
Originally Posted by slavik262 View Post
We had a huge bug with the watchdog tripping this year because our extra threads were hogging too much CPU time.
Would you please elaborate on this? What exactly was the bug?


Quote:
Originally Posted by slavik262 View Post
you can play around with task priority or cause your tasks to sleep when they're not needed to make up for it in performance (i.e. have a task that updates your PWM outputs sleep the length of the Victor/Jaguar update speed).
Can you give a couple of examples of 2010 FRC breakaway functionality which would require (or even benefit from) changing task priority?

In the 2010 FRC LabVIEW framework, all user-created periodic tasks have the same priority, and they are preemptively time-slice multitasked by the O/S. Running these periodic tasks at a reasonable rate, as you suggested, frees up the CPU so that it should have enough throughput to service all the tasks you need, no?

~