Go to Post We can't quite define FIRST according to past standards and traditions, because it is shaping the future and does not conform to today's model of sports. - JaneYoung [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

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #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
 


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 05:25.

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