![]() Searching for “header” will find the right (or “a good”) schematic element. I honestly don’t understand what the pushback is against making the product better for people who transfer in? It doesn’t make it worse for anyone else.įirst, the schematic and electrical function of all of those headers are the same (unless you use grounded sheath/shroud) so that’s fine. If you search the forums (which I should have done before posting shame on me!) then you will see that I’m not alone in this, and assuming that most people DO search the forums, we have a significant under-count in the number of people who have this quesiton. That’s not a particularly hard ask, and it will solve this problem to everybody’s satisfaction. I also understand that “connector” is one of the commonly used terms for these devices – no complaint from me there.Īll I’m saying is that many people think of these, and search for these as “pin headers” so it would be very helpful to add the words “pin header” to the description of these parts. (I don’t want to draw out yet another SOIC-8 footprint for adding yet another MOSFET part – much better to associate with a footprint I already know!) I understand the KiCad separation, and I even think it’s pretty good. If you want a library of fully specified symbols you can create it quite easily from the symbols and footprints supplied with kicad. I’m not sure it’s really worse.īy the way: What i tried to communicate above is that you can recreate the eagle way in kicad.īut don’t expect the library maintainers to maintain such a big library. If i find out that this footprint makes problems in my production process, i need to change all of them separately. My eagle library had many ic footprints stored in multiple libraries. You don’t need the same symbol or footprint stored more than once. (It is an abstraction of the complete component. This entity connects footprints to symbols and holds stuff like ordering information. You can connect them in your library or you can run cvpcb or you can do it per symbol in the schematic editor. There is no requirement of a connection between symbols and footprints. (but it again does not hold ordering information or something similar.) The footprint is what creates the connection to reality. In kicad you have symbols which are an abstract representation of the parts function. In the official library we generally ignore this fact and treat it like a standalone footprint and require the 0.5mm courtyard clearance just to make it easier (in reality one footprint can not really fulfil all possible usecases for such parts).Īny uers that then places multiple footprints side by side will get the DRC error (not in v4 as this does not check courtyards).Kicad has a quite unique idea of how to manage a library. The thing with connectors that can be placed side by side is that there is not really an easy answer to give regarding courtyard. The courtyard is generally meant to help with ensuring space for tooling. Should the courtyard be the exact outer edge of the connector, or should there be some air around it. I would like to put two of them side-by-side, which will cover 1-inch of my board edge. The connector was designed such that putting more than one in adjacent will allow the same pitch as if there was one longer connector. ![]() What layers do I need to draw from those to get something useful for both placement on the board edge, and pads (and possibly vias) ? I probably care less at the moment about generating a 3D file. I have confirmed that the objects imported have the correct dimensions, based both on older MOLEX datasheet and measuring one with my caliper. All the line segments appear to have been loaded on the same layer. For the footprint the top is the best one to begin with, so I did an Import from DXF in the Footprint Editor. So went to the MOLEX web site, and it generated DXF12 2D files for top/side/front views. I need a footprint for a particular MOLEX connector (22-15-2056). This is my first footprint file, so I'm feeling my way around.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |