Thread: Output Not Updated Often Enough
View Single Post
  #2   Spotlight this post!  
Unread 10-02-2014, 17:45
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
  
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,042
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: Output Not Updated Often Enough
Quote:
Originally Posted by JamesMcD_4505 View Post
Hello. We are using a motor to control an arm until it hits a limit switch. While this is in operation we get the "output not updated often enough" error and we are not able to control the drive train. How might we get around this?

Thank you for all of your help. We know that we have been asking a ton of questions this build season and we are extremely grateful for your patience.

-James 4505
TeleOp must complete execution well within 20ms, so it can be called again when the next data packet becomes available.

If you have code that takes longer than that to execute, you must either move the time-cosuming code to a separate thread, or use a "state machine" within TeleOp.


Reply With Quote