Having trouble getting Adis 16470 working with wpilib

Technical C/C++
1

We are having problems getting the libraries we have to work with. Is there another source to get the libraries, or someway to get this to work.
Btw we got the libraries from the GitHub listed on analog’s site.

2

The driver is now bundled with WPILib, a separate vendor dependency is no longer required. However, be aware that this sensor will not currently work due to an issue with the Rio kickoff image. A new image will be coming out soon to fix this issue.

1 Like
3

Is there currently an expected date or rough ETA on when that new image might release?

Or is it just, when they get around to it.

4

I don’t have an exact availability date, but it’s actively being worked and it should be soon.

1 Like
5

Allright, thanks

6

Hi Peter

Should we consider a Plan B regarding the " Analog Devices Gyros don’t work properly" issue, or should we just chill and assume that it will for sure be fixed within the next few days?

(and if we need a plan B, what do you suggest?)

Thanks!

1 Like
7

I’m expecting the fix will be released very soon, very likely later this week.

To provide an answer to your second question, potential alternatives would be a NavX or Pigeon IMU.

4 Likes
8

Thanks!

1 Like
9

Is there a way to get the heading from Kinematics? I saw that DifferentialDriveWheelSpeeds has a omega method and it kinda works to track heading (works in that you get a number but it seems to accumulate error quickly), but I couldn’t find anything just off of raw distances.

Thanks,

Sean

10

With FRC scale robots, trying to track heading solely from wheel position is going to be pretty inaccurate due to wheel slip/scrub. The odometry stuff really needs an independent source of heading information such as a gyro or IMU.

1 Like
11

Thank you, @Peter_Johnson, for your updates in the various posts on this topic. Unfortunately, we’re at the end of the week with no updated release, and this is now a severe impediment to our team. Do you or anyone have a more certain word on the expected release date? I’m unfamiliar with who works on this side of things but assume you’re just relaying what you know, so again thank you for being that conduit. (We’ve perhaps been spoiled by the quick turnaround on WPILib fixes.)

2 Likes
12

Unfortunately, the latest info I have is that while the fixes are complete, the release process is taking longer than anticipated, and so the release has slipped to next week.

13

Thanks for the update. Time to get creative!

14

@Peter_Johnson Any updated ETA on the fix? We are very much hoping that it’ll be released this week as we will be ready to test our code for field-oriented driving, but are waiting on this fix.

2 Likes
15

NI seems to have published an update this evening - “2022 f1” - containing a 2022 v4 image. The online installer threw an error, so I had to download and install from the full .iso image. We switched to a really old beat up navX, for now, so we probably won’t test whether this fixed our gyro issues for at least another week.

1 Like
16

Now that NI has published we are finishing releasing an updated WPILib to match, should be later tonight, worst case tomorrow.

10 Likes
17

That’s awesome, sounds great!

18

Thanks for your work on this!

19

Great!

20

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