From:  Michael Binning@MITEL on 06/01/2001 12:30 PM GDT

I'd be lying if I said I had never forgotten to merge.

To help things out though, we always use the same layers.

Mech 1 - board outline and production details

Mech 2 - top side designators that are not wanted on overlay

Mech 3 - top copper that is to be merged

Mech 4 - bottom side designators that are not wanted on overlay

Mech 5 - bottom copper that is to be merged

If either mechanical layers 3 or 5 are present, I need to pay attention.

Mike.





"Jason Morgan" <[EMAIL PROTECTED]> on 01/06/2001 12:20:03

Please respond to "Protel EDA Forum" <[EMAIL PROTECTED]>

To:   "'Protel EDA Forum'" <[EMAIL PROTECTED]>
cc:    (bcc: Michael Binning/SWI/Mitel)

Subject:  Re: [PEDA] PCB Library part with internal connection



Also a good idea, though open to error, I can hear cries of "oops forgot to
merge" already.

I suppose though this would also work with embedded inductors; Create an
embedded
component layer pair for each routing layer, place metal for inductor
component
on embedded component layer then when producing the Gerber merge the layers
together.

Bummer if you forgot to merge though and no DRC is going to notice a
'missing'
component.

A DRC rule that allowed a short between two pads for a given footprint with
a net
class or default net name (a bit like no-net) called 'embedded component'
would be a much better solution as its less open to human error. -
Suggestion No2 for the day, (though not new as I expect this has been asked
for many times in the past)

J.







* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
*
* To leave this list visit:
* http://www.techservinc.com/protelusers/subscrib.html
*                      - or email -
* mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum
*
* Contact the list manager:
* mailto:[EMAIL PROTECTED]
*
* Browse or Search previous postings:
* http://www.mail-archive.com/[email protected]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to