Hybrid Smartwatch Design Inquiry


Enlarged the PCB from 40 mm circular to 42 mm circular on a 4-layer stackup. This keeps it within the 44 mm case target while improving density from critical to high.
Open items:
  • Routing is still tight, especially around the ESP32/RTC/regulator area.
  • A few passives may still need to move to the bottom layer for clean routing.
Suggested next steps:
  1. Spread the crowded ESP32/RTC/power components.
  2. Move low-profile passives to the bottom side.
  3. Run routing feasibility again before autorouting.
the esp doesnt fit
I’ll inspect the ESP32 module placement and board clearance, then move/orient it so the module body and antenna keepout fit within the enlarged round PCB/case constraints.
Fixed the ESP32 fit issue: U1 was protruding past the 42 mm circular board, so I moved it inward. It is now fully inside the PCB outline at approximately (0, 5 mm).
Open items:
  • Moving U1 inward created new routing congestion between U1, U5, J1, and J3.
  • The next placement pass should spread the motor driver/AMOLED connector area and possibly move small passives to the bottom side.
Suggested next steps:
  1. Re-place the crowded U1/U5/J1/J3 cluster.
  2. Move selected passives to the bottom layer.
  3. Run routing feasibility again.
Re-place and check
Re-place crowded cluster
Move passives bottom
Run layout review
Protect antenna keepout

U1
U5
J4
Project Specification — 007-Inspired Hybrid ESP32 Smartwatch
Project Overview
Status: Draft
Design a 44 mm hybrid smartwatch inspired by the 007 First Light in-game watch aesthetic. The device combines a round AMOLED/OLED dial, physical mechanical hands showing real time, wireless/BLE connectivity, rechargeable battery power, sealed charging, and a red strap-mounted laser feature.
This document captures the current agreed design direction before schematic capture.
Intended Use
  • Wearable prototype / production-intent hobbyist design.
  • Everyday-use form factor with a degree of water resistance.
  • Designed to look more like a real analog watch than a dev-board smartwatch.
  • Not intended as a certified laser product at this stage; laser safety must be treated as a core design constraint.
What the Device Should Do
  • Display a digital UI on a round AMOLED/OLED screen.
  • Leave a visible decorative outer ring/bezel region around the display to match the 007-inspired styling.
  • Show real time using physical analog hands above the display.
  • Provide 2.4 GHz Wi-Fi and BLE connectivity using an ESP32-class module.
  • Recharge from a sealed charging method, preferably wireless; magnetic pogo pins are the fallback.
  • Use the largest practical LiPo battery that fits without compromising display, hand mechanics, charging, antenna, or water-resistance requirements.
  • Include a red laser diode in the strap for visual matching with the in-game version.
Main Features

Table


FeatureCurrent Direction
Case size44 mm diameter target, 17.2 mm max thickness target
Lug-to-lug52.8 mm target
Between lugs21 mm target
Display1.32 inch round QSPI AMOLED, 466×466, Ø33.55 mm active area
HandsMechanical real-time hour/minute hands above display
WirelessESP32-S3-MINI-1-N8, 2.4 GHz Wi-Fi + BLE; 5 GHz Wi-Fi dropped
ChargingWireless receiver or magnetic pogo into MP2662-class LiPo power-path charger
BatteryLargest safe LiPo pouch/cell that fits the mechanical stack
LaserRed strap-mounted laser with hardware enable, current limiting, and safety interlocks
Water resistanceEveryday splash / sealed-use goal, pending case design
System Architecture

Diagram


"Wireless or magnetic charger" "LiPo charger / power path" "LiPo battery" "3.3 V regulator" "ESP32-class 2.4 GHz Wi-Fi / BLE module" "Round AMOLED / OLED display" "Watch hand motor driver" "Coaxial hour/minute hand stack" "Laser safety + current driver" "Red laser diode in strap" "Optional RTC / sensors / buttons"
Hardware Subsystems
Compute / Wireless
  • Use ESP32-S3-MINI-1-N8 as the primary MCU/wireless module.
  • 2.4 GHz Wi-Fi is acceptable; 5 GHz Wi-Fi is not required.
  • ESP32-S3-MINI-1-N8 provides compact module RF, native USB Serial/JTAG, more GPIO, and better display/UI headroom than ESP32-C3/C6 for this design.
  • Antenna must be placed at a board edge/clear zone, away from metal case elements where possible.
Display
  • Use a 1.32 inch round QSPI AMOLED, 466×466, active diameter approximately Ø33.55 mm.
  • The 44 mm case OD minus Ø33.55 mm active area leaves approximately 5.2 mm radial margin before case-wall, gasket, crystal, and bezel allocation.
  • Display selection must consider:
    • outer active diameter,
    • driver interface,
    • display PCB/flex shape,
    • central hand-shaft clearance strategy,
    • maximum stack height.
Mechanical Hands
  • Motor/gear system should not sit over the active display area.
  • Preferred mechanical architecture:
    • motor/gear train behind the display or around the display perimeter,
    • only a small coaxial shaft stack passes through the display center,
    • decorative center cap hides the shaft and any display dead zone,
    • hands show real time rather than animations.
  • Position reference should be provided by one of:
    • mechanical home/index position,
    • Hall sensor + magnet,
    • optical index sensor,
    • or a known reset/alignment routine.
Power / Charging
  • Battery: largest practical LiPo that fits the round case stack safely.
  • Charger direction: MP2662-class 500 mA single-cell Li-ion/LiPo charger with power-path management.
  • 3.3 V rail direction: MP28160GC-Z-class 3.3 V buck-boost regulator so the ESP32/display rail remains regulated across the full LiPo range.
  • Charging preference:
    1. Wireless charging if thickness, heating, efficiency, and case-back material allow it.
    2. Magnetic pogo charging as the thinner, cooler, easier-to-seal fallback.
  • Include battery protection, charging status, thermal considerations, and safe charge current sizing.
Laser Subsystem
  • Red laser diode located in the strap for game-inspired appearance.
  • User requested “a tiny bit of power,” potentially enough for a party trick such as marking paper or popping a balloon.
  • Design constraint: this crosses into hazardous laser territory and may require Class 3B/4-like safety handling depending on optical power and focusing.
  • Electrical design must include:
    • constant-current laser driver,
    • hardware enable line independent of firmware,
    • current limit set by resistor/component selection,
    • normally-off default state,
    • timeout in firmware,
    • physical safety interlock or deliberate multi-action trigger,
    • warning/indicator when armed.
  • Initial schematic should provision the laser driver safely; final optical power should not be selected until legal/safety constraints are confirmed.
Interfaces and Connections

Table


InterfacePurposeNotes
QSPI display bus1.32 in round AMOLEDPrefer CO5300-class QSPI module; avoid raw MIPI-only panel if possible
GPIO / motor driveHand movementDepends on Lavet stepper vs custom driver
I2COptional RTC, sensors, fuel gaugeOne shared bus with pull-ups
USB pads or pogoCharging / optional debugIf no USB-C, provide internal programming access
Battery connector / welded cellLiPo connectionMust fit the mechanical case stack
Strap flex/cableLaser diode connectionNeeds strain relief and water-resistant routing
Power and Runtime Expectations
  • Battery runtime target: maximize within mechanical constraints.
  • Key loads:
    • ESP32 Wi-Fi peaks,
    • display brightness/current,
    • motor stepping pulses,
    • laser driver pulses,
    • charging losses / wireless charging heat.
  • Low-power firmware is expected:
    • display dim/sleep states,
    • Wi-Fi off except when needed,
    • BLE preferred for standby connectivity,
    • mechanical hands continue timekeeping with minimal stepping.
Power Tree and Power Budget
Preliminary power tree:

Diagram


"Wireless receiver or pogo node_5V input" "MP2662-class LiPo charger / protection / power path" "Single-cell LiPo" "3.3 V buck-boost rail" "ESP32-S3-MINI-1-N8" "1.32 in QSPI AMOLED" "Motor driver" "Laser driver rail, if required"
Initial budget is not finalized until display, battery, motor, and laser part selections are made. Wi-Fi transmit peaks and display brightness are expected to dominate normal runtime; laser power is treated as momentary only.
Manufacturing and Assembly Expectations
  • Compact wearable PCB, likely custom round/segmented board.
  • Likely requires flex or board-to-board connection to display and strap laser.
  • Case sealing strategy should avoid exposed USB-C if everyday water resistance is desired.
  • Use module-based RF to reduce certification and layout risk.
  • Mechanical integration is a primary design risk and should be validated with a stack-up model before final PCB layout.
Firmware-Relevant Hardware Requirements
  • Maintain real-time clock using ESP32 RTC plus optional external RTC for lower drift.
  • Drive hands to real time and recover alignment after battery depletion/reset.
  • Display UI over selected display interface.
  • Manage power modes, display dimming, BLE/Wi-Fi connectivity, and charging state.
  • Laser firmware must enforce timeout, arming state, and lockout behavior, but hardware must remain fail-safe without firmware.
Physical Design Expectations

Table


DimensionTarget
Case diameter44 mm
Lug-to-lug52.8 mm
Between lugs21 mm
Max case thickness17.2 mm
Physical stack target from top to bottom:
  1. Crystal / cover lens.
  2. Physical hands and center cap.
  3. Round display and decorative ring/bezel.
  4. Hand shaft through center.
  5. Display PCB / spacer.
  6. Motor/gear module behind or around display.
  7. Main PCB and ESP32 antenna clearance.
  8. LiPo battery.
  9. Wireless charging coil or pogo interface near case back.
Important Design Decisions
  • 1.32 inch QSPI AMOLED is selected as the target display.
  • ESP32-S3-MINI-1-N8 is selected as the MCU/wireless module.
  • MP2662-class power-path charger and MP28160GC-Z-class 3.3 V buck-boost regulator are selected as the power architecture direction.
  • 2.4 GHz Wi-Fi/BLE is accepted; 5 GHz Wi-Fi is no longer required.
  • Mechanical hands are real-time hands, not primarily animation hands.
  • Motor must be hidden behind/around the display; only the center shaft penetrates the dial region.
  • Wireless charging is preferred for watch-like appearance; magnetic pogo is allowed if wireless charging is too thick/hot/inefficient.
  • Laser subsystem must be designed conservatively with hardware safety controls.
Assumptions
  • The project is inspired by the 007 First Light watch but will avoid exact copyrighted branding/logos unless supplied/authorized by the user.
  • The first PCB pass will prioritize feasibility and safe architecture over final miniaturization.
  • The laser will be disabled by default and treated as a hazardous subsystem until final optical power is selected.
  • The case mechanical design will be developed alongside electronics because hand stack, display, battery, and charging coil all compete for thickness.
Change Notes
  • Captured user requirements for 44 mm hybrid analog/digital watch form factor.
  • Confirmed display should leave room for decorative outer ring.
  • Confirmed physical hands show real time.
  • Confirmed laser diode must be red and strap-mounted.
  • Confirmed wireless or magnetic charging preferred, with wireless best.
  • Confirmed everyday water-resistance goal.
  • Confirmed 2.4 GHz Wi-Fi is acceptable.
  • Selected 1.32 inch QSPI AMOLED display architecture.
  • Selected ESP32-S3-MINI-1-N8 MCU/wireless module direction.
  • Selected MP2662-class charger/power-path and 3.3 V buck-boost power architecture direction.
  • Project Overview

  • Intended Use

  • What the Device Should Do

  • Main Features

  • System Architecture

  • Hardware Subsystems

  • Compute / Wireless

  • Display

  • Mechanical Hands

  • Power / Charging

  • Laser Subsystem

  • Interfaces and Connections

  • Power and Runtime Expectations

  • Power Tree and Power Budget

  • Manufacturing and Assembly Expectations

  • Firmware-Relevant Hardware Requirements

  • Physical Design Expectations

  • Important Design Decisions

  • Assumptions

  • Change Notes