ScorePost

• In/Out's original net-post-only device judged baselines poorly (20–30 mm error in a 2021 test), and its v4 added line devices → the CAD geometry report shows why: from 1.2 m on the post, lines across the view resolve 53–117 mm per pixel, so ScorePost only gives verdicts on lines that run along a camera's view and adds a BaseClip on the side fence for each baseline (2–8 mm per pixel)
• Outdoor courts have no power → an ESP32 runs the e-paper score for about a year per charge (est.); the Pi 5 and cameras switch on only for a Camera match, about 5 matches per 20,000 mAh charge (est.)
• Leagues may not allow electronic calls → ScorePost shows evidence that the players agree to; it never overrides the player's call and is not ITF classified
• Cameras on public courts raise privacy concerns → a 20 s RAM ring buffer, nothing saved unless CHALLENGE is pressed, and ball-only crops on the display
• Pickleball doubles has no referee and forgetting the server number or the score is the commonest argument (pickleball.com, The Dink; 2026 USA Pickleball rules want prompt calls) → RallyCall: one pad per team on the post, one press per rally, side-out and server 1/2 logic tested in-house over 200 rallies, the score called aloud, CHECK when both teams press
• Club cricket rarely has the two scorers Law 3 asks for, disputed books cannot say whether the batting or bowling figures are wrong, and umpires allow 5- and 7-ball overs (Law 3, Raging Turner, Cricket NSW, ACS) → OverCheck: one ball log keeps batting = bowling = total, and the umpire's OverClick count is checked against the book every over (20-over test: a 7-ball over and a missed dot both flagged)
• Junior cricket retires batters at a set score or ball count (ECB U10/U11 25 runs; NCU 30/40/50; SA schools 20 straight away; AGSV 25 balls) and brings them back in a set order (after everyone, at the last wicket, or the 9th wicket, ACS), all tracked by one volunteer scorer → RetireCall: the TallyPad applies the league's rule every ball, the umpire's OverClick buzzes at the limit, and a hooked e-paper order board shows NEXT IN and the return queue (11/11 checks, including 50 random innings)
• Club tennis has no umpire: any player may call a service let but only before the return is out of play, and a net touch is often silent; USTA Code 24 lets the receiver call only flagrant foot faults after a warning, and Tennis Australia lets the receiver call none (USHSTA, USTA, Tennis Australia, ITF Rules 18 and 22) → LetCall + FootCheck: a LetTap on the net band beeps only for a cord touch on the serve, and the BaseClips check the server's toes against the baseline up to the strike, shown to the server or the league referee, never as a call (13/13 checks, 300 random points)

PlayersLeague captainClub pro

1. 01Trigger: a deep ball is called out and the hitter disagrees
2. 02Detection: a player presses CHALLENGE; the BaseClip and post pods hold the last 20 s and the final bounce is fitted from the two ball paths before and after it
3. 03Alert: the e-paper shows the line with the ball mark and the gap, or 'TOO CLOSE TO SHOW' under 10 mm, and the clip goes to both phones
4. 04Action: the players agree on the call; the captain has the clip if the dispute goes further

Outcome: The point is settled in about 10 seconds from evidence instead of an argument, and the match goes on