mirror of
https://github.com/PhotonVision/photonvision
synced 2026-07-03 03:01:40 +00:00
Switch from RST to MyST Markdown (#1395)
This commit is contained in:
Mohammad Durrani
@@ -1,49 +1,39 @@
|
||||
Camera Troubleshooting
|
||||
======================
|
||||
# Camera Troubleshooting
|
||||
|
||||
Pi Cameras
|
||||
----------
|
||||
## Pi Cameras
|
||||
|
||||
If you haven't yet, please refer to :ref:`the Pi CSI Camera Configuration page <docs/hardware/picamconfig:Pi Camera Configuration>` for information on updating :code:`config.txt` for your use case. If you've tried that, and things still aren't working, restart PhotonVision using the restart button in the settings tab, and press tilde (\`) in the web UI once connection is restored. This should show the most recent boot log.
|
||||
If you haven't yet, please refer to {ref}`the Pi CSI Camera Configuration page <docs/hardware/picamconfig:Pi Camera Configuration>` for information on updating {code}`config.txt` for your use case. If you've tried that, and things still aren't working, restart PhotonVision using the restart button in the settings tab, and press tilde (\`) in the web UI once connection is restored. This should show the most recent boot log.
|
||||
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| | Expected output | Bad |
|
||||
+==================================+========================================================+====================================+
|
||||
| LibCamera driver initialization | Successfully loaded libpicam shared object | Failed to load native libraries! |
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| Camera detected | Adding local video device - "unicam" at "/dev/video0" | No output from VisionSourceManager |
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| VisionSource created | Adding 1 configs to VMM. | No output from VisionSourceManager |
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| | Expected output | Bad |
|
||||
| ------------------------------- | ----------------------------------------------------- | ---------------------------------- |
|
||||
| LibCamera driver initialization | Successfully loaded libpicam shared object | Failed to load native libraries! |
|
||||
| Camera detected | Adding local video device - "unicam" at "/dev/video0" | No output from VisionSourceManager |
|
||||
| VisionSource created | Adding 1 configs to VMM. | No output from VisionSourceManager |
|
||||
|
||||
If the driver isn't loaded, you may be using a non-official Pi image, or an image not new enough. Try updating to the most recent image available (one released for 2023) -- if that doesn't resolve the problem, :ref:`contact us<index:Contact Us>` with your settings ZIP file and Pi version/camera version/config.txt file used.
|
||||
If the driver isn't loaded, you may be using a non-official Pi image, or an image not new enough. Try updating to the most recent image available (one released for 2023) -- if that doesn't resolve the problem, {ref}`contact us<index:Contact Us>` with your settings ZIP file and Pi version/camera version/config.txt file used.
|
||||
|
||||
If the camera is not detected, the most likely cause is either a config.txt file incorrectly set-up, or a ribbon cable attached backwards. Review the :ref:`picam configuration page <docs/hardware/picamconfig:pi camera configuration>`, and verify the ribbon cable is properly oriented at both ends, and that it is _fully_ inserted into the FFC connector. Then, :ref:`contact us<index:Contact Us>` with your settings ZIP file and Pi version/camera version/config.txt file used.
|
||||
If the camera is not detected, the most likely cause is either a config.txt file incorrectly set-up, or a ribbon cable attached backwards. Review the {ref}`picam configuration page <docs/hardware/picamconfig:pi camera configuration>`, and verify the ribbon cable is properly oriented at both ends, and that it is \_fully\_ inserted into the FFC connector. Then, {ref}`contact us<index:Contact Us>` with your settings ZIP file and Pi version/camera version/config.txt file used.
|
||||
|
||||
USB cameras
|
||||
-----------
|
||||
## USB cameras
|
||||
|
||||
USB cameras supported by CSCore require no libcamera driver initialization to work -- however, similar troubleshooting steps apply. Restart PhotonVision using the restart button in the settings tab, and press tilde on your keyboard (\`) when you're in the web UI once connection is restored. We expect to see the following output:
|
||||
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| | Expected output | Bad |
|
||||
+==================================+========================================================+====================================+
|
||||
| Camera detected | Adding local video device - "foobar" at "/dev/foobar" | No output from VisionSourceManager |
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| VisionSource created | Adding 1 configs to VMM. | No output from VisionSourceManager |
|
||||
+----------------------------------+--------------------------------------------------------+------------------------------------+
|
||||
| | Expected output | Bad |
|
||||
| -------------------- | ----------------------------------------------------- | ---------------------------------- |
|
||||
| Camera detected | Adding local video device - "foobar" at "/dev/foobar" | No output from VisionSourceManager |
|
||||
| VisionSource created | Adding 1 configs to VMM. | No output from VisionSourceManager |
|
||||
|
||||
Determining detected cameras in Video4Linux (v4l2)
|
||||
--------------------------------------------------
|
||||
## Determining detected cameras in Video4Linux (v4l2)
|
||||
|
||||
On Linux devices (including Raspberry Pi), PhotonVision uses WPILib's CSCore to interact with video devices, which internally uses Video4Linux (v4l2). CSCore, and therefore Photon, requires that cameras attached have good v4l drivers for proper functionality. These should be built into the Linux kernel, and do not need to be installed manually. Valid picamera setup (from /boot/config.txt) can also be determined using these steps. The list-devices command will show all valid video devices detected, and list-formats the list of "video modes" each camera can be in.
|
||||
|
||||
- For picams: edit the config.txt file as described in the :ref:`picam configuration page <docs/hardware/picamconfig:pi camera configuration>`
|
||||
- SSH into your Pi: :code:`ssh pi@photonvision.local` and enter the username "pi" & password "raspberry"
|
||||
- run :code:`v4l2-ctl --list-devices` and :code:`v4l2-ctl --list-formats`
|
||||
- For picams: edit the config.txt file as described in the {ref}`picam configuration page <docs/hardware/picamconfig:pi camera configuration>`
|
||||
- SSH into your Pi: {code}`ssh pi@photonvision.local` and enter the username "pi" & password "raspberry"
|
||||
- run {code}`v4l2-ctl --list-devices` and {code}`v4l2-ctl --list-formats`
|
||||
|
||||
We expect an output similar to the following. For picameras, note the "unicam" entry with path :code:`platform:3f801000.csi` (if we don't see this, that's bad), and a huge list of valid video formats. USB cameras should show up similarly in the output of these commands.
|
||||
We expect an output similar to the following. For picameras, note the "unicam" entry with path {code}`platform:3f801000.csi` (if we don't see this, that's bad), and a huge list of valid video formats. USB cameras should show up similarly in the output of these commands.
|
||||
|
||||
```{eval-rst}
|
||||
.. tab-set::
|
||||
.. tab-item:: Working
|
||||
|
||||
@@ -115,3 +105,4 @@ We expect an output similar to the following. For picameras, note the "unicam" e
|
||||
/dev/video19
|
||||
/dev/media2
|
||||
Cannot open device /dev/video0, exiting.
|
||||
```
|
||||
@@ -1,69 +1,63 @@
|
||||
Common Issues / Questions
|
||||
=========================
|
||||
# Common Issues / Questions
|
||||
|
||||
This page will grow as needed in order to cover commonly seen issues by teams. If this page doesn't help you and you need further assistance, feel free to :ref:`Contact Us<index:Contact Us>`.
|
||||
This page will grow as needed in order to cover commonly seen issues by teams. If this page doesn't help you and you need further assistance, feel free to {ref}`Contact Us<index:Contact Us>`.
|
||||
|
||||
Known Issues
|
||||
------------
|
||||
All known issues can be found on our `GitHub page <https://github.com/PhotonVision/photonvision/issues>`_.
|
||||
## Known Issues
|
||||
|
||||
PS3Eye
|
||||
^^^^^^
|
||||
Due to an issue with Linux kernels, the drivers for the PS3Eye are no longer supported. If you would still like to use the PS3Eye, you can downgrade your kernel with the following command: ``sudo CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt rpi-update 866751bfd023e72bd96a8225cf567e03c334ecc4``. Note: You must be connected to the internet to run the command.
|
||||
All known issues can be found on our [GitHub page](https://github.com/PhotonVision/photonvision/issues).
|
||||
|
||||
LED Control
|
||||
^^^^^^^^^^^
|
||||
### PS3Eye
|
||||
|
||||
Due to an issue with Linux kernels, the drivers for the PS3Eye are no longer supported. If you would still like to use the PS3Eye, you can downgrade your kernel with the following command: `sudo CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt rpi-update 866751bfd023e72bd96a8225cf567e03c334ecc4`. Note: You must be connected to the internet to run the command.
|
||||
|
||||
### LED Control
|
||||
|
||||
The logic for controlling LED mode when `multiple cameras are connected` is not fully fleshed out. In its current state, LED control is only enabled when a Pi Camera Module is not in driver mode—meaning a USB camera on its own is unable to control the LEDs.
|
||||
|
||||
For now, if you are using multiple cameras, it is recommended that teams set the value of the NetworkTables entry :code:`photonvision/ledMode` from the robot code to control LED state.
|
||||
For now, if you are using multiple cameras, it is recommended that teams set the value of the NetworkTables entry {code}`photonvision/ledMode` from the robot code to control LED state.
|
||||
|
||||
Commonly Seen Issues
|
||||
--------------------
|
||||
## Commonly Seen Issues
|
||||
|
||||
### Networking Issues
|
||||
|
||||
Networking Issues
|
||||
^^^^^^^^^^^^^^^^^
|
||||
Please refer to our comprehensive {ref}`networking troubleshooting tips <docs/troubleshooting/networking-troubleshooting:Networking Troubleshooting>` for debugging suggestions and possible causes.
|
||||
|
||||
Please refer to our comprehensive :ref:`networking troubleshooting tips <docs/troubleshooting/networking-troubleshooting:Networking Troubleshooting>` for debugging suggestions and possible causes.
|
||||
### Camera won't show up
|
||||
|
||||
Camera won't show up
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
Try these steps to :ref:`troubleshoot your camera connection <docs/troubleshooting/camera-troubleshooting:Camera Troubleshooting>`.
|
||||
Try these steps to {ref}`troubleshoot your camera connection <docs/troubleshooting/camera-troubleshooting:Camera Troubleshooting>`.
|
||||
|
||||
If you are using a USB camera, it is possible your USB Camera isn't supported by CSCore and therefore won't work with PhotonVision. See :ref:`supported hardware page for more information <docs/hardware/selecting-hardware:Recommended Cameras>`, or the above Camera Troubleshooting page for more information on determining this locally.
|
||||
If you are using a USB camera, it is possible your USB Camera isn't supported by CSCore and therefore won't work with PhotonVision. See {ref}`supported hardware page for more information <docs/hardware/selecting-hardware:Recommended Cameras>`, or the above Camera Troubleshooting page for more information on determining this locally.
|
||||
|
||||
Camera is consistently returning incorrect values when in 3D mode
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Read the tips on the :ref:`camera calibration page<docs/calibration/calibration:Calibration Tips>`, follow the advice there, and redo the calibration.
|
||||
### Camera is consistently returning incorrect values when in 3D mode
|
||||
|
||||
Not getting data from PhotonLib
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Read the tips on the {ref}`camera calibration page<docs/calibration/calibration:Calibration Tips>`, follow the advice there, and redo the calibration.
|
||||
|
||||
### Not getting data from PhotonLib
|
||||
|
||||
1. Ensure your coprocessor version and PhotonLib version match. This can be checked by the settings tab and examining the .json itself (respectively).
|
||||
|
||||
2. Ensure that you have your team number set properly.
|
||||
|
||||
3. Use Glass to verify that PhotonVision has connected to the NetworkTables server served by your robot. With Glass connected in client mode to your RoboRIO, we expect to see "photonvision" listed under the Clients tab of the NetworkTables Info pane.
|
||||
|
||||
.. image:: images/glass-connections.png
|
||||
:width: 600
|
||||
:alt: Using Glass to check NT connections
|
||||
```{image} images/glass-connections.png
|
||||
:alt: Using Glass to check NT connections
|
||||
:width: 600
|
||||
```
|
||||
|
||||
4. When creating a `PhotonCamera` in code, does the `cameraName` provided match the name in the upper-right card of the web interface? Glass can be used to verify the RoboRIO is receiving NetworkTables data by inspecting the `photonvision` subtable for your camera nickname.
|
||||
|
||||
.. image:: images/camera-subtable.png
|
||||
:width: 600
|
||||
:alt: Using Glass to check camera publishing
|
||||
```{image} images/camera-subtable.png
|
||||
:alt: Using Glass to check camera publishing
|
||||
:width: 600
|
||||
```
|
||||
|
||||
### Unable to download PhotonLib
|
||||
|
||||
Unable to download PhotonLib
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Ensure all of your network firewalls are disabled and you aren't on a school-network.
|
||||
|
||||
PhotonVision prompts for login on startup
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
This is normal. You don't need to connect a display to your Raspberry Pi to use PhotonVision, just navigate to the relevant webpage (ex. ``photonvision.local:5800``) in order to see the dashboard.
|
||||
### PhotonVision prompts for login on startup
|
||||
|
||||
This is normal. You don't need to connect a display to your Raspberry Pi to use PhotonVision, just navigate to the relevant webpage (ex. `photonvision.local:5800`) in order to see the dashboard.
|
||||
|
||||
### Raspberry Pi enters into boot looping state when using PhotonVision
|
||||
|
||||
Raspberry Pi enters into boot looping state when using PhotonVision
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
This is most commonly seen when your Pi doesn't have adequate power / is being undervolted. Ensure that your power supply is functioning properly.
|
||||
10
docs/source/docs/troubleshooting/index.md
Normal file
10
docs/source/docs/troubleshooting/index.md
Normal file
@@ -0,0 +1,10 @@
|
||||
# Troubleshooting
|
||||
|
||||
```{toctree}
|
||||
:maxdepth: 1
|
||||
|
||||
common-errors
|
||||
logging
|
||||
camera-troubleshooting
|
||||
networking-troubleshooting
|
||||
```
|
||||
@@ -1,10 +0,0 @@
|
||||
Troubleshooting
|
||||
================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
common-errors
|
||||
logging
|
||||
camera-troubleshooting
|
||||
networking-troubleshooting
|
||||
22
docs/source/docs/troubleshooting/logging.md
Normal file
22
docs/source/docs/troubleshooting/logging.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# Logging
|
||||
|
||||
:::{note}
|
||||
Logging is very helpful when trying to debug issues within PhotonVision, as it allows us to see what is happening within the program after it is ran. Whenever reporting an issue to PhotonVision, we request that you include logs whenever possible.
|
||||
:::
|
||||
|
||||
In addition to storing logs in timestamped files in the config directory, PhotonVision streams logs to the web dashboard. These logs can be viewed later by pressing the \` key. In this view, logs can be filtered by level or downloaded.
|
||||
|
||||
:::{note}
|
||||
When the program first starts, it sends logs from startup to the client that first connects. This does not happen on subsequent connections.
|
||||
:::
|
||||
|
||||
:::{note}
|
||||
Logs are stored inside the {code}`photonvision_config/logs` directory. Exporting the settings ZIP will also download all old logs for further review.
|
||||
:::
|
||||
|
||||
```{raw} html
|
||||
<video width="85%" controls>
|
||||
<source src="../../_static/assets/logGui.mp4" type="video/mp4">
|
||||
Your browser does not support the video tag.
|
||||
</video>
|
||||
```
|
||||
@@ -1,17 +0,0 @@
|
||||
Logging
|
||||
=======
|
||||
|
||||
.. note:: Logging is very helpful when trying to debug issues within PhotonVision, as it allows us to see what is happening within the program after it is ran. Whenever reporting an issue to PhotonVision, we request that you include logs whenever possible.
|
||||
|
||||
In addition to storing logs in timestamped files in the config directory, PhotonVision streams logs to the web dashboard. These logs can be viewed later by pressing the \` key. In this view, logs can be filtered by level or downloaded.
|
||||
|
||||
.. note:: When the program first starts, it sends logs from startup to the client that first connects. This does not happen on subsequent connections.
|
||||
|
||||
.. note:: Logs are stored inside the :code:`photonvision_config/logs` directory. Exporting the settings ZIP will also download all old logs for further review.
|
||||
|
||||
.. raw:: html
|
||||
|
||||
<video width="85%" controls>
|
||||
<source src="../../_static/assets/logGui.mp4" type="video/mp4">
|
||||
Your browser does not support the video tag.
|
||||
</video>
|
||||
@@ -0,0 +1,47 @@
|
||||
# Networking Troubleshooting
|
||||
|
||||
Before reading further, ensure that you follow all the recommendations {ref}`in our networking section <docs/installation/networking:Physical Networking>`. You should follow these guidelines in order for PhotonVision to work properly; other networking setups are not officially supported.
|
||||
|
||||
## Checklist
|
||||
|
||||
A few issues make up the majority of support requests. Run through this checklist quickly to catch some common mistakes.
|
||||
|
||||
- Is your camera connected to the robot's radio through a {ref}`network switch <docs/installation/networking:Physical Networking>`?
|
||||
- Ethernet straight from a laptop to a coprocessor will not work (most likely), due to the unreliability of link-local connections.
|
||||
- Even if there's a switch between your laptop and coprocessor, you'll still want a radio or router in the loop somehow.
|
||||
- The FRC radio is the *only* router we will officially support due to the innumerable variations between routers.
|
||||
- (Raspberry Pi, Orange Pi & Limelight only) have you flashed the correct image, and is it up to date?
|
||||
- Limelights 2/2+ and Gloworms should be flashed using the Limelight 2 image (eg, `photonvision-v2024.2.8-linuxarm64_limelight2.img.xz`).
|
||||
- Limelights 3 should be flashed using the Limelight 3 image (eg, `photonvision-v2024.2.8-linuxarm64_limelight3.img.xz`).
|
||||
- Raspberry Pi devices (including Pi 3, Pi 4, CM3 and CM4) should be flashed using the Raspberry Pi image (eg, `photonvision-v2024.2.8-linuxarm64_RaspberryPi.img.xz`).
|
||||
- Orange Pi 5 devices should be flashed using the Orange Pi 5 image (eg, `photonvision-v2024.2.8-linuxarm64_orangepi5.img.xz`).
|
||||
- Orange Pi 5+ devices should be flashed using the Orange Pi 5+ image (eg, `photonvision-v2024.2.8-linuxarm64_orangepi5plus.img.xz`).
|
||||
- Is your robot code using a **2024** version of WPILib, and is your coprocessor using the most up to date **2024** release?
|
||||
- 2022, 2023 and 2024 versions of either cannot be mix-and-matched!
|
||||
- Your PhotonVision version can be checked on the {ref}`settings tab<docs/settings:settings>`.
|
||||
- Is your team number correctly set on the {ref}`settings tab<docs/settings:settings>`?
|
||||
|
||||
### photonvision.local Not Found
|
||||
|
||||
Use [Angry IP Scanner](https://angryip.org/) and look for an IP that has port 5800 open. Then go to your web browser and do \<IP ADDRESS>:5800.
|
||||
|
||||
Alternatively, you can plug your coprocessor into a display, plug in a keyboard, and run `hostname -I` in the terminal. This should give you the IP Address of your coprocessor, then go to your web browser and do \<IP ADDRESS>:5800.
|
||||
|
||||
If nothing shows up, ensure your coprocessor has power, and you are following all of our networking recommendations, feel free to {ref}`contact us <index:contact us>` and we will help you.
|
||||
|
||||
### Can't Connect To Robot
|
||||
|
||||
Please check that:
|
||||
1\. You don't have the NetworkTables Server on (toggleable in the settings tab). Turn this off when doing work on a robot.
|
||||
2\. You have your team number set properly in the settings tab.
|
||||
3\. Your camera name in the `PhotonCamera` constructor matches the name in the UI.
|
||||
4\. You are using the 2024 version of WPILib and RoboRIO image.
|
||||
5\. Your robot is on.
|
||||
|
||||
If all of the above are met and you still have issues, feel free to {ref}`contact us <index:contact us>` and provide the following information:
|
||||
|
||||
- The WPILib version used by your robot code
|
||||
- PhotonLib vendor dependency version
|
||||
- PhotonVision version (from the UI)
|
||||
- Your settings exported from your coprocessor (if you're able to access it)
|
||||
- How your RoboRIO/coprocessor are networked together
|
||||
@@ -1,53 +0,0 @@
|
||||
Networking Troubleshooting
|
||||
==========================
|
||||
|
||||
Before reading further, ensure that you follow all the recommendations :ref:`in our networking section <docs/installation/networking:Physical Networking>`. You should follow these guidelines in order for PhotonVision to work properly; other networking setups are not officially supported.
|
||||
|
||||
|
||||
Checklist
|
||||
^^^^^^^^^
|
||||
|
||||
A few issues make up the majority of support requests. Run through this checklist quickly to catch some common mistakes.
|
||||
|
||||
- Is your camera connected to the robot's radio through a :ref:`network switch <docs/installation/networking:Physical Networking>`?
|
||||
- Ethernet straight from a laptop to a coprocessor will not work (most likely), due to the unreliability of link-local connections.
|
||||
- Even if there's a switch between your laptop and coprocessor, you'll still want a radio or router in the loop somehow.
|
||||
- The FRC radio is the *only* router we will officially support due to the innumerable variations between routers.
|
||||
- (Raspberry Pi, Orange Pi & Limelight only) have you flashed the correct image, and is it up to date?
|
||||
- Limelights 2/2+ and Gloworms should be flashed using the Limelight 2 image (eg, `photonvision-v2024.2.8-linuxarm64_limelight2.img.xz`).
|
||||
- Limelights 3 should be flashed using the Limelight 3 image (eg, `photonvision-v2024.2.8-linuxarm64_limelight3.img.xz`).
|
||||
- Raspberry Pi devices (including Pi 3, Pi 4, CM3 and CM4) should be flashed using the Raspberry Pi image (eg, `photonvision-v2024.2.8-linuxarm64_RaspberryPi.img.xz`).
|
||||
- Orange Pi 5 devices should be flashed using the Orange Pi 5 image (eg, `photonvision-v2024.2.8-linuxarm64_orangepi5.img.xz`).
|
||||
- Orange Pi 5+ devices should be flashed using the Orange Pi 5+ image (eg, `photonvision-v2024.2.8-linuxarm64_orangepi5plus.img.xz`).
|
||||
- Is your robot code using a **2024** version of WPILib, and is your coprocessor using the most up to date **2024** release?
|
||||
- 2022, 2023 and 2024 versions of either cannot be mix-and-matched!
|
||||
- Your PhotonVision version can be checked on the :ref:`settings tab<docs/settings:settings>`.
|
||||
- Is your team number correctly set on the :ref:`settings tab<docs/settings:settings>`?
|
||||
|
||||
|
||||
photonvision.local Not Found
|
||||
----------------------------
|
||||
|
||||
Use `Angry IP Scanner <https://angryip.org/>`_ and look for an IP that has port 5800 open. Then go to your web browser and do <IP ADDRESS>:5800.
|
||||
|
||||
Alternatively, you can plug your coprocessor into a display, plug in a keyboard, and run ``hostname -I`` in the terminal. This should give you the IP Address of your coprocessor, then go to your web browser and do <IP ADDRESS>:5800.
|
||||
|
||||
If nothing shows up, ensure your coprocessor has power, and you are following all of our networking recommendations, feel free to :ref:`contact us <index:contact us>` and we will help you.
|
||||
|
||||
Can't Connect To Robot
|
||||
----------------------
|
||||
|
||||
Please check that:
|
||||
1. You don't have the NetworkTables Server on (toggleable in the settings tab). Turn this off when doing work on a robot.
|
||||
2. You have your team number set properly in the settings tab.
|
||||
3. Your camera name in the ``PhotonCamera`` constructor matches the name in the UI.
|
||||
4. You are using the 2024 version of WPILib and RoboRIO image.
|
||||
5. Your robot is on.
|
||||
|
||||
If all of the above are met and you still have issues, feel free to :ref:`contact us <index:contact us>` and provide the following information:
|
||||
|
||||
- The WPILib version used by your robot code
|
||||
- PhotonLib vendor dependency version
|
||||
- PhotonVision version (from the UI)
|
||||
- Your settings exported from your coprocessor (if you're able to access it)
|
||||
- How your RoboRIO/coprocessor are networked together
|
||||
Reference in New Issue
Block a user