View Single Post
  #1   Spotlight this post!  
Unread 02-02-2017, 12:52
Ty Tremblay's Avatar
Ty Tremblay Ty Tremblay is offline
Robotics Engineer
FRC #0319 (Big Bad Bob)
Team Role: Mentor
 
Join Date: Feb 2006
Rookie Year: 2004
Location: Alton NH
Posts: 848
Ty Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond reputeTy Tremblay has a reputation beyond repute
SRX Motion Profiling Control

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.
__________________
Reply With Quote