Thread: Overhead using Test Mode?
View Single Post
  #2   Spotlight this post!  
Unread 23-06-2013, 10:20
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,753
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Overhead using Test Mode?
Test mode is an alternative to autonomous and teleop. The field will not put your robot into test mode, and on the field, your DS does not control the mode.

Test mode is intended for development, troubleshooting, and validation before you run a match, not during a match.

If you want to run a test and have the test results/progress show in another window, this should be fine. The overhead will depend on what the window does and how the code for it is written.

The test mode is implemented using network tables, but of there are no updates to a variable, there is no/little overhead.

I hope I'm answering your questions, but if not, please give more background on what you are trying to accomplish or how you are thinking of using test mode.

Greg McKaskle