Go to Post Don't give FIRST ideas...we like our 45 day build season. They can make it shorter. Never underestimate the power of the GDC. - Littleboy [more]
Home
Go Back   Chief Delphi > Technical > 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 29-01-2017, 23:16
ultimate360's Avatar
ultimate360 ultimate360 is offline
Director of programming/electrical
AKA: Logan Steffen
FRC #4607 (CIS Robotics)
Team Role: Programmer
 
Join Date: Nov 2014
Rookie Year: 2014
Location: Becker, MN
Posts: 18
ultimate360 will become famous soon enough
Robot communication issues

Hey folks!

4607 has been working on testing out the new control system updates and firmware. I have been the one working on this and have hit a brick wall when it comes to connecting to a robot.

When I open the driver station and connect to the robot through either wifi or tethered USB/Ethernet, we notice a strange thing happen. The connection lights in the driver station come on for a brief second, then the robot communication indicator halfway goes off (it's red and green side by side). Everything then goes back to red and acts like there is zero connection. However, when I open the diagnostics tab, both the Robot and Robot Radio indicators are green, yet robot comm and code are red and I cannot drive. The battery voltage is also not present and just shows the red box. What's weird is that I can still deploy code to the robot even when the driver station won't show us that it's connected and ready to drive.

There are rare times where I will open the driver station and the comm indicator will go green, cut to red, then come back about 20 seconds later and i'm then allowed to drive. The only surefire way to get connection with the robot is immediately after freshly imaging the Roborio.


Here are the details of what we are running:

Laptop: Lenovo Thinkpad E560
OS: Windows 10 Pro x64
Roborio image: 2017 v8 (current)
Installed update suite: 2017.0.0 (current)
Robot Radio: OpenMesh AC, programmed from new bridge tool (new 2017 version)


We have multiple laptops that have been tried and we still get the same results. If anyone has seen this issue yet or knows how to fix it, we'd greatly appreciate the help. We have had no issues at all with robot communication until we upgraded to the 2017 FRC software and radio. This is my fourth year of programming with 4607, and I haven't noticed something like this before now.

I wanted to bring this issue forward in case we are discovering a potential firmware issue or other problem. Hopefully we can get it figured out and maybe help others with a similar problem.
Reply With Quote
  #2   Spotlight this post!  
Unread 29-01-2017, 23:30
Bkeeneykid's Avatar
Bkeeneykid Bkeeneykid is offline
#wheatcoastneatcoast
AKA: Devin Keeney
FRC #1982 (Cougar Robotics); Season Long Fantasy FIRST (F3)
Team Role: Leadership
 
Join Date: Feb 2015
Rookie Year: 2015
Location: Lenexa, Kansas
Posts: 369
Bkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud of
Re: Robot communication issues

When you have no communications, can you access the roboRIO webpage (roborio-4607-FRC.local in IE)? Have you disabled all other network adapters as well as disabled all firewalls?
__________________

F4 Network Website Designer

2010-2012: A Whole Buncha FLL Teams; Team Spirit, Gracious Professionalism Award winner
2015-Current: FRC 1982, Captain, Electrical Lead
Beginning FIRST Volunteer

Moderator on the FIRSTwiki
Reply With Quote
  #3   Spotlight this post!  
Unread 30-01-2017, 23:23
BrianK BrianK is offline
Registered User
FRC #1622
 
Join Date: Oct 2012
Location: San Diego
Posts: 5
BrianK is an unknown quantity at this point
Re: Robot communication issues

Based on the information you've provided, there are some elements of deterministic behavior (performs the same using any laptop & still seems to be able to download code), and some random behavior (i.e., the rare times it behaves differently). Through your troubleshooting you've already removed one source of potential randomness from consideration: It's not a wireless issue since you've tested it tethered. Are you testing the using code that is known to be operational with an older firmware version? If not, I'd recommend either reverting firmware to the previous one or using the current firmware with code that you've written that's known to work with the current firmware.

You don't say what language you are using or what type of control (e.g., Iterative). I don't have experience with the RoboRIO -- my experience is a bit more dated, so others might set me straight. However, based on the information you provided, it could be possible that your code is simply failing most of the time and dropping out the the bottom of your code. You might try wrapping all your methods in a catch block and have the contents of the catch block do something to demonstrate that the catch block was entered (e.g., turn on an LED).
Reply With Quote
  #4   Spotlight this post!  
Unread 30-01-2017, 23:41
wesleyac's Avatar
wesleyac wesleyac is offline
Registered Luser
AKA: Wesley Aptekar-Cassels
FRC #1678 (Citrus Circuits)
Team Role: Programmer
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Davis, CA
Posts: 61
wesleyac is a splendid one to beholdwesleyac is a splendid one to beholdwesleyac is a splendid one to beholdwesleyac is a splendid one to beholdwesleyac is a splendid one to beholdwesleyac is a splendid one to beholdwesleyac is a splendid one to beholdwesleyac is a splendid one to behold
Re: Robot communication issues

Try setting a static IP for the roboRIO. I've seen that help issues like this before.

Also, what Bkeeneykid is good advice. It seems like you're having a driver station issue, and not a connection issue, as you can deploy code.

You could also try QDriverStation - although you won't be able to use it in official competition, and it does have some issues, you can set the IP for it to try to connect to, which can be useful in debugging.

Downgrading the roborio, radio, and DS firmware one at a time could also help isolate where the issue is. I would save that as a last resort though, since it will take a lot of time.
__________________
Quote:
Originally Posted by The programming team
Define "works."
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 12:36.

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