[PCB_FORUM] Re: Cadence set-up question

Get a copy of the free IPC land pattern viewer.

http://landpatterns.ipc.org/default.asp


There is no standard naming convention. That's the fun part.

Each part vendor and IPC has managed to name the same package different names.

I like the structure of the IPC names and the mechanicals are included for the 
actual part.

If the vendor's mechanicals match the IPC mechanicals then chances are that the 
land patterns will work.

Look over the naming convention in the viewer and if part name has not been 
created then use the same syntax to create your own names.

My personal order of preference:

IPC suggested land pattern

Manufacturer suggested land pattern

Create my own land pattern


Hope this helps.

Dave



Dave Seymour
Ixia
919.267.4840
________________________________
From: icu-pcb-forum-bounce@xxxxxxxxxxxxx 
[mailto:icu-pcb-forum-bounce@xxxxxxxxxxxxx] On Behalf Of Carrow, Dennis
Sent: Friday, May 29, 2009 10:44 AM
To: 'icu-pcb-forum@xxxxxxxxxxxxx'
Subject: [PCB_FORUM] Cadence set-up question

Good Day everyone,
            I'm an ex-cadence user that has been using Expedition for the past 
4 years.  My company has now bought a seat of Allegro(16.2 PCB Design HDL L 
with Design Entry HDL)  and I'm in the process of setting up the file structure 
and library.  This isn't my area of expertise so I was hoping I can get some 
expert advice from those that have gone through this process before.  I'm to 
the point where I need to start creating library parts.  My question is what is 
the standard naming convention used for footprint land patterns?  Some places I 
worked used the RLP numbers and some have used Jedec.  I understand there's no 
right or wrong way but I'm just interested in what other folks are doing and 
why.  This is the first time I've had to set-up any PCB system and man, there 
are a lot of details to hammer out.  If anyone has some valuable does and 
don'ts they would like to share I'd love to hear them- off line of course.  
Thanks!  -Dennis

dcarrow@xxxxxxxxxx

Other related posts: