-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Occasional components shift / FP anchor not honored? #391
Comments
Forgot to mention, but generating .pos file directly from KiCAD (File > Fabrication Outputs > Component Placement) changes the component positions after modyfing FP anchor. So the behavior of built-in KiCAD tools is correct. |
Can you please test again, I just merged PR #381 which might fix this issue. |
I think #381 will not fix anchor placement issue. I was contemplating about this here #379 (comment). I still think, having dedicated JLC part offset setting would be better than anchor manipulation. However #381 may fix thru-hole component placement, because now it ignores silkscreen when finding center of the component. |
I just tried to reproduce this, my results are not 100% correct but seem to be better than yours: The problem is that we don't know for each part what offsets JLC uses, so thats a game of cat and mouse which we will never be able to win. As this does not mean the board is manufactured wrong, I'll close this as I can not do much about it. If somebody comes up with a smart idea on how to fix this, re-open or create a new issue or even better a PR! |
Describe the bug
Inconsistent / random components shift, especially non-standard ones like connectors, etc.
Seems like the plugin doesn't honour a footprint anchor (moving an anchor in FP editor, then updating footprints generate the same CPL file while updated footprints should have different components placing than before.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A correct components position in CPL file.
KiCad Version
The text was updated successfully, but these errors were encountered: