Thread: Getting the Network Tables to work with an off loaded vision system
View Single Post
  #2   Spotlight this post!  
Unread 02-02-2016, 15:40
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,748
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: Getting the Network Tables to work with an off loaded vision system
The Kangaroo would act as another client. Everyone that has access to network tables is a client except for the robot -- which is the server. This is, of course, assuming that they all have IP addresses on the same subnet and all clients know the server's IP.

One that is working, anyone can read and anyone can write. So I'd add writes to the kangaroo code. The dashboard is a completely separate client. There shouldn't be any need to modify it unless you also want it to show variable values written by the kangaroo. To get the SW running on the kangaroo, make sure that your EXE is built and set to autolaunch. By the way, I don't have one of these, so I'm making assumptions about how you generally have it setup.

Greg McKaskle
Reply With Quote