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

[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.

[slibert]

Originally Posted by 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!

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]

Originally Posted by slibert

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]

Originally Posted by slibert

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.

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]

Originally Posted by madz

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]

Originally Posted by madz

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]

Originally Posted by slibert

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

[inform880]

Hi,

I'm using Labview (updated), and have just installed the library, but it can't find this file:

FRIC_SF2_ProcessingLoopStatesTypeDef_I2C.ctl

Any ideas on what's wrong?

[slibert]

Originally Posted by madz

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

Ok, there's now a FRC RoboRIO Java Tank-drive example demonstrating Rotate-to-Angle and Drive-straight techniques using navX-MXP, as well as zeroing the yaw.

Let us know how the testing goes.

- scott

[aeastet]

Originally Posted by inform880

Hi,

I'm using Labview (updated), and have just installed the library, but it can't find this file:

FRIC_SF2_ProcessingLoopStatesTypeDef_I2C.ctl

Any ideas on what's wrong?

I would try reinstalling the navX-AE library again. Something must have gone wrong with your install. Is that the only file that can not be found?

[inform880]

Originally Posted by aeastet

I would try reinstalling the navX-AE library again. Something must have gone wrong with your install. Is that the only file that can not be found?

Sorry for the long delay, the SF2 stuff was put on hold while we had to work something else out, but now I'm back and remembered about the post. Yes, that is the only file missing, I installed it twice to try and work it out but it didn't fix it.

[aeastet]

Originally Posted by inform880

Sorry for the long delay, the SF2 stuff was put on hold while we had to work something else out, but now I'm back and remembered about the post. Yes, that is the only file missing, I installed it twice to try and work it out but it didn't fix it.

You should be able to download this file from here:

https://github.com/kauailabs/navxmxp...ewae/_TypeDefs

I would just check that you have your robot project file open when you place the navX into your robot code. As far as I know I have not heard of anyone else having this problem.

[madz]

Originally Posted by slibert

Ok, there's now a FRC RoboRIO Java Tank-drive example demonstrating Rotate-to-Angle and Drive-straight techniques using navX-MXP, as well as zeroing the yaw.

Let us know how the testing goes.

- scott

OK, thank you for the example. We were able to pull from that and get the turns to work. We're new to FRC Java, and after struggling with it for a while today we realized that this is more like an FTC opMode (same code is called every 20 ms) and not a LinearOpMode (everything executes once and then moves on) so we are going to have to readjust our thinking so that more than one command in the sequence gets executed. Hopefully we can learn it in the next couple of weeks.