Go to Post you should be putting forth you best effort every time you enter the field. - Protronie [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

 
Reply
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 06-04-2016, 00:00
Jpatterson1710's Avatar
Jpatterson1710 Jpatterson1710 is offline
Registered User
AKA: Josh Patterson
FRC #1710 (Ravonics Revolution)
Team Role: Alumni
 
Join Date: Feb 2014
Rookie Year: 2012
Location: Olathe, KS
Posts: 101
Jpatterson1710 has a spectacular aura aboutJpatterson1710 has a spectacular aura aboutJpatterson1710 has a spectacular aura about
Re: Connection issues at regionals

Quote:
Originally Posted by Cecil View Post
Static IP addresses WILL work on the field
Right, we just normally don't do it that way.
__________________
2012-2014 Mechanical Team FRC 1710
2014-2015 Chief Operations Officer FRC 1710
2016-Present FTAA
Reply With Quote
  #17   Spotlight this post!  
Unread 06-04-2016, 00:06
Jpatterson1710's Avatar
Jpatterson1710 Jpatterson1710 is offline
Registered User
AKA: Josh Patterson
FRC #1710 (Ravonics Revolution)
Team Role: Alumni
 
Join Date: Feb 2014
Rookie Year: 2012
Location: Olathe, KS
Posts: 101
Jpatterson1710 has a spectacular aura aboutJpatterson1710 has a spectacular aura aboutJpatterson1710 has a spectacular aura about
Re: Connection issues at regionals

Quote:
Originally Posted by rtfgnow View Post
The recommendation is to use DHCP unless you have a reason not to, most of the time being an additional ip based device. If that is the case than CSAs are told to use static IPs and they will work fine with the field if the last octet is less than 20 and not 1 or 4. As a rule of thumb I use 2 for the roboRIO and 5 for the DS.

The robot should not have a DHCP server when in the pits. Edit: An external router can act as a DHCP server in the pits if not wifi enabled.
This is true. It's much more simple to use DHCP. Additional IP devices aren't usually an issue if the IP on that device is set correctly. (Should be under 20 on the last octet.) FMS begins assigning the DS at 20, reserving lower addresses for these cases.
__________________
2012-2014 Mechanical Team FRC 1710
2014-2015 Chief Operations Officer FRC 1710
2016-Present FTAA
Reply With Quote
  #18   Spotlight this post!  
Unread 06-04-2016, 08:23
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,752
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: Connection issues at regionals

Wes, if/when this happens, did you happen to notice if the link lights on the RoboRIO were on?

This is one of the indications that the radio and roboRIO link didn't come up and one of the devices needs to be rebooted -- we generally reboot the roboRIO because it is faster. This is likely caused by power saving features on one or both devices, and we are hoping to fix this for good, but it happens quite rarely, so didn't get enough instances during beta. The general guideline is to swap to the other radio port. It appears the the one near the power does this less frequently, but there are only two, so it is a quick experiment.

FIRST does have much more control over the firmware, but things like this are rare, and there are many configuration options. Why would they fiddle with POE and power settings away from the factory settings unless they see an issue? I think there are already far fewer gremlins in the system than the end-of-life Dlink, but with a season and another beta period, we will really know how beneficial the open image is.

As for static and dynamic IPs. The majority of teams are configured for dynamic, or the CSAs and FTAs do it for them. Occasionally, a team wants to be static, which is compatible with the field DHCP, so we ensure that they stay out of the range of the dynamic server and have the recommended values. As long as you are consistent, both work fine. I prefer DHCP in almost all instances, but let the team decide after I explain why their current settings were not working.

Greg McKaskle
Reply With Quote
  #19   Spotlight this post!  
Unread 06-04-2016, 13:54
MamaSpoldi's Avatar
MamaSpoldi MamaSpoldi is online now
Programming Mentor
AKA: Laura Spoldi
FRC #0230 (Gaelhawks)
Team Role: Engineer
 
Join Date: Jan 2009
Rookie Year: 2007
Location: Shelton, CT
Posts: 305
MamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant futureMamaSpoldi has a brilliant future
Re: Connection issues at regionals

Quote:
Originally Posted by Wes2443 View Post
If it helps we have the ethernet to the roboRIO connected through the port furthest away from the power.
Note that it was specifically noted in Update 8 that you should plug into the other port. I think that would be worth a try.

Quote:
Control System Note:We have heard sporadic reports of link failure between the roboRIO and the radio after a cold boot, characterized by the amber and green link LEDs on the roboRIO Ethernet port remaining off (and a roboRIO reset resolving the issue). We have located a set of hardware that reproduces the issue and are currently investigating the root cause. In the meantime, teams experiencing this issue can connect the roboRIO Ethernet to the radio port labeled “18-24v POE” (next to the power connector) as a temporary workaround (the issue only affects the port labeled “802.3af POE”).
__________________
Reply With Quote
  #20   Spotlight this post!  
Unread 06-04-2016, 23:34
Wes2443's Avatar
Wes2443 Wes2443 is offline
Registered User
AKA: Wesley Sakutori
FRC #2443 (Blue Thunder)
Team Role: Programmer
 
Join Date: Jan 2016
Rookie Year: 2014
Location: Kahului, HI
Posts: 10
Wes2443 is an unknown quantity at this point
Re: Connection issues at regionals

Quote:
Originally Posted by Greg McKaskle View Post
Wes, if/when this happens, did you happen to notice if the link lights on the RoboRIO were on?

This is one of the indications that the radio and roboRIO link didn't come up and one of the devices needs to be rebooted -- we generally reboot the roboRIO because it is faster. This is likely caused by power saving features on one or both devices, and we are hoping to fix this for good, but it happens quite rarely, so didn't get enough instances during beta. The general guideline is to swap to the other radio port. It appears the the one near the power does this less frequently, but there are only two, so it is a quick experiment.

FIRST does have much more control over the firmware, but things like this are rare, and there are many configuration options. Why would they fiddle with POE and power settings away from the factory settings unless they see an issue? I think there are already far fewer gremlins in the system than the end-of-life Dlink, but with a season and another beta period, we will really know how beneficial the open image is.

As for static and dynamic IPs. The majority of teams are configured for dynamic, or the CSAs and FTAs do it for them. Occasionally, a team wants to be static, which is compatible with the field DHCP, so we ensure that they stay out of the range of the dynamic server and have the recommended values. As long as you are consistent, both work fine. I prefer DHCP in almost all instances, but let the team decide after I explain why their current settings were not working.

Greg McKaskle
I believe the COMMS light was on on the roboRIO, didn't notice the link light. Now I'm starting to think whether disconnecting the ethernet and reconnecting it on the DS would help. We only used static IPs on the rio and camera components because we were testing it with the ethernet switch which wouldnt work on DHCP.

Quote:
Originally Posted by MamaSpoldi View Post
Note that it was specifically noted in Update 8 that you should plug into the other port. I think that would be worth a try.
We will try switching the ethernet port on the radio. We also noticed long startup times on the radio. On the typical startup, the radio would boot and light would come on normally, then the lights would go off then start acting like it is rebooting which confused many of us.
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 16:46.

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