Skip to content

Docs: quick start focus — small-turn technique and touch-up guidance - #546

Merged
brickbots merged 2 commits into
mainfrom
docs-quick-start-focus-technique
Jul 23, 2026
Merged

Docs: quick start focus — small-turn technique and touch-up guidance#546
brickbots merged 2 commits into
mainfrom
docs-quick-start-focus-technique

Conversation

@brickbots

@brickbots brickbots commented Jul 23, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

Summary

Folds hard-won guidance from a recent support exchange into the docs, to raise first-night focus success rates:

quick_start.rst — Setting Focus & First Solve

  • Work in small steps — a new paragraph right after the HFD readout description explaining that the whole range from badly defocused to sharp is only a few lens turns, fair-to-good is under half a turn, and the winning technique is 1/8–1/4 turn at a time with a pause for vibration to settle. Larger or continuous turns sweep straight through best focus.
  • Touch-up guidance — a paragraph noting that a solve takes a second or so to catch up with the lens, so the camera icon lags; later-night touch-ups should be judged on the Focus screen's faster HFD readout, with the same small-turn-then-pause technique.

troubleshooting.rst — It won't plate solve

  • The "Focus, properly" step now carries the same technique: half-turn window, 1/8–1/4 turn steps with a settle pause, and judge by the HFD rather than the lagging camera icon.

Verification

  • sphinx-build -b html -n (nitpicky mode) with the pinned docs/source/requirements.txt — clean, no warnings or errors, after each change.

🤖 Generated with Claude Code

brickbots and others added 2 commits July 23, 2026 13:38
@brickbots @claude
Docs: quick start focus — small-turn technique and touch-up guidance
7b3cf3a 
Distilled from a support exchange: the full focus range is only a few
lens turns wide (fair to good is under half a turn), so advise 1/8-1/4
turn adjustments with a pause for vibration to settle. Note that the
camera icon lags a solve behind the lens, so touch-ups should be judged
on the Focus screen's HFD readout.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@brickbots @claude
Docs: troubleshooting — small-turn focus technique in the no-solve list
ad8fc57 
Extends the "Focus, properly" step with the same support-exchange
guidance as the quick start: fair-to-good focus is under half a turn,
work in 1/8-1/4 turn steps with a settle pause, and judge by the HFD
since the camera icon lags a solve behind the lens.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@brickbots
brickbots marked this pull request as ready for review July 23, 2026 21:16
@brickbots
brickbots merged commit e9cbfe5 into main Jul 23, 2026
4 checks passed
@brickbots brickbots mentioned this pull request Jul 23, 2026
Merged
brickbots added a commit that referenced this pull request Jul 24, 2026
@brickbots @claude
Docs: focus technique guidance for quick start and troubleshooting (r…
3e23052 
…elease) (#547)

Backport of the focus guidance from PR #546, adapted to the focus-strip
version of the Focus screen documented on this branch: the full focus
range is only a few lens turns wide (fair to good is under half a turn),
so advise 1/8-1/4 turn adjustments with a pause for vibration to settle,
and judge touch-ups by the HFD readout since the camera icon lags a
solve behind the lens.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
brickbots added a commit that referenced this pull request Jul 31, 2026
@brickbots @claude
Merge release into main to reconcile the branches before the 2.6.1 cut
e7c1660 
release had accumulated CI work that was never on main (#514, #515,
#516, #519, #522, #545), and both branches had independently applied the
same focus-technique docs (#546 on main, #547 on release) and the same
manifest/PR-builder changes. Merging release in first makes the coming
main -> release promotion clean instead of carrying four conflicts into
the release cut.

Four conflicts, each resolved by taking one side wholesale -- none was a
semantic disagreement, only the same work committed twice:

  .github/scripts/update_manifest.py    -> release
      Strict superset: newest-first entry ordering plus the
      --migration-url / --migration-sha256-url arguments from #516.
      main had nothing release lacked.

  .github/workflows/nixos-pr-build.yml  -> release
      Genuinely divergent designs. main (#493) polls a self-hosted Pi5
      first via a native-wait job, falling back to a hosted arm64
      runner; release (#495 + #545) was re-architected ARM-primary with
      the Pi5 as last-resort fallback, drops the polling job, and adds
      allow-unsafe-pr-checkout for fork PRs under pull_request_target.
      release's is the newer and hardened design.

  docs/source/quick_start.rst           -> main
  docs/source/troubleshooting.rst       -> main
      Both branches carry the same small-turn focus technique, but
      release applied it to the old Focus screen's prose (+/- zoom to
      2x/4x). main describes the rebuilt screen from #531 -- magnified
      star tiles, SQUARE cycling to the Image view, the central HFD --
      which is what 2.6.1 actually ships.

Net effect: main gains the release-only CI (release.yml, workflow_dispatch
only, so nothing fires on merge) and keeps its own newer docs. No source
changes. 1100 unit+smoke tests pass.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@brickbots