X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-UW-Orig-Sender: fpm AT homer02 DOT u DOT washington DOT edu
Date: Mon, 11 Jan 2016 10:52:26 -0800 (PST)
From: "Frank Miles (fpm AT u DOT washington DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Re: off-board parts/wiring
In-Reply-To: <20160108182822.3c4b5f2d183143b4a41680dd@gmail.com>
Message-ID: <alpine.LRH.2.01.1601111041200.28725@homer02.u.washington.edu>
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com> <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601040930510 DOT 18447 AT homer02 DOT u DOT washington DOT edu> <AF9F11C6-29A4-4558-85C8-973AB80BADFF AT noqsi DOT com>
 <CAC4O8c_ckyybeLDoV9oGM8cdH08goyqw6zG0eFn4dYdG_wchwg AT mail DOT gmail DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601060831110 DOT 31979 AT homer02 DOT u DOT washington DOT edu> <29B50AD8-DCD0-4048-B888-711C5D8E1E65 AT noqsi DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601070826250 DOT 1447 AT homer01 DOT u DOT washington DOT edu>
 <20160107175042 DOT 5e06aad2bf09818a8886d6f7 AT gmail DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601080823510 DOT 14656 AT homer03 DOT u DOT washington DOT edu> <20160108182822 DOT 3c4b5f2d183143b4a41680dd AT gmail DOT com>
User-Agent: Alpine 2.01 (LRH 1217 2009-02-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-PMX-Version: 6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.1.11.184816
X-PMX-Server: mxout21.s.uw.edu
X-Uwash-Spam: Gauge=X, Probability=10%, Report='
 TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, NO_URI_HTTPS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __FRAUD_BODY_WEBMAIL 0, __FRAUD_WEBMAIL 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0'
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
Precedence: bulk

On Fri, 8 Jan 2016, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:

>>>>>>  I can't use the
>>>>>> recommended direct PCB gschem-schematic-import method due to some special
>>>>>> schematic post-processing (mostly eliminating off-board parts/wiring, which I
>>>>>> want to have on the schematic),
>>>>>
>>>>> I attach graphical=1 to those to tell gnetlist that they don?t go into the netlist.
>>>>
>>>> That may work for whole parts, but doesn't work when particular pins/nodes need
>>>> to be separated from the board (thus the "/wiring").
>>>>
>>>>  	-F
>>>
>>> If you make one schematic for each circuit board it will work.
>>>
>>> It is possible to make a symbol matching connector output and put it higher than the circuit board(s) in the hierarchy. If you add a "source=board.sch" attribute you could get down into the hierarchy but symbol is not electrically connected to connector so for example DRC will not work for the whole circuit.
>>
>> ...
>>
>> I have to wonder - what's so hard about getting pcb to understand
>> a circuit from a netlist?
>
> Well you said if you make one schematic for each circuit board which suggest you try to make several circuit board from one schematic. Symbols without a footprint do not show up on the circuit board.

Sorry, but that's not quite what I said.  Most commonly my
need is for a single circuit board.  And as I said, I want
these few connections to be on the same sheet as it is more
readily comprehended by others.

> Sometimes it is useful to draw a schematic connecting several circuit boards and if you add a source attribute with the filename of the schematic to the symbol you get hieratchical design.

Thanks.  I am quite familiar with hierarchical design in gschem,
having used it on a variety of projects.  Its current implementation
is kinda unwieldly but (other than the problem with buses) useful.

To repeat my previous question:  what's so hard about getting pcb to
understand a circuit from a netlist?  This would allow a variety of
custom "schematic alterations" that cannot happen if gPCB reads the
schematic directly.

Maybe there's an alternative - if a duplicate schematic can be made,
and the duplicate schematic altered appropriately.  This seems much
more complicated than editing a netlist without some non-graphical
tool for editing the schematic, so I'm not recommending this approach.

 	-F