Audio and Haptic Controller Overview
Context — reference hardware (uploaded image)
I uploaded a photo of our assembled prototype: a separate high-power AC-DC or DC power module (green board, transformer, bulk caps, heavy red/black leads) wired to a dense black main PCB with SMT, microSD, a small RF/wireless module, multi-channel support parts, and JST-style harnesses. Use this image ONLY as a system-integration reference: physical partitioning, connector placement intent, harness routing style, and thermal/EMI “keep power away from sensitive RF/analog” intent. Do NOT infer netlists, part numbers, or electrical ratings from the photo alone—always follow datasheets and this Flux project.
Project goal — complete THIS Flux project for the production-intent music vibrator host PCBA
- MCU: ESP32 dual-mode (Classic Bluetooth audio A2DP + BLE control). Firmware and mobile app are already validated on a dev board; keep pin/peripheral allocation compatible with the VAT / WhenYoung handoff (BLE GATT: service 6E400001-…, control 6E400002-…, ack 6E400003-…; JSON commands; Bluedroid stack for A2DP coexistence—do not switch to NimBLE).
- Power: onboard AC–DC is OUT OF SCOPE. External adapter feeds DC input to the unit (nominal 12 V class—follow the design brief in-project). Main rails and amplifier supplies must match the chosen PMIC/amp datasheets.
- Outputs: 8× vibrator channels (QY97R-Z6 class, low-ohm haptic loads) + 2× 5 W speakers.
- Safety / control: 8× NTC temperature channels with host-side overtemperature policy (MUX/ADC expansion per firmware notes—do not assume a single GPIO ADC for all 8 in production).
- Layout intent: separate zones for power conversion, digital/ESP32, RF, and multi-channel power audio/haptics (consistent with the photo’s two-board separation).
Hard constraints for Copilot
- Align schematic blocks with the photo’s subsystem story (power feed, main logic/audio, wireless, storage, channel outputs) but verify every connection against datasheets and this project—not the JPEG.
- Do NOT merge unrelated nets (e.g. do NOT tie ESP32 UART TX to GND).
- U1 is a fixed 3.3 V buck (AP63203-class)—use correct BST/boot strap per datasheet; remove or do not apply R/C networks meant for adjustable bucks.
- Bootstrap caps for class-D amps: no accidental shorts between BST nodes (historical issue: C23–C26 style nets).
- Footprint/焊盘 geometry: if chat cannot edit a broken footprint, say so and stop instead of looping.
This run — execution scope (critical)
Use Planning internally, but APPLY EDITS FOR ONLY ONE schematic sub-circuit in this single run—choose the single highest-risk incomplete block that blocks everything else (e.g. one Class-D path, or ESP32 power/clock/UART, or NTC mux chain—pick one). Do NOT edit other ICs or run full-board ERC cleanup in this run. Explicitly end with: which block you edited, what remains next, and “Stop.”
@project — proceed.
Thought for 7 mins 16 sec
Net Connections to be added
Table
| Net | Connections |
|---|
Net Connections to be removed
Table
| Net | Connections |
|---|
Updated 1 connection
5:27
Connected U1:BST, C62:P1 to ^U1_BST
Welcome 👋
Flux helps you build PCBs faster with an AI teammate!
Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.