Getting the Network Tables to work with an off loaded vision system

[Greg McKaskle]

The client name is just an identifier and is just for documenting which client is which. It shouldn't have any impact on a connection. If not provided, the IP address is formatted and used for the name.

The important parameter is the server IP. You either need to "know" this or have mDNS be able to find it using the name. You may want to install the nimdnsResponder or another mdns tool to help with this. I'm not sure if StrToIP node in LV will work for this situation. The server is the robot, by the way, and if that isn't present, the clients do not actually communicate to one another. They go into unsynchronized mode and should run locally at full speed. I'm not sure what is causing your vision code to run more slowly. Can you explain it?

Greg McKaskle

[aeastet]

Come to find out I only see the overload problem when the driver station is running and not connected to the robot. I was testing on a different computer so it did not have the correct team number in it for the RoboRio. It seemed that the driver station must have been blasting the RoboRio with data and slowing down all of the connections.. As sson as I closed the driver station I had vision running normally with or without the RoboRio.

[Greg McKaskle]

If the DS isn't connected to the roboRIO, it isn't directly basting it because it doesn't know who to blast. But it is making mDNS requests to find it every two seconds, and it may be pinging if you are on the diagnostic tab.

Greg McKaskle