Go to Post How come so many engineering types don't understand sarcasm? :) - IndySam [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
  #16   Spotlight this post!  
Unread 31-01-2017, 08:41
Mark McLeod's Avatar
Mark McLeod Mark McLeod is online now
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,945
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Can't connect to the robot

It'd be so much easier if you'd tell us what troubleshooting steps you have taken.
What other directions suggested in this thread and others have you followed?

- Does last year's radio still work as you said before?

- Turn off all firewalls, anti-virus, and third party network management software on your PC. Those all can block communications depending on how they were configured.

- Disable all other network connections (Disable not unplug)

- You can also try pinging roborio-6026-frc.local, roborio-6026-frc.lan, roborio-6026-frc.frc-robot.local
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Reply With Quote
  #17   Spotlight this post!  
Unread 31-01-2017, 20:29
Judge2005 Judge2005 is offline
Registered User
FRC #1277
 
Join Date: Mar 2016
Location: Groton MA
Posts: 8
Judge2005 is an unknown quantity at this point
Re: Can't connect to the robot

We were having very similar problems as described in the first post in this thread. This fixed it:
  1. Open a cmd window as admin.
  2. Type: netsh int ip reset c:\resetlog.txt and press enter
  3. Restart your computer

Hope this works for anyone looking for a solution to this.
Reply With Quote
  #18   Spotlight this post!  
Unread 01-02-2017, 00:42
BSV BSV is offline
FTC / FRC mentor
AKA: Travis
FRC #2723
 
Join Date: May 2013
Rookie Year: 2011
Location: Oklahoma City
Posts: 152
BSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud ofBSV has much to be proud of
Re: Can't connect to the robot

Quote:
Originally Posted by Mark McLeod View Post
It'd be so much easier if you'd tell us what troubleshooting steps you have taken.
What other directions suggested in this thread and others have you followed?

- Does last year's radio still work as you said before?

- Turn off all firewalls, anti-virus, and third party network management software on your PC. Those all can block communications depending on how they were configured.

- Disable all other network connections (Disable not unplug)

- You can also try pinging roborio-6026-frc.local, roborio-6026-frc.lan, roborio-6026-frc.frc-robot.local
Sorry, I should have said that we looked at the WPI troubleshooting here: http://wpilib.screenstepslive.com/s/...anual-id=24193

as well as trying the other suggestions on this thread.

After your response, we tried a "ping roborio-2723-frc.lan" (did not work, couldn't find IP) "ping roborio-2723-frc.local" (also failed) and "ping roborio-2723-frc.frc-robot.local" (which got a response).

There is no firewall running. It seems that the DNS name is getting assigned incorrectly or not at all by the router, but I'm not a networking expert so I've no idea. Hopefully we can try again with the old radio in the next couple of days to compare results more closely.

Quote:
Originally Posted by Judge2005
Open a cmd window as admin.
Type: netsh int ip reset c:\resetlog.txt and press enter
Restart your computer
This worked... for about 5 seconds before the driver station lost connection again. "ping roborio-2723-frc.local" continued to work after this, though, at least until we restarted the RoboRio to try to get the connection back. When we reconnected after the reboot, that address failed again.

Entering the IP address in the driver station in place of the team number seems to work, but, like I said, it's kind of a guess. It usually comes up as 10.27.23.21 but not always.

Thanks for the suggestions.
Reply With Quote
  #19   Spotlight this post!  
Unread 01-02-2017, 08:09
Mark McLeod's Avatar
Mark McLeod Mark McLeod is online now
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,945
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Can't connect to the robot

Since it works, you can type roborio-2723-frc.frc-robot.local into the Driver Station in place of the team number. That should keep you connected.

There does appear to be an oddity in the construction of the roboRIO DNS name on some setups where it throws that extra frc-robot into the mix.

It really disrupts Java/C++ downloads which check a variety of addresses to connect, but not that extra frc-robot address.
Then you have to add that extra address to the list it checks.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 01-02-2017 at 08:43.
Reply With Quote
  #20   Spotlight this post!  
Unread 01-02-2017, 12:42
buchanan buchanan is offline
Registered User
FRC #2077 (Laser Robotics)
Team Role: Mentor
 
Join Date: Mar 2009
Rookie Year: 2007
Location: Wales, WI
Posts: 71
buchanan is just really nicebuchanan is just really nicebuchanan is just really nicebuchanan is just really nice
Re: Can't connect to the robot

Quote:
Originally Posted by Mark McLeod View Post
Since it works, you can type roborio-2723-frc.frc-robot.local into the Driver Station in place of the team number. That should keep you connected.

There does appear to be an oddity in the construction of the roboRIO DNS name on some setups where it throws that extra frc-robot into the mix.

It really disrupts Java/C++ downloads which check a variety of addresses to connect, but not that extra frc-robot address.
Then you have to add that extra address to the list it checks.
Thanks Mark! This is the condition we've been struggling with.It's great to know someone understands the problem; a solution is sure to follow. No pressure.

The "what do we do meanwhile" bottom line appears to be:
1) The DS won't connect. The workaround you gave handles this.
2) Cannot deploy from Eclipse. Direct connection via USB works around this. Back to the old IFI days.
Reply With Quote
  #21   Spotlight this post!  
Unread 01-02-2017, 13:37
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,766
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Can't connect to the robot

Can you clarify what the web page says that the device name is? Is it roboRIO-####-frc or does the name shown in the web page end in .frc-robot?

If so, can you remove .frc-robot to get it to work?

Greg McKaskle

Last edited by Greg McKaskle : 01-02-2017 at 13:42. Reason: rephrase to clarify
Reply With Quote
  #22   Spotlight this post!  
Unread 01-02-2017, 14:00
Mark McLeod's Avatar
Mark McLeod Mark McLeod is online now
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,945
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Can't connect to the robot

In the cases I've seen the roboRIO has the expected
  • Hostname: roboRIO-team#-FRC
But with
  • DNS Name: roboRIO-team#-FRC.frc-robot.local
I can't edit the DNS name through the web browser and I haven't tried other methods.

On the PC connected to run the Driver Station it might or might not include a DNS Suffix Search List: frc-robot.local (from an ipconfig /all).
It appears to be somewhat random on any particular PC, i.e., I can have two side-by-side PC's attempting to connect and one will work, but the other fail. After disconnecting/restarting the radio both PCs may work.
Depending on if the PC has the search suffix then the Driver Station will connect, but code download still might fail probably from not including the unexpected DNS suffix.

I made Kevin aware of the issue.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 01-02-2017 at 14:28.
Reply With Quote
  #23   Spotlight this post!  
Unread 02-02-2017, 00:28
buchanan buchanan is offline
Registered User
FRC #2077 (Laser Robotics)
Team Role: Mentor
 
Join Date: Mar 2009
Rookie Year: 2007
Location: Wales, WI
Posts: 71
buchanan is just really nicebuchanan is just really nicebuchanan is just really nicebuchanan is just really nice
Re: Can't connect to the robot

Quote:
Originally Posted by Mark McLeod View Post
roboRIO-team#-FRC.frc-robot.local
The unexpected ".frc-robot" is apparently confusing both the DS and Eclipse deployment.

What I have seen on my system (Windows 10):

1) Somebody, somewhere, is setting the "Connection-specific DNS Suffix" for the wireless adapter to "frc-robot.local" (see "ipconfig /all"). I don't know how this is happening but it looks broken to me. Radio firmware?

2) If you go to Control Panel->Network and Internet->Network and Sharing Center->Change Adapter Settings->(select) Wi-Fi->(tab)Change settings of this connection->(in dialog, select)Internet Protocol Version 4->Properties->Advanced->(tab)DNS, you'll see what appear to be a couple of ways to override the above setting:

a) Change "Append primary..." to "Append these..." and put "local" in the list.
-or-
b) Put "local" into the "DNS suffix for this connection" box.

In very limited testing either seems to work for me.

I am NOT a Windows expert (and wouldn't admit it if I were). If those who are disagree, trust them not me.

Last edited by buchanan : 02-02-2017 at 00:31.
Reply With Quote
  #24   Spotlight this post!  
Unread 02-02-2017, 09:59
Mark McLeod's Avatar
Mark McLeod Mark McLeod is online now
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,945
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Can't connect to the robot

Quote:
Originally Posted by buchanan View Post
a) Change "Append primary..." to "Append these..." and put "local" in the list.
-or-
b) Put "local" into the "DNS suffix for this connection" box.
I've had success with this as well, but I haven't been able to vet it in all cases yet. I have to make my team rounds.
I had one case where it didn't help, because the PC suffix was wrong, but I didn't try adding frc-robot.local as an ending on that one.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 02-02-2017 at 10:40.
Reply With Quote
  #25   Spotlight this post!  
Unread 02-02-2017, 13:46
Judge2005 Judge2005 is offline
Registered User
FRC #1277
 
Join Date: Mar 2016
Location: Groton MA
Posts: 8
Judge2005 is an unknown quantity at this point
Re: Can't connect to the robot

One more observation to throw into the mix: everything works for over Ethernet. Interestingly, if I ping the roboRIO over Ethernet, it uses an IPv6 address.

Also, further to my post about netsh: for us it works until we switch the wifi to the Internet. Then when we switch back it is all broken again.

The only solution we have which seems to work for eclipse and the drive station (and hopefully GRIP) is to set a static IP address on the roboRIO, then add all host name variants to the Windows host file.

This makes me very nervous though: What is going to happen when we get to competition? We really need a permanent solution to this soon.
Reply With Quote
  #26   Spotlight this post!  
Unread 03-02-2017, 06:56
Judge2005 Judge2005 is offline
Registered User
FRC #1277
 
Join Date: Mar 2016
Location: Groton MA
Posts: 8
Judge2005 is an unknown quantity at this point
Re: Can't connect to the robot

One more observation to throw into the mix: everything works for over Ethernet. Interestingly, if I ping the roboRIO over Ethernet, it uses an IPv6 address.

Also, further to my post about netsh: for us it works until we switch the wifi to the Internet. Then when we switch back it is all broken again.

The only solution we have which seems to work for eclipse and the drive station (and hopefully GRIP) is to set a static IP address on the roboRIO, then add all host name variants to the Windows host file.

This makes me very nervous though: What is going to happen when we get to competition? We really need a permanent solution to this soon.
Reply With Quote
  #27   Spotlight this post!  
Unread 04-02-2017, 10:42
SOBS7 SOBS7 is offline
Registered User
None #6003
 
Join Date: Jan 2017
Location: North Carolina
Posts: 6
SOBS7 is an unknown quantity at this point
Re: Can't connect to the robot

We're expecting the Sam problem and easy fixes yet?
Reply With Quote
  #28   Spotlight this post!  
Unread 04-02-2017, 10:46
SOBS7 SOBS7 is offline
Registered User
None #6003
 
Join Date: Jan 2017
Location: North Carolina
Posts: 6
SOBS7 is an unknown quantity at this point
Re: Can't connect to the robot

Unable to ping the Wifi but able to ping with USB cable to RoboRio.
Reply With Quote
  #29   Spotlight this post!  
Unread 04-02-2017, 15:09
SOBS7 SOBS7 is offline
Registered User
None #6003
 
Join Date: Jan 2017
Location: North Carolina
Posts: 6
SOBS7 is an unknown quantity at this point
Re: Can't connect to the robot

Don't know how to edit previous post sorry. We solved our problem by simply disabling all wifi connections on the PC except the robot and it connected perfectly. It appears the wifi connection to the internet on the PC was the problem.
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 19:58.

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