View Single Post
  #13   Spotlight this post!  
Unread 04-02-2017, 10:35
Eric222 Eric222 is offline
Registered User
FRC #0222 (Tigertrons)
Team Role: Mentor
 
Join Date: Jan 2011
Rookie Year: 2009
Location: Tunkhannock
Posts: 21
Eric222 is an unknown quantity at this point
Re: Nav-X error - Cant get readings

Quote:
Originally Posted by slibert View Post
Here are a few suggestions:

1) I found during testing of the USB2 option (which based on our testing is not working as expected currently) that after attempting to use USB2, it was required to reboot the roborio in order to get things working again. It's as if when USB2 is used, something gets in a bad state that requires a reboot to clear. So if you haven't you might try rebooting the RoboRIO and then re-testing with just the navX-Micro in USB slot 1.

2) To make sure the navX-Micro is completely healthy, you can verify the two green (S1 and S2) LEDs on the board are lit during operation. If they are not both on during operation, there is a problem w/the board itself.

3) if 2) succeds, next use the navXUI application (installed when you run the setup program). This would entail connecting the USB cable from the navX-Micro to a Windows PC and verifying that you get a correct reading from the sensor as displayed in the navXUI display.

4) If 2) or 3) above fails, we'll be happy to replace the board for you.

5) If 2) and 3) both work, then there's something particular to your configuration limiting USB communication. Perhaps it's the USB cable, perhaps it's the RoboRIO USB connector. You can check both of these by using the LifeCAM in the slot you are wanting to use the navX-Micro, and the USB cable you were using w/the navX-Micro, and verify that works correctly.

6) If that's still not working, you have the option in this case to use the navX-Micro I2C interface instead, as described in the navX-Micro RoboRIO installation page.

1) So we have tried restarting the roborio multiple times
2) Both green LEDs light up
3) The board works when plugged into the computer and running NavXUI
4) So the board is functioning properly
5) And it definitely looks like a communication issue
6) When we plug into the I2C ports, the 2 green LEDs do not stay on after startup...

The problem appears to be within the WPI_SerialPortQueryHubPaths.vi after following the initial error code posted.

If we run robot main, and look at some of the internal errors in the Navx main VI, we see the pictures attached.

Any other suggestions? Thanks for your help!
Attached Thumbnails
Click image for larger version

Name:	WPI_SerialPortQueryHubPaths_vi.PNG
Views:	8
Size:	108.5 KB
ID:	21686  Click image for larger version

Name:	Navx Error.PNG
Views:	6
Size:	3.0 KB
ID:	21687  Click image for larger version

Name:	Navx Error 2.PNG
Views:	3
Size:	2.4 KB
ID:	21688  Click image for larger version

Name:	Navx Error 3.PNG
Views:	3
Size:	2.2 KB
ID:	21689  
__________________
http://tigertrons.net/
Reply With Quote