View Single Post
  #1   Spotlight this post!  
Unread 21-06-2014, 16:26
Zylviij's Avatar
Zylviij Zylviij is offline
The quieter you become...
AKA: Blake
FRC #1732 (Hilltoppers)
Team Role: Programmer
 
Join Date: Apr 2014
Rookie Year: 2014
Location: Franklin, WI
Posts: 7
Zylviij is an unknown quantity at this point
Field Timing vs. Local Timing

Team 1732's Robot has autonomous modes which are heavily based upon timing. While in competition, our timing seems to work very consistently, however in testing, (without the field's timers) our robot has became more inconsistent. This difference is more greatly evident while using "CheesyVision".

My guess to why the timing is different while the timer is run locally is that our CPU is unable to handle the timer with the required precision while running the robot code simultaneously.

I know very little about threads and multithreading, but want to know if this is the root of the problem. If so, what can our team do to emulate the field timers? Do I simply need to configure windows to give the timer process a higher priority? Is this possible to do in LabView, or do I have to make a greater change to the testing code?

Thank you,
Team 1732
Reply With Quote