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=20120113;
	h=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=I3scpUFBYjv60G4WqkBqGbOdsZZSiKfzMYdrzmZ/OSc=;
	b=OWh2BqN+xiNlc3kuuIWgryp/gCrGPnBtpokZOCCSDYDGH2TubJEU6cL+Mjddx6bjoo
	iPrMp7G95UMaErms/1PIsijCaYz6LUI+Q9vkBDcHlvK06vQ9WDMLJlyijVV/azJOGdlf
	GeCxpJ1kEisnL3pfDHOE6Ufat9evMc3nIQEVPuyFRHNn7jHqpCR3zonvDbvKC1omCZdN
	IVxaFg0wouMwUreP4cr7N7//pRIpcPsb0byUFP5jH78kyIITFEJIkfzo0FOkc4i11VaS
	jJfD4PUNUUCsgicgQeUvXEhwuMH53dVEVhosCBujpyTtGgs1dB+qa4r6etEFcxIZuMeQ
	Gd1A==
X-Received:	by 10.180.189.41 with SMTP id gf9mr14567419wic.95.1445797574807;
	Sun, 25 Oct 2015 11:26:14 -0700 (PDT)
Date:	Sun, 25 Oct 2015 19:26:08 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Pin mapping (separate symbols from mappings)
Message-Id:	<20151025192608.afc58478b5e9e3a59378ba30@gmail.com>
In-Reply-To:	<27CCBD21-273A-45CD-B0E9-6FAA64AFFFB7@noqsi.com>
References:	<20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com>
	<1A419AED-FCCA-4B1F-8589-912435534E2E AT noqsi DOT com>
	<201510191647 DOT t9JGlu4j024585 AT envy DOT delorie DOT com>
	<041FF42A-691F-4E6B-9DEB-8C6B3C2F3E53 AT noqsi DOT com>
	<201510191850 DOT t9JIop8Y029095 AT envy DOT delorie DOT com>
	<A5C4636C-6064-4D9C-9F55-03185FE35379 AT noqsi DOT com>
	<201510192055 DOT t9JKt2o6005861 AT envy DOT delorie DOT com>
	<1E816300-E31E-4B85-B51D-7EAEC5A466BF AT noqsi DOT com>
	<201510192110 DOT t9JLAFKG007281 AT envy DOT delorie DOT com>
	<AAAC7015-AF0E-41BE-83F0-C64862CF2670 AT noqsi DOT com>
	<201510192340 DOT t9JNeo6n020302 AT envy DOT delorie DOT com>
	<D892D347-2B31-4063-9A02-0D54B358070D AT noqsi DOT com>
	<!
	CAC4O8c8O9H5YN+xmiKjU5nfHrO9S2mjn+3bB35MCFpdUDWdtHw AT mail DOT gmail DOT com>
	<EC68D243-0569-4932-B62E-7B068D815CDE AT noqsi DOT com>
	<CAC4O8c9d+U_itePrfKktZ6=XUykscLzg8EFu3Md1VZ=fS_yopQ AT mail DOT gmail DOT com>
	<201510240510 DOT t9O5AvSi019180 AT envy DOT delorie DOT com>
	<CAC4O8c8wD923YXdEr7SJHvc7T+jnNwVM7S6ZO_fiLijq4fCxgw AT mail DOT gmail DOT com>
	<27CCBD21-273A-45CD-B0E9-6FAA64AFFFB7 AT noqsi DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.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

> ...
> For big projects, schematics wind up in printable documentation for reviewers, layout engineers, fabricators, test engineers, and technicians. ...
> ...
A common problem is then last problem is to approve the documents with a signature in the schematic which is first document in the chain. I think a good work flow is to start thin and add inormation in each step. Then some ordering information is changed there should be no need to change all documents because this information is added further down the line maybe in the BOM script or a script added after gEDA BOM script.

> When I wrote gnet-spice-noqsi, I didn’t anticipate how it would change my design flow. It can generate a subcircuit from the same symbol/attribute conventions that the gnetlist core uses when expanding hierarchy. As a consequence, it is very convenient to make the first draft of a subsystem as a subcircuit. It’s much handier to instantiate the subsystem in a test schematic of SPICE-specific components than to mix SPICE components with physical components. One result is that my top level schematics look more like block diagrams.

Then i used gschem today on a hierarchical design today I was thinking why do there need to be numbers on pins in schematic at all? Another work flow be to add the numbers by gnetlist there may still be numbers in special cases then there is a need to distinguish pins with same name. Purpose of netlister then doing layout is to assign footprint pin number but then doing simulation there is no need to assign footprint pin number.


> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com


Nicklas Karlsson

- Raw text -