View Single Post
  #3   Spotlight this post!  
Unread 15-02-2012, 21:05
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 delay on startup

I've seen this happen when Begin was allocating a number of things that fail out --serial and camera can both contribute.

One thing I often do is to put a small wire from the i terminal to the edge of the loop. For teleop, that turns into a feedback with a +1. Then I can probe some of these spots and see which loops are running, which are not, and get a sense of performance. A step up from this in terms of info is to use the Elapsed Times VI in the Support folder. You place this wherever you like and open the Elapsed Times to see the rate info.

This should help narrow down which code is responsible.

Greg Mckaskle
Reply With Quote