Hacker News new | ask | show | jobs
by dragontamer 983 days ago
Each of the steps I outlined above, #1, #2, #3 and #4, are a new set of keyboard buttons and GUIs to learn for KiCad.

Yes, it's a lot to take at once. But fortunately, you only have to move forward one step at a time.

--------

Maybe starting at #2, Schematic, would be the only 'out of order' thing I'd recommend. There might be enough library parts to fill out a large section of your schematic (or maybe not...).

Inevitably, you will have to tackle #1 (symbol editor) and #3 (footprint editor) before you finish #2 and start step #4.

---------

I agree it's a lot to take in at once. But after you do all four steps and understand them, there is a sense of order and process. Especially as #1 (setting the pinout on a symbol), #2 (saying what pins are connected) and #3 (saying which pins belong where physically) are all accomplishing computerized checks to make #4 less error prone.

It's a lot of info to tell KiCad, and any other PCB editor will need all this information as well, so none of it was wasted effort.

It's just a lot of up front complexity that really is intimidating.

---------

#2 schematic editor might be a good starting point because it's what you expect to do. #1 and #3 are somewhat unintuitive steps.