Quote:
Originally Posted by Techwiz
a.)
I can confirm that we tested the NavX connected via USB and via the MXP port and the only code change between the two was
serial_port = new SerialPort(57600,SerialPort.Port.kUSB);
-- to:
serial_port = new SerialPort(57600,SerialPort.Port.kMXP);
b.) We tried the Navx with the NavX UI and did not seem to have the same disconnect issues.
We then reconnected the NavX to the RoboRio and continued to have the same disconnect issues.
I'm beginning to think its a bad board. I tried changing the update rate from 50 to 60 to 30 and saw no difference in the disconnects.
Thoughts?
|
Sorry for the slow reply, Blake, we just returned from the Hawaii Regional. Thanks for taking the time to run these tests. I agree the best thing to do now is to return the board for a replacement.
Once I get the board I'll debug it; it's possible you've helped us discover a board failure mode that our factory QA tests are not currently covering. Since we use the navX MXP UI as our primary board validation engine, and that's working OK for you, what we learn could help us improve our process and quality.
Please accept my apology for the inconvenience you've encountered as a result of this; please let me know immediately if you have any further troubles - you can reach me at
scott@kauailabs.com.
Aloha,
- scott