-
Notifications
You must be signed in to change notification settings - Fork 70
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
Convention for Packages, Symbols, etc. #8
Comments
It looks like GitHub's wikis don't allow pull requests, so I created a repository for my draft: https://github.com/fruchti/horizon-library-convention. This also has the advantage that issues in this dedicated repository can be used as a place for discussions on controversial subjects so they won't have to be here anymore ;) For now, basically everything interesting or useful is missing but you can have a look at what I thought the general structure of the convention might look like. My next steps would to find suitable naming conventions for footprints (KiCAD has a lot of them), detail the silkscreen and schematic symbol rules and to include some images for clarification. |
Awesome! You really got the idea of the pool :) Some aspects that caught my eye:
In case you haven't come across it yet: http://www.pcblibraries.com/downloads/Guidelines%21PCB_Design_Optimization_Starts_in_the_CAD_Library.asp Appears to be the closest thing to IPC-7351 that you get for free. |
Thanks! I fixed the default text size. The 1.2 mm come from http://www.ocipcdc.org/archive/What_is_New_in_IPC-7351C_03_11_2015.pdf page 18. Interestingly the PDF you linked to says 1 mm. I didn't find a date in the former so I don't know which is the newer revision. Frankly, I didn't really bother to look into all the existing reference designator conventions yet so I copied the KLC's table as a starting point. I actually disagree both with the KLC and the IPC's table on some points, namely:
The table in the IPC slides looks more like a enumeration of the typically used designators than a recommendation to me, e. g. because it lists both D and CR for diodes. Yes, both are common but I'd expect either one or the other from a convention. |
Looks yours is newer. I also asked my copy of "PCB library expert for IPC", looks like it also produces 1.2mm pin 1 indicators, so let's settle on that one.
I don't like this one either.
Ok, I'm with you, these should be "U" as every other IC.
The fact that the the Entities "Generic 13 pin connector" and friends are supposed to be used equally for jacks and plugs makes this distinction even more pointless, so let's use J for both. |
Nice to see we're on the same page! I changed the designator table and also left out those:
Another idea to think about: X for connectors instead of J. It isn't really common but I've seen it a few times. The main advantage would be that it makes the distinction between jumpers and connectors clear. I think they shouldn't both be J. I'll open new issues for topics needing clarification in my repository from now on because I think the issues here should be about individual parts and not the general rules. |
|
Or JP for jumpers and J for connectors. |
We definitly should try to put all rules we come up with into one central place (wiki?), as a guide for pool contributers. |
@carrotIndustries could link to my repository in the pool's readme (as soon as he thinks it's mature enough), or Horizon could become an organisation. I really like using a repository with a readme instead of GItHub's wiki for the convention as long as it is work in progress, because there are a lot more options for contribution. With a repository, a suggestion can be a pull request and all discussion on rules can happen in the issues, where it's well-ordered and all in one place. |
@fruchti Okay that's a much better idea : ) |
+1 for organization |
KiCad folks have the kicad library convention: http://kicad-pcb.org/libraries/klc/ Let's see what we can leverage.
The text was updated successfully, but these errors were encountered: