ESP32-S3 Round Board Requirements


esp32s3 based custom board.
should hav neo m9l or neo max gps module wih compatible antennae
should ahve sd card slot and support upto 512gb
should have lcd connector to conect 1.8 or 2.1 inch round display.
should have onboard battery connector with battery charging capability
should have rtc
should have magnetometer bmm150 or any other.
should be have voltage regulator built in as it wil be cnnected to 12v system so it should down volt to 5v.
should have a usb-c port for debug and comms.
make sure the gps module is placed such that it has minimal intereference with other modules especially magnetometer.
form factor should be round and minimal footprint.
the battery should be serviceable so it needs to be pin connector. same for rtc battery.
the device will be connected to base mount that will charge it via pogo pins.
Created a project doc

Design Requirements

View Document

Design Requirements Status
Requirements captured only. No components, nets, schematic, PCB layout, or part verification completed. Execution stopped because the account ran out of ACUs.
Requested device
Compact round ESP32-S3-based custom board, with minimum practical footprint. Device docks to a base mount and charges through pogo pins.
User requirements
  • ESP32-S3 MCU.
  • GNSS: NEO-M9L or a 'NEO MAX' GPS module (exact alternative needs clarification), with a compatible antenna.
  • microSD card slot supporting cards up to 512 GB.
  • LCD connector for a 1.8-inch or 2.1-inch round display.
  • Serviceable main battery connected by a removable pin connector, with onboard charging.
  • RTC with separate serviceable backup battery connected by a removable pin connector.
I saved your board requirements in Design Requirements, including the round ESP32-S3 board, GNSS, 512 GB microSD support, display connector, serviceable batteries, 12 V regulation, USB-C, and pogo-pin charging. No components, schematic, or PCB layout have been created yet.
Before implementation, I need the maximum board diameter, exact display, battery specifications, and whether the dock supplies 12 V or 5 V; I also recorded GNSS noise isolation and magnetometer clearance from inductors, high-current paths, and mounting magnets as layout requirements. Part verification and board design require Agent mode.
Execution stopped because your ACUs ran out.
What is Agent mode?
Agent mode lets Flux build, do deep research, validate designs, and work through complex assignments.
Chat mode is just as smart and has the same engineering knowledge, but it cannot work autonomously.
Only Agent mode consumes your plan's included AI usage (measured in ACUs).
Continue in Agent Mode

Waiting for input

No schematic yet

Talk to Flux to get started.

Design Requirements
Status
Requirements captured only. No components, nets, schematic, PCB layout, or part verification completed. Execution stopped because the account ran out of ACUs.
Requested device
Compact round ESP32-S3-based custom board, with minimum practical footprint. Device docks to a base mount and charges through pogo pins.
User requirements
  • ESP32-S3 MCU.
  • GNSS: NEO-M9L or a 'NEO MAX' GPS module (exact alternative needs clarification), with a compatible antenna.
  • microSD card slot supporting cards up to 512 GB.
  • LCD connector for a 1.8-inch or 2.1-inch round display.
  • Serviceable main battery connected by a removable pin connector, with onboard charging.
  • RTC with separate serviceable backup battery connected by a removable pin connector.
  • Magnetometer: BMM150 or suitable alternative.
  • Input from a 12 V system, with onboard regulation to 5 V and other required rails.
  • USB-C for debug and communications.
  • Pogo-pin docking interface for charging.
  • Place GNSS and its antenna to minimize interference from the rest of the board, including the magnetometer subsystem.
Engineering considerations to resolve and verify
  • Exact GNSS module identity, availability, antenna type, placement, and required antenna ground plane. 'NEO MAX' is not yet an identified part.
  • Maximum board diameter, usable height, mounting details, and display mechanical envelope.
  • Exact display part number, connector pinout, interface, supply, and backlight current. Diagonal size alone does not define compatibility.
  • Main battery chemistry, cell count, capacity, connector, polarity, and charging current; select charger and power-path topology only after this is established.
  • Whether dock pogo pins deliver raw 12 V or regulated 5 V; whether 12 V also enters elsewhere; input range and transient environment, including whether this is an automotive installation.
  • USB, dock, and battery source arbitration, reverse-current prevention, input protection, and operation while charging.
  • RTC accuracy and backup battery chemistry; do not charge a non-rechargeable backup cell.
  • 512 GB card support requires appropriate firmware/filesystem support (typically exFAT for SDXC) as well as interface and power integrity; slot size alone does not guarantee support.
  • GNSS RF noise isolation from switching regulators, MCU clocks, USB, SD, and display signals. Separately protect magnetometer accuracy from inductors, high-current paths, magnets, and ferrous hardware; GNSS separation alone is insufficient.
  • Confirm whether the docking mount uses magnets; their fields may compromise compass readings.
  • Battery life target, display operating duty cycle, GNSS update rate, and thermal/power budgets.
Next session
Clarify the mechanical envelope, display, battery, and dock electrical supply first; then verify parts and architecture, capture schematic, and obtain layout-stage confirmation before round-board placement and routing. No specific parts or electrical implementation have been approved or verified yet.
  • Status

  • Requested device

  • User requirements

  • Engineering considerations to resolve and verify

  • Next session