View Single Post
  #9   Spotlight this post!  
Unread 20-02-2013, 08:30
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: Driverstation - Robot Communication Issue

If you have a sequence that gets it into this state, here is what I'd like you to do.

Click on the DS Diagnostics tab. The Communications LEDs on the central column are mostly ping results. The DS is pinging one a second and showing the results. Please report what you see.

Go to the taskbar and hover over the network icon and see if the laptop is connected to a network that makes sense.

Next, launch a command prompt, ideally as admin. Enter the command

arp -av

and copy/paste the results for a post. Then try an arp -d and see if that enables the connection to proceed.

Finally, please log into the DLink and see if mac address cloning it on or off.

My suspicion is that the boot order and boot time are causing the DLink to build a routing table that is incorrect. The DS actually looks for this and invokes the arp -d to try to correct the issue, but I think the OS may now require elevation to do that.

Please report back with what you find along with the step by step procedure you use to get your robot into that state.

Greg McKaskle
Reply With Quote