• 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 PCB Editor
  3. Newbie intro

Stats

  • Replies 1
  • Subscribers 160
  • Views 12259
  • Members are here 0
More Content

Newbie intro

Psycho Pete
Psycho Pete over 15 years ago
Hello you MASTER SKILLERS out there!

I would like some information on the following feasibility \capabilities using skill files and this forum locating information files.

Background:

My end goal is for a method for easy library management since Allegro does not already have that capability built into it for land patterns that are contained within a library.  The only true libraries that can be created as far as I know (ones that actually contain schematic symbols etc.) are ones for schematic capture only and not libraries used for land patterns etc.  I will also create libraries in schematic capture that already have thePCB footprint names for the appropriate land pattern based on the version of the schematic symbol part name used along with the manufacture package style in the case of components.  Currently there is no way to make sure that I have or even able to extract library correct library components before placing them into a design.

I am planning on creating a master land pattern library with board files that contain related dra components such as BGA, uBGA, Thru hole components SMD parts and user defined dra files for particular projects.  I will then have all of the dra, pad stacks and flash symbols etc. in one working library folder with the master board file placing the dra component into it so they can all be seen in one board file for easy choosing what land patters are to be used or changed or whatever.  Then if subsequent parts are changed the master library folder they are in can be updated and reviewed with revision dates etc. inside the board file.

 Does any of this make sense?  If it does then maybe SKILL file can help!

My goal is to create SKILL files as follows:

1) I need a skill file to check to see if all pad stacks, shape and flash symbols for a group of .dra symbol files are all present in a working folder.

2) Next,  I need to copy and extract all selected or listed pcb dra\psa symbols and there relevant pad stacks, shape and flash symbols to a separate folder were designated.

3) I would like to check to see if revision dates located in a working directory are current with master library items at another location(s).

Does anyone know of a starting skill files similar to this that I can use OR  if SKILL is not capable of meeting these objectives or a better\easier way before I start all of this work?  (Easier being one person can manage it and not any librarians)

 Also I found a link to this skill tutorial folder but don't understand how to get to it.  Maybe someone can help with intro to manuvering around etc.  <ICinstDir>/doc/sklanguser/sklanguser.pdf

 Thanks in advance,

Pete
  • Sign in to reply
  • Cancel
  • Romme
    Romme over 15 years ago

    Last one is easy :-) :

    <ICinstDir>/doc/sklanguser/sklanguser.pdf

    <ICinstDir> could be C:\Cadence\spb16.3, but is the actual installation folder.

     

    The main question is NOT for newbies...at all.

    1) Search this forum because it has been ask for before.

    2) Shell commands can be done from skill, try look in the sklangref.pdf or algroskill.pdf.

    3) Look at properties and look at the Revision property.

    But do not use the name Revision, as if they (Cadence) ever do a revision check in Allegro, You might have conflicks between Your "revision" and the buildin name Revision. Instead call it like my_Revision.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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.

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

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