

Mainboard v2 r1
Modular ESP32-S3 geophysical data-acquisition system with custom hardware, multi-channel ADC, GNSS, IMU, removable analog sensor cards, firmware, and host tools
- Size
- 208 × 129 mm
- Copper layers
- 4
- Thickness
- 1.6 mm
- Parts
- 287
- Nets
- 257
- Pads
- 1,049
- Tracks, vias
- 1,928, 970
- Pours
- 30
- Routed
- Yes
- KiCad
- KiCad 10.0 (file 20260206)
- Created
- 19 Aug 2026
- Updated
- 27 Oct 2026
Overview
Mainboard v2 r1 is an open-source printed circuit board by Benjamin-girard-1, from the Benjamin-girard-1/geophys_acquisition_module repository on GitHub. It is a 4-layer board of 208 × 129 mm with 287 parts on 257 nets, routed with 1,928 tracks and 970 vias.
It is built around the ESP32-S3-DEVKITC-1-N8, AD7779ACPZ and LM27313XMF, with the TPS54331DR-JSM, TPS61170DRV and TPS63700DRCR among its other parts. Its parts include 111 capacitors, 104 resistors, 19 ICs, 15 diodes and 11 connectors. It belongs with the sensors and measurement and computers and single-board computers boards and the ESP32 boards of this library.
Main components
12ESP32-S3-DEVKITC-1-N8
-- WiFi Modules ROHSEspressif SystemsWiFi ModulesAD7779ACPZ
LFCSP-64-40℃~+105℃ 1.8V~3.6V 108dB 10ppm/℃ 16kHz 2.5V 24 4.096MHz、8.192MHz 4kHz、16kHz 8 Built-in Built-in Built-in SPI Sigma-Delta Support Yes LFCSP-64 Analog to Digital Converters (ADC) ROHSAnalog DevicesAnalog To Digital Converters (ADCs)LM27313XMF
SOT-23-5-40℃~+125℃@(TJ) 1 1.6MHz 2.7V~14V 400uA 5V~28V 800mA Adjustable Boost Boost Built-in No Overcurrent Protection、Cycle-by-cycle current limiting SOT-23-5 DC-DC Converters ROHSTexas InstrumentsDC-DC ConvertersTPS54331DR-JSM
SOP-8-40℃~+125℃ 1 2mA 3A 4.5V~40V 400kHz Adjustable Buck Built-in No Overcurrent Protection、Light load efficient mode、Cycle-by-cycle current limiting Step-down type SOP-8 DC-DC Converters ROHSJSMSEMIDC-DC ConvertersTPS61170DRV
SON63V to 18V Input, 3V to 38V Output, 1.2A High Voltage Boost ConverterTexas InstrumentsUncategorisedTPS63700DRCR
VSON-10-EP(3x3)-15V~-2V -40℃~+85℃@(TA) 1 1.38MHz 2.7V~5.5V 360mA 400uA Adjustable Buck-Boost Built-in Inverting No VSON-10-EP(3x3) DC-DC Converters ROHSTexas InstrumentsDC-DC ConvertersUSB2641-HZH-02
QFN-483.3V Hub I2C、SPI USB 2.0 QFN-48 USB HUB Controllers ROHSMicrochip TechnologyUSB Converters74HC595D,118
SOIC-16-40℃~+125℃ 1 100MHz 19ns@4.5V,50pF 2V~6V 74HC 8 Serial-to-Serial or Parallel Tri-State SOIC-16 Shift Registers ROHSNexperiaShift RegistersTPS7A4901DGNR
HVSSOP-8-40℃~+125℃@(Tj) 1 1.194V~33V 15.4uVrms 150mA 260mV@(100mA) 35V 49uA 72dB@(120Hz) Adjustable Positive Under Voltage Lockout、Over Current Protection、Over Temperature Protection、Enable HVSSOP-8 Voltage Regulators - Linear, Low Drop Out (LDO) Regulators ROHSTexas InstrumentsVoltage Regulators - Linear, Low Drop Out (LDO) RegulatorsTPS7A2033PDBVR-TP
SOT-23-5-40℃~+85℃ 1 180uV@(300mA) 2uA 3.3V 300mA 5.5V 75dB@(1kHz) Fixed Over Current Protection、Enable、Thermal Shutdown Positive SOT-23-5 Voltage Regulators - Linear, Low Drop Out (LDO) Regulators ROHSTECH PUBLICUncategorisedTPS7A3301RGWR
VQFN-20-EP(5x5)-40℃~+125℃@(Tj) 1 1.175V~33.2V 16uVrms 1A 210uA 290mV@(500mA) 35V 72dB@(10kHz) Adjustable Negative Under Voltage Lockout、Over Current Protection、Over Temperature Protection、Enable VQFN-20-EP(5x5) Voltage Regulators - Linear, Low Drop Out (LDO) Regulators ROHSTexas InstrumentsVoltage Regulators - Linear, Low Drop Out (LDO) RegulatorsSS34
SMA(DO-214AC)-55℃~+125℃ 3A 40V 500uA@40V 550mV@3A Independent SMA(DO-214AC) Schottky Diodes ROHSMDDSchottky Diodes
README
README.mdGeophysical Acquisition Module
Hardware, embedded firmware, protocol, and host-side software for a modular geophysical data-acquisition system.
Version 2 uses an ESP32-S3 DevKit as its immutable compute platform and a custom carrier PCB organized by hardware revision. The current hardware design includes an AD7779 ADC, an LSM6DSV IMU, MAX-M10S GNSS, SD storage shared with a USB2641, 74HC/HCT595 GPIO expansion, and removable analog acquisition cards.
Current status
The Version 2 firmware builds with ESP-IDF 5.5. Board safe-state and power
control, portable GPIO/SPI/UART, calibrated analog-input, and ROM-backed CRC
mechanisms, the 74HC/HCT595 driver, bounded analog-card ID measurement, and the
AD7779 register, lifecycle, channel/gain, fixed output-rate, signed sample
decoding, and conversion-frame validation foundations are implemented.
The acquisition task, SD recording owner, and recording controller now provide
the first end-to-end recording implementation and UART live-stream path, while
the remaining protocol inventory is still in progress. Hardware verification
is being completed incrementally.
The authoritative protocol defines fixed 64-byte command messages and portable
512-byte ADC data blocks shared by live capture and SD recording. Fixed command
framing, incremental stream recovery, CRC validation, and the
HELLO/DEVICE_INFO plus DEVICE_GET_CONFIG/DEVICE_SET_CONFIG UART slices
are implemented and verified on Rev-1 hardware. Live start/stop, complete
512-byte UART data delivery, the five SD-recording commands,
the portable \DAT encoder/decoder, fixed recording-buffer pool, and FatFs
writer are implemented; a clean Rev-1 build mounts and catalogs the SD card,
and now creates, syncs, closes, catalogs, and deletes ADC data files on Rev-1
hardware. A temporary test-only 0xf000 command can read closed recording
files in 38-byte UART chunks; it is implemented in the firmware and host codec
and was used to retrieve and CRC-validate a stored 512-byte block. A two-second
protocol probe produced and cleanly closed 404 fixed
512-byte records while configuration commands remained responsive. The probe
also exposed and led to correction of acquisition-task starvation and a
FreeRTOS queue-set accounting error that rebooted the device after several SD
records. Comparison with the working V1 driver identified and corrected
premature post-reset polling failure, missing reference-output power, missing
SPI software reset, and missing filter synchronization. The earlier all-zero
ADC response was a bench power issue: the main +5 V supply was absent, so 3V3A
was unavailable. Restoring +5 V allowed AD7779 initialization and recording to
proceed. The two expendable recordings that filled the card were enumerated
and deleted through the recording protocol, leaving an empty catalog. A
subsequent fresh probe recorded, downloaded, validated, and deleted ten
512-byte records. All record framing and CRCs passed. That early capture
contained 80 startup conversions near the AD7779 reset rate followed by a
sequence gap. The cause was an ESP-IDF side effect that enabled the DRDY pin
while its handler was attached, before ADC synchronization and SRC settling
completed. The platform attach operation now restores the pin to disabled and
the application enables it explicitly after ad7779_start(). A fresh 1 kSPS
probe then produced 25 status-OK records with no missing conversions. The
acquisition hot path now reserves SPI2 and its DMA resources once and launches
one hardware-CS-framed, prepared 32-byte transfer for each DRDY event. A
dedicated core-1 capture task advances the two-buffer DMA pipeline and
copies completed frames into a 256-frame ring; CRC validation, DAT construction,
and storage handoff run independently on core 0. The hardware-tested storage
baseline used two 2 MiB PSRAM buffers: acquisition filled one continuously
while the storage task wrote the other through a 32 KiB internal SDMMC staging
window. A 50-second four-channel 8 kSPS probe crossed both 2 MiB boundaries
without stopping acquisition or losing a conversion. The current
noise-diagnostic implementation expands this to three 2 MiB buffers. Two
buffers accumulate one conversion-count-scheduled batch, while the third keeps
acquisition running during the grouped SD write and single filesystem sync.
Stored-record CRC generation is also deferred to that same SD activity window,
removing the 508-byte PSRAM reread from each 40-conversion record boundary;
live-stream records continue to receive their CRC immediately.
For four channels, batches occur every five minutes at 1 kSPS, two minutes at
2 kSPS, one minute at 4 kSPS, and 30 seconds at 8 kSPS. A Rev-1 8 kSPS test
recorded 35,333 records, crossed five scheduled 6,000-record boundaries with
status-OK and sequence-contiguous records on both sides, and cleanly flushed
the final partial batch. Magnetic-noise comparison remains open. The four-bit
SDMMC bus runs at its verified 40 MHz
high-speed setting; every scheduled batch and the recording close are
synchronized to the filesystem. The SD volume uses FAT32
with 32 KiB clusters so FatFs can issue 32 KiB multi-sector writes instead of
splitting at the former 4 KiB cluster boundaries. A two-second
channels-0–3 probe at 16 kSPS retained all 32,840 consecutive conversions at
625 x 100 ns spacing, with zero sequence gaps and an effective 16,000.04
conversions/s. DAT production waits for eight consecutive ADC frames to pass
CRC; the final short 16 kSPS probe and one-second 1 kSPS control contained only
status-OK records with zero missing conversions. A later 237-second capture retained
every conversion but exposed 72 isolated CRC-marked frame-phase errors at the
fixed 20 MHz SPI clock. Because AD7779 SDO output-valid timing does not support
that read rate in the worst case, lower clocks were tested. Fixed 8 MHz was
clean at 1 kSPS but could not complete valid frames at 16 kSPS with the current
DRDY-to-DMA launch latency. Fixed 10 MHz and 12 MHz produced records but still
lost conversions. A longer fixed-16-MHz capture then lost 23,438 conversions
and contained 243 CRC-marked frame errors in 93.9 seconds. The current
diagnostic build returned to fixed 20 MHz and lets the SPI peripheral assert
and release CS around every DMA burst. A two-second channels-0–3 16 kSPS probe
retained all 32,480 conversions with zero gaps, but two isolated phase errors
remained. Per-frame CS is therefore fast enough but does not by itself correct
the 20 MHz SDO integrity failure.
Configuration currently applies the stopped-device ADC rate, channel mask,
per-channel gains, and three sequenced acquisition rails; +5 VA and IMU remain
status-only. The +18 V rail is owned by a dedicated stopped-acquisition
magnetic SET/RESET command that returns the rail and pulse outputs to their
safe state. The Python host now has streaming
start/stop codecs, an incremental mixed command/data parser, named-reply
matching during live data, byte-exact validated capture, continuity counters,
and a desktop GUI with manual USB/COM selection, recording management, and a
separate live-plot tab. Its Config tab now reads device status and applies the
stopped-device ADC rate, four-channel slot selection, per-channel gains, and
acquisition-rail requests.
It also separates device-reported power-rail states from editable manual rail
requests and provides a detected-card-gated SET/RESET pulse control.
The GUI connection and recording catalog were exercised against Rev-1,
including creation, stop/close, catalog, and deletion of a GUI test recording.
A reversible channels-0–3 configuration update also passed on Rev-1. Firmware
live delivery was then exercised at 921600 baud with eight channels at 1 kSPS
and with four-channel decimation-by-5: start/stop replies and all received block
CRCs passed, streaming continued while an SD recording was opened, and
reconnect succeeded after the five-second session timeout. The live blocks
still expose the known ADC critical status and startup sequence loss, so
scientific-data validation remains open.
On 2026-09-29, the currently inserted SD card mounted and its six-file catalog
remained readable, but a new recording faulted on its first 512-byte write.
The failure reproduced with the untouched default 0xFF configuration and
with channels 0–3 (0x0F), including after a device reset, while an 0x0F
live stream continued to deliver validly framed blocks. Querying the retained
recording failure through RECORDING_STOP returned 0x0a (storage full).
This isolates the failure from host configuration and four-channel
acquisition; space must be freed or the FAT32 volume repaired before recording.
The first Bluetooth Low Energy slice is also implemented. When enabled, the
ESP32-S3 advertises Geophys Acquisition, accepts one BLE central, and answers
HELLO with the existing DEVICE_INFO message. The desktop host can scan,
connect, and display that identity; other commands and live data remain
disabled on Bluetooth for now. Rev-1 bench verification passed BLE discovery
and HELLO while a USB command session remained active. The current
2026-10-03 field-test build intentionally sets APP_BLUETOOTH_ENABLED to zero
in version_2/firmware/app/app.c. This radio-silent diagnostic configuration
removed the measured 60–70 ms BLE advertising disturbance and preserves the
implemented BLE code for later re-enablement.
The same field-test build enables unattended SD recording. With no valid saved
configuration, its defaults are 8 kSPS, channels 0–3 enabled, gain x8 on
channels 0–2, and gain x1 on channel 3; channels 4–7 are disabled. A successful
wired DEVICE_SET_CONFIG commits the sample rate, channel mask, and all eight
gains to the ESP32's wear-levelled internal flash. These settings are restored
after reset or power loss; live rail/status fields are not persistent. The
firmware waits five seconds after application initialization, then creates the
first free name from field000 through field254 and starts acquisition with
the restored settings. Holding the ESP32-S3 DevKitC BOOT button for three
seconds stops the ADC, drains the PSRAM buffers, syncs the file, and closes it.
A hard power-off cannot run that cleanup: after holding BOOT, wait for the
close to finish before switching the battery off. The RESET button remains an
immediate reset and must not be used to stop a recording.
New SD recordings reserve a self-contained 32 KiB header region. Its first
4096 bytes are printable JSON containing the recording name, device and
firmware/hardware identity, card types, channel mask, gain for every channel,
sample rate, power state, channel mapping, and a link to the project tools.
The rest reserves 896 fixed 32-byte UTC/orientation checkpoints; they are
currently zero placeholders because GNSS is not installed and the IMU path is
not yet implemented. ADC DAT blocks begin at byte 32768. The JSON descriptor
passed native/Python tests and a Rev-1 readback after the 2026-10-07 flash:
field023 had a CRC-valid, printable JSON descriptor with the configured
per-channel gains and a CRC-valid first \DAT block at byte 32768. The firmware
now keeps unattended recording stopped after a wired RECORDING_STOP, matching
the BOOT-button stop behavior. A short field025 check confirmed that the board
stayed idle and the closed file could be read. Long-duration timing verification
remains open.
The complete wire contract is shared/protocol/protocol.md. It is the sole authority for framing, identifiers, results, command payloads, and ADC data blocks.
See ARCHITECTURE.md for module responsibilities, dependency rules, initialization order, and the detailed implementation-status table. Milestone-1 execution and verification are tracked in version_2/docs/firmware_implementation_checklist.md.
Repository layout
.
├── ARCHITECTURE.md Firmware architecture and dependency rules
├── shared/
│ ├── kicad-libraries/ Shared KiCad symbols and footprints
│ ├── protocol/ Firmware/host wire-protocol specification
│ ├── third_party/ Pinned external dependencies
│ └── tools/ Repository-wide development utilities
├── version_1/ Earlier product generation
└── version_2/
├── docs/ Datasheets and documentation
├── firmware/
│ ├── common/ Portable types shared across firmware layers
│ ├── main/ ESP-IDF entry point and composition root
│ ├── app/ Product behavior and FreeRTOS tasks
│ ├── boards/ Custom carrier-board integration by revision
│ ├── analog_cards/ Removable analog-card integration
│ ├── drivers/ Portable component-specific drivers
│ ├── data_format/ Portable serialized acquisition records
│ ├── protocol/ Firmware framing and message encoding
│ ├── transports/ UART, USB, and future byte transports
│ ├── platform/
│ │ └── esp32s3_devkit/ Immutable DevKit and ESP-IDF integration
│ └── cmake/ Shared build helpers when required
├── hardware/Firmware boundaries
common/defines dependency-free status categories and other truly cross-layer portable types.main/initializes the platform, selected board, and application.app/owns acquisition, processing, storage, communication, and product state.boards/maps the custom PCB wiring to portable drivers and platform services, including the Rev-1 mainboard's 18 V rail and physical shift-register outputs.analog_cards/describes complete removable card assemblies. Magnetic SET/RESET pulse generation belongs inanalog_cards/magnetic/and is not shared withanalog_cards/acc_geoph/.drivers/implements individual components without depending on ESP-IDF, FreeRTOS, or board wiring.data_format/defines transport- and storage-independent acquisition-record serialization.platform/esp32s3_devkit/isolates ESP-IDF and immutable DevKit details.protocol/implements transport-independent framing and messages.transports/move bytes without interpreting application commands.shared/protocol/defines the wire contract used by firmware and host tools.
Version 2 firmware components
The current scaffolds cover:
- AD7779 eight-channel ADC
- LSM6DSV accelerometer and gyroscope
- MAX-M10S GNSS receiver
- 74HC/HCT595 shift register
- Magnetic analog acquisition card
- Geophysical accelerometer card
- Analog-card detection
- Acquisition, processing, storage, communication, and Bluetooth tasks
- UART and USB transports
- Transport-independent protocol framing and messages
- Portable 512-byte ADC-record format
Building
Activate an ESP-IDF 5.5 environment, then build from version_2/firmware/:
cd version_2/firmware
idf.py build
idf.py flash monitorRun idf.py set-target esp32s3 first only when creating a fresh local build
configuration or changing targets.
An existing local sdkconfig created before BLE support will not automatically
pick up the new Bluetooth defaults. Back it up once and regenerate it before
the first BLE-enabled build:
mv sdkconfig sdkconfig.pre-ble
idf.py set-target esp32s3Generated build/, sdkconfig, managed components, binaries, KiCad local state,
editor files, and locally stored vendor datasheet PDFs are excluded by the root
.gitignore. Datasheet source links remain tracked in
version_2/docs/datasheet.txt.
Development guidance
Before adding a module or function, consult the “Where new code belongs” table
in ARCHITECTURE.md. Keep component
drivers portable, keep physical Rev-1 wiring in boards/rev_1, and keep protocol
encoding independent of UART, USB, or Bluetooth.
Update the architecture implementation-status table when an interface becomes usable, an implementation passes its software tests, or functionality is verified on hardware.
Plotting an extracted recording
The small developer tool opens a file chooser in the sibling
geophys_experiments/ directory, then validates and plots the selected
recording:
python3 version_2/software/apps/dev_tools/launch_plot.pyPass a path as the first argument to plot a different recording. The application reads the binary file without modifying it and displays raw ADC counts.
Parts
287| Qty | Value | Footprint | References |
|---|---|---|---|
| 35 | 100n | Capacitor_SMD:C_0603_1608Metric | C1, C2, C10, C20, C22, C23, C24, C26, C28, C30, C31, C32, C33, C35, C37, C108 +19 |
| 22 | 100k | Resistor_SMD:R_0603_1608Metric | R1, R2, R4, R5, R30, R31, R32, R37, R38, R44, R46, R61, R65, R70, R74, R101 +6 |
| 22 | 10k | Resistor_SMD:R_0603_1608Metric | R3, R6, R35, R47, R48, R51, R54, R55, R56, R57, R58, R59, R60, R68, R103, R104 +6 |
| 21 | 22 | Resistor_SMD:R_0603_1608Metric | R10, R11, R12, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26 +5 |
| 18 | 4u7 | Capacitor_SMD:C_1206_3216Metric | C39, C41, C48, C49, C50, C57, C59, C67, C78, C82, C83, C84, C85, C86, C104, C107 +2 |
| 16 | 10u | Capacitor_SMD:C_0805_2012Metric | C3, C5, C27, C46, C47, C53, C61, C64, C87, C89, C92, C99, C102, C103, C106, C111 |
| 16 | MountingHole | MountingHole:MountingHole_4.3mm_M4 | H1, H2, H3, H4, H5, H6, H7, H8, H9, H10, H11, H12, H13, H14, H15, H16 |
| 8 | 1n | Capacitor_SMD:C_0603_1608Metric | C12, C13, C14, C15, C16, C17, C18, C19 |
| 7 | 10n | Capacitor_SMD:C_0603_1608Metric | C58, C79, C95, C98, C101, C109, C110 |
| 7 | 1u | Capacitor_SMD:C_0805_2012Metric | C11, C21, C25, C34, C36, C63, C72 |
| 7 | SS34 | Diode_SMD:D_SMA | D7, D8, D12, D13, D14, D15, D16 |
| 5 | 10u | Inductor_SMD:L_Sunlord_MWSA0503S | L1, L2, L3, L4, L5 |
| 5 | 1k | Resistor_SMD:R_0603_1608Metric | R13, R39, R42, R50, R92 |
| 5 | 300k | Resistor_SMD:R_0603_1608Metric | R36, R62, R66, R73, R81 |
| 4 | 47u | Capacitor_SMD:C_1206_3216Metric | C7, C56, C81, C105 |
| 4 | Conn_01x02_Pin | magnode_footprints:KEYSTONE_7817 | J4, J6, J7, J9 |
| 4 | H5VUD5BB | Diode_SMD:D_SOD-523 | D1, D2, D3, D4 |
| 3 | 100 | Resistor_SMD:R_0805_2012Metric | R43, R69, R76 |
| 3 | 12k | Resistor_SMD:R_0603_1608Metric | R49, R96, R99 |
| 3 | 20p | Capacitor_SMD:C_0402_1005Metric | C43, C44, C55 |
| 3 | 510k | Resistor_SMD:R_0603_1608Metric | R52, R53, R87 |
| 3 | 56k | Resistor_SMD:R_0603_1608Metric | R63, R67, R102 |
| 2 | 10p | Capacitor_SMD:C_0603_1608Metric | C65, C80 |
| 2 | 22n | Capacitor_SMD:C_0603_1608Metric | C52, C71 |
| 2 | 22u | Capacitor_SMD:C_1206_3216Metric | C66, C77 |
| 2 | 39k | Resistor_SMD:R_0603_1608Metric | R75, R98 |
| 2 | 49k9 | Resistor_SMD:R_0603_1608Metric | R71, R95 |
| 2 | 4n7 | Capacitor_SMD:C_0603_1608Metric | C68, C74 |
| 2 | 550910374 | magnode_footprints:CON_550910374_MOL | J1, J2 |
| 2 | 5k1 | Resistor_SMD:R_0603_1608Metric | R40, R41 |
| 2 | 74HC595D,118 | Package_SO:SOIC-16_3.9x9.9mm_P1.27mm | U1, U2 |
| 2 | 75k | Resistor_SMD:R_0603_1608Metric | R84, R88 |
| 2 | AO3400A | Package_TO_SOT_SMD:SOT-23 | Q1, Q2 |
| 2 | Conn_01x01_Pin | magnode_footprints:KEYSTONE_1267 | J11, J13 |
| 2 | SMAJ6.0CA | Diode_SMD:D_SMA | D5, D9 |
| 2 | TPS2116DRLR | Package_TO_SOT_SMD:SOT-583-8 | U10, U14 |
| 2 | TPS7A4901DGNR | magnode_footprints:HVSSOP-8-1EP_3x3mm_P0.65mm_EP1.57x1.89mm | U16, U19 |
| 1 | 10 | Resistor_SMD:R_0603_1608Metric | R79 |
| 1 | 120Ω@100MHz 2A 50mΩ | Inductor_SMD:L_0603_1608Metric | FB1 |
| 1 | 200k | Resistor_SMD:R_0603_1608Metric | R83 |
| 1 | 22 | Resistor_SMD:R_2512_6332Metric | R77 |
| 1 | 220n | Capacitor_SMD:C_0603_1608Metric | C75 |
| 1 | 24k | Resistor_SMD:R_0603_1608Metric | R89 |
| 1 | 330k | Resistor_SMD:R_0603_1608Metric | R100 |
| 1 | 330p | Capacitor_SMD:C_0603_1608Metric | C97 |
| 1 | 3k6 | Resistor_SMD:R_0603_1608Metric | R72 |
| 1 | 470mF | magnode_footprints:C_Radial_D8.0mm_P11.50mm | C62 |
| 1 | 4u7 | magnode_footprints:kelvin_connect_1206_SMD_CAP | C100 |
| 1 | 68k | Resistor_SMD:R_0603_1608Metric | R45 |
| 1 | 90k9 | Resistor_SMD:R_1206_3216Metric | R93 |
| 1 | AD7779ACPZ | magnode_footprints:QFN-64-1EP_9x9mm_P0.5mm_EP7.65x7.65mm | U4 |
| 1 | AO3401A | Package_TO_SOT_SMD:SOT-23 | Q3 |
| 1 | C_Polarized | Capacitor_THT:CP_Radial_D10.0mm_P5.00mm | C29 |
| 1 | Conn_01x08 | magnode_footprints:MAX_M10S_WITH_HEADER | J15 |
| 1 | ESP32-S3-DevKitC | magnode_footprints:MODULE_ESP32-S3-DEVKITC | U3 |
| 1 | LED | LED_SMD:LED_0805_2012Metric | D11 |
| 1 | LM27313XMF | Package_TO_SOT_SMD:SOT-23-5 | U15 |
| 1 | LSM6DSVETR | Package_LGA:LGA-14_3x2.5mm_P0.5mm_LayoutBorder3x4y | U5 |
| 1 | LT3042xMSE | Package_SO:MSOP-10-1EP_3x3mm_P0.5mm_EP1.68x1.88mm | U17 |
| 1 | Micro_SD_CARD | magnode_footprints:CONN_503398-1892_MOL | J14 |
| 1 | OT2JI-111-8.192M | Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mm | Y1 |
| 1 | SMAJ26CA | Diode_SMD:D_SMA | D6 |
| 1 | TPS54331DR | Package_SO:SOIC-8_3.9x4.9mm_P1.27mm | U12 |
| 1 | TPS61170 | Package_SON:WSON-6-1EP_2x2mm_P0.65mm_EP1x1.6mm | U9 |
| 1 | TPS62933DRLR | Package_TO_SOT_SMD:SOT-583-8 | U8 |
| 1 | TPS63700DRCR | Package_SON:VSON-10-1EP_3x3mm_P0.5mm_EP1.2x2mm | U11 |
| 1 | TPS7A2033PDBVR | Package_TO_SOT_SMD:SOT-23-5 | U13 |
| 1 | TPS7A3301RGWR | Package_DFN_QFN:Texas_RGW0020A_VQFN-20-1EP_5x5mm_P0.65mm_EP3.15x3.15mm | U18 |
| 1 | TS3A27518EPWR | Package_SO:TSSOP-24_4.4x7.8mm_P0.65mm | U7 |
| 1 | USB2641-HZH-02 | magnode_footprints:QFN-48-1EP_7x7mm_P0.5mm_EP5.3x5.3mm | U6 |
| 1 | USB_C_Receptacle_USB2.0_14P | magnode_footprints:AMPHENOL_12402054M611A | J3 |
| 1 | X322524MOB4SI | Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mm | X1 |
| 1 | ~ | Resistor_SMD:R_0603_1608Metric | R64 |
Similar boards
- 4 layers190 × 110 mm

- 4 layers160 × 100 mm

Smu main
PaulBichl/vibepcb-smu
VibePCB example: 4-quadrant SMU (+-30 V / +-1 A, USB-C PD, Ethernet) designed with an LLM
244 parts1 - 4 layers174 × 111 mm

Pedalboard hw
arjepsen/Pedalboard-integrated-audio
A custom Raspberry Pi Compute Module 5 guitar-processing platform with integrated low-latency audio and a separate ESP32-S3 user-interface board.
118 partsCERN-OHL-P-2.0 - 4 layers90 × 140 mm

Eeg hardware v1
es-ude/eeg-hardware
Repo of the Custom Hardware Design Files of the EEG-based Gaming Controller
460 partsMIT - 2 layers53.9 × 64.8 mm

VCO
MateoHadzimustafic/VCO
Voltage Controlled Oscillator (Square and Triangle Generator)
82 partsApache-2.0 - 4 layers50 × 70 mm

FOC2
IpinZhu/foc-esc
这是一个基于 STM32G473RC 的实验性三相 PMSM/BLDC 电机控制平台。仓库包含驱动板设计,以及使用 Rust 2024 + Embassy 实现的电流控制型磁场定向控制(FOC)固件。
124 partsMIT - 2 layers120 × 100 mm

- 4 layers100 × 100 mm

Questions
How big is the Mainboard v2 r1 PCB?
It measures 208 × 129 mm and has 4 copper layers, 1.6 mm thick.
What parts does the Mainboard v2 r1 use?
287 parts, built around the ESP32-S3-DEVKITC-1-N8, AD7779ACPZ, LM27313XMF and TPS54331DR-JSM. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
Where can I download the Mainboard v2 r1 KiCad files?
From the Benjamin-girard-1/geophys_acquisition_module repository on GitHub, at the commit this page was made from: the board is version_2/hardware/pcb/rev_1/mainboard_v2_r1/mainboard_v2_r1.kicad_pcb and its schematic version_2/hardware/pcb/rev_1/magnetic_board_v2_r1/magnetic_board_v2_r1.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the Mainboard v2 r1 design in my own project?
Its repository states no licence, so its author keeps all rights: ask Benjamin-girard-1 before reusing the design.