-
Notifications
You must be signed in to change notification settings - Fork 2
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
Power pin positioning #7
Comments
horizon-eda/horizon@7c432b2 adds support for horizontal text on vertical pins |
TBH, I'm still a fan of keeping the top and bottom of a (rectangular) symbol pin-free. It plays along nicely with most schematics' signal flow from left to right and doesn't take too much additional space. Some examples from KiCAD: But aesthetics are a matter of opinion, of course. With the perpendicular pin names of horizon-eda/horizon@c345cf4 a lot of the pain points for me of power pins on the top and bottom are addressed. If we want these pins on the top and bottom, I'd wager for having the same name orientation for all pins. |
As mentioned here, power pins on the top and bottom could look something like this: |
@carrotIndustries, @atoav: Any comments on this? |
With the recent input from @carrotIndustries in horizon-eda/horizon-pool#11 (comment) I’d consider this issue resolved for now. As always, I’m happy to re-open it if anyone has additional comments! |
Sorry that it has taken me so long to open this issue. Now, it's finally here for you all to discuss!
There should be a rule where power pins have to be placed in symbols. KiCad says that they must be on the top and bottom of a symbol. I already had started a discussion with @carrotIndustries about this question before I started this convention attempt.
In my opinion, the “always on top/bottom” rule isn't optimal, but finding a concise alternative isn't easy. In the issue linked above I proposed some, which I want to summarise along with some subjective pros and cons.
I'd like to hear some more possibilities from you where the power pins could be and how we can boil that down into a rule.
The text was updated successfully, but these errors were encountered: