Peter - I've done a series of tests on placing the gnetlistrc file and mucking around with other single changes and will be happy to send you the log file results - please send me a direct ping at trad...@ieee.org and I'll respond, rather than waste bandwidth here.
Long and short: 1) I GET the prefix, no matter the settings or if the rc file is local, in my ~home, or in the /usr/local/gEDA directory. 2) If I remove the reference designators from the level 1 blocks the designators go away, but so does a whole lotta my netlist as well, making the design useless. 3) When removing the Level 1 designators and a deliberate duplicate RefDes is placed in (two independent Level 2 sheets) the gnetlist -g drc2 command does NOT see the duplicate RefDes. 4) I'd love seeing your hacks, but until I understand how they work I will not incorporate them into my design flow - I appreciate but hate using blocks marked "Something Magic Happens Here".. ;-) 5) Current state: I'll clean up the designators in the glossing phase. Cheers! T. On Wed, 2009-12-02 at 13:25 -0500, geda-user-requ...@moria.seul.org wrote: > Send geda-user mailing list submissions to > geda-user@moria.seul.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > or, via email, send a message with subject or body 'help' to > geda-user-requ...@moria.seul.org > > You can reach the person managing the list at > geda-user-ow...@moria.seul.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of geda-user digest..." > > > Today's Topics: > > 1. Re: gsch2pcb Process switches (Peter Clifton) > 2. Re: gsch2pcb Process switches (Kai-Martin Knaak) > 3. Log files [was: Re: gsch2pcb Process switches] (Peter Clifton) > 4. Log files [was: Re: gsch2pcb Process switches] (Peter Clifton) > 5. Missing message? (Jim) > 6. Wrong pin assignment in an edited symbol. (Jim) > 7. Re: Wrong pin assignment in an edited symbol. (John Doty) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 02 Dec 2009 17:32:33 +0000 > From: Peter Clifton <pc...@cam.ac.uk> > Subject: Re: gEDA-user: gsch2pcb Process switches > To: gEDA user mailing list <geda-user@moria.seul.org> > Message-ID: <1259775153.20401.18.ca...@pcjc2lap> > Content-Type: text/plain; charset="UTF-8" > > On Wed, 2009-12-02 at 09:16 -0600, John Griessen wrote: > > Tony Radice wrote: > > > > > 8) What happened: All components got ripped off the board and the new > > > parts file was populated with the parts with prefix-appended part > > > numbers (SA4/R112). > > > > > > I think taking away the netname mangle settings is always going to need > > taking away > > the subschematic references source=SA4.sch etc. > > John's suggestion should work, but I don't think it is a _necessary_ > condition. The gnetlist run worked as expected, right.. > > What is perplexing is that gsch2pcb didn't appear to pick up your > gnetlistrc file. Did the copy of your design have the gnetlistrc file in > the directory? (Was that the directory where you ran gsch2pcb from?) > > Perhaps you could post the log output from the gnetlist.log, and console > output from gsch2pcb? > > NB: Logs are now stored in ~/.gEDA/logs/{progname}-{date}-{counter}.log > > (gsch2pcb doesn't have a log file, only console output). > > > > FWIW... > > I've hit similar issues with boards where disabling hierarchy name > mangling was not an option. (Re-used sub-schematics). > > The two hacks I used to combat the problem were: > > 1. Teach PCB to strip any hierarchy prefix from the displayed netname. I > then manually marked out each subcircuit block. "X1, X2" etc.. with a > box on the silk-screen, labelled with the block name. > > 2. When the board assembler didn't like the above approach, because it > was "confusing" for their assembly techs (and/or) pick+place machine > (and/or) optical inspection software: > > Teach gnetlist to re-map its output using a mapping file. (HACK) > Generated renumber mapping using PCB's "renumber" action. (Fine) > > Apply manual lookup between schematic hierarchy refdes and board refdes > during debugging - evil, but I can't see another way, not without making > a mass duplication of each re-used schematic. (That rather defeats the > purpose of having a single place to change the design of a sub-circuit!) > > > I can make either hack available (they probably already are on my > repo.or.cz branches), but beware that they are very much non-standard. > > > Best wishes, > > Peter C. > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 2 Dec 2009 17:39:29 +0000 (UTC) > From: Kai-Martin Knaak <k...@familieknaak.de> > Subject: Re: gEDA-user: gsch2pcb Process switches > To: geda-u...@seul.org > Message-ID: <hf68oh$ug...@ger.gmane.org> > Content-Type: text/plain; charset=UTF-8 > > On Wed, 02 Dec 2009 17:32:33 +0000, Peter Clifton wrote: > > > NB: Logs are now stored in ~/.gEDA/logs/{progname}-{date}-{counter}.log > > IMHO, $HOME/.foobar should be used for config purposes only. I wouldn't > expect log file there. Why not /var/log/gEDA/foobar.log ? > > ---<(kaimartin)>--- > -- > Kai-Martin Knaak tel: +49-511-762-2895 > Universit?t Hannover, Inst. f?r Quantenoptik fax: +49-511-762-2211 > Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de > GPG key: http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get > > > > ------------------------------ > > Message: 3 > Date: Wed, 02 Dec 2009 17:50:51 +0000 > From: Peter Clifton <pc...@cam.ac.uk> > Subject: gEDA-user: Log files [was: Re: gsch2pcb Process switches] > To: gEDA user mailing list <geda-user@moria.seul.org> > Cc: geda-u...@seul.org > Message-ID: <1259776251.20401.28.ca...@pcjc2lap> > Content-Type: text/plain; charset="UTF-8" > > On Wed, 2009-12-02 at 17:39 +0000, Kai-Martin Knaak wrote: > > On Wed, 02 Dec 2009 17:32:33 +0000, Peter Clifton wrote: > > > > > NB: Logs are now stored in ~/.gEDA/logs/{progname}-{date}-{counter}.log > > I don't like it either.. I was far happier when it dumped them into > `pwd`. My personal preference would be for no log files to be produced > at all (by default), and to dump in `pwd` or $configurable_place when > logging is enabled. > > > IMHO, $HOME/.foobar should be used for config purposes only. I wouldn't > > expect log file there. Why not /var/log/gEDA/foobar.log ? > > /var/ might not be a good place for user specific log files, due to > permission issues. > > In any case.. a big dump of log files in a particular directory means > that it is quite hard to find the one you want to read. (Not that gEDA > log files typically have anything "interesting" in them anyway). > > I'm sure I must have got near a file-count limit on my ~/.gEDA/logs dir > before now! > > Best wishes, > > Peter C. > > > > > ------------------------------ > > Message: 4 > Date: Wed, 02 Dec 2009 17:50:51 +0000 > From: Peter Clifton <pc...@cam.ac.uk> > Subject: gEDA-user: Log files [was: Re: gsch2pcb Process switches] > To: gEDA user mailing list <geda-user@moria.seul.org> > Cc: geda-u...@seul.org > Message-ID: <1259776251.20401.28.ca...@pcjc2lap> > Content-Type: text/plain; charset="UTF-8" > > On Wed, 2009-12-02 at 17:39 +0000, Kai-Martin Knaak wrote: > > On Wed, 02 Dec 2009 17:32:33 +0000, Peter Clifton wrote: > > > > > NB: Logs are now stored in ~/.gEDA/logs/{progname}-{date}-{counter}.log > > I don't like it either.. I was far happier when it dumped them into > `pwd`. My personal preference would be for no log files to be produced > at all (by default), and to dump in `pwd` or $configurable_place when > logging is enabled. > > > IMHO, $HOME/.foobar should be used for config purposes only. I wouldn't > > expect log file there. Why not /var/log/gEDA/foobar.log ? > > /var/ might not be a good place for user specific log files, due to > permission issues. > > In any case.. a big dump of log files in a particular directory means > that it is quite hard to find the one you want to read. (Not that gEDA > log files typically have anything "interesting" in them anyway). > > I'm sure I must have got near a file-count limit on my ~/.gEDA/logs dir > before now! > > Best wishes, > > Peter C. > > > > > ------------------------------ > > Message: 5 > Date: Wed, 02 Dec 2009 12:57:13 -0500 > From: Jim <j...@fayettedigital.com> > Subject: gEDA-user: Missing message? > To: geda-user@moria.seul.org > Message-ID: <4b16aa79.3080...@fayettedigital.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I sent a message to the list, but it hasn't appeared. I had an attached > jpg file, but it was small. Would that have prevented it from being > published? > > Thanks, > Jim. > > > ------------------------------ > > Message: 6 > Date: Wed, 02 Dec 2009 13:12:00 -0500 > From: Jim <j...@fayettedigital.com> > Subject: gEDA-user: Wrong pin assignment in an edited symbol. > To: geda-user@moria.seul.org > Message-ID: <4b16adf0.60...@fayettedigital.com> > Content-Type: text/plain; charset="iso-8859-1" > > Sent this once but never saw it, so I'll try again. Don't know what > happened to the first one. > > I was following the tutorial on > http://geda.seul.org/wiki/geda:gsch2pcb_tutorial#custom_gschem_symbols and > attempted to modify the dual op amp as directed in that tutorial. When > I went to add the two op amps to the schematic I noticed that when I > changed the second one to slot=2, that the output pin remained number 1, > but the input pins changed as expected. I examined the opamp-sym.sym > file that I had edited and found this: > > slot=1 > T 200 1300 5 10 0 0 0 0 1 > numslots=2 > T 200 1500 5 10 0 0 0 0 1 > slotdef=1:3,2,1 > T 200 1700 5 10 0 0 0 0 1 > slotdef=2:5,6,7 > T 200 1900 5 10 0 0 0 0 1 > footprint=SO8 > T 200 2100 5 10 0 0 0 0 1 > footprint2=DIP8 > T 200 2500 5 10 0 0 0 0 1 > symversion=0.2 > T 200 2700 5 10 0 0 0 0 1 > documentation=http://www.onsemi.com/pub/Collateral/LM358-D.PDF > T 200 2900 5 10 0 0 0 0 1 > description=opamp > T 1895 600 8 10 0 0 0 0 1 > net=Vcc:8 > T 1795 400 8 10 0 0 0 0 1 > net=Vee:4 > > That's not the whole file, but just the last few lines. There are no > other references to "slot" in the file. > > > I'm very new at this, so I'm not really sure where to start looking for > a solution. > > Thanks, > Jim. > -------------- next part -------------- > > Sent this once but never saw it, so I'll try again. Don't know what > happened to the first one. > I was following the tutorial on > [1]http://geda.seul.org/wiki/geda:gsch2pcb_tutorial#custom_gschem_symb > ols and attempted to modify the dual op amp as directed in that > tutorial. When I went to add the two op amps to the schematic I > noticed that when I changed the second one to slot=2, that the output > pin remained number 1, but the input pins changed as expected. I > examined the opamp-sym.sym file that I had edited and found this: > slot=1 > T 200 1300 5 10 0 0 0 0 1 > numslots=2 > T 200 1500 5 10 0 0 0 0 1 > slotdef=1:3,2,1 > T 200 1700 5 10 0 0 0 0 1 > slotdef=2:5,6,7 > T 200 1900 5 10 0 0 0 0 1 > footprint=SO8 > T 200 2100 5 10 0 0 0 0 1 > footprint2=DIP8 > T 200 2500 5 10 0 0 0 0 1 > symversion=0.2 > T 200 2700 5 10 0 0 0 0 1 > documentation=[2]http://www.onsemi.com/pub/Collateral/LM358-D.PDF > T 200 2900 5 10 0 0 0 0 1 > description=opamp > T 1895 600 8 10 0 0 0 0 1 > net=Vcc:8 > T 1795 400 8 10 0 0 0 0 1 > net=Vee:4 > That's not the whole file, but just the last few lines. There are no > other references to "slot" in the file. > [cid:part1.06020809.04010901@fayettedigital.com] > I'm very new at this, so I'm not really sure where to start looking > for a solution. > Thanks, > Jim. > > References > > 1. http://geda.seul.org/wiki/geda:gsch2pcb_tutorial#custom_gschem_symbols > 2. http://www.onsemi.com/pub/Collateral/LM358-D.PDF > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: slot2.jpg > Type: image/jpeg > Size: 7898 bytes > Desc: not available > Url : > http://www.seul.org/pipermail/geda-user/attachments/20091202/507c67b4/attachment-0001.jpg > > > ------------------------------ > > Message: 7 > Date: Wed, 2 Dec 2009 11:25:10 -0700 > From: John Doty <j...@noqsi.com> > Subject: Re: gEDA-user: Wrong pin assignment in an edited symbol. > To: j...@fayettedigital.com, gEDA user mailing list > <geda-user@moria.seul.org> > Message-ID: <bec3ddf1-9a97-463f-9e34-07c3ef73a...@noqsi.com> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Check the pinseq= attribute on the output pin. Should be 3, I > suppose, but maybe it isn't. > > On Dec 2, 2009, at 11:12 AM, Jim wrote: > > > When I went to add the two op amps to the schematic I > > noticed that when I changed the second one to slot=2, that the > > output > > pin remained number 1, but the input pins changed as expected. > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > j...@noqsi.com > > > > > ------------------------------ > > _______________________________________________ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > > > End of geda-user Digest, Vol 43, Issue 4 > **************************************** _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user