View Single Post
  #4   Spotlight this post!  
Unread 16-09-2015, 20:06
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: roboRIO COMM light green, no comms on driver station

I haven't tried to isolate this in a test, but according to the documentation, this indicates that the roboRIO is satisfied that it is in communication with a driver station.

I can think of a couple reasons why the roboRIO may think it is in comms, but the DS doesn't.
1. Perhaps there is more than one DS involved? Try using a simpler and more directed form of communication such as USB or ethernet. Does killing the DS laptop cause the roboRIO LED to turn off?

2. The communication is generally based on packet arrival. The DS sends packets to the roboRIO and the roboRIO sends status packets back. The symptoms you describe could indicate that the control packets are successfully arriving at the roboRIO, but the return status packets are being blocked.

Greg McKaskle
Reply With Quote