View Single Post
  #3   Spotlight this post!  
Unread 23-02-2012, 12:36
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,101
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: time-based or event-based TeleOp

Quote:
Originally Posted by Mark McLeod View Post
For LabVIEW, putting everything in Periodic Tasks and processing at a faster rate wouldn't change anything. We'd just be reprocessing the same old packets until a new one came along in it's own good time.
Teleop is just a slave task. It gets called every time there is a new packet available to process. If the packets came faster, then Teleop would just get called faster.
The point wasn't to process at a faster rate, it was to process at a more consistent rate. Hugh says his team has had success doing this. I'm wondering if it wouldn't be better to stay with the event-based processing, and read the elapsed time since the previous execution cycle, and make sure to use that elapsed time wherever appropriate instead of assuming a fixed elapsed time of 20ms.