| delorie.com/archives/browse.cgi | search |
| 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=wellesley.edu; s=gmail; | |
| h=subject:to:references:from:message-id:date:user-agent:mime-version | |
| :in-reply-to:content-language; | |
| bh=Gp2sgoIasOz8tHkyR42/lWKm42l/bjCByj4Rrldpuy0=; | |
| b=Hh5tqKtdqX4RJ+ALp4KaJvYSQ0DJhGfaX8Cn6geAyxbXOhZED0oYoSMbMj2rorD96D | |
| BnLGWaYKrdguYJR5pWJ1jged1Mz0XBF7DpEHQPYlUL82x+LvR9mIHKWEiChFlURcCc2U | |
| txSjwPYRyyYRASE41yRwtPKFwCGfRqUlOfcxlkmCQwLbLla82V+7ezJiV/6QJ1jLNk/t | |
| Qd3yHID2lWHKLN1kdq7PQbqh8UsfhDnWNWOt/+cl0WBX0FPJI4k3XJF6BEoRCvVS1ZZX | |
| 76qe9UckICGUkjX1BFizwlC6nPfHYwl6s5HbYjTKBr3AVIAqiTEvpD9sXQ2WNKiWMfpY | |
| 2ywg== | |
| X-Google-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
| d=1e100.net; s=20161025; | |
| h=x-gm-message-state:subject:to:references:from:message-id:date | |
| :user-agent:mime-version:in-reply-to:content-language; | |
| bh=Gp2sgoIasOz8tHkyR42/lWKm42l/bjCByj4Rrldpuy0=; | |
| b=IPgDHG+moJp0PaRytmM4/TrUn9mFxVGUwAi9VBp++NBt6BeN/CLCav9buXAXNyTWuQ | |
| TQUVNOtWjysixvzuVidZ4ylaQKgmnTTnBL+9QBVe3dcoYop6A2gV/3KXO3z6dsYYrwXQ | |
| KWs9x4xM1FMyfEX6mqBuahTm+M6R9l6vwYhsWCd72+LQmcO4YFXK099bntXI1DUbDR72 | |
| +zUL6yHQgceXzHS/t8LRSv5GK24LPVkYLpjFlig4wA0ahwpGCknRRuwoZwWOweiVDxt6 | |
| qkz/6CBDMoE6U3Xjch+sHcWOz2CULvVTPI3cUwg6P3TzbIWJtSetRea2XYEe/Gz4n/Vg | |
| SiuQ== | |
| X-Gm-Message-State: | AKGB3mLOCgxq0U9a0rOgU+7ICOriJK/ne2gbkCMKdKmKZVKmT09wEK+d |
| NAn4vEOW6ohhRlS19ZZFYXNQ+0g1o/Y= | |
| X-Google-Smtp-Source: | AGs4zMYCWM5++9T6NiD8GP77vqSQgAKqzuZqMhSEbVu7FEk0otUzMLLWl9lYa5CbMCz8+c356VZcCg== |
| X-Received: | by 10.55.222.21 with SMTP id h21mr16689800qkj.324.1512320871552; |
| Sun, 03 Dec 2017 09:07:51 -0800 (PST) | |
| Subject: | Re: [geda-user] Including parts in a BOM that are not on the board |
| To: | geda-user AT delorie DOT com |
| References: | <e9595dad-24b6-3507-faba-2c5816c6091c AT wellesley DOT edu> |
| <CA+qhd=8eGaicNHWm+GxuGme6spnMFooujyGUaSXWJ7viz7cOWg AT mail DOT gmail DOT com> | |
| From: | "James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
| Message-ID: | <b43afff6-a41f-74f5-a688-97a36cac4112@wellesley.edu> |
| Date: | Sun, 3 Dec 2017 12:07:50 -0500 |
| User-Agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) |
| Gecko/20100101 Thunderbird/52.4.0 | |
| MIME-Version: | 1.0 |
| In-Reply-To: | <CA+qhd=8eGaicNHWm+GxuGme6spnMFooujyGUaSXWJ7viz7cOWg@mail.gmail.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 |
This is a multi-part message in MIME format.
--------------439E2A8F100E271B97427C9A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
This sounds like a great approach.
John, would you be willing to share your utility script?
Thanks,
James
On 12/2/17 5:09 PM, John Luciani (jluciani AT gmail DOT com) [via
geda-user AT delorie DOT com] wrote:
> 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
> <mailto:jbattat AT wellesley DOT edu>) [via geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>] <geda-user AT delorie DOT com
> <mailto: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
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.
Assistant Professor of Physics
Wellesley College
781.283.3142 (office & lab)
jbattat AT wellesley DOT edu
--------------439E2A8F100E271B97427C9A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
This sounds like a great approach. <br>
John, would you be willing to share your utility script?<br>
<br>
Thanks,<br>
James<br>
<br>
<div class="moz-cite-prefix">On 12/2/17 5:09 PM, John Luciani
(<a class="moz-txt-link-abbreviated" href="mailto:jluciani AT gmail DOT com">jluciani AT gmail DOT com</a>) [via <a class="moz-txt-link-abbreviated" href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+qhd=8eGaicNHWm+GxuGme6spnMFooujyGUaSXWJ7viz7cOWg AT mail DOT gmail DOT com">
<div dir="ltr">
<div>I do this in a separate configuration file. After the BOM
is generated</div>
<div>from the schematics a utility script modifies the BOM using
the</div>
<div>rules in the configuration file.</div>
<div><br>
</div>
<div>The configuration looks something this ---</div>
<div><b><span style="font-family:monospace,monospace"><br>
</span></b></div>
<div><b><span style="font-family:monospace,monospace">[BOM
FILENAME]</span></b></div>
<div><b><span style="font-family:monospace,monospace">add = 1 |
PANASONIC | CR2032</span></b></div>
<div><b><span style="font-family:monospace,monospace">add = 5 |
KEYSTONE | 9061</span></b></div>
<div><b><span style="font-family:monospace,monospace">remove =
J1 | J2</span></b></div>
<div><b><span style="font-family:monospace,monospace">.</span></b></div>
<div><b><span style="font-family:monospace,monospace">.</span></b></div>
<div><b><span style="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>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Dec 1, 2017 at 12:05 PM, James
Battat (<a href="mailto:jbattat AT wellesley DOT edu"
moz-do-not-send="true">jbattat AT wellesley DOT edu</a>) [via <a
href="mailto:geda-user AT delorie DOT com" moz-do-not-send="true">geda-user AT delorie DOT com</a>]
<span dir="ltr"><<a href="mailto:geda-user AT delorie DOT com"
target="_blank" moz-do-not-send="true">geda-user AT delorie DOT com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="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 that are not part of the netlist or
board layout?<br>
<br>
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.<br>
<br>
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.<br>
<br>
Thanks,<br>
James<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature"><a
href="http://www.wiblocks.com" target="_blank"
moz-do-not-send="true">http://www.wiblocks.com</a> Â </div>
</div>
</blockquote>
<br>
<div class="moz-signature">.oOo.oOo.oOo.oOo.oOo.oOo.oOo.<br>
Assistant Professor of Physics<br>
Wellesley College<br>
781.283.3142 (office & lab)<br>
<a class="moz-txt-link-abbreviated" href="mailto:jbattat AT wellesley DOT edu">jbattat AT wellesley DOT edu</a>
</div>
</body>
</html>
--------------439E2A8F100E271B97427C9A--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |