View Single Post
  #2   Spotlight this post!  
Unread 02-02-2017, 12:54
notmattlythgoe's Avatar
notmattlythgoe notmattlythgoe is offline
Flywheel Police
AKA: Matthew Lythgoe
FRC #2363 (Triple Helix)
Team Role: Mentor
 
Join Date: Feb 2010
Rookie Year: 2009
Location: Newport News, VA
Posts: 1,729
notmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond reputenotmattlythgoe has a reputation beyond repute
Re: SRX Motion Profiling Control

Quote:
Originally Posted by Ty Tremblay View Post
In this example, and in the documentation, we're told that we should run

Code:
_talon.processMotionProfileBuffer();
about twice as fast as the duration of our trajectory points.

I'm just curious why this is implemented this way. If I'm running a trajectory point every 20ms, why do I need to tell the Talon to process its points every 10ms?

I'm not asking about the timing, but more why the talon needs to be notified instead of processing the buffer on its own. I'm sure I'm missing something, but I would have expected to be able to tell the Talon to start processing its buffer, and then check to see if it's done.
Why I gotta tell the talon to do the thing?
Reply With Quote