Go to Post What? Thinking is required? I certainly hope not! If so, I'm toast! - Robert Cawthon [more]
Home
Go Back   Chief Delphi > Technical > Control System > FRC Control System
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 02-03-2018, 02:14 PM
NathanStro's Avatar
NathanStro NathanStro is offline
Drive/Programming/Webmaster
AKA: Nathan Strodtbeck
FRC #5980 (East Grand Rapids Robotics)
Team Role: Driver
 
Join Date: Feb 2016
Rookie Year: 2016
Location: Grand Rapids, MI
Posts: 161
NathanStro is just really niceNathanStro is just really niceNathanStro is just really niceNathanStro is just really niceNathanStro is just really nice
Exclamation Random Connection Drop

Would rather figure this problem out myself but as the build deadline looms I need rather quick. the code team has had some problems with both of our robots lately. After driving for a bit the bot just drops connection in the Driver Station all while maintaining connection to the radio itself. The solution has been close the DS and power cycle the bot but that is simply unacceptable. The error in the console reads as follows:
Quote:
Warning 44004 FRC: The Driver Station has lost communication with the robot. Driver Station
Warning 44002 Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-GOOD, cRIO(.2)-GOOD, FMS-bad FRC: Driver Station ping status has changed.
I have no robot code or communications on the main tab but in Diagnostics I have Robot Radio, Robot, and Wifi all green.

If you could offer some help it would be appreciated. Thanks.
__________________



"Its not about the robot"
"Build A Robot, Build a Team, Build a Future"
"Robots is hard"
DRIVE TEAM Operator 2016: Worlds St. Louis | Driver 2017: Worlds St. Louis | Driver 2018: Worlds Detroit
Reply With Quote
  #2   Spotlight this post!  
Unread 02-03-2018, 02:55 PM
livia.13's Avatar
livia.13 livia.13 is offline
Registered User
AKA: Connor Murphy
FRC #0716 (WHO'S C-TEKS)
Team Role: Programmer
 
Join Date: Jan 2017
Rookie Year: 2016
Location: Sharon, CT
Posts: 14
livia.13 is an unknown quantity at this point
Re: Random Connection Drop

We had the same issue-whenever we went over a bump, the VRM to radio wires would drop out, due to the fact that the wires were loose

We had this problem before-we lost connection but remained connected to the camera-our Robo RIO image was outdated (this issue happens a lot in 2018, version 16). The most recent version is version 17-we haven't been having this issue since upgrading

Good luck!
Reply With Quote
  #3   Spotlight this post!  
Unread 02-03-2018, 02:59 PM
Dan Waxman Dan Waxman is offline
Registered User
FRC #0263 (Aftershock)
Team Role: Programmer
 
Join Date: Feb 2016
Rookie Year: 2016
Location: Long Island
Posts: 182
Dan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to behold
Re: Random Connection Drop

Quote:
Originally Posted by NathanStro View Post
Would rather figure this problem out myself but as the build deadline looms I need rather quick. the code team has had some problems with both of our robots lately. After driving for a bit the bot just drops connection in the Driver Station all while maintaining connection to the radio itself. The solution has been close the DS and power cycle the bot but that is simply unacceptable. The error in the console reads as follows:

I have no robot code or communications on the main tab but in Diagnostics I have Robot Radio, Robot, and Wifi all green.

If you could offer some help it would be appreciated. Thanks.
Are you printing out anything? There was an issue with WPILib at launch which would cause robot code to crash and not be recovered if RIOLog had a large volume of IO. Taking out print statements fixed this issue for us. Also check if you have a firewall up.
Reply With Quote
  #4   Spotlight this post!  
Unread 02-03-2018, 03:10 PM
epylko epylko is offline
Mentor!
AKA: Eric Pylko
FRC #3181 (Pittsford Panthers)
Team Role: Mentor
 
Join Date: Jan 2011
Rookie Year: 1970
Location: Pittsford, NY
Posts: 49
epylko is on a distinguished road
Re: Random Connection Drop

Quote:
Originally Posted by Dan Waxman View Post
Are you printing out anything? There was an issue with WPILib at launch which would cause robot code to crash and not be recovered if RIOLog had a large volume of IO. Taking out print statements fixed this issue for us. Also check if you have a firewall up.
I think that issue was fixed in the NI Update that came out last week. http://www.ni.com/download/first-rob...-2017/7183/en/
Reply With Quote
  #5   Spotlight this post!  
Unread 02-03-2018, 03:12 PM
Dan Waxman Dan Waxman is offline
Registered User
FRC #0263 (Aftershock)
Team Role: Programmer
 
Join Date: Feb 2016
Rookie Year: 2016
Location: Long Island
Posts: 182
Dan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to beholdDan Waxman is a splendid one to behold
Re: Random Connection Drop

Quote:
Originally Posted by epylko View Post
I think that issue was fixed in the NI Update that came out last week. http://www.ni.com/download/first-rob...-2017/7183/en/
It was, that's why I mentioned at launch. But if they haven't updated since launch, it will still be an issue for them.
Reply With Quote
  #6   Spotlight this post!  
Unread 02-04-2018, 11:50 AM
NathanStro's Avatar
NathanStro NathanStro is offline
Drive/Programming/Webmaster
AKA: Nathan Strodtbeck
FRC #5980 (East Grand Rapids Robotics)
Team Role: Driver
 
Join Date: Feb 2016
Rookie Year: 2016
Location: Grand Rapids, MI
Posts: 161
NathanStro is just really niceNathanStro is just really niceNathanStro is just really niceNathanStro is just really niceNathanStro is just really nice
Re: Random Connection Drop

Thanks everyone! my short term solution is removing all system.out.prinln actions. I read up and learned that the error was caused by an overload on console log inputs. We were printing out the throttle and wheel power every .2 seconds and now that it is removed we are all good. Thanks again. (don't worry we will get that update suite done soon.)
__________________



"Its not about the robot"
"Build A Robot, Build a Team, Build a Future"
"Robots is hard"
DRIVE TEAM Operator 2016: Worlds St. Louis | Driver 2017: Worlds St. Louis | Driver 2018: Worlds Detroit
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 03:04 PM.

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


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