X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
	bh=CrHS6jkJ4pDQfM/4x57Yxemw4t5YdArA4qcEy6MblnI=;
	b=hQHDwWgRGkGoyuYGwL3I859/ycVMH3aTNsC2ziqp209PvsyV4uoLnmIQjGM36m8gfN
	1PrziLZsqiJPL/IhuL1mhKT4R09+vP2vgcWfzCT2mQTifcVH6ZESOMTOmDgwbiUd8aWq
	97FMxAffcGfmS0FkNLCv6AC62MWuSQKWOB1IO9CFEHXFyq5Z0/i1EfyCb1+J+IGUcvqM
	sFRfVa0P+q6+lcp+Q3G+CmFbn+akjSvLuWbDeIMzbn7NiHeQZzRe2moLJBObLwC9FHYL
	L/H+bM7KCSK/XMGOtuqe9uTHfHnlBnrdEBYxhBDF8OSEy0Ul+3UmEPGTp1hbnuNP+pIR
	2p8Q==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=CrHS6jkJ4pDQfM/4x57Yxemw4t5YdArA4qcEy6MblnI=;
	b=AmvS4JVeGcoEolwZomqDmACrpGHmO6DdqLUtAjhaCXyyn5dbs2kHEnyQ9aXXwehl+H
	ozFOigHY3gsIJW+g0l/w61cdcpGJJZjergOhPPO4c3drAg+q3HaJsRkR/0AyojCVL48f
	Y6s1klkV0V+0JpNyltPGqmVmjtSDSTVeCZ0HpJzEWsdERSJB5M7yV2NFX5PXysiKdz+S
	n23rjVoUBmLhiNPVcLU37d2xapSzg1Cv6s46fBh3DYF12i+MKlKDv3ypOJcyMjstKEQt
	W8LPhjQDTJKcKEFi+zKE7q/avMcGxGaUAIEgGMQ6kLUbGvZtchwB8JwJDHfQI26beRaI
	QaUA==
X-Gm-Message-State:	AJaThX40876o1PRGgon4+K4COH6yQmRRDtcxUX6g1g7Fr8uyPiXfL26L
	ndZPvvcAGk6hZyRBrewerg7nDUzNfqyVQatLcNQ=
X-Google-Smtp-Source:	AGs4zMbxCIKcQ7zBDAEHhSdxs3Hdh5kqEuqjxsUMbn5CiKPPTOO/R42aRvmvhRfG01jqUZU2Dyl+6TYLMXgcMN2J0Sc=
X-Received:	by 10.25.160.212 with SMTP id j203mr5783807lfe.92.1512252556706;
	Sat, 02 Dec 2017 14:09:16 -0800 (PST)
MIME-Version:	1.0
In-Reply-To:	<e9595dad-24b6-3507-faba-2c5816c6091c@wellesley.edu>
References:	<e9595dad-24b6-3507-faba-2c5816c6091c AT wellesley DOT edu>
From:	"John Luciani (jluciani AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Sat, 2 Dec 2017 17:09:15 -0500
Message-ID:	<CA+qhd=8eGaicNHWm+GxuGme6spnMFooujyGUaSXWJ7viz7cOWg@mail.gmail.com>
Subject:	Re: [geda-user] Including parts in a BOM that are not on the board
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--001a114123787408fd055f62bc2c
Content-Type: text/plain; charset="UTF-8"

I do this in a separate configuration file. After the BOM is generated
from the schematics a utility script modifies the BOM using the
rules in the configuration file.

The configuration looks something this ---

*[BOM FILENAME]*
*add = 1 | PANASONIC | CR2032*
*add = 5 | KEYSTONE | 9061*
*remove = J1 | J2*
*.*
*.*
*.*


John L




On Fri, Dec 1, 2017 at 12:05 PM, James Battat (jbattat AT wellesley DOT edu) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> Hi folks,
>
> Do you have recommendations for how to incorporate components into a BOM
> that are not part of the netlist or board layout?
>
> For example, I'd like my BOM to include jumpers, specialized cabling, and
> the crimp pins and connector required to mate with an on-board header.
>
> I was thinking of creating a separate .sch file, e.g. "peripherals.sch"
> and including it in the BOM generation but not when I "import schematics"
> in the layout. But am curious to know how others handle this.
>
> Thanks,
> James
>



-- 
http://www.wiblocks.com

--001a114123787408fd055f62bc2c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I do this in a separate configuration file. After the=
 BOM is generated</div><div>from the schematics a utility script modifies t=
he BOM using the</div><div>rules in the configuration file.</div><div><br><=
/div><div>The configuration looks something this ---</div><div><b><span sty=
le=3D"font-family:monospace,monospace"><br></span></b></div><div><b><span s=
tyle=3D"font-family:monospace,monospace">[BOM FILENAME]</span></b></div><di=
v><b><span style=3D"font-family:monospace,monospace">add =3D 1 | PANASONIC =
| CR2032</span></b></div><div><b><span style=3D"font-family:monospace,monos=
pace">add =3D 5 | KEYSTONE | 9061</span></b></div><div><b><span style=3D"fo=
nt-family:monospace,monospace">remove =3D J1 | J2</span></b></div><div><b><=
span style=3D"font-family:monospace,monospace">.</span></b></div><div><b><s=
pan style=3D"font-family:monospace,monospace">.</span></b></div><div><b><sp=
an style=3D"font-family:monospace,monospace">.</span></b><br></div><div><br=
></div><div><br></div><div>John L<br></div><div><br></div><div><br></div><d=
iv><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Fri, Dec 1, 2017 at 12:05 PM, James Battat (<a href=3D"mailto:jbattat@=
wellesley.edu">jbattat AT wellesley DOT edu</a>) [via <a href=3D"mailto:geda-user@=
delorie.com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks,<br>
<br>
Do you have recommendations for how to incorporate components into a BOM th=
at are not part of the netlist or board layout?<br>
<br>
For example, I&#39;d like my BOM to include jumpers, specialized cabling, a=
nd the crimp pins and connector required to mate with an on-board header.<b=
r>
<br>
I was thinking of creating a separate .sch file, e.g. &quot;peripherals.sch=
&quot; and including it in the BOM generation but not when I &quot;import s=
chematics&quot; in the layout. But am curious to know how others handle thi=
s.<br>
<br>
Thanks,<br>
James<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature" data-smartmail=3D"gmail_signature"><a href=3D"http://www.wiblocks.c=
om" target=3D"_blank">http://www.wiblocks.com</a> =C2=A0</div>
</div>

--001a114123787408fd055f62bc2c--

- Raw text -