Hi Brad,

Right.  But these are very easy to spot visually.  The reason for a
systematic approach is to find anything one might have missed on visual
inspection.  I find the antenna problem a very annoying problem with Protel
and similarly (going back some years) PCAD and Tango.  The genesis of the
antennas is the approach of not deleting old junk traces from an update.  As
we talked about on the sci.electronics.cad newsgroup, this approach might be
better than Pads or Cadstar, where the routes can not exist without
connectivity.  But the good side of the Pads and Cadstar approach is that
you never get antennas unless you deliberately put them in by some
work-around technique.

Yours truly,
John W. Childers

----- Original Message -----
From: Brad Velander <[EMAIL PROTECTED]>
To: 'Protel EDA Forum' <[EMAIL PROTECTED]>
Sent: Friday, May 31, 2002 12:45 PM
Subject: Re: [PEDA] Systematically find unwanted antennas


> John,
> my personal thoughts on the spreadsheet method was that it would
> only work in the limited case where the track was only connected at one
end.
> In my past I have found a great deal of stubs where this method wouldn't
> work because there were actually two tracks connected at both ends to
tracks
> atop one another or just slightly misaligned atop each other.
>
> Sincerely,
> Brad Velander.
>
> Lead PCB Designer
> Norsat International Inc.
> Microwave Products
> Tel   (604) 292-9089 (direct line)
> Fax  (604) 292-9010
> email: [EMAIL PROTECTED]
> http://www.norsat.com
>
> Visit us at Booth 2G2-09 at CommunicAsia 2002 in Singapore June 18-21.
>
>
>
> > -----Original Message-----
> > From: John W. Childers [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, May 31, 2002 9:59 AM
> > To: Protel EDA Forum
> > Subject: Re: [PEDA] Systematically find unwanted antennas
> >
> >
> > From: Abd ulRahman Lomax <[EMAIL PROTECTED]>
> > > Most stubs can be classified into two kinds: stubs which
> > terminate at a
> > pad
> > > and stubs which do not. The latter could fairly easily be found by
> > > analyzing spreadsheet data from a PCB; essentially one
> > would be looking
> > for
> > > a track which has an endpoint which does not coincide with any other
> > > endpoint on the same layer, nor does it coincide with a via or pad.
> >
> > How would one generate a useful spreadsheet for this purpose?
> >
> >
> > Thanks
> > John W. Childers
>


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
*
* To leave this list visit:
* http://www.techservinc.com/protelusers/leave.html
*
* Contact the list manager:
* mailto:[EMAIL PROTECTED]
*
* Forum Guidelines Rules:
* http://www.techservinc.com/protelusers/forumrules.html
*
* Browse or Search previous postings:
* http://www.mail-archive.com/proteledaforum@techservinc.com
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to