Thread: Errors
View Single Post
  #3   Spotlight this post!  
Unread 24-01-2011, 07:33
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: Errors

Before changing the code, determine how long between subsequent calls to update the motors. You can do this with a millisecs and a feedback node, or you may be able locate a subVI called Loop Timing and place that near the motor updates.

According to the Safety manager, you are updating the motor setpoints pretty slowly. Determine why and resolve that issue.

If you are having trouble tracking down the slow code, you may also want to turn on the profiler and run your app.

Greg McKaskle
Reply With Quote