Re: No Comms at the Scrimmage
 

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

Re: No Comms at the Scrimmage
 

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.

Re: No Comms at the Scrimmage
 

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

Re: No Comms at the Scrimmage
 

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.