Skip to the content
4 layers208 × 129 mmMainboard v2 r1, the printed circuit board in 3D

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

12

README

README.md

Geophysical 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

text
.
├── 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 in analog_cards/magnetic/ and is not shared with analog_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/:

sh
cd version_2/firmware
idf.py build
idf.py flash monitor

Run 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:

sh
mv sdkconfig sdkconfig.pre-ble
idf.py set-target esp32s3

Generated 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:

sh
python3 version_2/software/apps/dev_tools/launch_plot.py

Pass 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
QtyValueFootprintReferences
35100nCapacitor_SMD:C_0603_1608MetricC1, C2, C10, C20, C22, C23, C24, C26, C28, C30, C31, C32, C33, C35, C37, C108 +19
22100kResistor_SMD:R_0603_1608MetricR1, R2, R4, R5, R30, R31, R32, R37, R38, R44, R46, R61, R65, R70, R74, R101 +6
2210kResistor_SMD:R_0603_1608MetricR3, R6, R35, R47, R48, R51, R54, R55, R56, R57, R58, R59, R60, R68, R103, R104 +6
2122Resistor_SMD:R_0603_1608MetricR10, R11, R12, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26 +5
184u7Capacitor_SMD:C_1206_3216MetricC39, C41, C48, C49, C50, C57, C59, C67, C78, C82, C83, C84, C85, C86, C104, C107 +2
1610uCapacitor_SMD:C_0805_2012MetricC3, C5, C27, C46, C47, C53, C61, C64, C87, C89, C92, C99, C102, C103, C106, C111
16MountingHoleMountingHole:MountingHole_4.3mm_M4H1, H2, H3, H4, H5, H6, H7, H8, H9, H10, H11, H12, H13, H14, H15, H16
81nCapacitor_SMD:C_0603_1608MetricC12, C13, C14, C15, C16, C17, C18, C19
710nCapacitor_SMD:C_0603_1608MetricC58, C79, C95, C98, C101, C109, C110
71uCapacitor_SMD:C_0805_2012MetricC11, C21, C25, C34, C36, C63, C72
7SS34Diode_SMD:D_SMAD7, D8, D12, D13, D14, D15, D16
510uInductor_SMD:L_Sunlord_MWSA0503SL1, L2, L3, L4, L5
51kResistor_SMD:R_0603_1608MetricR13, R39, R42, R50, R92
5300kResistor_SMD:R_0603_1608MetricR36, R62, R66, R73, R81
447uCapacitor_SMD:C_1206_3216MetricC7, C56, C81, C105
4Conn_01x02_Pinmagnode_footprints:KEYSTONE_7817J4, J6, J7, J9
4H5VUD5BBDiode_SMD:D_SOD-523D1, D2, D3, D4
3100Resistor_SMD:R_0805_2012MetricR43, R69, R76
312kResistor_SMD:R_0603_1608MetricR49, R96, R99
320pCapacitor_SMD:C_0402_1005MetricC43, C44, C55
3510kResistor_SMD:R_0603_1608MetricR52, R53, R87
356kResistor_SMD:R_0603_1608MetricR63, R67, R102
210pCapacitor_SMD:C_0603_1608MetricC65, C80
222nCapacitor_SMD:C_0603_1608MetricC52, C71
222uCapacitor_SMD:C_1206_3216MetricC66, C77
239kResistor_SMD:R_0603_1608MetricR75, R98
249k9Resistor_SMD:R_0603_1608MetricR71, R95
24n7Capacitor_SMD:C_0603_1608MetricC68, C74
2550910374magnode_footprints:CON_550910374_MOLJ1, J2
25k1Resistor_SMD:R_0603_1608MetricR40, R41
274HC595D,118Package_SO:SOIC-16_3.9x9.9mm_P1.27mmU1, U2
275kResistor_SMD:R_0603_1608MetricR84, R88
2AO3400APackage_TO_SOT_SMD:SOT-23Q1, Q2
2Conn_01x01_Pinmagnode_footprints:KEYSTONE_1267J11, J13
2SMAJ6.0CADiode_SMD:D_SMAD5, D9
2TPS2116DRLRPackage_TO_SOT_SMD:SOT-583-8U10, U14
2TPS7A4901DGNRmagnode_footprints:HVSSOP-8-1EP_3x3mm_P0.65mm_EP1.57x1.89mmU16, U19
110Resistor_SMD:R_0603_1608MetricR79
1120Ω@100MHz 2A 50mΩInductor_SMD:L_0603_1608MetricFB1
1200kResistor_SMD:R_0603_1608MetricR83
122Resistor_SMD:R_2512_6332MetricR77
1220nCapacitor_SMD:C_0603_1608MetricC75
124kResistor_SMD:R_0603_1608MetricR89
1330kResistor_SMD:R_0603_1608MetricR100
1330pCapacitor_SMD:C_0603_1608MetricC97
13k6Resistor_SMD:R_0603_1608MetricR72
1470mFmagnode_footprints:C_Radial_D8.0mm_P11.50mmC62
14u7magnode_footprints:kelvin_connect_1206_SMD_CAPC100
168kResistor_SMD:R_0603_1608MetricR45
190k9Resistor_SMD:R_1206_3216MetricR93
1AD7779ACPZmagnode_footprints:QFN-64-1EP_9x9mm_P0.5mm_EP7.65x7.65mmU4
1AO3401APackage_TO_SOT_SMD:SOT-23Q3
1C_PolarizedCapacitor_THT:CP_Radial_D10.0mm_P5.00mmC29
1Conn_01x08magnode_footprints:MAX_M10S_WITH_HEADERJ15
1ESP32-S3-DevKitCmagnode_footprints:MODULE_ESP32-S3-DEVKITCU3
1LEDLED_SMD:LED_0805_2012MetricD11
1LM27313XMFPackage_TO_SOT_SMD:SOT-23-5U15
1LSM6DSVETRPackage_LGA:LGA-14_3x2.5mm_P0.5mm_LayoutBorder3x4yU5
1LT3042xMSEPackage_SO:MSOP-10-1EP_3x3mm_P0.5mm_EP1.68x1.88mmU17
1Micro_SD_CARDmagnode_footprints:CONN_503398-1892_MOLJ14
1OT2JI-111-8.192MCrystal:Crystal_SMD_3225-4Pin_3.2x2.5mmY1
1SMAJ26CADiode_SMD:D_SMAD6
1TPS54331DRPackage_SO:SOIC-8_3.9x4.9mm_P1.27mmU12
1TPS61170Package_SON:WSON-6-1EP_2x2mm_P0.65mm_EP1x1.6mmU9
1TPS62933DRLRPackage_TO_SOT_SMD:SOT-583-8U8
1TPS63700DRCRPackage_SON:VSON-10-1EP_3x3mm_P0.5mm_EP1.2x2mmU11
1TPS7A2033PDBVRPackage_TO_SOT_SMD:SOT-23-5U13
1TPS7A3301RGWRPackage_DFN_QFN:Texas_RGW0020A_VQFN-20-1EP_5x5mm_P0.65mm_EP3.15x3.15mmU18
1TS3A27518EPWRPackage_SO:TSSOP-24_4.4x7.8mm_P0.65mmU7
1USB2641-HZH-02magnode_footprints:QFN-48-1EP_7x7mm_P0.5mm_EP5.3x5.3mmU6
1USB_C_Receptacle_USB2.0_14Pmagnode_footprints:AMPHENOL_12402054M611AJ3
1X322524MOB4SICrystal:Crystal_SMD_3225-4Pin_3.2x2.5mmX1
1~Resistor_SMD:R_0603_1608MetricR64

Similar boards

  • 4 layers160 × 100 mmSmu main, the printed circuit board in 3D

    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 mmPedalboard hw, the printed circuit board in 3D

    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 mmEeg hardware v1, the printed circuit board in 3D

    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 mmVCO, the printed circuit board in 3D

    VCO

    MateoHadzimustafic/VCO

    Voltage Controlled Oscillator (Square and Triangle Generator)

    82 partsApache-2.0
  • 4 layers50 × 70 mmFOC2, the printed circuit board in 3D

    FOC2

    IpinZhu/foc-esc

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

    124 partsMIT
  • 2 layers120 × 100 mmInoovatest Sub, the printed circuit board in 3D

    Inoovatest Sub

    jcchincheong-bb/Verificationator_GP-WS25-26

    Files for Group Project WS2526

    115 parts
  • 4 layers100 × 100 mmDIY AWG V1.1, the printed circuit board in 3D

    DIY AWG V1.1

    Xpeditor15/DIY_AWG_V1.0

    235 parts

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.