• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X Capture CIS
  3. Can I Copy Third-Party .pad, .dra, and .psm Files into the...

Stats

  • State Suggested Answer
  • Replies 1
  • Answers 1
  • Subscribers 51
  • Views 78
  • Members are here 0
More Content

Can I Copy Third-Party .pad, .dra, and .psm Files into the Default OrCAD X 26.1 Symbols Folder?

MR202611151244
MR202611151244 1 day ago

Hi everyone,

I’m using OrCAD X 26.1 on Windows. I downloaded a SOD-123FL footprint library that includes three pairs of .dra and .psm files, along with three .pad files.

Within each pair, the .dra and .psm files have the same base name apart from capitalization. For example, one pair is CR_SOD-123FL_SME.dra and cr_sod-123fl_sme.psm. The three .pad files each have a different name, and none of their base names match any of the .dra or .psm files.

  • rx26y47d0t.pad

  • rx38y49d0t.pad

  • rx50y51d0t.pad

Can I copy all of these .pad, .dra, and .psm files into the folder below without editing or renaming them?

C:\Cadence\OrCADX_26.1\share\pcb\pcb_lib\symbols

Does OrCAD X 26.1 search this folder for both package symbols and padstacks by default, or do I need to add it explicitly to psmpath or padpath? If I enter cr_sod-123fl_sme in Capture’s PCB Footprint property, will PCB Editor automatically load the padstack files referenced by that footprint using their original names?

Thanks for your help.

  • Sign in to reply
  • Cancel
  • excellon1
    0 excellon1 1 day ago

    Hi.

    Each footprint should have a unique name otherwise when you copy them to a folder one will overwrite the other. A footprint can use the same padstack that could be used by a different footprint.

    Some notes that may help. Starting with the schematic symbol first.

    Assume a simple 2n3904 transistor that uses a SOD123 Footprint.

    When the symbol is created you need to add attributes to the symbol so that when you package the schematic & generate a netlist it will tell the system what footprint to use.
    The attribute to use is PCB Footprint. If you wanted to uses different footprints for the same schematic symbol also use ALT_Symbols. In the pcb editor this will allow you to place an alternate symbol. Can be very useful.

    Back to the symbol: 3 pins 1, 2, 3  PCB Footprint = SOD123 ( btw dont add the extension of the footprint .dra, Just use the name.)
    Over in the PCB Editor Next: 3 Pins 1. 2 .3 - Suitable padstack for each pin. The saved file will have SOD123.Psm, SOD123.dra, SOD123.PAD.

    In Allegro you need to add suitable paths to where the symbols & padstacks are located. That's under "Setup User Preferences > Paths > Library. Update both the padpath & psm path to where your library is located. There is also a steppath that is used or can be used for step files which are the 3d model of your footprint. Not really needed but nice if you want to display your board in 3d.

    From the perspective of your footprint library maybe something like this for disc folders

    C:\Allegro_Libs
    Transistors
    Resistors
    Caps
    etc.

    When creating footprints try use the same name for the PCB symbol and padstack if possible. As your library grows it will be easier to see what padstacks goes with each symbol footprint. It is also important to have no duplicate footprint names in different folders, otherwise packaging errors will occur when netlisting the schematic.

    One last thing, there are lots of free footprints available on the net. Don't assume they are correct. they may not be. Better to confirm before hitting the go button and producing a board.

    Best Regards.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information