|
Re: Driver Station connects using old laptop but not new one
One thing to try is to use the other port to connect the radio to the roboRIO. There are distinct config differences on the ports -- I don't know much beyond that. And .local versus .lan is, I think, a symptom that the switch ports are separated.
The DS diagnostics tab shows lower level info. The link is not truly like the ethernet link LED, but is as close as I could get in SW and helps indicate that the cable presence. The other LEDs are pings, or rather ICMP API calls that cause a ping and give good result data.
The Communications LED in the central area is higher level and indicates whether the protocol is running. This is the light you really care about, and you go to diagnostics when this is off, to see if ping works or if it is a port issue or a problem with what is running on the RIO. The Robot Code light is signaled by a small part of the protocol and tries to convey whether user code is barking out commands.
By the way, the Comms LED is really a pair of side-by-side ones, one for UDP and one for TCP. UDP is the one required to run the robot, and TCP is more informational, and we sometimes see it fail, so we gave it a subLED for that reason to help get to the bottom of it.
Greg McKaskle
|