X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
Message-ID: <57B4BDC6.202@xs4all.nl>
Date: Wed, 17 Aug 2016 21:40:54 +0200
From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14
MIME-Version: 1.0
To: geda-help AT delorie DOT com
Subject: Re: [geda-help] Adding BOM items to the Schematic
References: <1471113613 DOT 4652 DOT 21 DOT camel AT yahoo DOT com> <20160817183731 DOT GA6846 AT localhost DOT localdomain> <57B4B832 DOT 1090403 AT xs4all DOT nl>
In-Reply-To: <57B4B832.1090403@xs4all.nl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-help AT delorie DOT com

Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-help AT delorie DOT com] 
wrote:
> Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-help AT delorie DOT com] wrote:
>> On Sat, Aug 13, 2016 at 06:40:13PM +0000, Glen Ruch 
>> (GW DOT Ruch AT yahoo DOT com) [via geda-help AT delorie DOT com] wrote:
>>> I would like to add BOM items to the schematic.  The schematic is the
>>> source and I would like to avoid the tracking issues that crop up when
>>> using a separate spreadsheet.
>>>
>>> Typically adding things without a refdes e.g. enclosure, Solder 60/40,
>>> screws, stand-offs, IC sockets, PCB part number, etc.
>>>
>>> gattrib would not allow me to add line items.
>>>
>>> For example, if I add a LM555 to a schematic, it is really an assembly
>>> consisting of a DIP socket and an IC.  If I would use a text editor on
>>> the .sch file, I can add a DIP socket to the LM555 component, however
>>> when viewing the BOM using gattrib the U2 LM555 device name is
>>> overwritten by the DIP socket device name and there is only one line
>>> item not two.
>>>
>>> Extract from test schematic:
>>> C 43000 57000 1 0 0 lm555-1.sym
>>> {
>>> T 45300 59400 5 10 0 0 0 0 1
>>> device=LM555
>>> T 44800 57000 5 10 1 1 0 0 1
>>> refdes=U2
>>> T 43000 57000 5 10 0 0 0 0 1
>>> footprint=DIL 8 300
>>> T 43000 57000 5 10 0 1 0 0 1
>>> Distributer=DigiKey
>>> T 43000 57000 5 10 0 1 0 0 3
>>> device=DIP_Socket
>>> Distributer=DigiKey
>>> DistrPartNumber=112233-4455-11
>>> }
>>>
>>>
>>> I've tried the gnetlister without success, cycling thru the various
>>> backends:
>>> gnetlist -g partslist3 -o test.bom test.sch
>>>
>>> Suggestions?
>> Use other attribute names for socket properties, say:
>> socket-device, socket-Distributer and so on.
>>
> Hi,
>
> FWIW, in case you didn't read already ... have a look at:
>
> http://wiki.geda-project.org/geda:faq-gnetlist
>
> and read the paragraph which mentions the use of a file named 
> "attribs" with the "key"s listed (maybe order does matter ?, and use 
> "key" and "value" as in "key=value" as per gschem attribute convention.
>
> Just my 0.02 EUR.
>
> Kind regards,
>
> Bert Timmerman.
>
>
oh, and one attribute per text entity ... parsing of multiline 
attributes is probably not implemented yet,

oh, and BTW: dashes "-" do not always play nice in a "key".

Kind regards,

Bert Timmerman.