You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team and I have been having connection issues on our Limelight 2+ and recently discovered the solution.
I'm sharing what worked for us in this issue to help other teams experiencing the same issue and to bring the issue to your attention.
Prerequisites
A fresh Limelight 2+ flashed with v2020.4 (hardware version may not matter)
roboRIO v1 flashed with the initial 2022 version
Open-Mesh router flashed with the initial 2022 version
You turn on your robot and observe that every component successfully starts.
The Limelight fans turn on, blinks its lights, etc.
Problem
The Limelight finder can't detect the device
limelight.local:5801 does not resolve
There are no Limelight entries in NetworkTables
Solution
Go to your roboRIO's configuration page at http://10.TE.AM.2
Set the IP to static (docs)
These instructions may not be applicable when at an FRC tournament
Power cycle Limelight, roboRIO, and router
The Limelight finder should now work
I'm not sure if this issue is caused by a misconfiguration on our part or if this is unexpected behavior from the Limelight.
The text was updated successfully, but these errors were encountered:
My team and I have been having connection issues on our Limelight 2+ and recently discovered the solution.
I'm sharing what worked for us in this issue to help other teams experiencing the same issue and to bring the issue to your attention.
Prerequisites
You turn on your robot and observe that every component successfully starts.
The Limelight fans turn on, blinks its lights, etc.
Problem
limelight.local:5801
does not resolveSolution
http://10.TE.AM.2
These instructions may not be applicable when at an FRC tournament
I'm not sure if this issue is caused by a misconfiguration on our part or if this is unexpected behavior from the Limelight.
The text was updated successfully, but these errors were encountered: