Rep5x: Open-Source 5-Axis Printer Retrofit
Rep5x was my master’s thesis, and the thing I spent most of a year on. It’s an open-source five-axis retrofit for consumer desktop 3D printers, released under GPL v3.
Multi-axis printing promises support-free overhangs, smoother curved surfaces, and parts whose layers follow their load paths. It also stays stubbornly inside research labs and industry.
The interesting part is why. Earlier work in the group, by my supervisor Janis Andersons, had already shown that an affordable five-axis retrofit of a consumer FDM printer works. The technology wasn’t the obstacle. A working prototype existed, and almost nobody reproduced it, because doing so meant commercial software, specialist knowledge, and far more effort than the makers it was aimed at could reasonably take on.
So the thesis asked a different question than “can this be built”: why isn’t a working prototype being reproduced, and what does it take to change that. I diagnosed the adoption barriers through Rogers’ diffusion of innovations and the open-source-hardware reproducibility literature, then went and addressed them.
That produced four things:
- a retrofit redesigned to adapt to several common desktop printers, rather than one machine in one lab
- a Marlin fork with native five-axis kinematics
- a suite of browser-based tools replacing the command line and commercial licences with no-install workflows for firmware, setup, printer control and G-code
- the documentation, website and community that let someone actually build it
I evaluated it through a pre-build interest survey, community-driven iteration on Discord, and independent build attempts by other people. The finding: the barrier to multi-axis FDM isn’t the mechanism. It’s the toolchain and the infrastructure around it. Removing the specialist-software dependency, packaging the workflow for non-experts, and building a community where feedback drives the design are what turn a working prototype into something independent makers can reproduce.
The full write-up lives on the academic work page.