 
| Received: |
by ipc.org (Smail3.1.28.1 #2)
id m0tpRxy-00005JC; Wed, 21 Feb 96 21:45 CST |
| Content-Type: |
TEXT/PLAIN; charset=US-ASCII |
| Old-Return-Path: |
|
| Date: |
Wed, 21 Feb 1996 22:49:00 -0500 (EST) |
| Precedence: |
list |
| Resent-From: |
|
| cc: |
|
| MIME-Version: |
1.0 |
| Status: |
O |
| From [log in to unmask] Mon Feb 26 12: |
33:17 1996 |
| TO: |
|
| Return-Path: |
|
| X-Status: |
|
| Resent-Sender: |
|
| Resent-Message-ID: |
<"fmyr31.0.-_E.9R-An"@ipc> |
| Subject: |
|
| From: |
|
| X-Loop: |
|
| In-Reply-To: |
<199602212121.QAA23186@electron> |
| X-Mailing-List: |
|
| Message-ID: |
|
| Parts/Attachments: |
|
|
Thats why they have D Code lists to check against and thats why you
do Gerber Ins so that you check your artwork so that there are no
errors before you have film developed and go to board...food for
thought...
Henry R. Linneweh
CAD PCB Design Specialist.....
On Wed, 21 Feb 1996, Tom Kavendek wrote:
> You should be delivering a CAD generated netlist which identifies
> every pad on the board (top and bottom) and it's associated net name,
> and xy location. In this way, if the gerber post processing does
> something strange, it would be caught. You have to remember that gerber
> artwork generation is a post process that is normally robust, but may
> introduce errors.
> If a gerber extraction is done by the bareboard mfr., number 1 - it is
> more expensive and 2) it will include these possible gerber errors.
>
> Most bareboard mfrs can send you the format that this netlist file
> should be in.
>
> Tom Kavendek
> Lucent Technologies
> Murray Hill, N.J.
>
|
|
|
