Project Idea Start
Image
Image
Thought for 37 sec
That identifies it: it’s a WEMOS D1 R32 V1.0.0, an Arduino Uno-form-factor ESP32 board. I’ll update the carrier design to use its shield-header pinout and mechanical pattern.
Worked for 2 mins 26 sec
The photos confirm your board is a WEMOS D1 R32 V1.0.0, using the Arduino Uno-style shield connector layout—not the current 38-pin ESP32 DevKit footprint.
The existing sensor-carrier schematic remains intact. The following update is still pending because no ACUs are currently available:
- Replace the ESP32 DevKit interface with D1 R32 shield headers
- Verify and remap the sensor GPIO connections
- Apply the Arduino Uno R3 mechanical header pattern
- Update the specification, firmware, and bring-up files
- Re-run ERC/connectivity checks
No partial replacement was made, so the current schematic has not been left broken.
Map sensor GPIOs
Find D1 R32 footprint
Show header pinout
Check pin conflicts
Update requirements
Refine this doc
Ask about this doc
Board Bring-Up Plan
- With modules removed, resistance-check 5V_PROTECTED and 3V3_RADAR to GND.
- Apply 5 V with a bench supply limited to 100 mA; verify no heating and power LED operation.
- Raise limit and verify 5V_PROTECTED, approximately 4.6–4.8 V after D2 at the ESP32 5V pin, and 3.30 V on 3V3_RADAR.
- Connect the laptop USB to the ESP32 with carrier power off; confirm no voltage appears upstream of D2 on 5V_PROTECTED.
- Connect carrier and laptop simultaneously; confirm stable rails and no reverse current.
- Add one radar at a time; verify idle/load current and raw UART bytes at documented baud rates.
- Add INMP441, DHT11, and MQ-2; confirm I2S samples, 2 s DHT reads, and ADC voltage below 3.3 V.
- Pass criteria: no rail exceeds ±5%, no component overheats, no backfeed, and all interfaces produce repeatable basic data.
