Quote:
Originally Posted by Roboshant
|
Full disclosure: As founder of Kauai Labs, I'm biased towards the navX-Micro so you should take this w/a grain of salt - but I wanted to toss out a couple of system-level considerations.
A few features the navX-Micro has you might consider useful are it's dual simultaneous interfaces (I2C and USB), which allow you to:
- Connect I2C to RoboRIO, and USB to your vision processor (to share the high-resolution timestamp and IMU data w/both processors simultaneously), and
- Connect USB to RoboRIO and mount the navX-Micro USB anywhere on the robot (USB supports up to a 6 meter range).
One other distinction is that navX-Micro has a dual power supply (5V on the I2C pins, and 5V on the USB interface), whereas the ADIS16448 MXP board (based upon the published
schematic) does not.
If a MXP board doesn't provide a secondary power supply, it's only power supply (from the RoboRIO) is subject to
brownout whenever the RoboRIO voltage drops below 6.3V (even for an instant). So during that time no data is available, and since the ADIS16448 MXP Board runs the sensor fusion algorithms on the RoboRIO, these algorithms will be missing data for some period of time. For normal matches where you change out a battery before each match this is almost surely not an issue, esp. if you use the sensor only for autonomous (at the beginning of the match). But it could be an issue if you use the sensor for teleop and esp. during longer practice matches.