-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Center finding not accurate due to silk screen #379
Comments
For Kicad 7.99, this seems to work for some reason without even selecting copper layers:
Alternatively combining boundboxes of each pad works with Kicad 7:
|
@dzid26 are you submitting a PR for this? Is your approach with combining the bounding boxes of all pads working for V7 and V7.99? |
I can submit the PR. Bounding box logic will work with 7.0. Should the same logic be applied to SMD components though? kicad-jlcpcb-tools/fabrication.py Line 116 in eca019d
|
In the PR, I prioritized point 1. (I removed |
I wanted this to work, because for my footprint anchors are defined at pin1.
Unfortunately, it seems GetBoundingBox takes the silk screen into account.
kicad-jlcpcb-tools/fabrication.py
Line 118 in eca019d
As a result for a footprint like this with dot on silk:
![image](https://cdn.statically.io/img/private-user-images.githubusercontent.com/841061/277835860-aaffbfb0-02a6-4dd8-8d75-cd3d5b36cb75.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyNTU3MjksIm5iZiI6MTcyMjI1NTQyOSwicGF0aCI6Ii84NDEwNjEvMjc3ODM1ODYwLWFhZmZiZmIwLTAyYTYtNGRkOC04ZDc1LWNkM2Q1YjM2Y2I3NS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcyOVQxMjE3MDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05NjUxZGEwZGU1N2RiZDgzOWRmYzYxMGMyYjFkYTE5YzU4ZDUzMWIzMThjMDUyYzZjMmFiNWJjYTBkNDFiZmFjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9._F77dNluytQpJmAa43VkVDMTTeTyszOageudXa5FRC0)
the calculated center is too low.
The text was updated successfully, but these errors were encountered: