Another tip, when doing schematic capture, say you want to create a new transistor: Simply grab the "NPN" or "PNP" component from the "Symbols" library and place it on your schematic, double click and edit the properties (for example, change the name to MMBT3906) now click attach pattern and select SOT-23, make sure the pins are connected correctly (click a pad on the pattern and then click a corresponding pin on the component in the double pane window at the top), now click OK and OK, right click the new transistor on the schematic and save it to your component library. You can also place an existing pattern from the library, right click it and select "Ungroup Pattern", edit it, regroup the pattern and save it back to the library. right on the board, then select all the items, right click and select "Group into Pattern", now double click the new pattern, give it a name and click OK, then right click the new pattern and select "Save to Library" and it will be saved into the currently select library. You can do this in DipTrace! While doing a PCB layout, you can create pads, silkscreen, mask, etc. To modify them, save the specific footprint to your own private library & work on it from there. That library contains about 95% of all the different footprint variations for SOJ, SOP, SOT, TO devices. Do remember, if you are looking for lots of stock footprints, open the standard DipTrace "Pattern" library. If there was a component in an existing library that was close to what you required, you simply placed it in your current design space, modified it & saved it with a different name. It was very straight forward & easy to understand. You could design your own component (schematic & footprint) within your actual design space, then highlight it & save it directly to your own library. I actually preferred how Protel (the predecessor to Altium) did it many years ago. but this operational requirement is not that easy for new-comers to understand. I understand why the standard DipTrace Libraries are "locked" (can't be changed by the end user) & that we have to generate a new library to save all our own specific parts. Yes, DipTrace's library operation is the weakest part of their software, mainly because many aspects of their library operation are not so logical.
0 Comments
Leave a Reply. |