ANNOUNCING: navX MXP Robotics Navigation Sensor

[slibert]

Originally Posted by SpaceOsc

A New NavX 3.0 has hit AndyMark, given that we just bought NavX 2.0 a few weeks ago, I wonder if anyone knows what the differences are between the two?

The navX 3.0 firmware adds support for 200Hz update rate, which provides even lower latency. The currently-released FRC Java/C++ libraries support 200Hz operation; the LabVIEW library support for 200Hz operation will be released at a later time.

This is a free upgrade for existing navX-MXP customers, so your navX 2.0 can be upgraded.

Note that there will be new library features announced in the coming months. These will be announced on ChiefDelphi and to all subscribers of the KauaiLabs Newsletter when they are released.

[SpaceOsc]

Wow fantastic! thank you for the response, there are no hardware differences between theses products?

[slibert]

Originally Posted by SpaceOsc

Wow fantastic! thank you for the response, there are no hardware differences between theses products?

V2 and V3 navX-MXP have the same hardware; firmware is the difference.

[mkopack]

Hey all!

Our team picked up one of the NavX-Micro's for use in this year's Steamworks game. We're having a heck of a time just trying to get the demo programs to run though...

We are developing on Linux machines. we followed the directions found on: http://www.pdocs.kauailabs.com/navx-mxp/installation/ and did the Linux/Mac install stuff, pointed to the library in eclipse's settings and made sure the project settings had the references set up.

Whenever we go to run the "Robot" program though it fails with the following stack trace:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no wpilibJavaJNI in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java :1865)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1119)
at edu.wpi.first.wpilibj.hal.JNIWrapper.<clinit>(JNIW rapper.java:22)
at edu.wpi.first.wpilibj.RobotBase.initializeHardware Configuration(RobotBase.java:171)
at edu.wpi.first.wpilibj.RobotBase.main(RobotBase.jav a:194)


I remember some discussion about the WPILibs being split out some this year, but I have no idea how to fix this.

Ideas? Do the instructions need to be updated???

Any help is appreciated...

[slibert]

Originally Posted by mkopack

Hey all!

Our team picked up one of the NavX-Micro's for use in this year's Steamworks game. We're having a heck of a time just trying to get the demo programs to run though...

We are developing on Linux machines. we followed the directions found on: http://www.pdocs.kauailabs.com/navx-mxp/installation/ and did the Linux/Mac install stuff, pointed to the library in eclipse's settings and made sure the project settings had the references set up.

Whenever we go to run the "Robot" program though it fails with the following stack trace:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no wpilibJavaJNI in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java :1865)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1119)
at edu.wpi.first.wpilibj.hal.JNIWrapper.<clinit>(JNIW rapper.java:22)
at edu.wpi.first.wpilibj.RobotBase.initializeHardware Configuration(RobotBase.java:171)
at edu.wpi.first.wpilibj.RobotBase.main(RobotBase.jav a:194)


I remember some discussion about the WPILibs being split out some this year, but I have no idea how to fix this.

Ideas? Do the instructions need to be updated???

Any help is appreciated...

Where is the WPI library installed on your Linux machine, and are your eclipse settings configured correctly to locate the WPI library?

Linux development environments are a bit off the beaten path, so you'll need to do a little extra legwork to track that down than most people do. If in your investigation you do find an issue in the navX libraries, please post that after you complete your research.

[Jonathan L.]

We are about to integrate the navX LabVIEW libraries into our code. Since the navX code can be installed and then placed on the block diagram from the functions pallet I am thinking we should have all our programmers install the navX software. However, I am a bit worried that if the software is updated, different programmers may end up with different versions of the software unknowingly. Because of that, I am thinking it may be better to bring all of the navX LabVIEW dependencies into of Robot Project, not require that everyone install the software, and place the navX VIs in LabVIEW from the project window.

Which method do you recommend?

[aeastet]

Hi Jonathan,

This year the library is installed int the third party sensors folder inside the WPI section. If everyone uses the installer to install the library you should not have a problem. Your robot program automatically looks in this folder for the navX vi's.

Let me know if you have problems.

Thanks,

[aeastet]

Hi Jonathan,

You can also add these dependencies into your code. That would not be a problem. I do not think we are planning any other releases until right before competition. I know there is one fix that should be very minor. If your team is planning to edit this library then I would add it to your dependencies. If not I think you are OK.

Tim