View Single Post
  #4   Spotlight this post!  
Unread 23-02-2012, 12:45
Mark McLeod's Avatar
Mark McLeod Mark McLeod is online now
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,854
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: time-based or event-based TeleOp

Oh, I'd never use the nominal Teleop 20ms as a timing device. Only if the event/action doesn't make sense without a new driver order. The 20ms certainly isn't guaranteed, and for many teams isn't even close.

Anything I want to do based on a period, I do in Periodic Tasks.
If it's a time critical task, then I'll perform calculations based on a system time check.
If it's a really critical task, then I'll use a Timed Structure loop.

As you say, doing a system time check and calculation would work in Teleop, but the response action is still going to be occurring at wacky time intervals.

You've seen this Timing is Everything whitepaper before. I suppose I should add a watch on Teleop under different programming/cRIO/DS PC conditions that all contribute to really sloppy times.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 23-02-2012 at 12:53.