View Single Post
  #2   Spotlight this post!  
Unread 11-03-2012, 08:06
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: Speeding up Teleop

That could run normally, but I doubt it will change the error messages. The default teleop is more event based, running when a new joystick packet comes in. Presumeably, the new way would read the joysticks as fast as possible and update the motors. I can't tell from what you posted.

The issue causing the messages is probably in a parallel loop already. Perhaps vision. I would suggest measuring what is running at what rate before making such a radical change.

In the project, there is a Support Folder that contains the elapsed times VI. If you drop it into a VI or a loop, you can leave the panel open and see how long between runs. Be sure to open the charts tab on the DS and watch the CPU usage too. Keep in mind that open panels with lots of updates adds CPU overhead.

Determine the appropriate rate for various loops and watch for untimed loops that are running far faster than needed.

If vision is on, you may want to change the Framerate in Begin to get the CPU usage down a bit.

Please post if you find things or need more suggestions.

Greg Mckaskle
Reply With Quote