TL;DR: I built a satellite antenna rotator on a hobbyist budget using PA3AXA and PE1CKK's 3D-printed az/el design, an Arduino Nano and DB8LE's firmware. It speaks the Yaesu GS-232 protocol, so Hamlib's rotctld and Gpredict drive it from PC. It carries my M1GEO dual-band Moxon/Yagi on a camera tripod and followed a low ISS pass in an indoor test. The things that cost me time, all covered below: centr the 10-turn pots with a meter instead of counting turns, a negative azimuth reading breaks Hamlib, the firmware's LCD code has a bug that leaves the screen blank, and there is no stop command.
Total cost about $100-125
LMK if you have any questions.
Why I built it
I wanted hands-free satellite tracking and I didn't wanna pay a ton of money for a commercial rotator, which costs several hundred dollars at the very least. The answer was PA3AXA and PE1CKK's 3D-printed az/el rotor.
It carries my M1GEO dual-band Moxon/Yagi on a roughly 7/8 inch dowel, sits on a camera tripod, and runs from a 12 V battery. An Arduino Nano emulates the Yaesu GS-232 protocol, so Hamlib's rotctld can drive it and Gpredict can track with it.
Parts (Mostly from Amazon)
Controller
ALMOCN Arduino Nano V3 with a screw-terminal shield (Saves a bunch of soldering!)
L298N dual H-bridge motor driver
DIYables 16x2 I2C LCD
Four 6 mm tactile switches for manual jog (up, down, left, right) from the adafruit parts pal.
1N4148 diodes, 560 ohm resistors and a 10 uF capacitor from RST to ground adafruit parts pal.
Mechanics
2 x QWORK JGY-370 12 V, 10 rpm worm-gear motors
2 x Taiss 3590S 10-turn, 10k ohm potentiometers for position feedback
uxcell 6707-2RS bearings (35 x 44 x 5 mm)
M3 and M4 stainless hardware (assorted but you need a few 50MM)
Everything printed in Overture PETG on a Bambu A1
Antenna and support
M1GEO dual-band Moxon/Yagi on a wooden dowel
A camera tripod and a printed two-piece clamp that holds the dowel and bolts to the elevation plate
A 12 V battery for the motors
Credits and links
The printed rotor is by PA3AXA and PE1CKK (PE1CKK's page, Libre Space thread). The firmware is DB8LE's pe1ckk_rotor_software, built on PE1CKK and W9KE's SimpleSat. On the PC side I use VS Code with PlatformIO, Hamlib, Gpredict and PuTTY on Windows.
The build
I printed the rotor in PETG, pressed in the bearings, mounted the motors and set the two 10-turn pots in their slots.
The wiring is simple:
Both pots take 5 V and ground from the Nano's 5 V rail. The azimuth wiper goes to A0 and the elevation wiper to A1.
Nano pins D7 to D10 (elevation up and down, azimuth left and right) go through 560 ohm resistors to the L298N inputs IN1 to IN4.
The jog switches pull those same L298N inputs low through 1N4148 diodes. That means the jog buttons drive the motors directly and never pass through the Nano. This matters later.
The 12 V battery feeds the L298N, whose 5 V terminal powers the Nano. A shared ground ties it together.
The LCD sits on A4 and A5.
I designed and printed my own controller enclosure with the LCD and a four-button jog pad on the lid it's not perfect (switches glued in. The two-piece boom clamp bolts to the elevation plate's four-hole 50 x 50 mm pattern.
Firmware and software on Windows
Flash the Nano from VS Code with PlatformIO (board nanoatmega328; use nanoatmega328new if you get a sync error). Take the Nano out of the shield first, because the 10 uF reset capacitor blocks uploading in circuit. Never seat or remove the Nano with USB or 12 V connected. With the capacitor in place, the controller doesn't reset when a program opens the serial port.
Leave homing off. //#define startUpHome stays commented out until calibration is finished.
Raw check with PuTTY. Choose Serial, your COM port and 9600, then type C2 and Enter. The controller answers with something like +0180+0180, which is azimuth then elevation.
Start Hamlib's rotctld. The firmware speaks Yaesu GS-232A, so use model 601:
.\rotctld.exe -m 601 -r COM16 -s 9600 -t 4533 -vv
Test it from a second window with .\rotctl.exe -m 2 -r localhost:4533, then type p.
I run with Hamlib's default limits. If you want guard rails, add --set-conf=min_az=1,max_az=359,min_el=2,max_el=90 to the command.
Two small traps: PowerShell won't run a program from the current folder without the .\ prefix, and only one program can hold the COM port at a time. The firmware README also has a typo in the limits (max_az-359), which should be max_az=359.
Calibration: center the pots with a meter
The firmware maps the pot's whole range to 0 to 360 degrees, so one full turn of a 10-turn pot is 36 degrees on the reading. Mid-travel, half the supply voltage at the wiper, reads about 180.
Don't count turns by hand. I set the pots by counting five turns, and the azimuth ran out of travel near 320 degrees. I then re-centered the azimuth pot with a meter, and it now travels its whole range without stalling.
Power the controller with the pot's pinion gear off. Measure the 5 V rail first rather than assuming 5.00.
Put the meter between ground and the wiper and turn the shaft until it reads half the rail, about 2.50 V.
Park the rotor at its mid-travel mark and refit the gear without turning the shaft. One tooth of the 10-tooth gear is 3.6 degrees.
Leave _azAdZeroOffset at 0. Use _elAdZeroOffset only to trim the elevation. Offsets are in hundredths of a degree, and a positive value lowers the reading:
new offset = old offset + (reading - true angle) x 100
I paced a phone inclinometer on the boom plate for the true angle, and my elevation offset ended up at 18040.
Azimuth center is south. With the pot centered, mid-travel is 180, which is true south, and north sits at the ends of the pot. A phone compass is unreliable indoors, so finish the south alignment outside. Connecticut is about 13 degrees west, so true south reads about 167 on a magnetic compass.
Things that bit me
Elevation ran away on the first P command. I told it to go from 45 to 50 degrees and it kept going until the reading hit -43. The jog buttons drive the L298N directly, so a jog that works proves the motor and pot agree, but says nothing about whether the Nano's own outputs (D7 to D10) are wired to the right inputs. After any wiring change, test both a jog and a small P move on every axis. If only the automatic move is backward, swap that axis's Nano-side pair (D7/D8 or D9/D10). If both jog and automatic are backward, swap the motor leads. Both of my motors needed their leads swapped. I suspected the wiring for the runaway too, but I now think it traced back to the pot setup.
A negative reading breaks Hamlib. The firmware pads a small negative angle into a malformed reply (+00-2), and rotctl throws a protocol error. Zeroing the azimuth at an arbitrary spot with a big offset puts it right on that edge. Keep the azimuth offset at 0 and centre the pot instead.
The LCD stayed blank after the banner. The firmware declares a second, local lcd object inside setup() that shadows the global one. The local copy draws the banner, but the global copy used by every later update never gets initialized, and its backlight flag defaults to off. Deleting that one line fixes it. The elevation and azimuth numbers are also hard-coded to 90.0 and 100, so I removed those two lines. The screen now shows live readings, and I added my own text.
There is no stop command. The firmware ignores everything except C2 and W, so Hamlib's stop command does nothing. Pulling the 12 V plug is the stop, so keep a hand near it for the first moves.
Gpredict's Track box was grayed out. Engage the rotator first, and Track becomes available. Gpredict also only sends positions while the satellite is above the horizon, so a satellite below the horizon looks like a rotator that ignores it.
Testing indoors with Gpredict
You can check the whole chain without waiting for a pass.
Manual moves first. Open rotctl against the running daemon and send small P moves, for example P 0 50. The axis should move, stop within about 1 to 2 degrees, and p should match. Keep a hand on the battery plug.
Add the rotator in Gpredict under Edit, Preferences, Interfaces, Rotators: host localhost, port 4533, with limits that match your rotctld command.
Engage, then Track. In Antenna Control, pick the satellite and the rotator, set Tolerance to 2 degrees, and click Engage. The -vv window will show the position commands scroll by.
Simulate a pass. From the module's menu open the Time Controller and set the time a few minutes before a pass starts, at normal speed. The satellite rises in the simulation and Gpredict drives the rotor through the pass.
Pick a pass that peaks between about 25 and 60 degrees and doesn't cross north. Passes that peak near 90 degrees swing the azimuth very fast, and a pass through north makes the rotor unwind nearly a full turn.
Before any of that, check mechanical clearance. A long boom tail swings down toward the tripod head as elevation rises, so sweep it slowly and cap your maximum elevation below the point where anything touches. On my tripod it cleared through the full range, so I run no cap.
Where it stands
It's assembled and wired, the antenna is mounted, the firmware is flashed, and both axes move under jog and under rotctl. The pots are centered with a meter, the LCD works, and the controller talks to Hamlib.
I've tracked a low ISS pass indoors, pointing the antenna around the room, and it followed without any problems. I couldn't get outside in time to align to true south, so next I'll do that outdoors and track a higher pass in clear sky. I'll post an update with the results. Let me know if you have any questions.
73, Mike K1MRE