Closed Loop Stepper Test Bench with Ball Screw Rail

Nov 17, 2026 Last reply: 12 minutes ago 2 Replies
Jump to replies (2)

Stepper setups usually run open loop, where missed steps just go unnoticed and the motion drifts from where the controller thinks it is. That is the problem this build addresses: Proto G Engineering put together a test bench to compare two closed loop NEMA 17 stepper motors, each coupled to a linear ball screw actuator rail, all driven by an ESP32. Instead of guessing which motor performs better on paper, the bench runs both side by side under identical conditions.



The assembly is nicely thought out. One motor connects to the ball screw shaft through a rigid white 3D-printed coupler, while the second motor rides on the moving carriage with a 3D-printed white pointer flag on its shaft, which makes the relative motion easy to follow. Both motors receive identical step and direction pin signals from a breadboard circuit, so the comparison is fair. The wiring runs off a digital DC benchtop power supply, and the wider workshop includes oscilloscopes, a Fluke multimeter, a Pace soldering station and Prusa-style printers in the background.



During the test cycle the carriage drives forward at 30 microseconds per step and returns at 15 microseconds per step, with both motors running simultaneously. The striking result: motor B operates faster than the other despite the identical signals. That difference is exactly what makes this kind of side-by-side bench valuable.



The open question is why the two motors behave differently under the same inputs. The maker has not given a stated explanation yet, so whether it comes down to internal tuning, firmware or hardware variation is still unresolved. In my view that ambiguity is the whole point of the bench, and I would love to see a follow-up digging into the cause.



Project by Proto G Engineering. Watch it on their YouTube channel:

formatting link


Curious about the control side of this build. With both motors wired to the same breadboard signals, does the ESP32 code send one shared step and direction pair to both, or does each motor get its own pins that happen to be identical? And does the code expose the step timing values, like the 30 microsecond forward and 15 microsecond return speeds, as easy-to-change settings?

From what the maker has shown, both motors receive identical step and direction pin signals from the breadboard circuit, and both run simultaneously during the cycle. The carriage drives forward at 30 microseconds per step and returns at 15 microseconds per step. The maker offers a code link for the ESP32, and says viewers who comment a specific word get sent that code along with component links, so the source should show exactly how the timing values are set.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required