Haptic Glove Design Discussion
Thought for 2 sec
I can’t analyze or run auto-layout right now because the account currently has no available ACUs, so AI execution features are unavailable.
What has been accomplished so far:
- Complete schematic was created for the ESP32 haptic glove.
- ERC was clean at the last schematic check.
- PCB setup was started with an 80 × 90 mm, 4-layer wearable board.
- Major components were placed by functional block, including ESP32-S3, USB-C, LiPo JST connector, charger, regulator, DRV2605L, TCS34725 connector, LRA connector, buttons, and passives.
What remains:
- Inspect current PCB state to determine whether placement, routing, or both are still needed.
- Complete routing, including USB D+/D−, battery/SYS/3V3, I2C, and LRA outputs.
- Run DRC/board checks and fix remaining issues.
- Verify ESP32 antenna keepout, connector accessibility, and wearable mechanical constraints.
Once ACUs are available, I can run the PCB analysis and automatically apply the needed placement/routing updates.
Start Auto-Layout
Thought for 1 sec
I can’t run PCB analysis or auto-layout right now because the account currently has no available ACUs, so AI execution features are unavailable.
Current project state from the last completed work:
- Schematic is complete for the ESP32 haptic glove.
- ERC was clean at the last check.
- PCB was initialized as an 80 × 90 mm, 4-layer board.
- Major parts were already placed by functional block.
- Routing is still incomplete, with airwires remaining.
What still needs to be done:
- Inspect the current PCB to decide whether placement refinement, routing, or both are required.
- Auto-route key nets: USB D+/D−, battery/SYS/3V3, I2C, and LRA motor outputs.
- Run DRC/board checks after routing.
- Fix clearance, unrouted-net, and ESP32 antenna/ground-pad issues if present.
When ACUs are available again, I can execute the auto-layout workflow and apply the results automatically.
List unrouted nets
Review P1 placement
Run DRC review
Routing priorities
Refine this doc
Ask about this doc
Project Specification
Overview
Wearable haptic glove main PCB that reads a remote TCS34725 RGB sensor module and drives a remote fingertip LRA vibration motor with patterns selected by firmware.
Core Architecture
- MCU: ESP32-S3 module with native USB programming/debug.
- Haptic driver: TI DRV2605L for LRA motor drive over I2C.
- Sensor interface: 4-pin Qwiic/JST-SH-style connector for remote TCS34725 ring sensor module: 3V3_SENSOR, GND, SDA, SCL.
- Motor interface: 2-pin locking JST GH connector for remote fingertip LRA motor: LRA_OUT+ and LRA_OUT-.
- Power: USB-C 5 V sink input, single-cell LiPo battery connector, charger/power-path IC, and regulated 3.3 V rail.
- Programming: ESP32-S3 native USB D+/D- plus BOOT and RESET controls.
Design Assumptions
- The TCS34725 is on a small remote ring PCB or breakout with local decoupling.
- The LRA motor is remote at the fingertip and connects only to the DRV2605L differential output.
- Default firmware should run I2C at 100 kHz initially for cable robustness.
- Battery cell/capacity and exact LRA motor model are still TBD.
Power Budget Snapshot
- ESP32-S3 module: design for up to ~500 mA RF/transient current.
- DRV2605L + LRA: provision ~100 mA class motor load until exact motor is selected.
- Remote TCS34725 sensor: <10 mA class load.
- 3.3 V regulator target: at least 600 mA; this is acceptable for prototype BLE/light Wi-Fi use but may be tight for worst-case Wi-Fi + haptic operation.
Open Decisions
- Exact LiPo capacity and whether the pack is protected.
- Exact LRA motor rated voltage/resonant frequency.
- Cable lengths for the fingertip motor and ring sensor.
- Whether Rev B needs differential I2C/bus buffering for a longer sensor cable.
Overview
Core Architecture
Design Assumptions
Power Budget Snapshot
Open Decisions
