I hereby certify that I am not simply asking someone else to design a footprint for me.
I’m quite new to KiCad and am working on my first schematic, other than the tutorial and a few test schematics. This will be my first attempt to design a circuit and to then design the PCB and, after that, to export it, import it into my CNC software, so I can etch it with my CNC.
I’ve been looking for information on footprints for components and I have several questions that, at this point, I’m not at all sure how to answer or just what to search for. (I’m having trouble with searches on a few topics - not always finding the documentation I need and getting the same hits on Google over and over.)
I used several symbols in the Device library because I’m still getting used to everything and I couldn’t find some of the commonly found parts I needed (like LEDs and resistors). Unfortunately, a lot of these parts don’t have accompanying footprints. While trying to find appropriate footprints for the components, I’ve run into a number of questions:
-
I could not find “electrolytic” in the symbol library at all. I did find a symbol that matched it, so I used it. It’s “Polarized capacitor, small US symbol.” This is one of several situations where I could not find a specific device and used something by matching the symbol with what I’m used to seeing represent it in a schematic. Will this cause other problems in the later steps in this process? For instance, I know a schematic is evaluated to see if it follows the rules before I can do a PCB design. Will this kind of thing cause problems with that?
-
What would be the right way to deal with the issue above - when I can’t find a specific symbol, or I find a number of symbols, but they’re for specific part numbers. (For instance, I found a few LED symbols, but they had specific model numbers and I’m not sure just how compatible they would be with the LEDs I have.)
-
I use several gates on a 74HC00. I found a a gate easily as a symbol to use in the schematic, but how do I work with a footprint of an IC chip that has several different gates, all in use, in the circuit? If I use all 4 NAND gates in a 74HC00, how do I set up a single footprint that contains all the gates in use?
-
While looking for a match on the electrolytic capacitors I’m using (see question #1), I found several footprints listed. They all had numbers in the footprint title, like 4.0x5.8mm (as seen in the image below). It seems to me those numbers would be size. In this case, one would be the height, the other would be the diameter of the device. The caps I have on hand are typical sizing of this component - sizes I’ve seen for caps going back to the 70s. They measure 4mm in diameter and 11mm in height, but there are no devices in the library that match these measurements. Do I just go with one with the right diameter, so the PCB footprint is the right size? Or is there another meaning to these numbers?
5.To power my circuit, I’m using a USB-C jack that has only 4 pins for a connection. I see a number of USB- C connectors in the libraries, but I don’t see one that’s 4 pins and with the connections this jack has (GND, +5V, D+, D-). Do I need another library? What can I do to find the right footprint for this?
- I don’t want to just load in any library I find and end up with hundreds of libraries I won’t use, but, as I mentioned, some of the parts I’m using don’t seem to have a fitting footprint in the library. I do see a list of other libraries I can download in the KiCad docs on footprint libraries. Is there any information on which libraries will be the most useful or which most people find helpful with KiCad?
I’ve never done any kind of PCB design before now (well, none with a CAD program, what I did was back in the 70s and 80s, and this was only small stuff, but it was way before desktops could handle anything like PCB design or circuit simulation). I haven’t had to deal with footprints or understanding just what factors are important for me to consider when looking for a footprint to match the actual device I’m using. I’m feeling a bit overwhelmed in trying to explore and understand this particular KiCad feature.