NavX Help - USB issue

Technical Java
1

CD gurus - We are having an issue with communicating with our navX2-micro through the roboRIO.

We updated to latest firmware and we can get readings through the navX UI, but when we deploy code we get the following errors in the RIOlog -

Opening USB serial port to communicate with navX-Sensor.

Error opening USB serial port to communicate with navX-Sensor.

Unable to open USB serial port to communicate with navX-Sensor.

Seen in the image here.

20230128_115441
20230128_1154411920×1440 267 KB

Any input, thoughts, hopes, and dreams are appreciated. Thanks!

2

For reference we are trying to verify that the roboRIO can communicate or detect the navX sensor through USB. Looks like we are not seeing anything return from KauaiLabs help.

20230128_130914
20230128_1309141920×1440 289 KB

20230128_130846
20230128_1308461920×1440 268 KB

3

You are getting one of the two nasty errors that my team has experienced. The easy experimental tasks are:

  • use the other USB A port
  • press the NavX reset button
  • reboot the roboRIO
  • remove all other USB devices
  • try your other NavX
    Note that LInux takes some time (seems like a lot of time) to release the USB port if was in use or errored or something.
1 Like
4

We will give these a shot. Updating anyone reading this in the future- we swapped to i2C until we get the USB figured out and everything works as expected.

Is there a reset button on the navX2-micro? We are using that as opposed to the navX which sits onboard the roboRIO.

1 Like
5

If in a standard case, then poke into the little hole labeled something like reset.
You are aware of the (varying) advice not to use I2C on the roboRIO and certainly not the onboard. I tested a NavX-micro on the MXP and had no problems. Actually any one device worked fine for me on the MXP but more than one device and random fatal failures occurred.

I had to look twice at your team number - we’ve been next to each other in the pits.

6

Yes, I have read about the unknown issues with using the onboard I2C port. Although we have used that on an outreach robot for a couple of years now with no issues.

And yes, I’ve talked with Brad about how we are not allowed to be at the same events due go the confusion we cause the queuers and scouters. :slight_smile:

7

Were you able to get any resolution here? We’re having the same problem. If we swap the port the NavX is connected to while the Roborio is running, we can then read the navx successfully (despite the fact that our code calls out a specific USB port…). Have you tried to set any of the serial comm parameters (e.g. baud rate) directly?

8

Wish I had a good answer for you. We instead went ahead with the risky move of using the I2C connection which has worked without any issues all season so far.

We will revisit this issue after the season is over or just switch to Pigeon.

9

We haven’t used the I2C connection before. Are you able to use that directly when the NavX is plugged into the MXP port on the RoboRIO? Or do I need an I2C cable to connect it to the RoboRIO I2C port?

10

We are using the NavX2-micro which is NOT plugged into the roboRIO MXP port, but instead is placed at the bottom of our robot and connected via the I2C cable.

1 Like
11

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