Time-Appliances-Project / Time-Appliances-Project/Time-Card

OCXO Daughter Card V4 - Silkscreen Designator Mismatch for R8 and R33

Open
#107 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.5k
Forks
122
Avg merge
12m
Merged PRs (30d)
1

Description

There appears to be a mismatch between the silkscreen designators and the actual footprints for R8 and R33 on the OCXO Daughter Card V4 PCB.

According to the BOM, R33 is an 0201 component, and R8 is a 0402 component. However, the silkscreen designators on the PCB are swapped.

PCBWay noticed this discrepancy and reached out to confirm the correct placement, which prompted me to open this issue. Correcting this in a future revision might help streamline the manufacturing process.

BOM: OCXO_DaughterCard_AbraconAOCJYR.xlsx
Gerbers: OCXO_DaughterCardV4_Gerbers.zip

Below is an image provided by PCBWay highlighting the issue as well as a snapshot from Altium viewer showing the mismatch.

T-2P4W540732A

OCXO_DaughterCardV4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the R8 and R33 entries in OCXO_DaughterCard_AbraconAOCJYR.xlsx with their placements and silkscreen designators in OCXO_DaughterCardV4_Gerbers.zip. Confirm which designators are swapped and update the PCB revision source accordingly; done means the generated manufacturing files match the BOM and no longer prompt the reported discrepancy.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.