8 ms·

Getting Started in KiCad 7.0

140 points by _Microft 3y ago

stn8188 3y ago
I love that this document gives a very complete overview of all the steps that go into creating a printed circuit board! I always say, KiCad is easily better than any ECAD tool you can buy for $1,000 or less. They also have a better built-in library than I've ever encountered in a paid tool, which is worth a lot if someone just wants to crank out a quick project.
- deleted 3y ago
  [deleted]
- cushychicken 3y ago
  Kicad is good enough for 95% of all circuit designs. Maybe 99% in version 7 - haven’t really pulled the bandaid off yet in that regard. If you’re working in a big team, or making really complex stuff like telecom equipment or server motherboards, then I can see the appeal of shelling out for PADS or Altium with their library management and package automation tools. But, I’ve designed hardware on a consulting basis before using Kicad as my EE CAD package of choice. It was more than enough for my needs. That includes simple two layer boards all the way to pretty complicated six layer embedded Linux systems. I particularly like that it comes with an embedded 3D viewer. Coming from only ever using ORCAD before that, it was a huge breath of fresh air, and significantly cut down on the number of connector mistakes I’ve made since.
  - crote 3y ago
    KiCad has been significantly improving its library management lately. With 6.0 it got a Plugin and Content Manager, allowing you to trivially add external content libraries to it. The 7.0 release added support for ODBC-based Database Libraries, allowing you to hook it up to basically any database you want in order to provide part metadata. Personally, I thought 5.0 was a big pain to use. With 6.0 it actually got kinda decent, but I still had to write custom code to work around a few of its warts. However, 7.0 shows that it is rapidly moving towards being a serious threat to the proprietary market leaders, and I can't wait to see what the future will bring!
    - sho_hn 3y ago
      The 7.0.x point releases have also consistently addressed a lot of little quality of life pain points and bugs. It's really all so enjoyable to observe from the armchair. I'm not embedded into the Kicad community/project, but it certainly feels like the momentum is there. I love these tentpole moments/projects in the overall fabric of the industry, when an open source project reaches "momentum escape velocity" after sticking around long enough to snowball and eventually eclipse the proprietary alternatives in terms of sheer scale. For example, it's very hard to outcompete the Linux kernel for general applications now simply because everyone's working on it, and no single company can build and retain a team that can outcompete an entire ecosystem, outside of picking very particular battles (e.g. QNX<>Linux). Cynics will point out that this often describes an area of software simply commodity-fying enough that FOSS can now catch and keep up, and pragmatists will point out that the commercial packages often still retain a key feature for e.g. a leading edge/high-end application you can't get from anything else. But be that as it may, it's still beautiful. I like to identify and start watching the projects that may be on the verge of becoming this in their particular domain. For example, Blender may get there or is already there. Could Krita? 20 years from now, could this be Bevy for the game engine space? There's usually certain markers, e.g. healthy governance (this is what gives the project the legs to make it long enough), good mission statement, hygienic tech stack, that sort of thing. For young programmers, this is the type of project to find and join. You end up running an industry when you grow up, and, if that's important to you (there can be other priorities, e.g. shipping important products in general), your hard labor won't die and disappear one day with a company.
- jan_Sate 3y ago
  The main limitation I've encountered with KiCad is its component library ootb. Anyway those can often be downloaded from third party websites.
  - crote 3y ago
    That's not really a limitation for professionals, though. Built-in component libraries are always going to be incomplete, and literally all of them kinda suck. Professional PCB designers almost always have to either create their own footprints from the datasheet, or get them from someone else who did. Trusting third-party footprints is probably the easiest way to end up with fundamentally broken prototypes which are nothing more than fancy desk decorations - I can unfortunately speak from experience. The built-in libraries are basically only used for trivial things like resistor footprints, 2.54mm headers, or solder jumpers. KiCad's libraries are more than good enough for that.
    - ilyt 3y ago
      Footprints are less of an issue than schematic library. If you need to say tailor-make QFP-48 footprint that might be some work but you will likely reuse it for multiple parts.
      - crote 3y ago
        Until you find out that a manufacturer decided to use a footprint which looks standard, but uses a custom pin numbering. The schematic symbols are right and so are the KiCad-provided footprints, but they are still not going to work together. But yeah, a lot of chip footprints are quite standard, or require only small modifications from those standard footprints. I do still have to hand-draw quite a few of them, but that's because my designs are usually quite heavy on relatively obscure peripherals.
  - leptons 3y ago
    It's not a limitation at all. There are no PCB design programs that have every part ever manufactured in the library. At some point you're going to have to make a PCB footprint yourself no matter what software you use. Pretty much all datasheets have explicit measurements of the footprint layout. Even better if you have the physical part and some calipers.
- iancmceachern 3y ago
  Have you used Diptrace of Flux.ai? I've personally enjoyed using DipTrace, very intuitive and easy to pick up, it's far less than $1000. I've been hearing good things about Flux but haven't tried it myself yet. I hear it's not complete, but coming along quick.
  - coder543 3y ago
    Comments like that are hard to respond to. The topic here is KiCAD, but you haven’t addressed whether you have given KiCAD 7 (or 6) a real try. Without that information, and without understanding what you didn't like about KiCAD, it’s hard to address these other options, and you don’t really even mention what you actually like about DipTrace. “Intuitive” and “easy to pickup” are arguably properties of KiCAD, for anyone familiar with schematic capture and PCB design. It used to be harder, but tons of effort has been poured into KiCAD for many years now. Why would anyone want to use an old, proprietary program like DipTrace when KiCAD is free, cross-platform, open source, and arguably just plain better? DipTrace has a Mac version, but all of the discussions I see online indicate that it still hasn’t been updated to work properly on Apple Silicon. It’s been probably 7 or 8 years since I last saw someone using DipTrace, and I wasn’t impressed then. It’s also $995 for the full version (the closest to KiCAD’s feature set), which is hardly “far less” than $1000, but the absolute minimum version I would even consider would be $400. I’m amazed at how their website seems to be exactly as I remember it from so long ago. Looking through their marketing site, I literally don’t see a single thing that is better than KiCAD. I personally just don’t understand why anyone would buy DipTrace in 2023. So, it’s hard to respond without just coming off as dismissive. I wish I could provide a more balanced comment that makes it seem like DipTrace is still competitive, well-maintained software… but that isn’t what I believe. I’m sure it’s fine for basic use cases, but KiCAD is great for those use cases and so much more. Flux seems gimmicky at first, but browsing through their materials, I am at least impressed at the effort they seem to be putting in. They even had a comparison page against KiCAD, but this attempt to sell against KiCAD ended up being some disappointing nebulous statements that didn’t seem to have much merit, apart from the real time collaborative nature of their product, which seems to be their one actual advantage. Different people can have different opinions, of course, but KiCAD is great quality software with a lot of momentum. If you want to share what features you like most about DipTrace, or what you think it does better than KiCAD, that would certainly be interesting to hear.
- robomartin 3y ago
  > KiCad is easily better than any ECAD tool you can buy for $1,000 or less. Well, we pulled the plug on Altium when KiCad 6.0 was released and have not looked back. We got really sick of Altium nonsense, just had enough of it. Their focus on cloud to sell the company really caused damage and every release broke something new. We do everything from relatively simple four layer boards to complex multi-GHz boards with challenging signal and power integrity constraints. KiCad has no problem at all providing the tools we need to complete these designs. I can't see ever going back to Altium. As far as libraries are concerned. Professional organizations rarely (I would say, never) use built-in libraries. The reason for this is that you are responsible for reliability, manufacturability and product life-cycle. This means every component needs to be qualified and fully vetted to the extent required by the nature of the product. Which, in turn, means that you are always going to want to define all the components and use internally-built libraries you can trust. There are other reasons for this, that's just the basics.
dragontamer 3y ago
I think KiCad is suitable for beginners, even if you haven't breadboarded yet, but note that Breadboards exist to give you lots and lots of practice before you start spending money on PCBs. Each PCB is a bit of money after all, and if you are inevitably going to make a mistake it's better to breadboard. But as far as difficulty goes, things like KiCad exist for a reason. Computer automation and checks help, as well as parts libraries for you to download/copy rather than building your own footprints. So feel free to start KiCad + ordering boards the moment you are willing to lose money on your mistakes!!! It's not any harder IMO. Just costlier. ---------- As far as learning Kiad, this guide is good but it's missing the broad overview IMO. So here's my broad overview: 1. Build symbols representing each chip or part you plan to use. Standard parts (like resistors) already exist in KiCAD7.0 library, but inevitably there will be a few missing parts for your project. This may be called symbol editing, but perhaps it's more accurate to call it pin-naming. 2. Hook up the parts together in the schematic editor. Double check symbols and their pinouts now. Fix symbol mistakes now. This creates a computerized set of nets (connections) that KiCad will try to enforce moving forward. 3. Choose the footprints for every part in your schematic. Beginners should probably use 0805 (inches) parts or larger. (equivalent to 2012 metric). Like #1, there is a footprint library for common parts, but you will inevitably have to create at least one or two footprints of your own for your personal projects. Footprints tell KiCad where pins are located physically (inches or mm) here vs there. 4. PCB layout begins. KiCad has a 'rats nest' based on your schematic. As long as #1, #2, and #3 are correct (ie: correct symbols / pinouts, correct schematic, and finally correct footprints) you probably can't make a mistake anymore. Assuming a low speed beginner circuit anyway (the professional would focus on physical issues like heat, noise, EMI, crosstalk and other such issues. Beginners can likely ignore all of that assuming you chose a suitable beginner project). By step#4, KiCAD knows the name of every pin (#1), which pins should be connected to which pins (#2), and where each pin is located physically (#3). All that's left to do is draw your wires together in step#4.
- chunkyks 3y ago
  I'm brand new to this. I've got a relatively simple schematic from the 1950s I want to reimplement, to have a functioning thing on my desk. As you say, a few parts are missing (particular vacuum tubes). Unfortunately, every time I start implementing stuff in kicad, that's where I get overwhelmed... And to someone who's not a hardware guy, I'm completely stymied. Can you suggest what I should do?
amelius 3y ago
I installed KiCad 7 on Ubuntu using Snap. But my KiCad files are on a harddrive that is not my "/" drive, and Snap doesn't allow KiCad to read those files. I tried with a bind mount, but then the symlinks in my project files don't work ... Now I'm thinking of compiling everything myself, but it seems a daunting task.
- klysm 3y ago
  My advice is always to never use snap. If I have to use ubuntu for something, the first thing I do is uninstall it.
- fanf2 3y ago
  Install the .deb from https://www.kicad.org/download/details/ubuntu/ https://www.kicad.org/download/details/ubuntu/
  - amelius 3y ago
    Thanks!!
- kevin_thibedeau 3y ago
  Just compile it from source and install into the /usr/local tree. It is a pain free process.
snvzz 3y ago
Seems nice. Yet desperately needs dark mode.
- z2h-a6n 3y ago
  If you mean that KiCad needs dark mode, this can be done using a combination of GTK (or QT?) color themes, which are associated with your system configuration, not KiCad, and color themes for the editing tools, which can be changed in the preferences menu. I found some reasonable options here [1], but if you're picky (like I am), you can write (or generate) your own. In the current version of KiCad, you can choose between themes (files in the appropriate directory) with a drop-down menu in the KiCad preferences, rather than editing the default configuration. [1]: https://github.com/pointhi/kicad-color-schemes https://github.com/pointhi/kicad-color-schemes
  - snvzz 3y ago
    Yeah, I sorted out the kicad part. I meant the linked article specifically.
    - z2h-a6n 3y ago
      Ahh. In that case, this [1] is my (browser-specific) solution. The results are not always great, but they're generally not bad. [1]: https://news.ycombinator.com/item?id=30628457 https://news.ycombinator.com/item?id=30628457
- spamizbad 3y ago
  Works in dark mode on my machine (uses QT/GTK darkmode setting)
- deleted 3y ago
  [deleted]
klysm 3y ago
Love KiCad. It's enabled me as a complete armature to get custom PCBs made without an insane learning curve.
15155 3y ago
I moved from KiCad to Altium: Altium is 100x slower, but I am substantially more productive. KiCad desperately needs a stackup-aware constraints system, differential impedance/trace width computation, multi-trace routing, etc. in the same way that Altium has. I wish I had time to add the features I want: KiCad is so much more pleasurable to use on average.
- bsder 3y ago
  Alternatively, send KiCad money--especially if you can convince your company to do so.
wg0 3y ago
I know how to program. But how can one learn to design circuits just like one writes a program? Sounds totally black magic to me. Any starting points?
- analog31 3y ago
  A decade or two ago, I would have recommended The Art of Electronics by Horowitz and Hill. I learned from that textbook, plus a lot of home experimentation, and application notes from the IC manufacturers notably National Semiconductor. Those app notes are still available online from Texas Instruments, and still relevant. Today, I help colleagues get started in electronics. They often have some sort of science or non-EE engineering background. I recommend diving into the Arduino universe, perhaps by looking through the many tutorials at the Adafruit webiste. (And buying her stuff). Learn, the way a lot of us old-timers learned to code: Take some working program, duplicate it, and make minor changes, and see what happens. Even if your ultimate interest is analog rather than digital, the tools that you learn to make in the digital realm, such as measurement, will help you test your beginning analog circuits. On the other hand, if you're interested in analog, you may have a reason, such as audio or music electronics, in which case, there are a lot of documented projects out there to build and learn from. Don't work with anything potentially dangerous at first, if ever. Things that can release a large amount of energy (voltage, current, mechanical, heat) if your code has a bug are worth leaving to the real engineers.
  - mmac_ 3y ago
    This is solid advice. Find something you're interested in and go from there. If you can't find anything, maybe build something like a weather station. You'll start with a simple task: read the ambient temperature and display it somewhere (on an LCD, in a react app on the cloud etc). You'll then need to start solving problems, like how do you read outside temperature where you'll learn about batteries, wireless technology, water proofing etc. Don't stress about the electronics and certainly don't be intimidated by text books. When you're starting out you don't need to really know the theory of transistors, but maybe a few youtube videos on the basics won't go astray. Think about if you were learning to code... would you read a book and start stressing about computer architecture? Some people might, but most won't. They'll hit up create-react-app and mess around with that. When you're learning it's important to get instant feedback. Just learn how to blink an LED and you've completed the hello-world of electronics. If you can code, you can do electronics. Same for the reverse. The skill sets are closely aligned.
elcapitan 3y ago
Beginner question: What would be a good circuit simulator to combine with this? Or do you always breadboard?

140 points by _Microft 3y ago

I love that this document gives a very complete overview of all the steps that go into creating a printed circuit board! I always say, KiCad is easily better than any ECAD tool you can buy for $1,000 or less. They also have a better built-in library than I've ever encountered in a paid tool, which is worth a lot if someone just wants to crank out a quick project.

deleted 3y ago
[deleted]
cushychicken 3y ago
Kicad is good enough for 95% of all circuit designs. Maybe 99% in version 7 - haven’t really pulled the bandaid off yet in that regard. If you’re working in a big team, or making really complex stuff like telecom equipment or server motherboards, then I can see the appeal of shelling out for PADS or Altium with their library management and package automation tools. But, I’ve designed hardware on a consulting basis before using Kicad as my EE CAD package of choice. It was more than enough for my needs. That includes simple two layer boards all the way to pretty complicated six layer embedded Linux systems. I particularly like that it comes with an embedded 3D viewer. Coming from only ever using ORCAD before that, it was a huge breath of fresh air, and significantly cut down on the number of connector mistakes I’ve made since.
- crote 3y ago
  KiCad has been significantly improving its library management lately. With 6.0 it got a Plugin and Content Manager, allowing you to trivially add external content libraries to it. The 7.0 release added support for ODBC-based Database Libraries, allowing you to hook it up to basically any database you want in order to provide part metadata. Personally, I thought 5.0 was a big pain to use. With 6.0 it actually got kinda decent, but I still had to write custom code to work around a few of its warts. However, 7.0 shows that it is rapidly moving towards being a serious threat to the proprietary market leaders, and I can't wait to see what the future will bring!
  - sho_hn 3y ago
    The 7.0.x point releases have also consistently addressed a lot of little quality of life pain points and bugs. It's really all so enjoyable to observe from the armchair. I'm not embedded into the Kicad community/project, but it certainly feels like the momentum is there. I love these tentpole moments/projects in the overall fabric of the industry, when an open source project reaches "momentum escape velocity" after sticking around long enough to snowball and eventually eclipse the proprietary alternatives in terms of sheer scale. For example, it's very hard to outcompete the Linux kernel for general applications now simply because everyone's working on it, and no single company can build and retain a team that can outcompete an entire ecosystem, outside of picking very particular battles (e.g. QNX<>Linux). Cynics will point out that this often describes an area of software simply commodity-fying enough that FOSS can now catch and keep up, and pragmatists will point out that the commercial packages often still retain a key feature for e.g. a leading edge/high-end application you can't get from anything else. But be that as it may, it's still beautiful. I like to identify and start watching the projects that may be on the verge of becoming this in their particular domain. For example, Blender may get there or is already there. Could Krita? 20 years from now, could this be Bevy for the game engine space? There's usually certain markers, e.g. healthy governance (this is what gives the project the legs to make it long enough), good mission statement, hygienic tech stack, that sort of thing. For young programmers, this is the type of project to find and join. You end up running an industry when you grow up, and, if that's important to you (there can be other priorities, e.g. shipping important products in general), your hard labor won't die and disappear one day with a company.
jan_Sate 3y ago
The main limitation I've encountered with KiCad is its component library ootb. Anyway those can often be downloaded from third party websites.
- crote 3y ago
  That's not really a limitation for professionals, though. Built-in component libraries are always going to be incomplete, and literally all of them kinda suck. Professional PCB designers almost always have to either create their own footprints from the datasheet, or get them from someone else who did. Trusting third-party footprints is probably the easiest way to end up with fundamentally broken prototypes which are nothing more than fancy desk decorations - I can unfortunately speak from experience. The built-in libraries are basically only used for trivial things like resistor footprints, 2.54mm headers, or solder jumpers. KiCad's libraries are more than good enough for that.
  - ilyt 3y ago
    Footprints are less of an issue than schematic library. If you need to say tailor-make QFP-48 footprint that might be some work but you will likely reuse it for multiple parts.
    - crote 3y ago
      Until you find out that a manufacturer decided to use a footprint which looks standard, but uses a custom pin numbering. The schematic symbols are right and so are the KiCad-provided footprints, but they are still not going to work together. But yeah, a lot of chip footprints are quite standard, or require only small modifications from those standard footprints. I do still have to hand-draw quite a few of them, but that's because my designs are usually quite heavy on relatively obscure peripherals.
- leptons 3y ago
  It's not a limitation at all. There are no PCB design programs that have every part ever manufactured in the library. At some point you're going to have to make a PCB footprint yourself no matter what software you use. Pretty much all datasheets have explicit measurements of the footprint layout. Even better if you have the physical part and some calipers.
iancmceachern 3y ago
Have you used Diptrace of Flux.ai? I've personally enjoyed using DipTrace, very intuitive and easy to pick up, it's far less than $1000. I've been hearing good things about Flux but haven't tried it myself yet. I hear it's not complete, but coming along quick.
- coder543 3y ago
  Comments like that are hard to respond to. The topic here is KiCAD, but you haven’t addressed whether you have given KiCAD 7 (or 6) a real try. Without that information, and without understanding what you didn't like about KiCAD, it’s hard to address these other options, and you don’t really even mention what you actually like about DipTrace. “Intuitive” and “easy to pickup” are arguably properties of KiCAD, for anyone familiar with schematic capture and PCB design. It used to be harder, but tons of effort has been poured into KiCAD for many years now. Why would anyone want to use an old, proprietary program like DipTrace when KiCAD is free, cross-platform, open source, and arguably just plain better? DipTrace has a Mac version, but all of the discussions I see online indicate that it still hasn’t been updated to work properly on Apple Silicon. It’s been probably 7 or 8 years since I last saw someone using DipTrace, and I wasn’t impressed then. It’s also $995 for the full version (the closest to KiCAD’s feature set), which is hardly “far less” than $1000, but the absolute minimum version I would even consider would be $400. I’m amazed at how their website seems to be exactly as I remember it from so long ago. Looking through their marketing site, I literally don’t see a single thing that is better than KiCAD. I personally just don’t understand why anyone would buy DipTrace in 2023. So, it’s hard to respond without just coming off as dismissive. I wish I could provide a more balanced comment that makes it seem like DipTrace is still competitive, well-maintained software… but that isn’t what I believe. I’m sure it’s fine for basic use cases, but KiCAD is great for those use cases and so much more. Flux seems gimmicky at first, but browsing through their materials, I am at least impressed at the effort they seem to be putting in. They even had a comparison page against KiCAD, but this attempt to sell against KiCAD ended up being some disappointing nebulous statements that didn’t seem to have much merit, apart from the real time collaborative nature of their product, which seems to be their one actual advantage. Different people can have different opinions, of course, but KiCAD is great quality software with a lot of momentum. If you want to share what features you like most about DipTrace, or what you think it does better than KiCAD, that would certainly be interesting to hear.
robomartin 3y ago
> KiCad is easily better than any ECAD tool you can buy for $1,000 or less. Well, we pulled the plug on Altium when KiCad 6.0 was released and have not looked back. We got really sick of Altium nonsense, just had enough of it. Their focus on cloud to sell the company really caused damage and every release broke something new. We do everything from relatively simple four layer boards to complex multi-GHz boards with challenging signal and power integrity constraints. KiCad has no problem at all providing the tools we need to complete these designs. I can't see ever going back to Altium. As far as libraries are concerned. Professional organizations rarely (I would say, never) use built-in libraries. The reason for this is that you are responsible for reliability, manufacturability and product life-cycle. This means every component needs to be qualified and fully vetted to the extent required by the nature of the product. Which, in turn, means that you are always going to want to define all the components and use internally-built libraries you can trust. There are other reasons for this, that's just the basics.

dragontamer 3y ago

I think KiCad is suitable for beginners, even if you haven't breadboarded yet, but note that Breadboards exist to give you lots and lots of practice before you start spending money on PCBs. Each PCB is a bit of money after all, and if you are inevitably going to make a mistake it's better to breadboard. But as far as difficulty goes, things like KiCad exist for a reason. Computer automation and checks help, as well as parts libraries for you to download/copy rather than building your own footprints. So feel free to start KiCad + ordering boards the moment you are willing to lose money on your mistakes!!! It's not any harder IMO. Just costlier. ---------- As far as learning Kiad, this guide is good but it's missing the broad overview IMO. So here's my broad overview: 1. Build symbols representing each chip or part you plan to use. Standard parts (like resistors) already exist in KiCAD7.0 library, but inevitably there will be a few missing parts for your project. This may be called symbol editing, but perhaps it's more accurate to call it pin-naming. 2. Hook up the parts together in the schematic editor. Double check symbols and their pinouts now. Fix symbol mistakes now. This creates a computerized set of nets (connections) that KiCad will try to enforce moving forward. 3. Choose the footprints for every part in your schematic. Beginners should probably use 0805 (inches) parts or larger. (equivalent to 2012 metric). Like #1, there is a footprint library for common parts, but you will inevitably have to create at least one or two footprints of your own for your personal projects. Footprints tell KiCad where pins are located physically (inches or mm) here vs there. 4. PCB layout begins. KiCad has a 'rats nest' based on your schematic. As long as #1, #2, and #3 are correct (ie: correct symbols / pinouts, correct schematic, and finally correct footprints) you probably can't make a mistake anymore. Assuming a low speed beginner circuit anyway (the professional would focus on physical issues like heat, noise, EMI, crosstalk and other such issues. Beginners can likely ignore all of that assuming you chose a suitable beginner project). By step#4, KiCAD knows the name of every pin (#1), which pins should be connected to which pins (#2), and where each pin is located physically (#3). All that's left to do is draw your wires together in step#4.

chunkyks 3y ago
I'm brand new to this. I've got a relatively simple schematic from the 1950s I want to reimplement, to have a functioning thing on my desk. As you say, a few parts are missing (particular vacuum tubes). Unfortunately, every time I start implementing stuff in kicad, that's where I get overwhelmed... And to someone who's not a hardware guy, I'm completely stymied. Can you suggest what I should do?

amelius 3y ago

I installed KiCad 7 on Ubuntu using Snap. But my KiCad files are on a harddrive that is not my "/" drive, and Snap doesn't allow KiCad to read those files. I tried with a bind mount, but then the symlinks in my project files don't work ... Now I'm thinking of compiling everything myself, but it seems a daunting task.

klysm 3y ago
My advice is always to never use snap. If I have to use ubuntu for something, the first thing I do is uninstall it.
fanf2 3y ago
Install the .deb from https://www.kicad.org/download/details/ubuntu/ https://www.kicad.org/download/details/ubuntu/
- amelius 3y ago
  Thanks!!
kevin_thibedeau 3y ago
Just compile it from source and install into the /usr/local tree. It is a pain free process.

snvzz 3y ago

Seems nice. Yet desperately needs dark mode.

z2h-a6n 3y ago
If you mean that KiCad needs dark mode, this can be done using a combination of GTK (or QT?) color themes, which are associated with your system configuration, not KiCad, and color themes for the editing tools, which can be changed in the preferences menu. I found some reasonable options here [1], but if you're picky (like I am), you can write (or generate) your own. In the current version of KiCad, you can choose between themes (files in the appropriate directory) with a drop-down menu in the KiCad preferences, rather than editing the default configuration. [1]: https://github.com/pointhi/kicad-color-schemes https://github.com/pointhi/kicad-color-schemes
- snvzz 3y ago
  Yeah, I sorted out the kicad part. I meant the linked article specifically.
  - z2h-a6n 3y ago
    Ahh. In that case, this [1] is my (browser-specific) solution. The results are not always great, but they're generally not bad. [1]: https://news.ycombinator.com/item?id=30628457 https://news.ycombinator.com/item?id=30628457
spamizbad 3y ago
Works in dark mode on my machine (uses QT/GTK darkmode setting)
deleted 3y ago
[deleted]

klysm 3y ago

Love KiCad. It's enabled me as a complete armature to get custom PCBs made without an insane learning curve.

15155 3y ago

I moved from KiCad to Altium: Altium is 100x slower, but I am substantially more productive. KiCad desperately needs a stackup-aware constraints system, differential impedance/trace width computation, multi-trace routing, etc. in the same way that Altium has. I wish I had time to add the features I want: KiCad is so much more pleasurable to use on average.

bsder 3y ago
Alternatively, send KiCad money--especially if you can convince your company to do so.

wg0 3y ago

I know how to program. But how can one learn to design circuits just like one writes a program? Sounds totally black magic to me. Any starting points?

analog31 3y ago
A decade or two ago, I would have recommended The Art of Electronics by Horowitz and Hill. I learned from that textbook, plus a lot of home experimentation, and application notes from the IC manufacturers notably National Semiconductor. Those app notes are still available online from Texas Instruments, and still relevant. Today, I help colleagues get started in electronics. They often have some sort of science or non-EE engineering background. I recommend diving into the Arduino universe, perhaps by looking through the many tutorials at the Adafruit webiste. (And buying her stuff). Learn, the way a lot of us old-timers learned to code: Take some working program, duplicate it, and make minor changes, and see what happens. Even if your ultimate interest is analog rather than digital, the tools that you learn to make in the digital realm, such as measurement, will help you test your beginning analog circuits. On the other hand, if you're interested in analog, you may have a reason, such as audio or music electronics, in which case, there are a lot of documented projects out there to build and learn from. Don't work with anything potentially dangerous at first, if ever. Things that can release a large amount of energy (voltage, current, mechanical, heat) if your code has a bug are worth leaving to the real engineers.
- mmac_ 3y ago
  This is solid advice. Find something you're interested in and go from there. If you can't find anything, maybe build something like a weather station. You'll start with a simple task: read the ambient temperature and display it somewhere (on an LCD, in a react app on the cloud etc). You'll then need to start solving problems, like how do you read outside temperature where you'll learn about batteries, wireless technology, water proofing etc. Don't stress about the electronics and certainly don't be intimidated by text books. When you're starting out you don't need to really know the theory of transistors, but maybe a few youtube videos on the basics won't go astray. Think about if you were learning to code... would you read a book and start stressing about computer architecture? Some people might, but most won't. They'll hit up create-react-app and mess around with that. When you're learning it's important to get instant feedback. Just learn how to blink an LED and you've completed the hello-world of electronics. If you can code, you can do electronics. Same for the reverse. The skill sets are closely aligned.

elcapitan 3y ago

Beginner question: What would be a good circuit simulator to combine with this? Or do you always breadboard?