USB-C Sensor Node
Firmware Starter — ESP32-S3 Sensor Motor Carrier
Board Bring-Up Plan — ESP32-S3 Sensor Motor Carrier
Technical Construction File Notes — ESP32-S3 Sensor Motor Carrier
Preliminary FMEA — ESP32-S3 Sensor Motor Carrier
Table
| Subsystem | Failure Mode | Effect | Severity 1-10 | Likelihood 1-10 | Detection 1-10 | RPN | Mitigation |
|---|---|---|---|---|---|---|---|
| USB-C input | Overcurrent or downstream short | USB source trips, board heat/damage | 6 | 3 | 3 | 54 | F1 PTC on VBUS, first-power current limit, visual inspection |
| 3V3 regulator | Thermal overload from ESP32/GPS load | Brownout, reset, hot regulator | 5 | 4 | 4 | 80 | 1 A TO-220-class LDO selected; verify temperature under Wi-Fi/GPS load |
| ESP32 boot | Motor enable pin high during reset | Unexpected motor motion | 8 | 3 | 3 | 72 | R12/R13 pull-downs keep PWM/EN low; firmware starts safe-off |
| Motor supply | Wrong VMOTOR voltage or excessive stall current | Driver/carrier overheating, motor damage | 8 | 5 | 5 | 200 | Motor power is external and not applied until exact motor/driver are confirmed; size traces after stall current known |
| Motor carrier pinout | Header mismatch with selected carrier | Shorts or wrong control signals | 7 | 5 | 4 | 140 | Verify selected carrier pinout before layout; label J3 pinout clearly |
| Current sense | Driver outputs >3.3 V into ESP32 ADC | ESP32 GPIO damage | 7 | 4 | 5 | 140 | Require 0–3.3 V current-sense scaling; add divider/clamp once driver is selected |
| GPS header | 5 V logic GPS connected to ESP32 RX | ESP32 input damage | 6 | 3 | 5 | 90 | Document 3.3 V UART logic requirement; add level shifting if chosen GPS is 5 V logic |
| RF/EMI | Motor current routed near antenna/IMU | Poor Wi-Fi/BLE range, noisy IMU readings | 5 | 5 | 5 | 125 | Layout separation, antenna keepout, motor return routing, bulk cap C9 |
| Sensor placement | SHT40 near regulator/ESP heat | Temperature reading biased high | 3 | 6 | 4 | 72 | Place U3 at airflow/board edge away from heat sources |
| Firmware crash | Motor remains enabled | Possible uncontrolled motion | 8 | 3 | 5 | 120 | Add watchdog and safe-off fault handling in production firmware; consider hardware watchdog/driver enable gating for safety-critical use |
Scope
Failure Mode Table
Highest Priority Actions
Open Items