View Single Post
  #13   Spotlight this post!  
Unread 26-02-2014, 12:19
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,855
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Can't communicate with cRIO or d-link on power on

This is reminiscent of a problem from a few years ago when a race condition was identified between the bridge/router and the cRIO when they come up together.
The cRIO sends an arp hello, but the router isn't ready to receive it. They both are left waiting for the other one to speak first.
The router then won't forward traffic destined for the cRIO, because the router doesn't realize that the cRIO is there (no arp table entry).

That problem was worked around by having the DS force an arp request for the cRIO, so the router would snoop it out.

Another test I'd suggest is to pull the DLink power cable out, then cycle the robot power, and reconnect the DLink power after the rest of it is up and operating.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 26-02-2014 at 12:25.