Skip to the content
2 layers30 × 35 mmHt7k1401 breakout, the printed circuit board in 3D

A custom three-wheel omnidirectional robot: radial-mount wheels driven by FOC-controlled motors with magnetic angle encoders, steered by a Logitech F710 gamepad through a Raspberry Pi, with IMU-based orientation sensing…

Size
30 × 35 mm
Copper layers
2
Thickness
1.6 mm
Parts
21
Nets
17
Pads
62
Tracks, vias
63, 60
Pours
8
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
13 Jul 2026
Updated
12 Oct 2026

Overview

Ht7k1401 breakout is an open-source printed circuit board by nthuee822, from the nthuee822/project_meatball repository on GitHub. It is a 2-layer board of 30 × 35 mm with 21 parts on 17 nets, routed with 63 tracks and 60 vias.

It is built around the HT7K1401. Its parts include 7 resistors, 4 capacitors, 3 connectors and 2 ICs. It belongs with the robots and motor control and interfaces and adapters boards of this library.

Main components

1

README

README.md

project_meatball

A custom three-wheel omnidirectional robot: radial-mount wheels driven by FOC-controlled motors with magnetic angle encoders, steered by a Logitech F710 gamepad through a Raspberry Pi, with IMU-based orientation sensing and custom PCBs and 3D-printed mechanical parts.

Repository Layout

DirectoryContents
controller/Raspberry Pi Python controller: reads the gamepad, computes inverse kinematics for the three radial wheels, and streams motor commands over SPI (optionally fused with IMU data).
IMU/Standalone Python driver for the ICM-20948 9-axis IMU (accel/gyro/mag) over I2C on the Raspberry Pi, plus calibration and debug scripts.
stm32/STM32CubeIDE firmware projects for the per-wheel motor drivers: field-oriented control (foc_v0, foc_v1), AS5600 magnetic encoder angle measurement (angle_measurement_test, angle_measurement_kalman), ADC alignment testing, and a stepper/SPI test build. common_lib/ holds the shared AS5600 driver.
hardware/KiCad PCB projects: current-sense simulation, the ht7k1401 breakout board, and a shared component library.
3d_model/FreeCAD/3MF models for printed parts — motor holders, hall-sensor holders/washers, magnet mold, and corner brackets.
architecture/System architecture diagrams (drawio source + exported PDF).
images/Reference photos and renders.

System Overview

text
F710 gamepad --USB--> Raspberry Pi (controller/) --SPI--> STM32 motor drivers (stm32/foc_*)
                              ^                                    |
                              |                                    v
                        IMU/ (ICM-20948)                 AS5600 encoder + motor

Each wheel's STM32 board runs closed-loop FOC using position feedback from an AS5600 magnetic encoder (angle read directly, or Kalman-filtered — see stm32/angle_measurement_kalman). The Raspberry Pi computes per-wheel speed/ direction from gamepad input via radial-mount inverse kinematics and sends them as fixed-format SPI frames; see controller/README.md for the protocol and kinematics details.

Getting Started

Python Environment (uv)

All Python code (controller/, IMU/, stm32/*/ scripts) shares one environment managed by uv, defined in pyproject.toml and pinned by uv.lock. It lives in .venv/ at the repo root and does not touch your system Python.

bash
# 1. Install uv (once per machine)
curl -LsSf https://astral.sh/uv/install.sh | sh          # Linux / macOS
# powershell -c "irm https://astral.sh/uv/install.ps1 | iex"   # Windows

# 2. Create .venv and install dependencies (re-run after pulling changes)
uv sync

# 3. Run scripts through uv (works from any subdirectory)
cd controller && uv run python run_test.py

Hardware libraries (smbus2, spidev, rpi-lgpio which provides RPi.GPIO) are only installed on Raspberry Pi (Linux ARM64). On a laptop, uv sync skips them, so you can still run the hardware-independent parts (kinematics, gamepad/keyboard input, plotting).

On the Raspberry Pi, rpi-lgpio is compiled from source, so install the build dependencies once before the first uv sync:

bash
sudo apt install -y swig liblgpio-dev

To add a dependency: uv add <package> (commit both pyproject.toml and uv.lock).

Subsystems

Each subsystem has its own setup instructions:

  • Robot controller (gamepad + kinematics + SPI): controller/README.md
  • IMU driver and wiring/calibration: IMU/README.md
  • STM32 firmware: open the relevant .ioc project in STM32CubeIDE (each project directory is self-contained with CMake presets for building outside the IDE).
  • PCB designs: open the .kicad_pro files in KiCad.
  • 3D models: open the .FCStd files in FreeCAD; .3mf files are ready to slice/print.

Parts

21
QtyValueFootprintReferences
430kResistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolderR4, R5, R6, R7
3100nCapacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolderC1, C3, C4
210kResistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolderR2, R3
2Conn_01x02_SocketTerminalBlock:TerminalBlock_MaiXu_MX126-5.0-02P_1x02_P5.00mmJ1, J2
2JumperJumper:SolderJumper-2_P1.3mm_Open_RoundedPad1.0x1.5mmJP1, JP2
2TestPointTestPoint:TestPoint_THTPad_D1.5mm_Drill0.7mmTP1, TP2
1100uCapacitor_THT:CP_Radial_D6.3mm_P2.50mmC2
1200mcurrent_shunt:2512_shuntR1
1Conn_01x05_PinConnector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_VerticalJ3
1HT7K1401Package_SO:HSOP-8-1EP_3.9x4.9mm_P1.27mm_EP2.41x3.1mmU1
1LOGOLOGOG***
1OPAMPPackage_SO:SOIC-8_3.9x4.9mm_P1.27mmU2

Similar boards

  • 2 layers28.3 × 39.8 mmLevelShifter, the printed circuit board in 3D

    LevelShifter

    gusmanb/logicanalyzer

    24 channel, 100Msps logic analyzer hardware and software

    21 parts5.1kGPL-3.0
  • 2 layers171.2 × 72.9 mmAmiga gfxcard before pour, the printed circuit board in 3D

    Amiga gfxcard before pour

    mntmn/amiga2000-gfxcard

    MNT VA2000, an Open Source Amiga 2/3/4000 Graphics Card (Zorro II/III), written in Verilog

    21 parts1k
  • 2 layers93.9 × 46 mmRectifier, the printed circuit board in 3D

    Rectifier

    rene-dev/stmbl

    AC Servo Driver for STM32F4

    21 parts990GPL-3.0
  • 2 layers45.5 × 42.9 mmEsphome han reader, the printed circuit board in 3D

    Esphome han reader

    hackclub/OnBoard

    💡 Join 1,000 teenagers and make your first PCB with a $100 grant!

    21 parts915
  • 2 layers31.8 × 14.5 mmEsp prog, the printed circuit board in 3D

    Esp prog

    drandyhaas/KiCadRoutingTools

    A set of Python/Rust tools to aid routing in KiCad

    21 parts744MIT
  • 2 layers23.5 × 15.8 mmQuiverAttachPCB, the printed circuit board in 3D

    QuiverAttachPCB

    Arrow-air/project-quiver

    Project Quiver documentation, designs, and project artifacts.

    21 parts617CERN-OHL-S-2.0
  • 2 layers69.9 × 41.3 mmHeaterMeterLCD, the printed circuit board in 3D

    HeaterMeterLCD

    CapnBry/HeaterMeter

    HeaterMeter and LinkMeter Arduino BBQ Controller

    21 parts557MIT
  • 2 layers161.3 × 111.8 mmDoj, the printed circuit board in 3D

    Doj

    kelu124/echomods

    Open source ultrasound processing modules and building blocks

    21 parts463

Questions

How big is the Ht7k1401 breakout PCB?

It measures 30 × 35 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Ht7k1401 breakout use?

21 parts, built around the HT7K1401. 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 Ht7k1401 breakout KiCad files?

From the nthuee822/project_meatball repository on GitHub, at the commit this page was made from: the board is hardware/ht7k1401_breakout/ht7k1401_breakout.kicad_pcb and its schematic hardware/current_sense_simulation/current_sense_simulation.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Ht7k1401 breakout design in my own project?

Its repository states no licence, so its author keeps all rights: ask nthuee822 before reusing the design.