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
Describe the bug
We are running PhotonVision on Limelight 3 and 3G and have been having this problem occasionally for a while now. The camera can be found on Angry IP Scanner at the set static IP, but when we try to connect to the camera in browser at 10.TE.AM.XX:5800 we are not able to do so. The browser says "Unable to connect to [IP]".
To Reproduce
I have no clue. There isn't really a consistent way to make this happen or not happen, which makes this even more confusing to us.
Platform:
Hardware: Limelight 3 and 3G
Network Configuration: RoboRIO to network switch to Limelight
PhotonVision Version: 2025.1.1
Browser: Firefox 135, also tried on Google Chrome and also cannot connect
Additional context
We are able to ping the camera with 'ping ...' in terminal. We can also connect to it via SSH and I did not notice anything wrong.
Sometimes, the problem goes away by power cycling the robot, and always goes away by reimaging. However, it comes back after some time.
We are very confused on the source of the problem, especially as I have not found any one else with this problem. Thank you!
The text was updated successfully, but these errors were encountered:
Describe the bug
We are running PhotonVision on Limelight 3 and 3G and have been having this problem occasionally for a while now. The camera can be found on Angry IP Scanner at the set static IP, but when we try to connect to the camera in browser at 10.TE.AM.XX:5800 we are not able to do so. The browser says "Unable to connect to [IP]".
To Reproduce
I have no clue. There isn't really a consistent way to make this happen or not happen, which makes this even more confusing to us.
Platform:
Additional context
We are able to ping the camera with 'ping ...' in terminal. We can also connect to it via SSH and I did not notice anything wrong.
Sometimes, the problem goes away by power cycling the robot, and always goes away by reimaging. However, it comes back after some time.
We are very confused on the source of the problem, especially as I have not found any one else with this problem. Thank you!
The text was updated successfully, but these errors were encountered: