Go to Post Using a mouse is so 20th century! - Tom Bottiglieri [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
 
Thread Tools Rating: Thread Rating: 4 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 24-03-2015, 18:56
plnyyanks's Avatar
plnyyanks plnyyanks is offline
Data wins arguments.
AKA: Phil Lopreiato
FRC #1124 (The ÜberBots), FRC #2900 (The Mighty Penguins)
Team Role: College Student
 
Join Date: Apr 2010
Rookie Year: 2010
Location: NYC/Washington, DC
Posts: 1,114
plnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond repute
Re: How to determine root cause of robot dropping from Teleop to Disabled during matc

Quote:
Originally Posted by Monochron View Post
We had a very similar situation in our quarter finals match. The first one we exhibited similar behavior all throughout teleop (autonomous went fine). The second match we only dropped out for about 30 seconds or so. The DS logs showed that we lost communication with the FMS for the duration of those times. CSA's suggested that this was caused by our radio losing power, but it looked like they couldn't investigate the issue further than that.
It sounds like the CSA was on to something - a radio reboot typically takes between 30 and 40 seconds to come back (the DS logs tell you exactly how long your robot was down). In contrast, a roboRIO will take around 25 seconds to reboot.

Common causes of radio reboots:
- Brownouts due to your battery being low. These events correlate to large current draws
- PDP Fuses. Push them in all the way
- Multiple things plugged into the radio source on the VRM
- The barrel connector not being plugging in all the way, especially if it's an older one
__________________
Phil Lopreiato - "It's a hardware problem"
Team 1124 (2010 - 2013), Team 1418 (2014), Team 2900 (2016)
FRC Notebook The Blue Alliance for Android

Last edited by plnyyanks : 24-03-2015 at 22:57. Reason: Symptoms != causes
  #2   Spotlight this post!  
Unread 24-03-2015, 22:37
Monochron's Avatar
Monochron Monochron is offline
Engineering Mentor
AKA: Brian O'Sullivan
FRC #4561 (TerrorBytes)
Team Role: Engineer
 
Join Date: Feb 2007
Rookie Year: 2002
Location: Research Triangle Park, NC
Posts: 910
Monochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond repute
Re: How to determine root cause of robot dropping from Teleop to Disabled during matc

Quote:
Originally Posted by plnyyanks View Post
It sounds like the CSA was on to something - a radio reboot typically takes between 30 and 40 seconds to come back (the DS logs tell you exactly how long your robot was down). In contrast, a roboRIO will take around 25 seconds to reboot.

Common symptoms of radio reboots:
- Brownouts due to your battery being low. These events correlate to large current draws
- PDP Fuses. Push them in all the way
- Multiple things plugged into the radio source on the VRM
- The barrel connector not being plugging in all the way, especially if it's an older one
Yeah we didn't notice any unusually large voltage spikes in the logs but I'm still checking different possible causes.
  #3   Spotlight this post!  
Unread 25-03-2015, 13:08
MrRoboSteve MrRoboSteve is offline
Mentor
AKA: Steve Peterson
FRC #3081 (Kennedy RoboEagles)
Team Role: Mentor
 
Join Date: Mar 2012
Rookie Year: 2011
Location: Bloomington, MN
Posts: 578
MrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond reputeMrRoboSteve has a reputation beyond repute
Re: How to determine root cause of robot dropping from Teleop to Disabled during matc

Also make sure you are using the appropriately sized barrel connector. If the outer diameter is too small, intermittent power is possible.
__________________
2016-17 events: 10000 Lakes Regional, Northern Lights Regional, FTC Burnsville Qualifying Tournament

2011 - present · FRC 3081 Kennedy RoboEagles mentor
2013 - present · event volunteer at 10000 Lakes Regional, Northern Lights Regional, North Star Regional, Lake Superior Regional, Minnesota State Tournament, PNW District 4 Glacier Peak, MN FTC, CMP
http://twitter.com/MrRoboSteve · www.linkedin.com/in/speterson
Closed Thread


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 03:10.

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