Image credits and source versions

Creator base-PCB render, October 2023 ↗ · Scott Bezek · Apache-2.0 electronics and documentation
Creator screen-PCB rear render, October 2023 ↗ · Scott Bezek · Apache-2.0 electronics and documentation

View the creator’s animated exploded model (v145) ↗

CAIBI ASSESSMENT

SmartKnob

CAIBI VERDICTBUILD FOR THE EXPERIENCE

An open haptic control knob that uses a brushless gimbal motor and magnetic encoder to create software-defined detents, endstops, springs and other tactile behaviours.

See what the build involves Original source ↗

Build or buy?

Compare the documented build with the purchase reference.

Build it yourself

Known parts cost£74–£148Build total not establishedCreator allowance; complete BOM total not tallied

Time: Time-consuming advanced build
Difficulty: 5/5
Physical processes: PCB fabrication · SMD soldering · 3D printing · ESP32

See build requirements →

Purchase reference

Buy price referencePrice not checkedNo priced alternative recorded

Check the source for the exact model, availability and what is included.

Check comparison evidence →

Purchase comparison not yet priced

What the prices cover

The creator explicitly says the total is not yet fully tallied, but estimates a single build is probably under $200 and likely around $100 to $150 depending on fabrication and minimum-order quantities.

Includes: PCB/electronics; Motor/display; Printed mechanical parts.

Not included: Advanced soldering/rework tools; Minimum-order waste; Shipping from multiple suppliers.

Build evidence recorded 4 Sep 2026. Currency conversions are approximate.

SmartKnob is primarily an open haptic input platform. Consumer knobs and dials do not provide a sufficiently similar mechanical, haptic and development surface for a savings claim.

BUILD AT A GLANCE

Source view and main parts

Check the source ↗

**Creator base-PCB render, October 2023**Scott Bezek · Apache-2.0 electronics and documentationSource and version ↗

SmartKnob · Scott Bezek ↗

PHYSICAL BUILD8 key parts or groups

No.	Source specification
01	Base PCB
02	Screen PCB
03	ESP32 control electronics
04	Motor driver and angle sensor
05	Hollow-shaft gimbal motor
06	Round LCD and watch glass
07	Precision printed mechanics
08	Soldering and assembly supplies

Full source specifications

SmartKnob View base PCB, ordered at the specified 1.2 mm thickness with white solder mask
SmartKnob screen PCB, also specified at 1.2 mm thickness
ESP32-PICO-V3-02 based control electronics and very small-pitch surface-mount components
TMC6300 motor driver and magnetic angle-sensing hardware from the stable BOM
Recommended hollow-shaft brushless gimbal motor
240 x 240 GC9A01 round LCD and 39.5 mm watch glass
Six precision printed mechanical parts, preferably from the stable mechanical release
Solder paste, stencil, hot-air or reflow equipment, flux, microscope or strong magnification, and fine assembly tools

TOOLS / PROCESSES4 involved

PCB fabrication
SMD soldering
3D printing
ESP32

The real-world work

YOU STILL HAVE TOThe real-world work

Order PCBs and parts
Reflow or hot-air solder fine-pitch components
Print precision parts
Assemble motor and display
Calibrate and debug hardware

THE BUILD SEQUENCE

How it comes together

1Preparation

Choose stable artifacts before ordering
Do not order from the auto-generated master BOM and Gerbers simply because they are newest. The creator labels those artifacts untested and directs builders to tested release assets for stable hardware.
AI + YOU
Order the two PCBs and precision parts
Order the base and screen boards at the documented 1.2 mm thickness, source the recommended motor and electronics, and print or outsource the six mechanical parts. The published examples use MJF nylon where tight tolerances and surface finish matter.
YOU
Assemble the fine-pitch electronics
Populate the base and screen PCBs using a stencil, reflow or hot air where appropriate. The TMC6300 is especially small and has a bottom pad. This is advanced electronics assembly, not a beginner soldering exercise.
YOU

2Build and assembly

Route the display wiring through the rotor
Assemble the hollow-shaft motor, screen platform, glass and display while fitting the required wiring through limited internal space. The source specifically notes that eight wires must pass through the centre and recommends very fine wire.
YOU
Flash a known firmware build and calibrate
Bring the ESP32 firmware up using the documented environment and complete motor and sensor calibration before adding custom behaviour. AI can help trace build errors and code paths, but measurements and motor behaviour must be verified on the actual hardware.
AI + YOU

3Configure and test

Debug one subsystem at a time
Treat display, encoder, motor drive, press sensing, LEDs and USB communication as separate systems until each works. Independent builder evidence confirms that debugging is a substantial part of a successful first build.
AI + YOU
Create the interaction you actually want
Once the baseline works, change virtual detents, endstops, spring behaviour, display UI or host integrations. This software-defined physical feel is where AI can add the most value without pretending it assembled the device.
AI + YOU

Benchmark this project

Use the SmartKnob prompt. Compare what different models deliver, then add what happened when you tried it.

Try this benchmark

View the project prompt

CAIBI adaptation · Prompt 1.0 · Project source

Prompt for SmartKnob

CAIBI project benchmark: SmartKnob
Prompt version 1.0

Help me build SmartKnob using the existing creator project at https://github.com/scottbez1/smartknob. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- An open haptic control knob that uses a brushless gimbal motor and magnetic encoder to create software-defined detents, endstops, springs and other tactile behaviours.
- Build context: SmartKnob View base PCB, ordered at the specified 1.2 mm thickness with white solder mask; SmartKnob screen PCB, also specified at 1.2 mm thickness; ESP32-PICO-V3-02 based control electronics and very small-pitch surface-mount components; TMC6300 motor driver and magnetic angle-sensing hardware from the stable BOM; Recommended hollow-shaft brushless gimbal motor; 240 x 240 GC9A01 round LCD and 39.5 mm watch glass; Six precision printed mechanical parts, preferably from the stable mechanical release; Solder paste, stencil, hot-air or reflow equipment, flux, microscope or strong magnification, and fine assembly tools.
- Where AI helps: Firmware investigation, Haptic behaviour changes, Host integrations, Debugging support, CAD and enclosure iteration.
- Physical work: Order PCBs and parts, Reflow or hot-air solder fine-pitch components, Print precision parts, Assemble motor and display, Calibrate and debug hardware.
- Main limitation: The creator explicitly says SmartKnob View is not a mature plug-and-play project. It requires very small-pitch surface-mount soldering, delicate assembly and an expectation of hardware and firmware troubleshooting.

Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so.

Provide one practical build package:
1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications.
2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed.
3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability.
4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting.
5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions.
6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations.

Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why.

Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.

Open and copy prompt →

Benchmark results 0

No reviewed results yet for SmartKnob. Add the first result →

AI IN THIS PROJECT

Get AI help on this build

CAIBI · AI CAN HELP

AI can help with

Firmware investigation
Haptic behaviour changes
Host integrations
Debugging support
CAD and enclosure iteration

CAIBI · AI CAN'T DO

You still need to

Order PCBs and parts
Reflow or hot-air solder fine-pitch components
Print precision parts
Assemble motor and display
Calibrate and debug hardware

Original source AI use and prompts

SOURCEThe original project does not publish an AI prompt

The prompts below are CAIBI helpers for this build. They are not presented as instructions from the creator.

CAIBI STARTING PROMPTS

Copy a prompt for this build

Each prompt tells AI to keep the original project source as the reference and to flag anything you must verify on the real build.

Ways to take it further

AFTER THE FIRST BUILD

Ways to take it further

No-screen closed-top versionCustom host controlsVideo editing jog wheelHome automation controllerAlternative haptic profilesCustom enclosure and mounting

More routes and resources

OTHER WAYS TO GET THERE

You do not have to follow one route.

ORIGINAL BUILDFollow the creator route

Use the published files and instructions as the baseline.

OUTSOURCE A PROCESSGet specialist fabrication done

You do not necessarily need to own every capability used here: PCB fabrication, SMD soldering, 3D printing, ESP32.

ALTERNATIVE PROJECTClawd Mochi

A small ESP32-C3 desk companion with animated faces, web controls and a published low-cost parts list.

REVIEWED RESOURCES

Useful places beyond the main source

GITHUB REPOSmartKnob

Canonical hardware, firmware, CAD and release source. The creator distinguishes stable releases from untested master artifacts.

FILESSmartKnob stable releases

Use tested release assets for PCB and mechanical fabrication rather than assuming the latest generated master artifacts are build-ready.

DOCSSmartKnob interactive demo

Creator Web Serial demo for a calibrated SmartKnob, useful for proving the baseline control path before custom integrations.

COMMUNITYIndependent SmartKnob build report

Independent 2024 build account covering sourcing, printed parts, assembly and debugging from the perspective of a builder learning the required electronics skills.

COMMUNITYNanoFOC DevKit alternative

Open third-party FOC haptics development board recommended by the SmartKnob creator for people who want to experiment without fabricating the full View hardware.

SOURCE · CAIBI · BUILDERS

What supports the verdict

SOURCEScott Bezek

Canonical source remains public and unarchived, but the creator explicitly describes SmartKnob View as under active development and not recommended for general use. Stable release artifacts should be used instead of the latest auto-generated master artifacts.

Open source ↗

CAIBIBUILD FOR THE EXPERIENCE

It is an unusually capable physical interface whose feel is defined in software. AI can help understand the control code, create behaviours and debug integrations, but the value only appears after a difficult electronics and mechanical build works reliably.

Evidence: Strong

BUILDERSNo published reports yet

Actual time, cost, changes and outcomes appear here after submitted builds are reviewed.

Be the first builder to report ↓

Leave a build review

HAVE YOU MADE THIS?

Leave a build review.

First-hand evidence improves the assessment

What we want to know

What happened when you actually tried to make it.

Did it work?
Actual time and cost
What did you change?
What was harder than the source suggested?
Would you build it again?