Repository navigation
docs(harness): DIYLC project for the plate R carrier - #12
Merged
Merged
Conversation
make_carrier_diylc.py now writes one project per carrier on the same board layout: - hardware/carrier-stripboard-right.diy (new): R1-R4 with CS <- D7, D8, D9, A2, no DRDY, BUS IN from plate L's BUS OUT, BUS OUT left empty. - hardware/carrier-stripboard.diy: the bus strips and notes now say that BUS OUT goes on to plate R's BUS IN, and list the wires to the Q. - docs/harness.md: links both projects and spells out the chain wiring. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a DIY Layout Creator project for the second (plate R) carrier. It is generated by the same script, on the same board layout as the first:
hardware/carrier-stripboard-right.diy(new): R1, R2, R3, R4 at the same breakout positions as L1–L4. The CS labels readCS <- D7 / D8 / D9 / A2. There is no DRDY wire (strip H notes "DRDY not wired on plate R"). The inset drops the "L1 only: DRDY" wire.hardware/carrier-stripboard.diy(plate L): same layout. The bus strips now read "BUS OUT -> plate R BUS IN". The notes list everything that goes to the Q (5 bus wires, CS D3–D6, L1 DRDY → D2) and point to the right-plate file.docs/img/make_carrier_diylc.py:build(plate)with amodules(plate)helper;__main__writes both files.docs/harness.md§2: links both projects and spells out how the plate R carrier's BUS IN chains from plate L's BUS OUT.Why was this required?
The second carrier is nearly built: the same board as the first, but with different BUS IN/OUT wiring and different connections to the Q. The repo only had the plate L project, plus a one-line note that the right one is "the same board". Plate R differs in exactly the places that are easy to get wrong: where BUS IN comes from, BUS OUT left empty, A2 rather than D10, and no DRDY.
Automated tests
None added. This changes a docs generator and its output, not code covered by
tests/(the "Tests included" check only coversapp/python/open_fpandtools/sim|bench). Checked instead:ruff check docs/img: clean..diyfiles parse as XML.Manual (human) testing
docs/img/make_carrier_diylc.py. The plate L file's diff is text only: the five bus-strip labels and the notes. No component positions moved.hardware/carrier-stripboard-right.diyin DIYLC on macOS for the owner to look over against the half-built second carrier. Owner: please check it there before merging.Checklist
pytest)ruff check app/python tools tests docs/img)PYTHONPATH=app/python:tools/sim:tools/bench pylint app/python/open_fp tools/sim tools/bench --fail-under=9) — untouched pathsdocs/VERIFIED.md(measurements, fit checks, pin changes) — n/a, no measurement yetdocs/img/corner-assembly.svg, CAD STL/STEP)🤖 Generated with Claude Code