Mail Archives: geda-user/2015/09/08/18:44:13
On Sep 8, 2015, at 3:12 PM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>>> I often have many project-specific components. A project may have a default opamp, a default bypass cap, a default resistor package, etc. So, I have some moderately heavy symbols.
>>>
>>> Just come up with an idea of "gattrib". Most often you probably want to use same footprint for a certain "value" and "symbol" or "device" combination. It is also possible you want to add manufacturer part number in the same fashion.
>>>
>>
>> But gattrib is a “touch up” tool. It’s great at that. But when you want to change every low speed dual opamp in a 70 page project, it’s much easier to change attributes in a couple of symbols than to plow through every page and change attached attributes.
>
> gattrib is a attribute editing tool. I say it should be simpler to find "every low speed dual opamp in a 70 page project" in gattrib than searching the schematics. It might for example be useful to add manufacturer part number for every "symbol" <--> "value" <--> "footprint" combination.
>
But if you do this in the symbol, you don’t have to search the schematics. As long as you don’t promote the attribute, changing the attribute in project symbol changes the attribute in every instance in every schematic. This is why my big project gafrc files have (always-promote-attributes '()).
For manufacturer part numbers, in big projects, I do a join of the BOM to a database that relates part specs to part numbers. There are sometimes two such databases, as prototype and production parts are different.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -