Skip to the content
2 layers155 × 93 mmMotorized faders, the printed circuit board in 3D

RP2040 board (Pico-clone with RTL8720DN WiFi — GP4/GP5 not exposed) + TB6612FNG motor drivers + Alps motorized faders.

Size
155 × 93 mm
Copper layers
2
Thickness
1.6 mm
Parts
66
Nets
65
Pads
272
Tracks, vias
765, 82
Pours
2
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
21 Jun 2026
Updated
7 Nov 2026

Overview

Motorized faders is an open-source printed circuit board by Ilosariph, from the Ilosariph/motorized-faders repository on GitHub. It is a 2-layer board of 155 × 93 mm with 66 parts on 65 nets, routed with 765 tracks and 82 vias.

It is built around the MCP3208-BI/P and B3F-4050. It belongs with the RP2040 boards of this library.

Main components

2

README

README.md

Motorized Fader Controller

RP2040 board (Pico-clone with RTL8720DN WiFi — GP4/GP5 not exposed) + TB6612FNG motor drivers + Alps motorized faders.

Two builds exist:

2-fader breadboard4-fader PCB
Faders2x RS60N11M9 (60 mm, 5 kΩ)4x RSA0N11M9 (100 mm, 10 kΩ)
ADCRP2040 internal (GP26/27)MCP3208, 12-bit SPI
Drivers1x TB6612FNG breakout2x TB6612FNG
Displaysnone4x SSD1306 128x64 SPI
Buttonsnone4 per-fader + 2 general, ADC ladder
Motor rail10 V bench supply9 V USB-C PD trigger
Docsthis filepcb_design.md, firmware.md

The wiring below is the 2-fader breadboard build. For the 4-fader PCB see docs/pcb_design.md (hardware) and docs/firmware.md (protocol, mute, displays, buttons).

Firmware in pico/ is the 4-fader version. It needs the MCP3208 and will report RAIL:fail without the PD rail; the 2-fader build is kept in git history.


Wiring

Power

FromToNotes
10V supply +TB6612FNG VMMotor power
10V supply −Common GND
Pico 3.3V (pin 36)TB6612FNG VCCLogic power
Pico GND (any)TB6612FNG GND
Pico GND (any)10V supply −Common ground — important!

The Pico gets power from USB. The 10V supply powers the motors only. All grounds must be connected together.


Fader → TB6612FNG (Motor)

Fader terminalConnect to
Terminal 1 (GND)GND
Terminal 3 (3.3V)Pico 3.3V
Terminal ATB6612FNG AO1 (fader 1) or BO1 (fader 2)
Terminal BTB6612FNG AO2 (fader 1) or BO2 (fader 2)

If the fader moves in the wrong direction, swap A and B.


Fader → Pico (Sensing)

Fader terminalPico pinNotes
Terminal 2 (wiper)GP26 (fader 1)ADC position feedback
Terminal 2 (wiper)GP27 (fader 2)ADC position feedback

Terminal T (touch) is unused — the firmware detects move completion from the PID state machine (deadband + settle timer), not from touch.


TB6612FNG → Pico (Control)

TB6612FNG pinPico pinNotes
AIN1GP2Fader 1 direction
AIN2GP3Fader 1 direction
PWMAGP6Fader 1 speed
BIN1GP7Fader 2 direction
BIN2GP8Fader 2 direction
PWMBGP9Fader 2 speed
STBYGP10Driver enable

Note: GP4 and GP5 are skipped — this board does not expose them on the header. If you have a real Raspberry Pi Pico W, you can use the standard GP2–GP8 range instead and update pico/main.py accordingly.


One Fader Only

If you only have one fader connected, the firmware still works — fader 2 will sit at its default setpoint (50%) but won't move since nothing is connected. No code changes needed.

Just leave BIN1, BIN2, PWMB, BO1, BO2, and GP27 unconnected.


PC Software

Two interfaces. The terminal tool is for bring-up and PID tuning; the extension host is what you actually run day to day.

Terminal tool

bash
pip install pyserial
python host/host.py

Type 50 75 to set fader 1 to 50% and fader 2 to 75%. Type 50 to set fader 1 only.

If the Pico isn't detected automatically, pass the port explicitly:

bash
python host/host.py /dev/ttyACM0      # Linux
python host/host.py COM3              # Windows

Extension host

Binds faders to things on the PC. faders/config.json declares which extension owns which fader:

bash
python -m faders.run

With pulse_sink, each fader controls a PulseAudio/PipeWire sink: move the fader to change volume, change it in pavucontrol and the fader follows, and press the fader's button to mute. The fader's display shows that sink's label and volume — display content comes from whichever extension owns the fader, so it describes whatever that fader actually controls.

json
{"fader": 0, "sink": "sink-music", "min": 0, "max": 100, "label": "Music"}

"source": "source-mic" in place of sink puts an input (e.g. a mic) on the fader the same way. label is optional and defaults to the sink name — worth setting, since real sink names (alsa_output.pci-0000_00_1f.3.analog-stereo) do not fit a 128 px screen.

More sinks than faders → pages: fader 4-7 is page 2, 8-11 page 3 (G2 + F1/F4, x/y on the last screen; entries without fader fill slots in list order). The dict form sets paging and shares keys between entries:

json
"pulse_sink": {
  "paging": true,
  "max": 150,
  "faders": [{"sink": "sink-music"}, {"sink": "sink-comms"}, {"sink": "sink-apps"}]
}

paging: "auto" (default) pages only when a fader is past the last one; true always pages; false never pages and skips entries past the last fader. A/B works either way (tap G2 + Fn). Same for voicemeeter.

Layers and buttons

Plugins are grouped into layers that take turns owning the four faders. Each layer remembers its own fader levels, mutes, screens and creases. Without a layers key every plugin is its own layer (pulse_sink → "Audio", discord_voice → "Discord", home_assistant → "Home", voicemeeter → "Voicemeeter", filter_param → "FX"); to choose, list them:

json
"layers": [
  {"name": "Audio",   "extensions": {"pulse_sink": [...]}},
  {"name": "Discord", "extensions": {"discord_voice": {...}}}
],
ButtonsAction
F1-F4Mute that fader
G1 + F1 / F4Previous / next layer — screens show the name while G1 is held, faders move on its release
G2 + Fn (tap)A/B position swap
G2 + F1 / F4 (hold 0.4 s)Previous / next page (paged layers: Discord, Home / Audio / Voicemeeter / FX with >4 entries or "paging": true)
Discord

discord_voice puts the other people in your current voice channel on the faders: name on the screen, fader = their local volume 0-200%, fader button = Discord's per-user mute (right-click → Mute; volume untouched). More than four people → pages, shown as x/y on the last screen. Needs the official desktop client (Vesktop/arRPC lack voice RPC) and your own Discord application:

  1. https://discord.com/developers/applications → New Application.
  2. OAuth2 → copy Client ID and Client Secret, add redirect http://localhost.
  3. Config: "discord_voice": {"client_id": "...", "client_secret_file": "/path/to/secret"} (client_secret inline also works; keep the file private).
  4. Start the host, click Authorize in the Discord popup once. The token is cached in ~/.local/state/motorized-faders/discord_token.json.
Home Assistant

home_assistant binds faders to lights and covers over HA's WebSocket API:

  • Light: fader = brightness, dragged to the bottom = off; button = off / back on at its brightness. Turned off in HA → fader parks (muted).

  • Cover: "attribute": "position" (default) or "tilt". Two faders on one blind give position and slat angle. Button = close (0) / restore. Covers get one command when the fader comes to rest; the fader follows HA once the cover stops moving.

  • Switch (switch.*, input_boolean.*): fader bottom = off, above = on; button toggles.

Entries fill the faders in order; more than four → pages (hold G2 + F1/F4, x/y on the last screen). null leaves a fader empty, e.g. to keep a blind's pair on one page. Needs a long-lived access token (HA profile → Security):

json
"home_assistant": {
  "url": "http://homeassistant.local:8123",
  "token_file": "~/.config/motorized-faders/ha-token",
  "faders": [
    {"entity": "light.desk", "label": "Desk"},
    null,
    {"entity": "cover.office", "attribute": "position", "label": "Blinds"},
    {"entity": "cover.office", "attribute": "tilt", "label": "Slats"}
  ]
}

token inline also works (keep the config private); "verify_ssl": false for a self-signed https URL. "follow": false on an entry ignores the values HA reports for it (the fader alone is the truth) — for a device whose reports are wrong, e.g. a cover stuck at 1% until its travel is calibrated.

Voicemeeter (Windows)

voicemeeter binds faders to Voicemeeter (Basic, Banana or Potato) input strips and output buses, the way pulse_sink binds them to sinks: the fader sets the gain in dB, gain changed in Voicemeeter moves the fader, and the fader button toggles the strip's/bus's mute (both ways). Screens show the label set in Voicemeeter (or label) and the gain.

json
"voicemeeter": [
  {"fader": 0, "strip": 0, "label": "Mic"},
  {"fader": 1, "strip": 3},
  {"fader": 3, "bus": 0, "min": -40, "max": 0}
]

strip / bus are 0-based, left to right as in Voicemeeter's window. min/max are dB (default -60 / +12, the full slider). More than four entries → pages, and "paging" works as for pulse_sink. Talks to the Remote API DLL shipped with Voicemeeter via ctypes — only pyserial needed:

powershell
pip install pyserial
python -m faders.run --config my-config.json

Voicemeeter may start after the host or restart; faders resync when it shows up.

PipeWire filter controls

filter_param puts controls of plugins running in PipeWire filter-chain modules (an LSP compressor's threshold, ratio, makeup, a gate's threshold ...) on faders. The fader sets the control, changes made elsewhere move it, the screen shows the value in real units, and the button bypasses the plugin (every fader on that plugin parks while it is off). One detent marks the control's original value.

json
"filter_param": {
  "faders": [
    {"param": "fx-comp-apps:al", "scale": "db",  "min": -40, "max": 0,  "label": "Apps thr"},
    {"param": "fx-comp-apps:cr", "scale": "log", "min": 1,   "max": 10, "unit": ":1", "label": "Apps ratio"}
  ]
}

param is <filter node name>:<LV2 port symbol>, as pw-dump lists it under the node's Props. scale: db for controls that are linear gains (range in dB), log for times and ratios, linear otherwise. More than four entries → pages. Give it a layer of its own (a layer has one set of pages).

Values set from the faders are saved to ~/.local/state/motorized-faders/filter_param.json with the config's original next to each, and put back when PipeWire reloads the filter (restart, reboot). A changed value in the PipeWire config wins over a saved one. motorized-faders-fx status lists them, motorized-faders-fx reset [param ...] restores the originals. "persist": false turns saving off.

The host survives the Pico being unplugged: it waits for the port to come back (it may return as a different ttyACM node), then replays display text, A/B badges and creases, and extensions re-seed fader positions and mute via their on_connect hook. Starting without the Pico attached waits the same way.

NixOS

flake.nix exports the package (nix run .), a dev shell and nixosModules.default, which runs the host as a systemd user service (plugins like pulse_sink need the user's PipeWire session) and grants the logged-in user the Pico's tty via udev uaccess:

nix
{
  inputs.motorized-faders.url = "github:Ilosariph/motorized-faders";
  # in nixosSystem modules: inputs.motorized-faders.nixosModules.default
  services.motorized-faders = {
    enable = true;
    plugins.pulse_sink = [
      { fader = 0; sink = "sink-master"; max = 100; label = "Master"; }
      { fader = 3; sink = "sink-music"; max = 150; label = "Music"; }
    ];
    plugins.discord_voice = {
      client_id = "1234567890";
      client_secret_file = "/run/secrets/discord-faders";  # not in the store
    };
  };
}

plugins keys are module names in faders/extensions/ (checked at eval); each value is one instance config or a list. layers (list of { name; extensions; }) sets explicit layers. Logs: journalctl --user -u motorized-faders -f.

Tests

No hardware needed — the fader is simulated and machine/utime are stubbed:

bash
python3 tests/run_all.py

Files

FileDescription
pico/main.pyMicroPython firmware — copy to Pico as main.py
pico/lib/Device drivers: MCP3208, buttons, SSD1306, screen layout — upload with main.py
host/host.pyPC terminal interface (calibrated 0–100% display)
host/host_raw.pyRaw 16-bit ADC viewer for wiring diagnostics
faders/Extension host — serial transport, button/mute dispatch, plugins
faders/extensions/pulse_sink.pyBinds a fader to a PulseAudio/PipeWire sink
faders/extensions/discord_voice.pyVoice-channel users on the faders: volume, mute, pages
faders/extensions/home_assistant.pyHA lights (brightness, on/off) and covers (position, tilt), paged
faders/extensions/voicemeeter.pyBinds a fader to a Voicemeeter strip or bus (Windows)
faders/extensions/filter_param.pyPipeWire filter-chain plugin controls (compressor, gate ...), saved across restarts
tests/Test suites — run python3 tests/run_all.py, no hardware required
docs/upload.mdHow to flash firmware to the Pico (Thonny + mpremote)
docs/pid_tuning.mdHow to tune the PID controller
docs/firmware.md4-fader firmware — protocol, buttons, mute, displays
docs/pcb_design.md4-fader PCB design — ADC choice, TB6612FNG, BOM
docs/modular_design.mdFuture modular expansion plan (RP2040-Zero modules)

Parts

66
QtyValueFootprintReferences
910kOhmResistor_SMD:R_0805_2012MetricR_BTN_FADER, R_BTN_GEN, R_DISP_RES, R_F1_WIPER, R_F2_WIPER, R_F3_WIPER, R_F4_WIPER, R_SW_F4, R_VM_SENSE_TOP
8Conn_01x08Connector_PinHeader_2.54mm:PinHeader_1x08_P2.54mm_VerticalJ_DISP1, J_DISP2, J_DISP3, J_DISP4, J_MOT_BOB_A_P1, J_MOT_BOB_A_P2, J_MOT_BOB_B_P1, J_MOT_BOB_B_P2
6B3F-4050Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalSW_F1, SW_F2, SW_F3, SW_F4, SW_G1, SW_G2
6TestPointTestPoint:TestPoint_THTPad_D1.5mm_Drill0.7mmTP_3V3, TP_F1_ADC, TP_GND, TP_GNDPWR, TP_SCK, TP_VM1
5100nFCapacitor_SMD:C_0805_2012MetricC_BTN_FADER, C_BTN_GEN, C_DISP_RES, C_MCP3208_VDD_GND, C_MCP3208_VREF_GND
4100nF ceramicCapacitor_SMD:C_0805_2012MetricC_VCC_A, C_VCC_B, C_VM_A_HF, C_VM_B_HF
410nFCapacitor_SMD:C_0805_2012MetricC_F1_WIPER, C_F2_WIPER, C_F3_WIPER, C_F4_WIPER
4Conn_01x02Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ_F1_MOT1, J_F2_MOT1, J_F3_MOT1, J_F4_MOT1
4Conn_01x03Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ_F1_GEN1, J_F2_GEN1, J_F3_GEN1, J_F4_GEN1
2100uF electrolyticCapacitor_THT:CP_Radial_D8.0mm_P5.00mmC_VM_A, C_VM_B
24.7kOhmResistor_SMD:R_0805_2012MetricR_SW_F3, R_SW_G2
2TB6612FNGPackage_SO:SSOP-24_5.3x8.2mm_P0.65mmU_MOT_A, U_MOT_B
12.2kOhmResistor_SMD:R_0805_2012MetricR_SW_F2
13.3kOhmResistor_SMD:R_0805_2012MetricR_VM_SENSE_BOT
1Conn_01x04Connector_PinHeader_2.54mm:PinHeader_1x04_P2.54mm_VerticalJ_PD
1MCP3208Package_DIP:DIP-16_W7.62mmU_ADC
1NetTie_2NetTie:NetTie-2_SMD_Pad2.0mmNT1
1RaspberryPi_PicoModule:RaspberryPi_Pico_Common_THTA1

The 62 most common of 66 parts.

Similar boards

  • 4 layers55 × 85 mmPokodoro, the printed circuit board in 3D

    Pokodoro

    justinjchae/poko

    Poko: a phone-free MagSafe companion. nRF52840 + Zephyr, round display, haptic ring, voice memos, iPhone app, parametric CAD, KiCad.

    52 parts
  • 4 layers100 × 100 mmKvm switch, the printed circuit board in 3D

    Kvm switch

    Rithvik-Vadlamani/kvm-switch

    Four-layer HDMI/USB KVM design with STM32 firmware, supply supervision, and verification evidence

    170 parts
  • 2 layers102 × 45 mmChess clock pcb, the printed circuit board in 3D

    Chess clock pcb

    vekkuli/chess_clock

    This repo contains design and fabrication files for my DIY chess clock project. The main components in the design are

    16 partsMIT
  • 2 layers138.6 × 120 mmHexiLux v1, the printed circuit board in 3D

    HexiLux v1

    ZeusyBoy98/HexiLux

    A custom open-source smart lighting solution, using tiling hexagonal panels. Featuring music sync and home assistant compatibility.

    38 partsAGPL-3.0
  • 2 layers33.5 × 15 mmPanel, the printed circuit board in 3D

    Panel

    marqs85/ossc_pro_hw

    OSSC Pro HW files

    5 parts31CERN-OHL-P-2.0
  • 4 layers100 × 100 mmESP32-Eurorack Audio, the printed circuit board in 3D

    ESP32-Eurorack Audio

    ctag-fh-kiel/esp32-eurorack-audio

    Open source eurorack audio module based on ESP32

    173 parts71
  • 2 layers150.5 × 127 mmEurorack engine, the printed circuit board in 3D

    Eurorack engine

    sinneb/esp32-hvcc

    Heavy compiler (hvcc) sources running on ESP32-DevKitC powered eurorack module

    81 parts29
  • 2 layers100 × 100 mmTroll-8, the printed circuit board in 3D

    Troll-8

    ctag-fh-kiel/troll-8

    Arduino-Based μSynth / μMidiController Development Platform

    94 parts14

Questions

How big is the Motorized faders PCB?

It measures 155 × 93 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Motorized faders use?

66 parts, built around the MCP3208-BI/P and B3F-4050. 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 Motorized faders KiCad files?

From the Ilosariph/motorized-faders repository on GitHub, at the commit this page was made from: the board is motorized-faders/motorized-faders.kicad_pcb and its schematic motorized-faders/display.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Motorized faders design in my own project?

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