Skip to content
This repository was archived by the owner on Jul 16, 2024. It is now read-only.

Commit 5f5097d

Browse files
Update
1 parent 85729b9 commit 5f5097d

File tree

10 files changed

+48
-11
lines changed

10 files changed

+48
-11
lines changed
202 KB
Loading

source/docs/getting-started/installation/wiring.rst

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,13 @@ Coprocessor without Passive POE
2828
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2929
1a. Option 1: Get a micro USB (may be USB-C if using a newer Pi) to USB-A cable and plug the USB A side into a regulator like `this <https://www.amazon.com/KNACRO-Voltage-Regulator-Converter-Module/dp/B01HM12N2C/ref=sr_1_2>`_. Then, wire the regulator into your PDP/PDB and the Micro USB / USB C into your coprocessor.
3030

31-
1b. Option 2: Use a USB power bank to power your coprocessor. Refer to this year's robot rulebook on legal implementations of this.
31+
.. note:: Raspberry Pi 5 may need a higher current power supply like the one in option 1b.
32+
33+
1b. Option 2: Get a DC regulator like `this<https://www.amazon.com/UCTRONICS-Converter-Transformer-Voltage-Regulator/dp/B07XXWQ49N/>` and use two wires to the ground and 5v gpio pins on the PI.
34+
35+
.. image:: images/gpiopinout.jpg
36+
37+
1c. Option 3: Use a USB power bank to power your coprocessor. Refer to this year's robot rulebook on legal implementations of this.
3238

3339
1. Run an ethernet cable from your Pi to your network switch / radio (we *STRONGLY* recommend the usage of a network switch, see the networking section for more info.)
3440

source/docs/hardware/images/pi4.png

1.04 MB
Loading
14.6 KB
Loading

source/docs/hardware/images/pi5.png

422 KB
Loading
91.1 KB
Loading

source/docs/hardware/index.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ Hardware
55
:maxdepth: 2
66

77
supportedhardware
8+
picamerawiring
89
picamconfig
910
customhardware
1011
config

source/docs/hardware/picamconfig.rst

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The GPU is not always capable of detecting other cameras automatically. The file
1313
Updating ``config.txt``
1414
-----------------------
1515

16-
After flashing the pi image onto an SD card, open the ``boot`` segment in a file browser.
16+
After flashing the Pi image onto an SD card, open the ``boot`` segment in a file browser.
1717

1818
.. note:: Windows may report "There is a problem with this drive". This should be ignored.
1919

@@ -33,13 +33,17 @@ Within the file, find this block of text:
3333
### IMX290/327/OV9281/Any other cameras that require additional overlays:
3434
### Comment out (add a # ) to camera_auto_detect=1, and uncomment the line for
3535
### the sensor you're trying to user
36+
### On devices with multiple CSI cameras like the CM4 and Pi 5 you will need to
37+
### declare which port each camera is plugged into (assuming your not using
38+
### autodetect). Remove the # before ",cam0" to define if a camera is plugged into
39+
### csi0. The config automatically assumes no port definition to be CSI1.
3640
3741
cameraAutoDetect=1
3842
39-
# dtoverlay=imx290,clock-frequency=74250000
40-
# dtoverlay=imx290,clock-frequency=37125000
41-
# dtoverlay=imx378
42-
# dtoverlay=ov9281
43+
# dtoverlay=imx290,clock-frequency=74250000#,cam0
44+
# dtoverlay=imx290,clock-frequency=37125000#,cam0
45+
# dtoverlay=imx378#,cam0
46+
# dtoverlay=ov9281#,cam0
4347
4448
##############################################################
4549
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
Pi Camera Wiring
2+
=======================
3+
4+
Background
5+
----------
6+
7+
The Raspberry Pi boards feature dedicated CSI ports (1 on Pi 3 and 4, while Pi 5 and CM4 have two), which is a ribbon cable connector designed for connecting a camera module to the Raspberry Pi. This port allows users to attach a compatible camera and leverage its capabilities for various applications, such as image and video capture, computer vision projects, and more.
8+
9+
.. warning:: Incorrect camera connection may not work or cause damage to the board or camera.
10+
.. warning:: Long ribbon cables are not recommended for use in FRC as they are very fragile and may be susceptible to noise.
11+
12+
Pi 3 and 4
13+
-----------------------
14+
15+
The Raspberry Pi 3 and 4 both have a single 15 pin CSI camera port.
16+
17+
.. image:: images/pi4.png
18+
.. image:: images/pi4cable.png
19+
20+
Pi 5
21+
-----------------------
22+
23+
The Raspberry Pi 5 has two much smaller 22 pin CSI camera port.
24+
25+
.. image:: images/pi5.png
26+
.. image:: images/pi5cable.png

source/docs/hardware/supportedhardware.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Pi cameras are always recommended over USB cameras as they have lower latency an
1616

1717
* The V1 is strongly preferred over the V2 due to the V2 having undesirable FOV choices
1818

19-
* `Innomaker OV9281 Global Shutter Camera <https://www.amazon.com/Raspberry-External-Monochrome-Bullseye-libcamera/dp/B09WTP5GZH>`_ (AprilTag Tracking)
19+
* `Innomaker OV9281 Global Shutter Camera <https://www.amazon.com/Raspberry-External-Monochrome-Bullseye-libcamera/dp/B09WTP5GZH>`_ (AprilTag Tracking) (Currently not supported on Pi 5)
2020

2121
.. note:: Note that there are many CSI based OV9281 cameras but this is the only one that has been tested by the development team.
2222

@@ -34,7 +34,7 @@ Pi cameras are always recommended over USB cameras as they have lower latency an
3434

3535
The following cameras / setups are known to not work:
3636

37-
* Using two of the same USB cameras does not currently work because it is hard to identify the two different cameras.
37+
* OV9281 on Pi 5 current does not work since tuning files dont exist from Raspberry Pi yet.
3838

3939
* Most Logitech cameras (specifically the Logitech C270 HD Webcam (PN: 960-000694)) will not work with PhotonVision.
4040

@@ -44,8 +44,8 @@ Pi cameras are always recommended over USB cameras as they have lower latency an
4444

4545
Supported Coprocessors
4646
----------------------
47-
* Raspberry Pi 3 / 4, with the newest variants of each being preferred (3B+ and B, respectively).
48-
* Raspberry Pi 4 is preferred for all forms of target tracking.
47+
* Raspberry Pi 3 / 4 / 5, with the newest variants of each being preferred (3B+ and B, respectively).
48+
* Raspberry Pi 4 is preferred for all forms of target tracking, Raspberry Pi 5 will have better preformance however has much less testing.
4949
* Orange Pi 4 / 5 will have better performance but will require more work to get working.
5050
* Mini PCs (such as Beelink N5095) have been testing and show significantly better performance than a Raspberry Pi, but require extra effort to wire to the robot / get set up. More information can be found in the set up guide `here. <https://docs.google.com/document/d/1lOSzG8iNE43cK-PgJDDzbwtf6ASyf4vbW8lQuFswxzw/edit?usp=drivesdk>`_
5151
* Other coprocessors can be used but may require some extra work / command line usage in order to get it working properly.
@@ -86,7 +86,7 @@ Support Levels
8686
* All features will work
8787
* Everything will be kept up to date
8888
- * Gloworm
89-
* Raspberry Pi 3 and Raspberry Pi 4 with the official Pi image with the Pi Cam or CSCore compatible USB Cameras
89+
* Raspberry Pi 3, 4, and 5 with the official Pi image with the Pi Cam or CSCore compatible USB Cameras
9090
* - Compatible
9191
- * No guarantee of support on Discord
9292
* Major features will work

0 commit comments

Comments
 (0)