navX-MXP Version Number: vendordeps vs. source

Technical Programming
1

All:

Through the 2020 FIRST Choice we were able to acquire a Kauai Labs navX-MXP inertial maneuvering unit (IMU).

Our team uses C++, but since the navX-MXP software is also available for Java and LabView, I have placed it in the programming category, and not just the C++ category.

Just like the WPILibC libraries, our team decided to use Doxygen for documenting our code, starting with our rookie year in the 2019 season. As we went along, we saw the value of adding the WPILibC source into our Doxygen output, and did so.

Since we got the IMU, we wanted to also include the navX-MXP source in our Doxygen output. However, we are having some difficulty determining how the version indicated in the vendordeps/navx_frc.json file correlates to a version of the navX-MXP source.

The WPILibC version listed in the build.gradle file (2020.3.2) correlates with the WPILibC version # in the git tag (v2020.3.2) from the source. However, I did not find that version in the actual source, just the git tags.

However, as far as I can tell, there is no tags on the navX-MXP source. Is there some other way to ensure that the navX-MXP code downloaded from github.com matches the version listed in vendordeps/navx_frc.json file? As of 3/13/2020, v3.1.413 is shown in vendordeps/navx_frc.json.

Any help would be greatly appreciated!

2

The WPILib version file is auto-generated during the build, so it’s not going to be visible on GitHub.

Regarding the NavX sources, you can grab the sources artifact from maven to get the sources for that particular version. E.g. these are the sources for 3.1.413: https://repo1.maven.org/maven2/com/kauailabs/navx/frc/navx-cpp/3.1.413/navx-cpp-3.1.413-sources.zip (technically you also need to grab the headers artifact to get the headers as well)

3

But it is visible in the source in maven and installed with the WPILib installer.

1 Like
4

Thank you both Joe and Peter!

I’ll take a look at maven repo that Peter mentioned.

Thanks again.

5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.