Open MicroManipulator – A sub-micrometer 3D motion control plattform
- ID
- 36875
- Status
- summarized
- Published
- 18 Oct 2026, 7:16 PM
- Fetched
- 19 Oct 2026, 10:08 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/0x23/MicroManipulatorStepper
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.0
- Created
- 19 Oct 2026, 10:08 AM
- Tags
- Audience
- developersvibe_coders
What happened
An open-source hardware project (GitHub 0x23/MicroManipulatorStepper) publishes a build-it-yourself motorized XYZ micro-manipulator that reaches sub-micrometer positioning for optical alignment, electronic component probing, and microscopy. It uses off-the-shelf stepper motors driven by a 30 kHz closed-loop controller, and a 'magnetic gearing' trick that multiplies low-cost magnetic rotary encoder resolution by 30, giving steps down to 50nm — though the README explicitly warns absolute accuracy is significantly worse than that resolution figure. Control is via plain G-Code over USB serial, and the repo ships firmware with a full look-ahead motion-planning stack, BOM, datasheets, a hw_config.h to adapt to your build, PlatformIO upload instructions, and a calibration/setup guide (2.1k stars, 276 forks, 240 commits, 174 points / 13 comments on HN).
Why it matters
The 50nm number is a step size, not accuracy — the README itself says absolute accuracy is significantly worse, so anyone quoting this as a precision instrument spec is misreading it; if you need positioning, budget for external metrology rather than trusting the encoder. The practical win is the interface: G-Code over USB serial plus an open firmware stack means you can drive it from an existing toolchain instead of buying a closed controller, and the BOM + hw_config.h means you can cost it against local part availability before committing. There is no Malaysian or Southeast Asian angle in this text — relevance is purely for people who build or integrate hardware.
Discussion angle
Resolution vs accuracy: the project advertises 50nm steps but concedes absolute accuracy is much worse — a good live example of why 'resolution' on a spec sheet is not the number that decides whether a build works, and what you'd have to add (external metrology, closed-loop verification) to close the gap.