ESP32 Chicken Coop PCB

Thought for 3 sec

PCB thickness is chosen when ordering; it is not determined automatically by the schematic.

For this controller, select:

Finished PCB thickness: 1.6 mm
Copper weight: 1 oz
Layers: 2

1.6 mm is the common default and is strong enough for the ESP32 sockets, headers, and wiring. It also works with most ordinary mounting hardware and enclosures.

You can verify the selected thickness in three places:

The PCB manufacturer’s order form under PCB Thickness.
The manufacturer’s final order summary.
With digital calipers after receiving the board; a nominal 1.6 mm board may measure slightly above or below 1.6 mm because of manufacturing tolerance.

Do not confuse board thickness with copper thickness. “1 oz copper” is about 35 µm (0.035 mm) per copper layer.

hsac

Can you add me a couple screw holes? Use as small of an amount of ACU's as possible. Don't go rearranging the whole board just like 1-2 holes to pin it down will suffice in the already empty areas

Thought for 6 sec

flux

I’ll inspect the board once, place two small mounting holes in existing clear corners without moving components or traces, then run only the targeted clearance checks.

Worked for 1 min 16 sec

flux

Added two 3.2 mm non-plated mounting holes for M3 screws in the open lower-right area. No components or routing were moved, and the targeted clearance/edge checks are clean.

Export manufacturing files

Add mounting-hole labels

Check enclosure fit

Files

Schematic

Layout

3D View

R16

Resistance

1kohms

Resistance

1kohms

Resistance

10kohms

R15

Resistance

10kohms

R11

Resistance

1kohms

Resistance

330ohms

Resistance

10kohms

Resistance

10kohms

R14

Resistance

200 ohms

Resistance

1kohms

R10

Resistance

10kohms

Resistance

220 ohms

R13

Resistance

100kohms

Resistance

1kohms

R12

Resistance

100 ohms

Resistance

360ohms

Capacitance

100uF

Capacitance

100nF

Capacitance

100nF

Capacitance

10nF

Capacitance

100nF

Capacitance

10uF

J10

J11

J12

Block Diagram

System Architecture

Text
12V SUPPLY ──┬──> External L298N motor supply ──> 12V linear actuator (3A; internal end limits)
             └──> External 12V→5V buck (≥1A) ──> Controller 5V/VIN ──> DOIT ESP32 DevKit V1
                                                   │
                                                   └──> DevKit 3V3 accessory rail

ESP32 GPIO18/19/5 ──> L298N CLOSE/OPEN/PWM signal header (common GND)
ESP32 GPIO23/22 ──> red/green status LEDs
ESP32 GPIO32/33 <── manual OPEN/CLOSE buttons with external 10k pulldowns
ESP32 GPIO36 <── protected/filtered photoresistor divider
ESP32 GPIO39 <── protected 3.3V break-beam receiver
ESP32 GPIO21 ──> transistor-switched break-beam emitter power
ESP32 GPIO14 <── security-disable switch with defined bias

Functional Blocks and Sourcing Decisions

Table

Block	Reference classification	Decision
External power interfaces / filtering	None anticipated	From scratch; connector and passive protection network
ESP32 development-board interface	None anticipated	Use verified 2×15 headers / module if available; do not invent a footprint
External L298N interface	None anticipated	Signal/header interface only; motor current remains off-board
Manual controls and indicators	None anticipated	From scratch with generic passives and verified switches/LEDs/connectors
Outdoor photoresistor and break-beam	None anticipated	From scratch; protected cable interfaces and documented firmware polarity
Security-disable input	None anticipated	From scratch; defined 10k bias and explicit switch behavior

Placement Intent

Beginner-readable schematic organized by functional groups: power entry, ESP32 headers, motor-driver interface, user controls/LEDs, light sensor, break-beam, and security switch. Cross-block signals use explicit named nets; all returns join GND.

System Architecture
Functional Blocks and Sourcing Decisions
Placement Intent