Mime-Version: |
1.0 |
Content-Type: |
text/plain; charset="us-ascii" |
Old-Return-Path: |
|
Date: |
Mon, 1 Apr 1996 08:29:53 -0500 |
Precedence: |
list |
Resent-From: |
|
Resent-Sender: |
|
X-Status: |
|
Status: |
O |
X-Mailing-List: |
|
X-Sender: |
|
TO: |
|
Return-Path: |
<TechNet-request> |
Resent-Message-ID: |
<"T8UQQ.0.nW6.GYzNn"@ipc> |
Subject: |
|
From: |
|
X-Loop: |
|
Received: |
by ipc.org (Smail3.1.28.1 #2)
id m0u3jYv-00006hC; Mon, 1 Apr 96 07:22 CST |
From [log in to unmask] Wed Apr 3 16: |
45:10 1996 |
Message-Id: |
<v01510100ad85887058a3@[11.18.1.8]> |
Parts/Attachments: |
|
|
>
> Has anyone had experience outputing CAD netlists using the IPC-D-356
> format?
>
> In addition, has anyone had experience doing this in Intergraph?
>
We have a DRC (design rule check) which outputs the IPC-D-356. It pulls in
the Allegro skematic and the gerber files and output the IPC-D-356, and all
the other DRC-type violations. It is a stand alone DRC. It does not
require the Allegro skematic to generate the IPC-D-356 file.
When we buy boards, we send the IPC-D-356 out with the other design data,
and ask suppliers to use it to validate their test program which they
generate from the Gerber Data. So far so good, but have less than one
years history.
Call if you want more info.
====================================================================
George Franck
PWB Product Assurance Phone (703) 560-5000 x2648
E-Systems M/S N408 Fax (703) 280-4613
7700 Arlington Blvd E-Mail: [log in to unmask]
Falls Church Va 22046 E-Mail: [log in to unmask]
====================================================================
|
|
|