Breaking down foot print libraries into categories

Hi Tom

Yes you can have sub directories but they all need to be listed in the psmpath setting, You can also have a padstacks folder that can be different - hence the padpath setting. The only thing you need to do is keep the dra and *.sm file together (a recommendation).

When the tools look for a symbol they start at the top of the psmpath list and work down the list until it finds the relevant symbol name. This means that you have to make sure you don't have duplicates in the folder that you use because it will use the first one it finds...

Tom you can have different folders for your symbols and padstacks but you would have to edit the PSMPATH & PADPATH to tell the system where to look. In Allegro go to Setup User Preferences then go to Paths, Libary.

When you create a package symbol for a footprint there will be 3 files created. .DRA, .PSM, .TXT. You will also have the padstacks used for that particular symbol. What I do is keep the pads,dra,psm, .txt files for each symbol in the same folder. This has helped me cut down on packaging problems when creating a board from the schematic.

By way of an example here is directory structure.

PSMPATH is configured to point to the following "Click expand in that dialog box first" and remove any paths you do not need before making your edits.

c:\my-libs
c:\my-libs\SMD
c:\my-libs\connectors
c:\my-libs\capacitors

PADPATH is configured the same but I also include a folder for vias, again "Click expand in that dialog box first" and remove any paths you do not need before making your edits.

c:\my-libs
c:\my-libs\vias
c:\my-libs\SMD
c:\my-libs\connectors
c:\my-libs\capacitors

When you create your symbols dont use spaces in the name as it will lead to packaging problems. For example SOT_23.dra,SOT23.dra are all ok to use.

Be aware also that it is possible for Allegro 16.5 to blow away your custom PSMPATH and custom PADPATH and replace them with system defaults. I kid you not. This one seems to be a bug. My work-around for this is to make the env file read-only after all edits have been made. Depending on your setup you may or may not come across this hidden treasure, hope you dont : )

Thanks Scott 

Scott, Steve

Exactly what I had in mind to do. Thanksfor the help. Looks like I'll be spending tomorrow converting old libs and setting up new directories / paths and the like.

I just received a PO for a job I quoted a while back and it requires using 16.5 so I am diving into the deep end........ and hoping to surface............

Tom

I keep the .dra organized as you suggested in their own folders.  But at the top of the library path I keep *all* of the .psm files. 
What is the advantage to this?  The pathing is simple and Allegro will package correctly since it only cares about .psm files.

The only disadvantage is preview in OrCAD for footprints which I don't use.

ScottCad said:

Be aware also that it is possible for Allegro 16.5 to blow away your custom PSMPATH and custom PADPATH and replace them with system defaults. I kid you not. This one seems to be a bug. My work-around for this is to make the env file read-only after all edits have been made. Depending on your setup you may or may not come across this hidden treasure, hope you dont : )

Thanks Scott 

Guess what just happened................................... Paths are gone.

Opened service ticket with EMA. We'll see what they say.

Tom