View Single Post
  #7   Spotlight this post!  
Unread 10-03-2012, 15:32
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,748
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: Driver Station cannot connect to cRio

I'll look into it. The DS calls netsh to request that the firewall allow through various programs, but I suppose it could have forgotten itself, it could be getting an error, etc.

Just a bit more background. The terminology of the Robot Comms is a bit confusing, as it really means that the DS isn't receiving the expected information from the FRC Communications library on the robot. This could be for many reasons, and the diagnostics tab can ping for you and show if that is the issue.

Also, the DS IP is not that important for development. After all, it is very convenient to have dev tools on other computers along with a copy of the DS. But I'm pretty sure that the field looks to talk to the DS at 10.te.am.05.

Greg McKaskle