I can make symbols, footprints, schematics, and PCB's with either a quick tutorial or the old copy/paste from existing, similar parts. I tried Eagle & KiCad and found them too awkward for a casual user. I'm not trying to have the program control impedances or define net classes no power user here. I typically use the autorouter with perhaps a few nets hand routed beforehand, finishing with a copper pour for ground, say. I can't comment on the quality of the copper pour for a heavy user or more than 2 layer capabilities. Once again, though, I'm a hobbyist with respect to PCB's, so the software doesn't represent my livelihood. I didn't want board physical size restrictions. I like to have my designs stored wherever I like and the software developed for the current OS, so I feel I can comfortably continue to use the software, even if the company goes out of business. I bought it at the Starter level (300 pins, 2 signal layers). I feel DipTrace has a reasonable price point for a light user as well as a reasonable upgrade path if/when your use becomes heavier. I wanted a program that was easy to learn and return to. I send out a board at most 1 time per 3 months. KiCad actually has a resistor 0805 and a capacitor 0805 which is a bit weird, but I expect it's just to stop forum posts from people asking "Where are the 0805 capacitor footprints?" Those same footprints can be used with a capacitor, meaning you only need ONE 0805 footprint. Thus you have ONE resistor and 100 different footprints. The relationship between component and footprint is many to many, so data doctrine would always point to a normalised join of two entities. It also makes sense to me from an entity modelling and normalization point of view. Granted in commercial the BOM is already more or less decided and changing a component is more difficult if you buyers are already ordering 400,000 of them.
I frequently change my mind about component footprints and change them. I was able to change an entire board from THT to SMT without changing the schematic once. I don't do commercial design, so it works for me. How does your current application create your BOM? I expect it's a script or a length setup you had to setup originally. I expect if you took the time to learn it you'd find it was probably just as fast.
I think it's just a different way of working and requires different procedures.
0 kommentar(er)
