-
The tennis feeder's wrongly advised instant contact, recaptured: today's firmware reads it as 0
One simulated build in 72 told builders to flash a 3.5 ms contact for an instant one. Unrounded it was never advised; recaptured today, 0 of 72.
-
The tennis feeder's one wrong contact-time advice came from rounding to whole ppm
One simulated build with an instant take was told to set a 3.5 ms contact time. Its frame rounded 6.81 and 4.32 ppm to 7 and 4. A guard now catches it.
-
The tennis feeder's wheels recover from a ball better when the loop trusts what it learned, but only one way
Scaling the wheel loop's gains by the learned plant gain failed a held-out set; capped to soften only, it cut ball undershoots 18 to 13 on a fresh set.
-
Four magnets on the tennis feeder's wheel: a pre-registered test that closed the idea
More tach pulses a revolution looked like the fix for short ball contacts. On 256 simulated balls it missed its own bar, and made the instant-take drop worse.
-
Two sessions built the same tennis-feeder fix in one morning, so one became the other's replication
Two agent sessions built the same wheel-loop fix in parallel. The second dropped its copy and tested the shipped one on a grid four times larger.
-
One more grid point in the tennis feeder's contact-time survey, and the test it had to pass first
Adding 7 ms to the feeder's contact-time grid put 185 of 216 held-out builds within 0.5 ms against 149, for 11% more survey time. It ships.
-
The tennis feeder's one-wheel verdicts: too rare in simulation to settle, so the rule left it alone
Six fresh simulated sets, 432 drills: only 6 rested a contact-time verdict on one informative wheel, so the pre-registered rule kept the minimum off.
-
The tennis feeder's honest bound gets a 2 ppm floor, and a fresh test says it now covers every build
Whole-ppm rounding made the feeder's contact-time bound too tight on quiet tachs. A 2 ppm floor, set before a fresh test, covered 48 of 48 builds.
-
The tennis feeder's contact-time report now goes in tenths of a ppm: five right answers back
One extra byte on the feeder board's survey frame: on 2,964 stored simulated drills the rounding guard now withholds 1 right verdict instead of 6.
-
The tennis feeder's short contacts that read 0: no ball saw them, so it now says how little it knows
Short simulated contacts read as instant because no ball's contact crossed a tach edge. The feeder now names the longest contact it can't rule out.
-
The tennis feeder's short contacts weren't invisible, and the fix missed its own test by one build
Short ball-on-wheel contacts were visible to the feeder's fit all along. A new grid cut large misses from 11 to 3, then failed its rule on one build.
-
The tennis feeder's short-contact grid passed its second test, with the rule fixed first
Swapping the feeder's 2 ms candidate for 1.5 and 2.5 ms put 49 of 66 held-out simulated builds within 0.5 ms against 39. It ships.
-
Releasing the e-stop should not restart a ball machine
The open tennis feeder now needs RESET pressed at the machine after an e-stop. One relay and one push button do it, with no ESP32 pin needed.
-
A tennis drill builder that knows what the ball machine can do, and how long it needs between balls
Open Tennis Robots' page now builds drills: every ball checked against the machine, the time it needs between balls estimated, and a drill.json to run.
-
How much tach noise the tennis feeder's contact-time survey can take
On 144 simulated drills the feeder's contact-time survey faded at half a microsecond of tach jitter and was blind from 1.5 us. A new command reads a real tach.
-
The fix that worked for one survey didn't help its sibling
A spline fixed our tennis machine's ESC-lag pick. On the ball-contact survey it tracked the residual better but landed no closer to the truth.
-
Send a drill from your phone to the tennis feeder, with a Stop button that needs no password
The drill builder can now hand a drill to the feeder's Pi. Why it opens the Pi's own page instead of calling it, and why Stop needs no key but Start does.
-
Fixing one bias in the tennis feeder's contact-time survey exposed a second one hiding under it
Stretched take offsets moved 7 ms contacts off the grid's end on 6 of 6 fresh builds and showed the survey's parabola pick reads about half a millisecond short.
-
The tennis feeder's board now surveys how long a ball touches its wheels, with a margin it had to earn
The feeder's ESP32 now refits each calibration ball at seven contact times. Spread contacts were named within 1 ms; a margin keeps instant ones out.
-
The tennis feeder's big take misses come from the fit, not the grid
A pre-registered test of a finer contact-time grid on three fresh simulated sets: 14 large misses against 12, so the grid stays. Most misses were shared.
-
The tennis feeder's contact-time survey was trimming away the only balls that could see the contact
A take inside one revolution fits like an instant one, so only balls straddling an edge count, and the outlier trim dropped them: 14 of 54 named, then 42.
-
The tennis feeder read ball contact times too long because its four-part model bunched up
Four equal shares of a half-sine carry 16% less spread than it, so the feeder read contact times 9% long. Stretching them fixed it held out.
-
A longer look helps the tennis feeder's drop reading, but only when its tach is noisy
Reading 24 revolutions after each ball instead of 8 cut the feeder's drop error on a jittery tach by a quarter, and did nothing on clean wheels.
-
The tennis feeder's ESC-lag survey was covering for a coarse grid
The feeder's board named a 12 ms ESC lag where there was none and 24 ms for 50. The cause was a skipped refinement, found by refitting its inputs.
-
The tennis feeder's ESC survey gets a 150 ms point, and a confidence check that failed its held-out test
An untold 150 ms ESC read 169-195 ms on the feeder's survey; a seventh grid lag fixes it. A check meant to flag unreliable picks did not hold out.
-
The tennis feeder's ESC survey had the right answer and misread it
The feeder board's ESC-lag survey read short lags about 10% low. The parabola was at fault, not the data. A spline took held-out hits from 27 to 39 of 44.
-
A finer clock made the tennis feeder's contact-time survey worse, and showed why it worked
Keeping the ESP32 capture's 12.5 ns ticks instead of whole microseconds halved the fit's residuals and lost the held-out survey: 14 of 54 against 43.
-
The tennis feeder's long ESC lags weren't unknowable: its survey only looked at 8 revolutions
Long ESC lags looked impossible to tell apart from a slow wheel. The fit was reading 8 revolutions; with 16, held-out drills all came within 15%.
-
The tennis feeder's nine-point take grid tied on fresh data, so the old grid stays
A finer contact-time grid looked better on the sets that suggested it. On three fresh sets with fairer takes it tied, so the old grid stays.
-
The tennis feeder's phantom contact time came from its own search, not the physics
Balls that left the feeder's wheels instantly kept being read as 2.5 ms contacts. The cause was a search that sometimes lands in the wrong basin.
-
The tennis feeder's speed-mode ESC needed a ramp and a step train
A drop fit for a speed-mode ESC that models the current-limited ramp: in simulation, drops over 2% off fell from 592 of 768 to 88, loop read from a step train.
-
The tennis feeder's survey queue was mostly tuples
Packing a queued survey's tick logs into arrays cut it from 12.8 KB to 4.0 KB of ESP32 heap, so the feeder board now queues three surveys, not two.
-
The tennis feeder's contact-time survey stops counting the balls that cannot see the contact
Most balls fit every contact time alike and only dilute the verdict. Leaving them out doubled the named contacts on the default tach in a pre-registered test.
-
The tennis feeder's tachometer gets a hardware clock, and its contact-time survey keeps its voice
Timing tach edges with ESP32 MCPWM capture kept the feeder's survey naming 36 of 54 contact times at 1.5-3 us of jitter, where the pin interrupt named none.
-
The tennis feeder's take survey keeps its one-wheel verdicts: a pre-registered minimum failed held out
Counting only informative wheels toward 16 would silence the feeder's contact-time survey; a two-wheel minimum was pre-registered and failed.
-
The tennis feeder's contact-time survey wants the short window its drop reading gave up
Reading 24 revolutions after each ball helped the feeder's drop reading but blurred its contact-time survey: held out, 9 takes named against 12.
-
The tennis feeder's wheel loop fought an ESC that runs its own speed loop
On the simulator, the feeder board's speed loop on top of a speed-mode ESC swung 48 of 144 wheels by over 1%. The fix, and a drop fit that failed.
-
The tennis robot's tests asked the same circuit question 1,330 times
70% of a CAD suite's contactor simulations repeated earlier ones exactly. A cache keyed on the numbers they read cut it from 74 s to 47 s.
-
Why the tennis feeder's slow wheel sat 3.6% low after each ball: its integrator was learning the wrong things
After each ball the feeder's slow wheel overshot 19%, then sat 3.6% low for 2 s. The integrator was learning the ball and the brake. Fixing both cut the wait.
-
A tennis ball is in the wheels for 6 ms, and the feeder's drop reading noticed
Spreading a ball's take over its contact time raised the drop readings' scatter up to sixfold. A contact-time term fixes it; the fit can pick the time itself.
-
The tennis feeder's reading floor was a search grid, not the physics
A ten-times-finer simulator left the 0.3% drop-reading scatter unchanged. The fit's grid for the ball's moment was the floor; one extra solve halves it.
-
The tennis feeder's spin error was there without the jitter
Plants with no tach jitter miss the spin fit by the same 0.5%. Timing every edge exactly barely moved the readings, so the 1 us timer is not the floor.
-
The tennis feeder's unsure marks find the noisy wheels, and weighting them down still doesn't help
The feeder firmware marks wheel readings it is unsure of. On 72 simulated builds the marks found the noisy wheels, but down-weighting them gained nothing.
-
The tennis feeder's wait for slow wheels made one shot in three late
A held-out test kept the feeder's 1,000 rpm fit floor and found its wait for slow wheels made shots up to 1.7 s late. An opt-in fix removed the delay.
-
The tennis feeder's worse result on a jittery tach was one seed's draw
One held-out seed made a firmware setting look worse on a jittery tach. Six seeds, 3,888 wheels and a check of each wheel's fit showed it was chance.
-
A ball machine's 1% speed bias was 0.7 grams of tennis ball
Our open tennis ball machine read its own launch speed 1-2% high on every simulated build. The cause was two ball masses in one codebase.
-
A release timeout that stopped a tennis feeder doing its job
One simulated build always aborted its slow drill at shot 2. The firmware was right to wait. The Pi's flat 2 s release timeout was wrong.
-
Our ball machine weighs each shot by how much its wheels slow, and the lowest revolution hid up to 38% of it
A two-wheel launcher's speed drop measures each ball's momentum. Fitting it to the tach's pulse times halved the speed fit's error in simulation.
-
The textbook fix for a jittery tachometer made our ball machine's spin estimate worse
Tach jitter sits on edge times, so fitting their running sums should beat fitting periods. On our simulator it read the spin worse. Numbers and likely cause.
-
One badly fitted wheel out of 56 told our ball machine its motor controller had no lag
The tennis feeder's ESC-lag survey picked 0 on one build because one wheel fit 30 times worse than the rest. Trimming such wheels fixed every simulated case.