Has anyone ever had problems with Toggling their Limelight ON and OFF? We are writing a “1” to turn the LEDS off the the network tables and a “3” to turn the LEDS on in the network tables. This way the LEDS only come on when AIMING.
Occasionally, the LEDS will not turn on. This writing of the network tables happen in Periodic Task in a 20 msec loop I believe, we are using Labview.
Sometimes the LEDS won’t toggle on, we have to release the button which writes a “1” again then press the button to force another “3” write to the LEDS to come on.
During Teleop, this is not a problem because you can just release and press again quickly, however this happened once in Autonomous, where the LEDS did not come on.
Has anyone ever had some issues like this and what did you do to make it more robust?
A network switch fixed this for is, but created other issues. We are fighting those currently. We actually get this to work reliably, I’ll let you know.
For us, it seems the limelight completely loses connection. For a few seconds. By looping the “led on” command, we at least get the robot to take the shot eventually.
When I first started trying to setup our Limelight, I was having issues toggling leds as well. Not sure if it will work, but you can check out my code and see if it would help at all. Here is the visionCamera subsystem and here is an example of where I call the setLedOn command
So we have installed a 5-port switch now, and don’t have anything connected to radio port #2 anymore per both Limelight and the CD thread about it.
We have not noticed any problems with no limelight connect “yet”, but definitely the LEDS not toggling on when they are told to come on is a gremlin still.
We are looping the “turn on” command for the duration we want the light on, so it’s possible we aren’t ever seeing this gremlin because it’s so quickly corrected.
Unless anyone has a better solution, that may be a quick work-around.