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
Board Bring-Up Plan — ESP32 Haptic Glove
Prerequisites
- Multimeter, current-limited USB supply or USB power meter, oscilloscope if available.
- USB-C cable for native ESP32-S3 programming.
- Firmware: see
Firmware Starter. - Use a protected 1-cell LiPo pack unless battery protection is added elsewhere.
1. Visual Inspection
- Inspect
U1,U2,U3,U4,U5, USB-CJ1, battery connectorJ2, sensor connectorJ3, and LRA connectorJ4for solder bridges. - Confirm
J2polarity: pin 1 =BAT, pin 2 =GND. - Confirm
J4wiring: pin 1 =LRA_OUT_P, pin 2 =LRA_OUT_N; neither LRA pin is ground.
2. Power Rail Verification
Table
| Rail | Source | Expected Voltage | Measure At | Current Limit | Pass Criteria |
|---|---|---|---|---|---|
VBUS | USB-C J1 | 5.0 V | U3:IN, D1:VBUS | 500 mA | 4.75–5.25 V |
BAT | J2 / U3:BAT | 3.0–4.2 V | J2:1, C8:P1 | Battery-limited | No reverse polarity, no short |
SYS | U3:OUT | ~3.5–4.4 V | U4:VIN, C7:P1 | 500 mA | Present from USB or battery |
3V3 | U4:VOUT | 3.3 V | TP1, U1:3V3 | 600 mA max regulator | 3.20–3.40 V |
3V3_SENSOR | U5:OUT | 0 V until enabled, then 3.3 V | J3:2, C14:P1 | Sensor rail only | Off at boot, 3.20–3.40 V when enabled |
Procedure:
- With no battery and no USB, measure resistance from
VBUS,BAT,SYS,3V3, and3V3_SENSORtoGND. - Apply USB-C power with current limit at 500 mA.
- Verify
VBUS,SYS, then3V3in order. - Connect a protected LiPo pack and verify
BATpolarity and charger status. - After firmware enables
TCS_PWR_EN, verify3V3_SENSORappears atJ3:2.
3. Critical Signal Verification
Table
| Signal | Net | Expected State | Measure At | Notes |
|---|---|---|---|---|
| ESP32 enable | ESP_EN | High after RC delay | U1:EN | SW2 pulls low for reset |
| Boot strap | ESP_BOOT | High normally | U1:IO0 | SW1 pulls low for bootloader |
| Haptic enable | HAPTIC_EN | Low at boot, firmware high | U2:EN | R15 pulldown |
| Sensor power enable | TCS_PWR_EN | Low at boot, firmware high | U5:ON | R14 pulldown |
| I2C SDA/SCL | I2C_SDA, I2C_SCL | Idle high at 3.3 V | TP3, TP4 | 4.7 kΩ pull-ups |
4. Connector and Interface Tests
Table
| Connector | Purpose | Pins to Verify | Test Method |
|---|---|---|---|
J1 | USB-C power/programming | VBUS, GND, D+, D-, CC1, CC2 | USB enumeration and 5 V check |
J2 | LiPo battery | pin 1 BAT, pin 2 GND | Polarity and charge test |
J3 | TCS34725 ring module | pin 1 GND, pin 2 3V3_SENSOR, pin 3 SDA, pin 4 SCL | I2C scan for 0x29 |
J4 | Fingertip LRA motor | pin 1 LRA_OUT_P, pin 2 LRA_OUT_N | DRV2605L effect playback |
5. Programming and Debug Interface
Table
| Interface | Signals | Connector | Tool |
|---|---|---|---|
| ESP32-S3 native USB | USB_D_P, USB_D_N | J1 | PlatformIO / esptool.py |
| Bootloader buttons | ESP_BOOT, ESP_EN | SW1, SW2 | Hold BOOT, tap RESET |
Procedure:
- Connect USB-C.
- Verify
3V3is stable. - Upload the firmware starter.
- Open serial monitor at 115200 baud.
- Confirm I2C device detection for DRV2605L (
0x5A) and TCS34725 (0x29).
6. Functional Validation
Table
| Test | Components | Input | Expected Output | Pass Criteria |
|---|---|---|---|---|
| I2C bus scan | U1, U2, J3 remote sensor | Firmware scan | Addresses 0x5A, 0x29 | Both detected |
| Color detection | TCS34725 remote board | Red/green/blue object | Raw RGB values change | Dominant channel matches object |
| Haptic playback | U2, J4, LRA | Firmware effect command | Motor vibrates | No overheating or continuous runaway |
| Battery ADC | R12/R13, U1:IO1 | Known battery voltage | Serial voltage estimate | Within about ±10% after calibration |
| Charger status | U3, R16/R17 | USB present / charging | CHG_STAT, PGOOD_STAT change | Active-low logic matches charger state |
Open Items
- Exact LRA motor model must be selected before final haptic tuning.
- Exact LiPo capacity must be selected before final charge-current approval.
- Long sensor cables may require I2C buffering in a later revision.
Prerequisites
1. Visual Inspection
2. Power Rail Verification
3. Critical Signal Verification
4. Connector and Interface Tests
5. Programming and Debug Interface
6. Functional Validation
Open Items
