Automating the creation of library components

[jmw]

This applies to Circuit Studio also but I suspect there are more eyes in this forum: has anyone managed to script the creation of components? Like if I have a CSV spreadsheet of info about a manufacturer's line of 0603 resistors with manufacturer and supplier P/Ns, create schematic library components for each of them, and link them to my high, low, and nominal density footprints that I trust. Right now my libraries grow just-in-time with each new value I use. I would really love a better way with less time spent on repetitive library work.

[Pseudobyte]

So with the component structure. You create symbols and footprints separately. You have the option to include parameter information with the symbol, however if you are looking to reuse that symbol for multiple resistors you don't include part information. Instead you create components directly from the line of your spreadsheet. When you pull a part from a component database you are merging a particular line of your spreadsheet with the symbol and footprint.


More information on the specifics can be found , not sure if the same feature set exists in circuit studio. https://www.altium.com/documentation/17.0/display/ADES/((Working+with+Database+Libraries))_AD

[ajb]

DBLibs work well for this.  Define the footprint and symbol once, create as many database entries as you want to define different values (with whatever additional parameters you want) that reference those symbols.  You can still define components 'just-in-time' which is what I do and would recommend (why would you add a component you aren't using or don't specifically intend to use?), in which case you can simply duplicate the database line and edit whatever values you need to create the new component.

[thm_w]

It looks like the AD documentation is quite good linked above. But for reference: https://www.eevblog.com/forum/altium/showing-the-footprint-name-on-the-schematic/msg2627130/#msg2627130

[ddavidebor]

Hello,
As AJB suggested dblibs are the way to go, it will be the easiest to manage. You can start doing them with an excel files, there are a few thread in this forum about it.

[voltsandjolts]

CircuitStudio doesn't support DBLibs so you need a friend with AD to convert them to IntLibs for you.