How are parts libraries? I see that there are a bunch on github maintained by companies like Digikey. It's been a while since I did a pcb design but my last was using jlpcb's online editor and I was pleasantly surprised how easy it was to do since they had a massive public parts library. I used to use eagle back in the day but stopped being a fan once it was bought/ruined by autodesk. I hate managing parts libraries.
KiCad 7.0
91–100 of 121 posts
Re: KiCad 7.0
#92>Custom Fonts Hell yeah. Finally schematics and PCBs with aesthetic text.
Putting a logo on a board as a footprint is fine, but footprints, for good reason, cannot be arbitrarily resized.
Re: KiCad 7.0
#93Downloading now...
Re: KiCad 7.0
#94I want to learn PCB design, mostly with ARM and ESP based designs. How would I learn basics? I know theory part but I really couldn't figure out why they determine which component and which value they have to use. I mean there are resistors, capacitors all over the place but I really want to learn reason behind it. Also I guess there are some basics related power, battery, UART, USB etc. Is there any source that cove…
Re: KiCad 7.0
#95How are parts libraries? I see that there are a bunch on github maintained by companies like Digikey. It's been a while since I did a pcb design but my last was using jlpcb's online editor and I was pleasantly surprised how easy it was to do since they had a massive public parts library. I used to use eagle back in the day but stopped being a fan once it was bought/ruined by autodesk. I hate managing parts libraries.
Re: KiCad 7.0
#96I want to learn PCB design, mostly with ARM and ESP based designs. How would I learn basics? I know theory part but I really couldn't figure out why they determine which component and which value they have to use. I mean there are resistors, capacitors all over the place but I really want to learn reason behind it. Also I guess there are some basics related power, battery, UART, USB etc. Is there any source that cove…
You can also see a nice progression there from beginner PCBs to more advanced things.
Re: KiCad 7.0
#97Earlier quoted context omitted.
I'm still on version 5 due to apt/snap issues, but what I miss the most is a way to place footprints of a group of components (as opposed to placing them all at once).
I'm still on version 5 due to apt/snap issues I'm still on 5.1.x as snapping is broken. Not apt/snap, but proximity snap. In 5.1.x the best way to place a group is to use https://github.com/MitjaNemec/Kicad_action_plugins 'replicate layout' (components and traces). See also, right click and Select ... Same schematic sheet (components only).
Re: KiCad 7.0
#98Earlier quoted context omitted.
I dunno, most PCBs programs I've tried can be summed up to "every single one has weird workflow and you just need to pick one and get used to it"
Seriously, as a kicad dev this is a neverending nightmare of subjective complaining. There was even an old-timer going on a rampage recently on the kicad forums about how PADS was the most superior EDA tool in the world, why aren't we a clone of PADS?? Basically the CAD world is exactly like people arguing over vim vs emacs
Even default keybindings are very personal. Some prefer to focus most of the common ones in one place (say around the qwer/asdf/zxcv cluster) so you don't need to move hand much, while others would rather go by easier to remember names and have [M]ove and [D]rag. I guess you can still define the "bad" here by neither intuitive nor convenient, which is to say "LTSpice", but most programs are not that.
Re: KiCad 7.0
#99Earlier quoted context omitted.
I'm still on version 5 due to apt/snap issues I'm still on 5.1.x as snapping is broken. Not apt/snap, but proximity snap. In 5.1.x the best way to place a group is to use https://github.com/MitjaNemec/Kicad_action_plugins 'replicate layout' (components and traces). See also, right click and Select ... Same schematic sheet (components only).
I believe GP is referring to the `snap` package manager on Linux, not snapping in the UI.
Re: KiCad 7.0
#100We said goodbye to Altium Designer when KiCad 6.0 was released. Altium’s focus and resources shifted towards trying to turn AD into a cloud-based tool. As a result the software people actually wanted to use suffered. Every release introduced a plethora of new bugs. Nobody really cared for cloud EDA. Altium thought they would be able to sell the company to Autodesk. This almost happened. In the end that did not happen…
> It makes no sense at all. Don't underestimate the inertia of processes at established companies. If a company maintains a part library, if the company has more than a few EEs- it can be a multi-man-month effort with potential for costly mistakes. I like KiCad very much, I use it professionally but I also was the one that mandated AD to be the tool everyone at $WORK must use for production designs a few years ago- s…
I understand. The approach we took was to start new designs on KiCad and leave prior work on AD, unless a port is absolutely necessary.
All of our libraries are created using custom tools we wrote nearly 20 years ago. The good news is that these tools can be updated to regenerate the libraries for KiCad. That’ the power of a part description data structure that is independent from the EDA tool.
Starting with KiCad version 6.0 I saw no compelling reason to throw money at AD for the shit job they have been doing maintaining their software. At the end of the day people vote with their wallets. For me this isn’t about free at all. It’s about tool quality and other parameters. We are donating money to KiCad because it is going in the right direction. Altium is not. We were with them for over 20 years. They took us for granted. Goodbye.