View Single Post
  #36   Spotlight this post!  
Unread 22-03-2015, 22:04
Jared's Avatar
Jared Jared is offline
Registered User
no team
Team Role: Programmer
 
Join Date: Aug 2013
Rookie Year: 2012
Location: Connecticut
Posts: 602
Jared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond reputeJared has a reputation beyond repute
Re: (Lack of) Value in the Regional Model

Quote:
Originally Posted by PayneTrain View Post
I can't remember the times since I am not a CSA or FTA, but isn't it something like >= 30 seconds for bootup and >= 50 seconds for connection to establish for the router, or are my numbers backwards or totally wrong?
From my experience at Waterbury week 1, the main delay was the driver station software sometimes not connecting to the field, which was blamed on mDNS. They had us enable/disable network adapters and restart the driver station application to get it to connect. The problem appeared to happen frequently when we tethered to the robot with the laptop while in queue, then unplugged and went straight to the field.

The problem also happens in reverse-going from field to tethered mode doesn't work with restarts, reset, and long delays.


When all worked well, match times weren't too bad because many teams turned on their robots before placing them out on the field.
Reply With Quote