remove LED and GPIO support

Author: samfreund

docs/source/docs/additional-resources/config.md

@@ -22,8 +22,6 @@ The directory structure is outlined below.
   - Contains images saved with the input/output save commands.
 - logs
   - Contains timestamped logs in the format {code}`photonvision-YYYY-MM-D_HH-MM-SS.log`. These timestamps will likely be significantly behind the real time. Coprocessors on the robot have no way to get current time.
-- hardwareSettings.json
-  - Contains hardware settings. Currently this includes only the LED brightness.
 - networkSettings.json
   - Contains network settings, including team number (or remote network tables address), static/dynamic settings, and hostname.
 
@@ -45,7 +43,6 @@ A variety of files can be imported back into PhotonVision:
 - Single Config File
   - Currently-supported Files
     - {code}`hardwareConfig.json`
-    - {code}`hardwareSettings.json`
     - {code}`networkSettings.json`
   - Useful for simple hardware or network configuration tasks without overwriting all settings.
 

docs/source/docs/additional-resources/nt-api.md

@@ -54,17 +54,3 @@ Images are returned as part of the .zip package from the "Export" operation in t
 :::{warning}
 If you manage to make calls to these commands faster than 500ms (between calls), additional photos will not be captured.
 :::
-
-### Global Entries
-
-These entries are global, meaning that they should be called on the main `photonvision` table.
-
-| Key       | Type  | Description                                              |
-| --------- | ----- | -------------------------------------------------------- |
-| `ledMode` | `int` | Sets the LED Mode (-1: default, 0: off, 1: on, 2: blink) |
-
-:::{warning}
-Setting the LED mode to -1 (default) when `multiple` cameras are connected may result in unexpected behavior. {ref}`This is a known limitation of PhotonVision. <docs/troubleshooting/common-errors:LED Control>`
-
-Single camera operation should work without issue.
-:::

docs/source/docs/advanced-installation/sw_install/files/Limelight2+/hardwareConfig.json

@@ -1,9 +1,5 @@
 {
   "deviceName" : "Limelight 2+",
   "supportURL" : "https://limelightvision.io",
-  "ledPins" : [ 13, 18 ],
-  "ledsCanDim" : true,
-  "ledPWMRange" : [ 0, 100 ],
-  "ledPWMFrequency" : 30000,
   "vendorFOV" : 75.76079874010732
 }

docs/source/docs/advanced-installation/sw_install/files/Limelight2/hardwareConfig.json

@@ -1,7 +1,5 @@
 {
   "deviceName" : "Limelight 2",
   "supportURL" : "https://limelightvision.io",
-  "ledPins" : [ 17, 18 ],
-  "ledsCanDim" : false,
   "vendorFOV" : 75.76079874010732
 }

docs/source/docs/hardware/customhardware.md

@@ -2,35 +2,10 @@
 
 ## Configuration
 
-By default, PhotonVision attempts to make minimal assumptions of the hardware it runs on. However, it may be configured to enable custom LED control, branding, and other functionality.
+By default, PhotonVision attempts to make minimal assumptions of the hardware it runs on. However, it may be configured to enable branding and other functionality.
 
 `hardwareConfig.json` is the location for this configuration. It is included when settings are exported, and can be uploaded as part of a .zip, or on its own.
 
-## LED Support
-
-For Raspberry-Pi based hardware, PhotonVision can use [PiGPIO](https://abyz.me.uk/rpi/pigpio/) to control IO pins. The mapping of which pins control which LED's is part of the hardware config. The pins are active-high: set high when LED's are commanded on, and set low when commanded off.
-
-```{eval-rst}
-.. tab-set-code::
-   .. code-block:: json
-
-      {
-        "ledPins" : [ 13 ],
-        "ledSetCommand" : "",
-        "ledsCanDim" : true,
-        "ledPWMRange" : [ 0, 100 ],
-        "ledPWMSetRange" : "",
-        "ledPWMFrequency" : 0,
-        "ledDimCommand" : "",
-        "ledBlinkCommand" : "",
-        "statusRGBPins" : [ ],
-      }
-```
-
-:::{note}
-No hardware boards with status RGB LED pins or non-dimming LED's have been tested yet. Please reach out to the development team if these features are desired, they can assist with configuration and testing.
-:::
-
 ## Hardware Interaction Commands
 
 For Non-Raspberry-Pi hardware, users must provide valid hardware-specific commands for some parts of the UI interaction (including performance metrics, and executing system restarts).
@@ -100,15 +75,6 @@ Here is a complete example `hardwareConfig.json`:
         "deviceName" : "Blinky McBlinkface",
         "deviceLogoPath" : "",
         "supportURL" : "https://www.youtube.com/watch?v=b-CvLWbfZhU",
-        "ledPins" : [2, 13],
-        "ledSetCommand" : "",
-        "ledsCanDim" : true,
-        "ledPWMRange" : [ 0, 100 ],
-        "ledPWMSetRange" : "",
-        "ledPWMFrequency" : 0,
-        "ledDimCommand" : "",
-        "ledBlinkCommand" : "",
-        "statusRGBPins" : [ ],
         "cpuTempCommand" : "",
         "cpuMemoryCommand" : "",
         "cpuUtilCommand" : "",

docs/source/docs/programming/photonlib/controlling-led.md

@@ -8,5 +8,4 @@ getting-target-data
 using-target-data
 robot-pose-estimator
 driver-mode-pipeline-index
-controlling-led
 ```

docs/source/docs/programming/photonlib/index.md

@@ -10,12 +10,6 @@ All known issues can be found on our [GitHub page](https://github.com/PhotonVisi
 
 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.
-
 ## Commonly Seen Issues
 
 ### Networking Issues

docs/source/docs/troubleshooting/common-errors.md

@@ -133,7 +133,6 @@ const openExportSettingsPrompt = () => {
 enum ImportType {
   AllSettings,
   HardwareConfig,
-  HardwareSettings,
   NetworkConfig,
   ApriltagFieldLayout
 }
@@ -151,9 +150,6 @@ const handleSettingsImport = () => {
     case ImportType.HardwareConfig:
       settingsEndpoint = "/hardwareConfig";
       break;
-    case ImportType.HardwareSettings:
-      settingsEndpoint = "/hardwareSettings";
-      break;
     case ImportType.NetworkConfig:
       settingsEndpoint = "/networkConfig";
       break;