15 Tips and Tricks for Using KiCad

[@StevenBedoya2]

This is top notch info, I have been an electronics technician for the last 10 years and I recently started designing PCBs. KiCad has so many options and functionalities that I recognize I have been literally assuming and guessing how to do many things while I familiarize and learn how to use it properly.

[@tonyradice4166]

Nice Job! As a designer with a few decades of experience I completely agree with all your points - especially the last two. One "Rule" we had at one of my employers is "Test points on all traces" - I regularly forced a violation of these rules designing the high speed memory busses (in order to maintain signal integrity). Gave the Fab folks fits... Another issue - with point #5 (Hierarchical design) it makes upgrading designs MUCH easier if a page is a function. Yank the page, throw in the new function and spin. If I had only had something like this available in the 90's... How about creating two specific videos on all the details in creating a PCB footprint (all the layers and details) and 3D Model (Again, all the details...) I think these would be very useful.

[@KuittheGeek]

I completely agree with you. And yes, test points on *most* lines I think is a very important rule, if you have the space. I have definitely done some very size confined boards where it wasn't feasible. But having test points on as many traces as possible is very useful in debugging. And yes, using pages as modules is a great way to do full function spins. I have also used it to start a project much faster too. I have used the ESP32 module on several designs, and it is very helpful to just pull in a few pages for the main chip and the programming interface and already have 40% of your design done. I really do need to get back to making videos, as I did enjoy it, and those two videos are definitely two that I have been thinking about for a long time. Hopefully, I can have things settle down a bit more in the coming months and I might be able to get those done. Thanks for the comment and the ideas.

[@4yearsago]

Thanks for sharing this information

[@klave8511]

Two more rules. 1 Add thermal relief to any pad or via that connects to ground or a large copper area. 2 Don’t overload your shelves, if they are bending then you have a problem and may soon have to pick parts off the floor 😀

[@KuittheGeek]

Haha, believe it or not, the shelves were bent even we bought the house, though I probably should have replaced then by now... 😅 And I agree with the thermal relief, and the best way to do this that I have found is to just have that included with the ground pour settings. That way, by default, any pad or via is automatically poured and connected to ground with thermal relief. Good tip to mention though.

[@adzijderlaan7070]

Tip 16 turn your shelves they will be straight again ;)

[@KuittheGeek]

Haha, definitely a good solution to that particular problem.

[@s1ckret]

Thanks for your advices! It would be better if a rule text was white. Because black is hard to read

[@Cutycats9]

Thanks bro 😍😍😊

[@jessevanderzouw619]

In tip 5 I see that you have used a bus between hierarchical sheets. How did you do that? Could you share the design files, then I can have a look. Or a stripped down version maybe, if it contains sensitive information.

[@KuittheGeek]

That is actually a really good question. Unfortunately, the picture I used is part of a sensitive document, so I can't share that. However, I think this is a really good tool that there doesn't seem to be enough information about, so let me see if I can get a video together quickly to cover that topic. If not, I will try to reach out and share some information more on that to you individually.

[@Berghiker]

How do I solve this problem? Symbol L1 pad ~ Not found in footprint Custom Components:T-68-6 CT.

[@KuittheGeek]

The error is saying that it is looking for a pad in the footprint "T-68-6 CT" in you Custom Components library, and there is no pin labeled with "~". So I would double check your schematic part and make sure all of the pins have the correct numbering, and none of the pins are labeled with "~".

[@Berghiker]

@@KuittheGeek How do I put a custom symbol in Custom Components Library?

[@Berghiker]

@@KuittheGeek How do I put a custom symbol in Custom Components Library?

[@KuittheGeek]

You should take a look at my video for creating libraries and parts in KiCad, That will help walk you through the process of creating a custom library. kzbin.info/www/bejne/pWG0pX2uqdB2rbc

[@khairulzeff]

The correct pronounce is "key-cad"

[@KuittheGeek]

I know that is how the developers pronounce it, and I've known that for years, but when I was first introduced to it, I learned it this way. As far as I'm concerned, it doesn't really matter. Say it as you want.

[@VladimirPutin-p3t]

For the longest time I pronounced it 'kick-a-kid' To be honest, I still do.

[@bobweiram6321]

EasyEda is far easier to learn.

[@KuittheGeek]

I've never used EasyEDA, but in my experience, KiCad is far more powerful. I've had discussions with classmates who have used EasyEDA and then I turn them on to KiCad, and they said it was difficult to learn but worth it for what they could do. There is also a lot of freedom with the software that you can't really find anywhere else, since the code is open source. I started as a fresh student on eagle, and I remember learning about the board size restrictions, and then when I moved to KiCad it seemed like everything was available to me and there was no pay wall. I've spent years using KiCad, and I would say it was always worth it to learn a more powerful tool.

[@justinc2633]

@@KuittheGeek when i first tried to learn electronics i used easyeda, thought it sucked and it discouraged me from learning, then i downloaded kicad and its 100x better

[@philgroudhog103]

terrible video

[@VladimirPutin-p3t]

Care to say why, or are you just having a bad day?