www.delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-help-bounces using -f |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-help AT delorie DOT com |
Subject: | Re: [geda-help] Picaxe 14M2 |
In-Reply-To: | <CAMw9acDYQfg5egZDxMOUD_EC9PcF7X8xYcnuaSE8G4o+A1=+HQ@mail.gmail.com> (geda-help@delorie.com) |
Date: | Wed, 06 Mar 2019 14:39:26 -0500 |
Message-ID: | <xnwolbvlld.fsf@envy.delorie.com> |
MIME-Version: | 1.0 |
Reply-To: | geda-help AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-help AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
"Torben Friis (friistf AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com> writes: > I think it all boils down to the question of where I should put the > following statements in hc-12.sym: > > device= hc-12 > footprint=hc-12.fp > refdes=U? Those go outside any pin/component clause; they could go right after the 'v' line for example. Of course, you still need a suitable T line for each. > Present hc-12.sym: > v 20110115 1 ... can go here ... > P 0 600 200 600 3 0 0 > { ... don't put here ... Or you could edit the symbol in gschem and add those attributes anywhere "on the background" (i.e. not part of any pin).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |