FMS/cRIO comm issue

[sdaustin]

Thanks for everyone's very quick and pertinent responses. To answer as many questions as possible:

- We were running cRIO image 28. The cRIO was imaged twice at Kettering; once by the Lead Robot Inspector and once by the NI rep. A match was attempted between each imaging.
- We tried different network cables from the DLink to the cRIO onboard. One was placed in different location from the original - it's unlikely that something else onboard was injecting noise into the cable.
- At Kettering, the FTA loaded the settings onto our DLink twice. We also tried two of their loaner DLinks which they had configured.
- We were running DS 2.27.11.00 on our Classmate. We also tried a loaner Classmate for one of our matches. It didn't help.
- We formatted the onboard cRIO flash "hard drive" and reinstalled image 28 between competitions. To my knowledge, image 29 was not yet available at that point.
- We had run the Team Update #17 procedure between competitions.

I too am thinking that a packet sniffer and side-by-side comparison under FMS is the next logical step. Unfortunately, the cRIO is in NI's hands for now, so that will have to wait.

We're done with competitions for this year. Now we're focused on things like giving demos of the robot to the Board of Education and middle schools, participating in the ACS Relay for Life, etc.