NavX micro with REV expansion hub?

[FTC Team 4962 The Rockettes]

Does this work with the REV hub?  We've loved the reliability and accuracy of the NavX so we'd like to use it again this year instead of the internal IMU.

It looks like there is a new set of sample code in external.samples (SensorKLNavxMicro) that doesn't use a hard-coded I2C port like in previous years.

It there anything we should be aware of?

[FTC Team 4962 The Rockettes]

It also looks like it's now included in the SDK so we don't need to manually add the aar file, is that correct?

The header says:

import com.qualcomm.hardware.kauailabs.NavxMicroNavigationSensor;
import com.qualcomm.robotcore.eventloop.opmode.Autonomous;
import com.qualcomm.robotcore.eventloop.opmode.Disabled;
import com.qualcomm.robotcore.eventloop.opmode.LinearOpMode;
import com.qualcomm.robotcore.hardware.Gyroscope;
import com.qualcomm.robotcore.hardware.IntegratingGyroscope;
import com.qualcomm.robotcore.util.ElapsedTime;

[admin]

If you are using the REV expansion hub w/the navX-Micro, you will need to use the new SensorKLNavXMicro class for it to work; this library class is now officially provided by FIRST.

Using the existing Kauai Labs-provided libraries works fine w/the Core Device Interface Module, but does not work currently w/the Rev Expansion Hub.

Please let me know if you have any more questions on that.

Cheers,

- scott

[admin]

Yes, that's exactly correct.  When using the new SensorKLNavxMicro class, the Kauai Labs navx_ftc library does not need to be installed or referenced by your Android project.

Note that this means that the other classes (like the PIDController) in the Kauai Labs library also won't be available.  These classes are designed to work w/the Kauai Labs AHRS class, so you'll need to use PID Controller logic from the ftc_app library from FIRST instead.

Cheers,

 scott