3D STEP NOTE: To create a 3D STEP model, in the Library Expert, you will need to make sure 3D STEP generation is on by selecting the '3D Model' checkbox underneath cancel to flyout the 3D Model tab, set the options, and click 'Create'. In Allegro (provided you have 3D functionality as part of the Allegro License), select 'Place 3D Models via Script' and save it as a preference.
To properly convert parts into Allegro, certain steps must be taken before any translation is performed.
1. Set the Pad Path and Psm Path
Open Allegro and select - Setup
> User Preferences
Choose the Paths + Library category and set your padpath and psmpath to point to your current working directory. Click Expand if it isn't selected.
At the top of the padpath list choose New (Insert) and place a "." (period) as the Directory name. Next, move the "." to the top of the form. This will direct the PCB Editor to look in the current working directory for the pad stack files. Select "OK" when complete. Repeat for the psmpath.
Both forms should look similar to this:
This sets the current directory as a searchable path for proper linkage when running the main script created by Library Expert.
2. Turn off the Drill Warnings
Open Allegro and go to Setup >
Choose the UI + Pad_designer (Padstack_Editor if 17.2) option in the tree on the left and set your padstack_nowarning_drill and padstack_nowarning_display to checked.
Click Apply and then OK to close the window.
Non-plated pad stacks will always have a pad smaller than the drill. With this checked, those warnings will be automatically bypassed. If you don't do this, you will need to save the pad stack with warnings. A process which must follow #3 exactly.
3. Bypass Drill Warnings
This step is only necessary if you weren't
able to set #2, and later tried to generate a part with a non-plated pad stack.
In that situation, you will get the following warning:
To bypass this, you cannot simply click the X of the Pad Stack Warnings window and then close pad_designer. The .pad file will not get generated and when the Footprint Script goes to draw the pins it will not be able to link to the proper pad stack. Instead, it will either use the latest pad stack it could generate, or no pad stack at all. Either way, it will be wrong. To fix this, use the following 5 steps every time you see the above window.
1) Close the Warning. Using the X is fine
2) Go File -> Save in Pad Designer
3) Close the Warning again
4) Click Yes to Save the Pad Stack with Warnings
5) Close Pad Designer
This generates the .pad file properly and when the footprint script goes to link to it, it will be successful.
4. Understanding the Options
There can be anywhere from 8 to 10 options to understand as shown in the window below:
Version - Drop-down that sets the version of Allegro you currently use.
Output Directory - This is the directory which contains a directory with the footprint name in which the files are to be generated.
Parts Per Script- Typically used when putting out lots of parts at once. If you're outputting say 100 parts, with this value set to 1, the program will open and close 100 times (once for each part) when generating parts. If you set this to 100 parts per script, the script would generate 100 parts and open and close Allegro once. It will save a lot of time when batch processing, but for most implementations where only a handful of parts may be put out at any one time, its suggested that you stick with the default.
No Probe - This will place a shape on the No Probe layer that will match the selected constraints. The options for constraints are Component Body, the Footprint Extents, or the Courtyard.
Excess - This expands or contracts the No Probe extents by a static amount in millimeters. This feature has no effect if No Probe area is not selected.
Run Scripts in Background (NoGraph) - This turns off the graphic display of the programs being run. This does have a major downside in that if there is an error, you won't be able to see it. Its particularly problematic if you run multiple licenses of various Allegro tools that provide a selector window. In that case, this must be turned off so you can select the proper tool, or the script will appear to be 'hung'. It's just waiting for input at the selector window as to which tool you want to run, but can't show you that because you have it running in the background. It's off by default and suggested to be off, particularly given that you can watch the scripts draw the parts.
Output Files in Lower Case - Just what it says. The script files will all be forced to lower case. Usually run with it off.
Auto-confirm Loss of Accuracy - When the
pad_designer goes to run, there is a quirk in that some versions of Allegro
will provide a message prompt for changing of the units, others will not. To
set this properly, set it to off. When the part goes to process and run
pad_designer, if you see the following window, turn it on and select the Save
Entries as Preferences button. From that point on it will auto-confirm this
Place 3D STEP Models Via Script - This is only usable if your license for Allegro supports 3D Modeling. If it doesn't, turn this off. If it does, what this will do is insert the model into the footprint just before script completion.
Auto-Confirm SSM Save - Certain versions of Allegro will pop a confirmation box when a SSM (complex pad stack) goes to save. This option is to allow auto-confirmation if you have one of those versions. Normally it's off, and you may want to turn it on if you get annoying confirmation boxes at the end of a complex pad stack save. If you do not get confirmation messages, simply leave as default.
Autorun Batch File - The program generates a set of files in the Output Directory. Selecting this will allow the overall batch file to immediately start once that translation is complete.
Skill - Currently unused and forced off.
Truncate Long Names - Certain versions of Allegro have a 30-character limit for names. Try running with it turned off, and if it has issues, turn it on. As such, this will keep the file names under the limit.
IMPORT TO ALLEGRO
I. Understanding the Script Files
These files are created in a directory containing
the footprint name in the Output Directory you select when creating the FPX
output. As an example, let's assume the Output Directory is C:\Temp. The
files will be placed in a new directory CAPC100X50X56L25N, which is the Footprint
Name of the part that was generated:
.psr - A pad_designer script which generates the pad stacks. These will be labelled .scr in v17.2 or later.
.txt - Device file used by Allegro.
.scr - Script for the full Allegro tool which draws the final footprint and places the pad stacks that were generated.
.bat - Batch file which runs each of the scripts in order to generate the final output. It first runs the pad_designer and generates the pad stacks, then it runs the full allegro tool and generates the part itself using those pad stacks.
There are also complex pad stacks for certain parts, which get generated before the regular pad stacks, but the scope of these instructions are to a high-level overview of the process, and not go too deep in detail.
II. Processing the Script Files
Simply run either Allegroload.bat, and the batch file should take care of the rest.
NOTE: Library Expert parts are built for Positive Plane Technology. If you have issues, simply switch over from Negative to Positive Plane.
1. Verify Pad Stack is created
a. Version 16.0? Current ISR is required Help > About - if the release is Version 16.0 Pxxx then it is the base release. Download current HotFix from Cadence.
b. Pad stack created and no pad in symbol verify - padpath is pointing to the directory that FPX is running in from Preparation #1.
2. Are there multiple versions of Allegro installed?
a. Is the PATH pointing to the correct version?
3. Files to aid in troubleshooting
a. Defined variables from Allegro. This lists the install path, working directory, system path.
Setup > User Preferences > List all save to text file
b. Journal files (recordings of current executed commands) usually located in working directory.
allegro.jrl (list Allegro commands and can indicate errors)
pad_designer.jrl (list pad designer commands and can indicate errors)
4. Scripts that include SKILL will only execute by Allegro L w/Performance and above.
5. Footprints created in Version 16.0 and 16.01 can NOT be used in version 15.7 or older.
6. After the Land Pattern is generated, the *.dra, *.psm and *.pad are created and package symbol is verified, the builder files can be deleted as desired.