Received: |
by ipc.org (Smail3.1.28.1 #2)
id m0v9CXj-0000QBC; Fri, 4 Oct 96 10:52 CDT |
Old-Return-Path: |
|
Date: |
Fri, 4 Oct 1996 08:53:15 -0700 |
Precedence: |
list |
Resent-From: |
|
Resent-Sender: |
|
X-Status: |
|
Status: |
O |
X-Mailing-List: |
|
TO: |
|
Return-Path: |
<DesignerCouncil-request> |
Resent-Message-ID: |
<"2rBUk1.0.bVK.YAJLo"@ipc> |
Subject: |
|
From: |
|
X-Loop: |
|
From [log in to unmask] Fri Oct 4 11: |
02:21 1996 |
Message-Id: |
|
Parts/Attachments: |
|
|
The problem of determining the differences in netlists is compounded
by the issue of component renumbering. For example, if in the old netlist
U1 pin 3 connected to U6 pin 2, and this net remained unchanged as far
as connectivity is concerned but the board was renumbered such that U1
is U2 on the new board and U6 is U7. If you go by the reference designators
this would be flagged as a change, but in terms of connectivity it in fact
is not a change. A program to determine netlist changes would have to
build a connectivity list and link this to the generic or function name
of the device (ls00 for example). You would have to build a two lists of
functions and pin numbers that are tied together, one for each board, then
compare them.
Depending on your cad system, it may be easier to extract this data from
your pcb database than to use the actual netlist. If you are using Cadence
Allegro I am sure it can be done this way, otherwise I suggest that you
contact an AE or some other knowledgable person.
Anyway, that's my two pennies worth.
Ken Barrett
Cisco Systems WBU
San Jose CA
[log in to unmask]
408.526.5625
****************************************************************************
* The mail list is provided as a service by IPC using SmartList v3.05 *
****************************************************************************
* To unsubscribe from this list at any time, send a message to: *
* [log in to unmask] with <subject: unsubscribe> and no text. *
****************************************************************************
|
|
|