X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Message-ID: <1382899250.20089.2.camel@pcjc2lap>
Subject: Re: [geda-user] Power to ICs with numslots > 1
From: Peter Clifton <pcjc2 AT cam DOT ac DOT uk>
To: geda-user AT delorie DOT com
Date: Sun, 27 Oct 2013 18:40:50 +0000
In-Reply-To: <CANhYM9GofUvnHj5M9s6oeKN7eO8hQ+sYSsHtdh+MQZfiwF=fgw@mail.gmail.com>
References: 
	<CANhYM9G+eK=9V8L59PyU8nCOO22GVVF1bRb3TRC9kbACazfg8w AT mail DOT gmail DOT com>
	 <201310261908 DOT r9QJ8Vv8025803 AT envy DOT delorie DOT com> <526C9628 DOT 7000201 AT sonic DOT net>
	 <CANhYM9GofUvnHj5M9s6oeKN7eO8hQ+sYSsHtdh+MQZfiwF=fgw AT mail DOT gmail DOT com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.4-0ubuntu1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
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 Sun, 2013-10-27 at 21:04 +0430, James Jackson wrote:
> Hi all,
> 
> 
> Many thanks for this - I've now got a fairly hefty multi-page
> schematic drawn up (using the source=x attribute to link subcircuits
> to a master sheet with the signal routes between subcircuits), with a
> separate schematic for power rails.
> 
> 
> I now have a problem when I run gsch2pcb - the 'split' ICs with the
> same refdes (i.e. power in subcircuit 1 (refdes SS1), signal in
> subcircuit 2 (refdes SS2)) are being placed twice on my PCB, with
> names SS1/U1 and SS2/U1.
> 
> 
> How can I force gsch2pcb to 'do the right thing' here? 


The simple answer is I you cannot.

If you are using a true hierarchy, then it must be separate components
in each piece, and each piece must be identical. slot=... attributes
would need to be identical as well.

If you actually have two different sub-circuits, then you could turn off
hierarchical naming, but I think that defeats the point.


One final option - export connections to the chip you wish to share, and
place that chip on the parent level of hierarchy.


Regards,


-- 
Peter Clifton <peter DOT clifton AT clifton-electronics DOT co DOT uk>

Clifton Electronics