USB-C Sensor Node
Worked for 6 mins 16 sec
Created 4 project docs
Firmware Starter — ESP32-S3 Sensor Motor Carrier
MCU/module: ESP32-S3-WROOM-1 Framework: Arduino on PlatformIO
Board Bring-Up Plan — ESP32-S3 Sensor Motor Carrier
Current-limited USB-C 5 V supply or USB power meter. Multimeter, oscilloscope if available, USB cable, PC with PlatformIO/esptool.
Technical Construction File Notes — ESP32-S3 Sensor Motor Carrier
Draft design-stage notes. FCC Part 15 / CE RED / ISED consideration due to ESP32-S3 Wi-Fi/BLE radio module.
Preliminary FMEA — ESP32-S3 Sensor Motor Carrier
Design-stage risk review for a USB-C powered ESP32-S3 carrier board with IMU, temperature sensor, GPS header, and a single brushed DC motor ...
I created the ESP32-S3 carrier schematic with USB-C 5 V input, protected 5 V/3.3 V rails, ESP32-S3-WROOM-1, BNO085, SHT40 temperature/humidity sensor, GPS UART header, motor-driver carrier header, boot/reset buttons, status LED, and supporting passives; ERC/passive checks were clean, while layout/routing and generic passive MPN selection remain unfinished because no ACUs are currently available.
Open items:
- PCB placement/routing not started; DRC airwires are expected.
- Exact GPS module, motor driver carrier, motor voltage, and stall current still need confirmation.
- Generic resistor/capacitor MPNs need to be assigned before manufacturing.
- Motor current-sense protection/scaling should be finalized after choosing the driver carrier.
Project files created:
Suggested next steps once ACUs are available:
- Confirm the exact GPS module and brushed DC motor driver carrier.
- Finalize VMOTOR voltage/current limits and current-sense scaling.
- Assign production MPNs for generic passives.
- Proceed to PCB placement with ESP32 antenna keepout and motor-current separation.
Set module choices
Fill passive MPNs
Run ERC/DRC
Set up layout
Document requirements
Refine this doc
Ask about this doc
Board Bring-Up Plan — ESP32-S3 Sensor Motor Carrier
Prerequisites
- Current-limited USB-C 5 V supply or USB power meter.
- Multimeter, oscilloscope if available, USB cable, PC with PlatformIO/esptool.
- Do not connect a motor until 3.3 V, USB, firmware, and motor-control default-off behavior are verified.
1. Visual Inspection
- Verify USB-C connector J1 solder joints and shield tabs.
- Verify U1 ESP32-S3 module orientation and antenna edge/keepout in layout.
- Verify U2 BNO085 and U3 SHT40 orientation.
- Verify U4 regulator, D1 USB ESD array, F1 fuse, and polarized/bulk capacitor footprints.
- Verify J2/J3/J4 pin-1 markings.
2. Power Rail Verification
Table
| Rail | Source | Expected Voltage | Measure At | Initial Current Limit | Pass Criteria |
|---|---|---|---|---|---|
| VBUS_RAW | J1 VBUS before F1 | 5.0 V | J1 VBUS/F1 P1 | 100 mA first power | 4.75–5.25 V |
| 5V_USB | F1 output | 5.0 V | F1 P2/U4 VI | 100 mA first power | 4.75–5.25 V, no fuse heating |
| 3V3 | U4 VO | 3.3 V | U4 VO/C3/U1 3V3 | 100 mA first power, then 700 mA test | 3.22–3.38 V |
| VMOTOR | J4/J3 motor supply | external | J4 pin 1/J3 VMOTOR pins | supply limited to selected motor | Only apply after driver spec is known |
Procedure:
- With no power, measure resistance from 5V_USB to GND and 3V3 to GND; investigate any near-short.
- Power through USB-C with a 100 mA current limit if possible.
- Confirm 5V_USB and 3V3 before plugging in GPS or motor driver carrier.
- Increase current limit and connect USB serial only after rails are stable.
- Leave VMOTOR disconnected until motor-driver pinout and motor current are confirmed.
3. Critical Signal Verification
Table
| Signal | Expected State | Notes |
|---|---|---|
| ESP_EN | High after RC delay | SW1 should pull low/reset |
| ESP_BOOT | High normally | SW2 pulls low for bootloader |
| I2C_SDA/SCL | Idle high at 3.3 V | Verify pull-ups R3/R4 |
| MOTOR_PWM | Low at reset | R12 default-off pull-down |
| MOTOR_EN_SLEEP | Low at reset | R13 default-off pull-down |
| USB_DP/USB_DN | Enumerates as ESP32-S3 USB device | Check D+/D− continuity through J1/D1/U1 |
4. Connector Tests
Table
| Connector | Pins to Verify | Test Method |
|---|---|---|
| J1 USB-C | VBUS, GND, CC1, CC2, D+, D− | USB power and enumeration |
| J2 GPS | GND, 3V3, 5V_USB, TX/RX, PPS, EN | Continuity and firmware serial read |
| J3 Motor Carrier | VMOTOR, GND, 3V3, 5V_USB, PWM, DIR, EN, FAULT, CSENSE | Continuity before carrier install; scope PWM after firmware |
| J4 VMOTOR | VMOTOR/GND | Apply only current-limited external motor supply |
5. Programming and Debug
- Interface: native ESP32-S3 USB over J1.
- Firmware doc: see Firmware Starter.
- Flash command:
pio run -t upload. - Bootloader entry: hold SW2 BOOT, press/release SW1 RESET, release SW2.
6. Functional Validation
Table
| Test | Expected Result |
|---|---|
| USB enumeration | ESP32-S3 serial/JTAG appears on host |
| I2C scan | SHT40 at 0x44 and BNO085 at expected address |
| SHT40 read | Room temperature and humidity are plausible |
| BNO085 read | Quaternion/accel values update when board moves |
| GPS UART | NMEA characters received; PPS increments when GPS has PPS output |
| Motor safe-off | PWM=0 and EN low immediately after reset |
| Motor PWM dry test | With no motor power, J3 PWM changes under firmware command |
| Motor powered test | Only after motor voltage/stall current/driver pinout are confirmed |
7. Open Bring-Up Items
- Confirm exact GPS module voltage and UART level before plugging in.
- Confirm exact motor driver carrier pinout before plugging into J3.
- Confirm motor stall current and VMOTOR voltage before layout trace-width decisions and powered motor tests.
Prerequisites
1. Visual Inspection
2. Power Rail Verification
3. Critical Signal Verification
4. Connector Tests
5. Programming and Debug
6. Functional Validation
7. Open Bring-Up Items
