View Single Post
  #9   Spotlight this post!  
Unread 15-01-2006, 20:33
intelitek_Chris intelitek_Chris is offline
Registered User
no team
 
Join Date: Dec 2005
Location: Manchester
Posts: 19
intelitek_Chris will become famous soon enoughintelitek_Chris will become famous soon enough
Re: Loop time for OperatorControl function? Debug blows...

Quote:
Originally Posted by chakorules
So what your saying above, is that EasyC excute different than FRC Default code last year?
We would like to think that the end result for every team, whether they run easyC or MPlab, will be a similar success story, but easyC does away with the concept of fast and slow loops made famous by the default code.

Quote:
Originally Posted by chakorules
We can poll the I/O faster than the 26ms?
The program will automatically poll the I/O, and send motor commands every 26 ms.

Quote:
Originally Posted by chakorules
In other words, if we have an encoder (quadature), we should be able to get a decent velocity measurement from the inputs correct?
Absolutely, the remainder of your program will run as fast as it is able. The results from your encoder will depend more on the type of encoder you are using than anything else.

Quote:
Originally Posted by chakorules
I think maybe if Intellitek updated their software to version 2.1, they should make a change to the "Competition Template" and just add a blank While Loop in the OperatorControl function. This would eliminate some of our guess work, and now maybe the timers won't reset on their own.
It was our intent / expectation that the user add the while loop themselves. Permanently adding this loop to the template seems an unnecessary restriction, however it is certainly something to consider.

Thank you for your suggestions. We are always interested in hearing constructive feedback about the software.

Chris G