No Comms at the Scrimmage

[Rick Vogl]

One more tidbit of information. Communication to the new cRio will not occur unless the reset button is pressed. A simple power on/off doesnt do the trick.

[Danny Diaz]

Okay, we are pretty sure we know your problem. However, don't thank me, thank Joe Hershberger (I swear, it's uncanny how fast he processes stuff like this).

Anyway, MAC Address Cloning is probably turned on in your DAP-1522. You've got to turn that off. MAC Address Cloning requires ARP traffic in order to get a MAC address to clone, and since the cRIO boots up first it does its gratuitous ARP way before the DAP is done booting - so, the DAP never sees anything to "clone" until you press the reset button on the cRIO - at that point the cRIO boots up, gives a gratuitous ARP, and the DAP clones that MAC Address and starts communicating.

Again, Thanks to Joe Hershberger if it works.

-Danny

[MamaSpoldi]

Thanks for that idea... but... we verified that the MAC address cloning is turned off... several times.

Although it does sound remarkably like what we are seeing... so perhaps there is an issue with what it displays for the settings as opposed to what it is actually set to... if so then all bets are off.

[JohnFogarty]

Go and try what I discovered. http://www.chiefdelphi.com/forums/sh...ad.php?t=92505

[Mark McLeod]

I recreated one instance where the cRIO and DLink failed to communicate properly and, in addition to the cRIO reset, I was able to simply unplug and replug in the cRIO Ethernet connection to get them talking again.

The symptoms in this particular case were no connectivity between the DLink and cRIO, but the cRIO Ethernet port lights were solid green and yellow, i.e., no packet traffic.

Unplugging and re-connecting to the cRIO port 1 started the yellow traffic light blinking and everything was fine again.

[jhersh]

What behavior do you see if you start from a working condition and reboot just the d-link radio? Will it go back to non-functional?

-Joe

[Mark McLeod]

The few times I experimented with cycling power just on the DLink didn't cause the problem, however, I only tried that twice.
I was sprinting through a test series while the mechanical and electrical guys were looking the other way...

Our DLink shipped three hours before you asked your question, so I'm not able to revisit it.

[Rick Vogl]

I'm wondering if there is some common element for all of the teams having problems. We're using C++.

[Rick Vogl]

There is good news to report. We RMAed a cRIO that had a power issue with National Instruments. The new cRIO that arrived has zero communications issues. The robot connects flawlessly through the Dlink bridge to the previous years Linksys AP to our driver station and programming laptop.

NI has also agreed to RMA the cRIO that still had the comms problem. This unit is an older one by the serial number so I am think that the problem lies someware in the low level firmware that prevents the ip address to ARP properly. This may also explain some of the other issues that have been posted where a cRIO reset is required after the robot powers up in order to establish communication.

We should be good to go at our first regional with a running robot, not just a pretty lawn ornament like we were at the Suffield Shakedown.