X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=date:from:to:subject:message-id:mail-followup-to:references
	:mime-version:content-type:content-disposition:in-reply-to
	:user-agent;
	bh=hWsCg5r251UCAnyopWPpHy0a8BXU/UVQdK0sr3CET80=;
	b=c40PHoBJ5sUDcgda1xPOzP4iWBC7qMRHKiHV53xR/AiehJbcGB88i0M9PRmePhfLGJ
	HGZOpq0f+BZAVY0nJD5BiKRZPi899Md0fz1MydDNDPa+HxKQPRYvj7/xcYkZ/Q8HdkrX
	ERqiFYPqaV+4CcS4tLuYLGa+a+ZYXmxRCXr4srOXlw/36C2rCbTVHSoCO0ib0OwN5Z3u
	4qki0b8tyz+wwCbz6gTD11M9ehpgOEDkE02VWwTnl273g8456KT/5x70zXZ/F20w8LDf
	vSAAGLOP/moHP75db+nceR6narVDKabTmE4gx4JlbsQGqQ3qO5CX6GRSDY6ef/WCNDBc
	NKtg==
Date:	Sat, 18 Aug 2012 22:23:19 +0400
From:	Vladimir Zhbanov <vzhbanov AT gmail DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user]
Message-ID:	<20120818182319.GA20043@localhost.localdomain>
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<CACPio-6k5KWuEeHhn=1r8mxYb2HRpXzC5DrTWSaqDxufw7u2YQ AT mail DOT gmail DOT com>
	<k0jl2k$ibn$1 AT ger DOT gmane DOT org>
	<CACPio-4unK57Re-HUn_yyhBTt-P-Fph5B0cmVnE6gBzYnXUyww AT mail DOT gmail DOT com>
	<20120817161012 DOT GA28947 AT localhost DOT localdomain>
	<CACPio-5yU_r49y5NcGK-9gHTPwuXmM17Cx_Qdigx_mnzcx7Z1w AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CACPio-5yU_r49y5NcGK-9gHTPwuXmM17Cx_Qdigx_mnzcx7Z1w@mail.gmail.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
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

On Sat, Aug 18, 2012 at 10:29:15AM -0400, Nathan Stewart wrote:
> Apparently, the INPUT and IO components need to have a value=INPUT or
> value=IO. I also had issues with the net= attributes on my power pins
> - I had them labeled +7V and -7V, and at least -7V is not legal.  So I
> replaced them all with Vdd and Vss, even though emotionally I'm going
> 'but but but there's nothing in the circuit that says it has to be
> MOSFET!!!") and I secretly know in my heart that these represent a +/-
> 7V split rail supply.
> 
> When I did fix the pin/subcircuits, the IO tags hooked up to the
> subcircuit symbols also lacked the value=IO, and this appears to have
> prevented the S1/PIN substitution in a way that confused me.  My schem
> _appears_ to be all good now.

To throw away all doubts you can see the gEDA gTAG example from the gEDA
distribution. It contains all you need to make schematics with
subcircuits. The simple 'grep' shows that its schematics have neither
'value=INPUT' nor 'value=IO' attributes. There is 'device=INPUT' there.
OTOH, I see that io-1.sym in the distribution does contain 'value=IO',
and input-2.sym contains 'value=INPUT' (while input-1.sym contains
'device=INPUT'). However, these symbols are not used in gTAG (this
project uses in-1.sym, out-1.sym with "device=..." attributes).
There are an example how to label your pins there. You probably can name
them something like 7V+ and 7V-. AFAIK, the attribute value cannot begin
with a dash.

-- 
VZh
http://vzhbanov.byethost33.com

- Raw text -