ANNOUNCING: navX MXP Robotics Navigation Sensor

[slibert]

Originally Posted by IndySam

We had to remove ours in the finals because our robot would sometimes just become impossible to drive when connected to the FMS. It would jump turn and move without driver input things it never did in practice.

I didn't see any brownout problems in the logs and until we unbag it for practice next week we do not have access to them.

At this point I doubt if we put it back on. BTW we are programming in Java.

Typically, in a field-oriented drive (or auto-rotate-to-zero) application, the robot's drive train Z-axis rotation is impacted by gyro data; in other words, a gyro anomaly should impact only rotational motion. So while unexpected turning (e.g., spinning in circles) could point to a gyro issue, a robot that unexpectedly "jumps" and "moves" may be a sign of other control-path issues (Joystick->DriverStation->Network->RoboRio).

Please send along any information you can, it's not clear what's different about robots that are FMS-connected, other than the communication path between the Driver Station and the Robot software. The on-field log data for lost packets between DS and RoboRio, CPU time and communication latency might provide valuable info that might help other teams.