View Single Post
  #8   Spotlight this post!  
Unread 21-02-2015, 09:04
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,751
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: Static IP from .2 to .20?

No need to apologize.

The dashboard relies on the DS to learn what the robot IP address is. It seemed like a good idea to not have the DB and DS looking at different robots. The notifier is necessary because the binding otherwise won't return. Storing the value in a local or global in the top loop or the third loop is a fine way to notify the rest of the DB of the robot IP.

So the way the IP sharing is supposed to work is for the robot IP and camera IP to be sent to the DB over TCP. The error handling for the DB TCP connection wasn't as good as it should have been, so I've seen some issues where the connection simply doesn't exist. The update last week corrected the known issues. PM me when you have access to the code, as I can tell you how to debug and improve it.

Greg McKaskle