Announcement: navX2-Micro - Generation 2 has arrived

Kauai Labs announces the immediate availability of the “Generation 2” navX2-Micro Robotics Navigation sensor for use on both FRC and FTC robots. navX2-Micro is completely backwards-compatible with the “Classic” navX-Micro sensor, and navX2-Micro is re-engineered using new components to be faster and more accurate:

  • navX2-Micro features a 6-axis LSM6DSM IMU and LIS2MDL Magnetometer from ST Microelectronics; these modern sensors feature lower noise, higher accuracy and improved shock resistance than the Invensense MPU-9250 found in the “Classic” navX-Micro sensor.

  • navX2-Micro features an upgraded 180Mhz onboard microcontroller which doubles the speed of that found on the “Classic” navX-Micro.

  • navX2-Micro uses a new Kalman Filter-based algorithm with improved accuracy and running at a much higher 416Hz update rate. Updates can be received at up to 200Hz over I2C and USB simultaneously.

  • As a result of these enhancements, yaw drift is now much lower (~2 degrees/hour when still, ~1 degree when moving), startup time is reduced to only 5 seconds, and pitch/roll accuracy is also increased.

  • As a result of noise-reduction due to newer sensing ICs and the 416Hz Kalman Filtering, velocity estimates are now much improved over previous generations.

For more info, visit the navX2-Micro website; there you’ll find specs, installation and software instructions/examples for FRC and FTC, and much more.

AndyMark has a new bundle including navX2-Micro and an enclosure and all cables needed for both FRC and FTC. navX2-Micro is also now available at the Kauai Labs store.


What is the hole size / spacing on the case that AndyMark is selling?

How does it compare to the navX-MXP? (other than size)

1 Like

The enclosure has 7 holes, spaced on a 16mm grid. The attached graphic displays the details of the layout.

The holes are designed to be used with 4/40 screws.

Also available are design files if you want to redesign the enclosure and print it w/a 3D printer. More info on that is here.

1 Like

Hopefully the FAQ answers your questions.

navX-MXP mounts directly on the RoboRIO (plug-n-play), navX2-Micro can be mounted anywhere on the robot using an enclosure. navX-MXP adds SPI and TTL UART interfaces and has expansion IO.

Due to navX2-Micro’s new technology, it starts up faster and is more accurate, as detailed in the FAQ and in the original post. And it’s a great fit for FTC robotics, too.

1 Like

So for FRC context, the navX-MXP is more appropriate?

Both are appropriate for FRC, given different use cases, as Scott described above.

@slibert What’s the purpose of the second set of I2C(?) connections? (To the left of the set with a header populated)

1 Like

Those 4 connections are only for internal use, and are used to perform in-circuit debugging (during development) on the device firmware. You can find more info about this debug interface by reading about the SWD debugging protocol defined by ARM. For reference, the microcontroller is an ARM 32-bit-based STM32F446.


This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.