Go to Post My brain is borderline mush, I don't have much of a voice, and I don't think I could be much happier. - Billfred [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 04-04-2016, 18:30
slibert slibert is offline
Software Mentor
AKA: Scott Libert
FRC #2465 (Kauaibots)
Team Role: Mentor
 
Join Date: Oct 2011
Rookie Year: 2005
Location: Kauai, Hawaii
Posts: 349
slibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud of
Re: navX Issues

Quote:
Originally Posted by s5511 View Post
During yesterday at tournament, our navX gyro sensor stopped returning values, causing our drivetrain PID to malfunction. The navX is protected by a plastic casing and is still directly plugged into the roborio. Are there any reasons that could cause the navX to stop functioning like this? We have been using it for over 4 weeks, and it has been working fine.
This is repeating the fine advice given by others, but the most likely issue is that the 5V power source to the navX-MXP, provided by the RoboRIO via the MXP connector, was cut due to a Stage 2 brownout. A related failure condition is the 5V power source was cut due to a short circuit that the RoboRIO detected as a current surge.

In each of these cases, the navX-MXP would lose power, and then begin re-initializing once power was restored. In the case of a stage 2 brownout, power could be restored as quickly as 100ms later, it just depends upon the conditions.

As discussed in the "Best Practices guide", using a USB cable to provide backup power in case the RoboRIO cuts the MXP power will address this issue.

Here at Kauai Labs, we have this year seen a few times a more fatal issue. Due to excessive current draw on the expansion IO pins, one of the expansion IO power (3.3V/5V depending upon the jumper setting on the navX-MXP) traces, or the ground return trace, can become damaged. This may cause the MXP power source to the navX-MXP processor to no longer work (a USB cable would fix this), and also mean that the power to anything connected to the Expansion IO pins on the navX-MXP would not work. If you see visible evidence of a burnt trace on the navX-MXP, please let us know (support@kauailabs.com) and we'll work with you to replace your board.

Aloha,

- scott
Reply With Quote
  #2   Spotlight this post!  
Unread 04-04-2016, 19:15
cjl2625's Avatar
cjl2625 cjl2625 is offline
apel py
AKA: Cory Lynch
FRC #2067 (Apple Pi)
Team Role: Programmer
 
Join Date: Jan 2013
Rookie Year: 2013
Location: Guilford, CT
Posts: 412
cjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to behold
Re: navX Issues

I've also had problems with the NavX randomly dying (plugged in both MXP and USB).
As such, we have a kit of parts gyro on the robot as a backup (that we can switch to at any time) because we can't always trust that the navX will get us through the match.

This week, it behaved pretty well, except for one match, where it was completely dead the whole match, and then was fine again upon reboot. No idea why.
__________________
Head Programmer / Driver

Last edited by cjl2625 : 04-04-2016 at 19:18.
Reply With Quote
  #3   Spotlight this post!  
Unread 04-04-2016, 22:59
slibert slibert is offline
Software Mentor
AKA: Scott Libert
FRC #2465 (Kauaibots)
Team Role: Mentor
 
Join Date: Oct 2011
Rookie Year: 2005
Location: Kauai, Hawaii
Posts: 349
slibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud of
Re: navX Issues

Quote:
Originally Posted by cjl2625 View Post
I've also had problems with the NavX randomly dying (plugged in both MXP and USB).
As such, we have a kit of parts gyro on the robot as a backup (that we can switch to at any time) because we can't always trust that the navX will get us through the match.

This week, it behaved pretty well, except for one match, where it was completely dead the whole match, and then was fine again upon reboot. No idea why.
Cory, we'd like to get to the bottom of what's going on here. Since I'm aware from our previous conversations you've followed all of the documented best practices, if you'd like we can send you a replacement navX-MXP to try; just contact support@kauailabs.com and we'll get that started for you.
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 23:42.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi