Coming from match day 1, I’m noticing an issue where in queuing we turn on our robots to do some last minute diagnostics. This happens to also turn on our limelights.
Our limelights are running DHCP, and are pingable in the commandline and the splash pages are accessible via the browser.
However, when we change over to connecting directly to the field (probably a network change is going on), the camera stream is frozen, but the cameras themselves are pingable and accessible bis commandline and browser respectively. The workaround for us is to powercycle the robot on the field.
This causes panic and frustration. Is there anyway to restart the stream via command to the limelight? Unfortnately we haven’t wired an on/off switch for our individual cameras.
We were having this issue as well. We have static IP’s, but camera stream is frozen. We usually just do a check right before the match starts, but one time our robot lost comms during a match and restarted comms and our limelights weren’t streaming anymore. Weird issue, but we had no problems with our backup USB cams (MS lifecam 3000). We are using shuffleboard.
We are having a slightly different issue. We have the Limelight2 firmware 2019.4 and it is losing its static IP address. Problem Description:
Set static IP according to provided LL documentation
Limelight reboots - static IP still good
Power cycle robot
Limelight IP address resets to dynamic and we no longer know LL IP to communicate with it
Solution we are trying to work this morning is to set radio and rio to static IPs to see if that solves the problem. Other than that any ideas?
Yes, we manually change the LL IP according to your Best Practices post and LL documentation.
We will update to 19.5.1 here in a few minutes. We have set radio and rio to static IP as well but have not had a chance to test yet. Will update as soon as tests are run this afternoon.
Also, started a separate thread for this issue. Am going to paste your reply there for anyone else who might be seeing this.
We think we got it figured out. Last night when they were trying to set the LL static IP they were working through the rio. Today they switched it to setting up through the laptop and it seems to be keeping configuration at this point.