Posting this issue we had, and the solution, to help other teams that may experience similar:
Problem:
We were having a problem with network tables not being read or written by the limelight. We used old and new Rio image, limelight firmware, and FRC tools. Our Rio code writes the table, but no reaction from the limelight. The crazy thing is that this all worked last year.
Limelight - The crux of the problem is that network table is not being updated from the limelight. If we set values from our robot code (like LEDMode) we see this one entry show up in the shuffleboard variable display but no reaction from the limelight. Also we don’t see any values that the limelight is supposed to be updating actually being transferred to any network table. We are able to access the limelight in the web browser and manipulate the limelight to our heart content but nothing from our robot code. We have set team numbers in all our devices and we have no problem downloading software to run on the roborio and setting breakpoints. We have tried turning off all virus protection and firewalls. We are using static IPs for all devices… 10.2.63.11 is the limelight, 10.2.63.44 is the roborio, 10.2.63.10 is the driver station… all with mask 255.255.255.0. Gateway that was setup for all has been 10.2.63.1 but I am not sure how much that has to do when we are on a local switch. We are not yet using a radio…but rather connecting the roborio directly to a 5 port switch which the other 2 devices are connected to as well. We are really at a loss here as to what else to try. We just updated our roborio wplib to the latest tools 2022.2.1. We have also tried an old Limelight 1.0 as well as our newer Limelights 2+. The newer limelights have 2022.0.3 …we will be attempting 2022.1 tomorrow. Not seeing data update in shuffleboard from the limelight is the key to our problem. We have a disconnect between the network tables the limelight may be writing to and what we attempt to manipulate. Our limelight is configured with the name limelight-shooter and that is the way we reference it when attempting to get the default network table. We have also tried leaving the limelight configured with no name (i.e. remove shooter from the name) and reference with just limelight and we still have an issue.
Solution:
Solution provided by Limelight developer Brandon Hjelstrom. He provided the insight to assign 10.TE.AM.2 (the .2) as the IP address for the RoboRIO, and 10.TE.AM.11 to the Limelight. That resulted in the Limelight to interact with network tables. We also attached a 2nd Limelight as 10.TE.AM.22 and ran it simultaneously. All working well now. Somewhere along the way we must have forgotten this was necessary.