Wiring the camera link
What you'll learn
- Why the camera board is connected by a one-way wire
- Why the pin labelled GND/R must not be used as ground
- How the camera board is powered in the tested setup, and what not to do
The camera board sends what it scans to the signer over a single wire. This step connects that wire and a shared ground. It’s the setup that was built and tested.
The wires
Section titled “The wires”Hover over, focus or tap a wire to see where it goes.
Schematic only: each board shows just the pins in use, not in their physical order. Always match the labels printed on your board. Dashed wires are not yet tested.
| From | To | Signal | Notes |
|---|---|---|---|
| ESP32-CAMGPIO14 (IO14) | ESP32 DevKitGPIO34 | One-way data | The only data wire between the boards. GPIO34 is input-only, so the DevKit can't send anything back. There is no wire from the DevKit to the CAM. |
| ESP32-CAMGND | ESP32 DevKitGND | Common ground | Required. Use the GND next to the CAM's 5V pin, never the pin labelled "GND/R", which is tied to reset on this board. |
| ESP32 DevKit5V / VIN | ESP32-CAM5V | Power (5V) | Not yet tested. Only for when the USB-TTL adapter is removed for good. Never connect two 5V supplies to the CAM at once. If the CAM browns out, use a separate 5V supply and keep GND shared. |
In the tested setup there are only two wires between the boards:
- Data: the camera board’s
GPIO14(labelledIO14) to the DevKit’sGPIO34. - Ground: a camera-board
GNDto a DevKitGND. A shared ground is required: without it, the data signal has nothing to be measured against.
The dashed wire (DevKit 5V to the camera board’s 5V) is not part of the tested setup. It’s described below.
Why there’s no wire back
Section titled “Why there’s no wire back”There is no wire from the DevKit to the camera board, and that’s deliberate. Data can only flow from the camera to the signer:
- The DevKit’s
GPIO34can only be an input. It can’t be switched to send anything. - The firmware assigns no transmit pin for the link.
So even if the signer’s firmware were wrong, it couldn’t send your keys or anything else to the camera board, which has a radio. See How it works for what the camera does with what it scans.
Don’t use the camera board’s GPIO1 or GPIO3 for the link: those carry its boot messages and are needed for flashing it. GPIO14 is free because the board’s SD card isn’t used.
Junk bytes are normal (the pull-up note)
Section titled “Junk bytes are normal (the pull-up note)”GPIO34 has no internal pull-up resistor, so its voltage floats whenever the camera board is off, in reset or starting up. The camera board’s GPIO14 also outputs a short burst at startup. Either way, the DevKit receives junk bytes. Its firmware checks every frame and throws them away, counted as “skipped”. That’s expected, not a fault.
Powering the camera board
Section titled “Powering the camera board”In the tested setup, the camera board is powered by the USB-TTL adapter, which also programs it. You’ll connect the adapter in the next step, when you flash the camera board. The DevKit’s 5V is not connected to the camera board. That keeps a single power supply on it, avoids drops on the DevKit’s USB supply (which also powers the shield’s backlight), and keeps the camera board ready for re-flashing.
Not yet tested: once the adapter is removed for good, the camera board can be powered from the DevKit’s 5V (or VIN), which is the dashed wire in the diagram. If the camera board then resets with “Brownout detector was triggered”, power it from a separate 5V supply instead, and keep the grounds connected.
Before you continue
Section titled “Before you continue”- One data wire: camera
GPIO14to DevKitGPIO34. - One ground wire, from the
GNDnext to the camera’s 5V pin, notGND/R. - No wire from the DevKit to the camera board, and no DevKit 5V to the camera board.