Audio and Haptic Controller Overview

whenyoung

whenyoung

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.
22 days

flux

7:16

Identifying project risks.

Running design review.

Reviewing the bill of materials.

Analyzing the schematic.

Preparing a plan for U1.

Checking if I can make the changes for you.

Analyzing the schematic.

Looking for "For AP63203WU-7 fixed 3.3V buck regulator, what is the recommended application circuit, especially BST capacitor, VIN bypass, output capacitor, inductor value, and whether FB should connect directly to VOUT for fixed-output versions? Also identify any pins or external RC networks that are only for adjustable versions." in AP63200-AP63201-AP63203-AP63205.pdf

Looking for "What does the AP63203 datasheet say about the BST to SW bootstrap capacitor value and placement, EN usage, and any notes about not using feedback divider or compensation networks on fixed-output variants?" in AP63200-AP63201-AP63203-AP63205.pdf

Running design review.

Analyzing the schematic.

Net Connections to be added

Table

NetConnections
Net Connections to be removed

Table

NetConnections
22 days

Updated 1 connection

5:27

Connected U1:BST, C62:P1 to ^U1_BST

22 days
Sign up to send

To get started, talk to Flux or create a New Document.

Documents

    Documents are markdown text files which describe project goals, capture details, or even simulation outputs.

    Assets

    Assets are files uploaded to this project which can be used in various ways.

    ESP32 Multi-Channel Audio Host thumbnail
    ESP32-based multi-channel audio and haptic control system powered by an external 12 V input, engineered to drive 8 vibrotactile outputs and 2 speaker channels. The design includes integrated thermal monitoring and offers optional support for AUX and microSD audio sources, ensuring flexible multimedia and feedback applications in a compact, efficient platform.

    Properties

    Diagram
    


  
    
  
  
    
  



""Digital and Control Block""


""Audio Source Block""


""Power Audio Block""


""Thermal Monitoring Block""







































External DC Barrel Jack
Input Protection and Inrush Block
High Current Amplifier Rail
Primary Buck Regulator
3V3 Digital and ESP32 Rail
Filtered node_3V3 Analog Sense Rail
ESP32 Dual Mode Bluetooth
BLE App Control
Bluetooth Classic Audio
System Control and Safety Logic
Audio Source Selection and Routing
Optional AUX Line In
Optional SD Playback
8 Class D Vibrator Channels
2 Speaker Driver Channels
Thermistor Channels 1 to 4
Thermistor Channels 5 to 8
Sense Filtering and ADC Front End

    Pricing & Availability

    Distributor

    Qty 1

    Controls