View Single Post
  #6   Spotlight this post!  
Unread 10-04-2012, 06: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: Robot Tethering Issues

If you are running the driver station, it has a Diagnostics page to help determine what is failing. The second column of LEDs starts with the equivalent of a link light. If off, it indicates that a cable is missing/bad, or the NIC is disabled. If it is good, the next light moves one step closer to the robot, and another, etc. The first LED is the result of an ipconfig, and the others are just pings of the expected IP addresses.

You also shouldn't need a crossover cable unless neither device implements auto-sense. Almost all laptops still running will. If they implement gig-E, it is almost guaranteed. The cRIO and camera do not, and that is the connections that requires a crossover cable.

Greg McKaskle