Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
-   -   ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2 (http://www.chiefdelphi.com/forums/showthread.php?t=152956)

slibert 04-01-2017 10:49

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

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
  • 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 04-01-2017 11:04

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
This is the announcement I've been waiting for.

Thanks Scott!

jojoguy10 04-01-2017 19:22

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
This is amazing! Can't wait to try out the Vision Latency library!

BrianAtlanta 04-01-2017 23:22

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
Some cool stuff! :D

euhlmann 05-01-2017 10:53

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
Are there any differences in accuracy between the NavX MXP and the micro? Does the micro support omnimount like the MXP?

slibert 05-01-2017 11:06

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

Originally Posted by euhlmann (Post 1625453)
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 06-01-2017 23:18

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
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 08-01-2017 19:37

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
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 09-01-2017 01:10

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

Originally Posted by naldarn (Post 1627446)
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 10-01-2017 19:14

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
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 10-01-2017 21:51

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
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 10-01-2017 22:57

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

Originally Posted by itsjustmrb (Post 1628899)
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

Please take a look at this post from a year ago, it might provide some ideas. A few others encountered similar troubles and found workarounds.

https://www.chiefdelphi.com/forums/s...d.php?t=143307

What you are encountering is an issue that appears on a small percentage of Windows computers.

As background, STDFUFiles.DLL is a user-mode driver from ST Microelectronics which provides USB-based access to the STM32 micro-controller firmware loader. This is used by the navXFirmwareUpdater. The navX-MXP/Micro setup programs install STDUFiles.DLL (using an installer from ST Microelectronics). There are two points:

- Certain operating system privileges are required to install this.
- STDUFiles.DLL is dependent upon some other DLLs, and it's possible they're either not getting installed, or conflict with other DLLs already on your machine.

So in addition to reviewing this post, I'd encourage you to run the navX-MXP/navX-Micro setup program as an administrator.

If that doesn't work, please send details about the configuration of your two computers (operating system version, 32 vs 64 bit, what are the privileges of the account you are using when installing, and anything else you might think is helpful).

If all else fails, we'll can replace your board with one that has the latest firmware (support@kauailabs.com), but let's see if we can resolve it using the above means first.

Aloha,

- scott

slibert 10-01-2017 22:59

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

Originally Posted by nickbrickmaster (Post 1628982)
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 10-01-2017 23:48

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
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 12-01-2017 17:44

Re: ANNOUNCING: Kauai Labs navX-MXP Upgrade, navX-Micro & SF2
 
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 13-01-2017 15:22

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

Originally Posted by kmrchiefdelphi (Post 1630189)
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.

slibert 13-01-2017 16:14

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

Originally Posted by madz (Post 1629052)
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!

If Kauai Labs creates a Java tank drive "straight-line driving" example using the WPI Library RobotDrive class, would your team be able to spend some time testing it? I realize everyone's busy right now...

kmrchiefdelphi 14-01-2017 09:36

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

Originally Posted by slibert (Post 1630675)
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.

Thanks a lot. That was the missing step.

madz 25-01-2017 00:24

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

Originally Posted by slibert (Post 1630724)
If Kauai Labs creates a Java tank drive "straight-line driving" example using the WPI Library RobotDrive class, would your team be able to spend some time testing it? I realize everyone's busy right now...


Sorry for the slow reply. We'd be happy to.

We are trying to get this to work right now, but are running into build problems just trying to test out the DataMonitor example. We followed the steps at http://www.pdocs.kauailabs.com/navx-...ibraries/java/ (three sets of eyes checked this) and are still getting an error:


...navx-mxp\java\examples\DataMonitor\src\org\usfirst\frc\ team2465\robot\Robot.java:3: error: package com.kauailabs.navx.frc does not exist
[javac] import com.kauailabs.navx.frc.AHRS;


Is there anything else we should check? This seems like a really basic thing. We've now spent two full meetings trying to figure it out. The navx-mxp jar path is right there in our Java Build Path, but its like it's invisible and gets letf out during the build.

Code:

Buildfile: C:\Users\robotics\navx-mxp\java\examples\DataMonitor\build.xml
Trying to override old definition of task classloader
clean:
  [delete] Deleting directory C:\Users\robotics\navx-mxp\java\examples\DataMonitor\build
compile:
    [mkdir] Created dir: C:\Users\robotics\navx-mxp\java\examples\DataMonitor\build
    [echo] [athena-compile] Compiling src with classpath=C:\Users\robotics/wpilib/java/current/lib/WPILib.jar:C:\Users\robotics/wpilib/java/current/lib/NetworkTables.jar: to build
    [javac] Compiling 1 source file to C:\Users\robotics\navx-mxp\java\examples\DataMonitor\build
    [javac] C:\Users\robotics\navx-mxp\java\examples\DataMonitor\src\org\usfirst\frc\team2465\robot\Robot.java:3: error: package com.kauailabs.navx.frc does not exist
    [javac] import com.kauailabs.navx.frc.AHRS;
    [javac]                              ^
    [javac] C:\Users\robotics\navx-mxp\java\examples\DataMonitor\src\org\usfirst\frc\team2465\robot\Robot.java:34: error: cannot find symbol
    [javac]    AHRS ahrs;
    [javac]    ^
    [javac]  symbol:  class AHRS
    [javac]  location: class Robot
    [javac] C:\Users\robotics\navx-mxp\java\examples\DataMonitor\src\org\usfirst\frc\team2465\robot\Robot.java:51: error: cannot find symbol
    [javac]            ahrs = new AHRS(SPI.Port.kMXP);
    [javac]                        ^
    [javac]  symbol:  class AHRS
    [javac]  location: class Robot
    [javac] C:\Users\robotics\navx-mxp\java\examples\DataMonitor\src\org\usfirst\frc\team2465\robot\Robot.java:135: error: package AHRS does not exist
    [javac]            AHRS.BoardYawAxis yaw_axis = ahrs.getBoardYawAxis();
    [javac]                ^
    [javac] 4 errors

BUILD FAILED
C:\Users\robotics\wpilib\java\current\ant\build.xml:71: Compile failed; see the compiler error output for details.

Total time: 610 milliseconds


madz 25-01-2017 09:46

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

Originally Posted by madz (Post 1635990)
We are trying to get this to work right now, but are running into build problems

OK, we think there is an issue on this particular computer's eclipse. We were able to get it to compile on another computer (after refresh/clean/rebuild) but not on our main computer. It's really weird.

We'd love to test the tank drive code, though. We have a test drivetrain wired and ready to go.

slibert 25-01-2017 10:45

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

Originally Posted by madz (Post 1636074)
OK, we think there is an issue on this particular computer's eclipse. We were able to get it to compile on another computer (after refresh/clean/rebuild) but not on our main computer. It's really weird.

We'd love to test the tank drive code, though. We have a test drivetrain wired and ready to go.

Glad to hear you've worked around the configuration problem. Now, let's work together on the tank drive code, and discuss what it exactly you'd like to accomplish.

With your tank drive system, is it your goal to:

- when stopped, rotate the robot to point to a particular angle?

- or -

- when moving, continue driving in a straight line?

madz 25-01-2017 11:14

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

Originally Posted by slibert (Post 1636104)
Glad to hear you've worked around the configuration problem. Now, let's work together on the tank drive code, and discuss what it exactly you'd like to accomplish.

With your tank drive system, is it your goal to:

- when stopped, rotate the robot to point to a particular angle?

- or -

- when moving, continue driving in a straight line?

Thanks for offering to help! It's actually both.

We're using a naxX micro for our FTC robot so are familiar with the FTC examples (we have a consistent 100 point autonomous in FTC). We are just trying to translate that into FRC where we have much less experience.

So, for instance, we may:

(1) drive on a heading for X encoder ticks
(2) stop, and turn in place
(3a) drive on a heading for X more encoder ticks AND/OR
(3b) drive using vision tracking for X more encoder ticks


All times are GMT -5. The time now is 16:59.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi