ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2

[slibert]

Just in time for the FIRST FRC 2017 "Steamworks" season, Kauai Labs announces the following exciting upgrades and new products - designed to help teams Build Better Robots®.

All software items below will be available for download on January 7, 2017.



Classic. Must-have. Featured on Championship Robots.

navX-MXP is a mature, must-have navigation sensor for a FRC RoboRIO-based robot control system. Over a thousand FRC teams have purchased navX-MXP to enhance drive-train navigation, including several teams competing in the FRC 2016 World Championship Finals.

navX-MXP 3.0 - a free software upgrade to existing navX-MXP customers - includes these new features:

• 200 Hz Update Rate

• Full RoboRIO support for USB, in addition to SPI, I2C and TTL UART

• Redesigned LabVIEW Library - now even easier to use

• New Linux library - great for integrating navX-MXP into a separate vision co-processor

• Libraries for integrating nav-MXP into Android-based FIRST FTC Robots

Reduced size and cost. Great as a second IMU. Sold out on day one of FIRST Choice 2017.

navX-Micro is a new, smaller, lower-cost IMU, great for FRC and FTC teams with limited budgets.

navX-Micro also works great as a second IMU for measuring orientation of robot arms and other moving devices.

navX-Micro is software-compatible with navX-MXP and works with all RoboRIO libraries, which now include support for multiple simultaneous navX-MXP & navX-Micro devices.




New for 2017.

SF2 is a free, open-source software framework making navX-MXP and navX-Micro even more powerful - fusing multiple sensors together to help you build even better robots.

Available in LabVIEW, C++ and Java for the RoboRIO, the initial SF2 release enables Video Processing Latency Correction on FRC robots.

[marshall]

This is the announcement I've been waiting for.

Thanks Scott!

[jojoguy10]

This is amazing! Can't wait to try out the Vision Latency library!

[BrianAtlanta]

Some cool stuff!

[euhlmann]

Are there any differences in accuracy between the NavX MXP and the micro? Does the micro support omnimount like the MXP?

[slibert]

Originally Posted by euhlmann

Are there any differences in accuracy between the NavX MXP and the micro? Does the micro support omnimount like the MXP?

navX-MXP and navX-Micro are identical with respect to accuracy - the same Invensense MPU-9250 is on both, and the firmware that performs automatic calibration and other cool features like Omnimount is also the same.

The only significant difference between navX-MXP and navX-Micro is that navX-MXP adds (a) SPI and TTL UART interfaces, (b) IO Expansion and (c) MXP connector.

[slibert]

The 2017 navX-MXP and navX-Micro upgrades are now available.

If your navX-MXP is at a firmware version lower than 3.0.289, you are encouraged to update your firmware as well.

The 2017 Sensor Fusion Framework (SF2) library is also now available.

Unleash the hounds!

[naldarn]

The Labview information is difficult to find, http://www.pdocs.kauailabs.com/navx-mxp/labview-ae/

has nothing on it.

and if you go to the navx-micro for the examples, it takes you to github and shows you the c++ examples instead of Labview.

[slibert]

Originally Posted by naldarn

The Labview information is difficult to find, http://www.pdocs.kauailabs.com/navx-mxp/labview-ae/

has nothing on it.

and if you go to the navx-micro for the examples, it takes you to github and shows you the c++ examples instead of Labview.

Thanks for the head's up; the path to the labview AE URL is fixed.

As far as the navX-Micro examples, you likely found yourself to the FTC examples; there are separate FRC examples linked to as well on the navX-Micro Examples page.

[itsjustmrb]

I am getting a navXFirmware error "unable to load DLL 'STDFUFiles.DLL' on 2 different laptops with the firmware downloaded on each laptop (not copied from USB). Can anyone please help?

Thanks in advance,

Mr. B

[nickbrickmaster]

Is there any plan to port SF2 to Python? If there are not any official plans, I'll probably try in my free time (hah!)

[slibert]

Originally Posted by nickbrickmaster

Is there any plan to port SF2 to Python? If there are not any official plans, I'll probably try in my free time (hah!)

We don't have this in the plans right now (we're focused on developing other very cool SF2 features). However, you might contact Dustin Spicuzza, he's done some amazing work to port the navX-MXP libraries to Python. And I'd be happy to provide support if you should choose to attempt this yourself.

Aloha,

- scott

[madz]

Are there any FRC Java examples for turning to or driving on a heading with a tank drive like there are for FTC? The FRC examples all seem to be for a mecanum drive. Thanks!

[kmrchiefdelphi]

Hi, after installing the latest navx_mxp jar file we are getting the following errors during deploy. We followed the Java coding steps from the Kauai Labs website. Any suggestions would be welcomed.

Thanks in advance.

[javac] RobotMap.java:3: error: package com.kauailabs.navx.frc does not exist
[javac] import com.kauailabs.navx.frc.AHRS;
[javac] ^
[javac] RobotMap.java:23: error: cannot find symbol
[javac] AHRS x = new AHRS(SerialPort.Port.kMXP);
[javac] ^
[javac] symbol: class AHRS
[javac] location: class RobotMap
[javac] RobotMap.java:23: error: cannot find symbol
[javac] AHRS x = new AHRS(SerialPort.Port.kMXP);
[javac] ^
[javac] symbol: class AHRS
[javac] location: class RobotMap
[javac] 3 errors

[slibert]

Originally Posted by kmrchiefdelphi

Hi, after installing the latest navx_mxp jar file we are getting the following errors during deploy. We followed the Java coding steps from the Kauai Labs website. Any suggestions would be welcomed.

Thanks in advance.

[javac] RobotMap.java:3: error: package com.kauailabs.navx.frc does not exist
[javac] import com.kauailabs.navx.frc.AHRS;
[javac] ^
[javac] RobotMap.java:23: error: cannot find symbol
[javac] AHRS x = new AHRS(SerialPort.Port.kMXP);
[javac] ^
[javac] symbol: class AHRS
[javac] location: class RobotMap
[javac] RobotMap.java:23: error: cannot find symbol
[javac] AHRS x = new AHRS(SerialPort.Port.kMXP);
[javac] ^
[javac] symbol: class AHRS
[javac] location: class RobotMap
[javac] 3 errors

The info you sent suggests that Eclipse can't locate the navx_frc.jar file (the navX-MXP RoboRIO Java Library).

For 2017, the location of the navX-MXP RoboRIO Java Library has changed, to match the new standard defined by the WPI Library for 3rd-party libraries.

This new location is:

C:\Users\<username>\wpilib\user\java\lib

This actually makes things simpler to configure in Eclipse than in previous years, but it involves a change to the Eclipse library paths.

Please review the RoboRIO Java Library instructions for Configuring Eclipse Library Paths, which have been recently updated to reflect this new location.