I have build a VB program that builds a schematic and board file based on some user inputs. I am seeing a problem during the board build section. I am using the command line interface to open a blank Allegro board file and run a script which runs a SKILL file that builds up a complete board. The problem I am seeing is that the build of the board is sometimes very slow. If I open Allegro seperatly, run the script with the File -> Script command the program runs much faster. I have looked online and there are mentions of memory issues with command lines.
Has anyone else seen this problem or does anyone know of a faster way to open a board file and build it up with a SKILL program.
Have you tried running the command line interface without opengl and graphics? then you could open the job afterwards, that might help?
start /wait allegro -s dostuff.scr -nographic myboardtemplate.brd
In reply to Ejlersen:
Thank you for your response. I considered that option but the -nographic switch is not available on a windows system according to the v16.3 documentation. Has this chnaged for v16.5.
In reply to phughes:
This is not new, I've used it on windows for years :-)
Thanks for your help. That worked and it seems to run faster.
Hello Cadence Users,
I have tried to use the non-graphical option to speed up the building of a board using the Allegro command line and an input script but the run time for the board build is still too long. Does anyone know of another option or workaround that may improve the speed.
You can turn off the master DRC switch and disable dynamic shapes (Display -> Status). When you are finished constructing the board, turn on dynamic shapes, update them and then do a drc update. If adding constraints to a board, it is much faster to load them via a techfile instead of using Allegro scripts to load individually via constraint manager (e.g. avoid "cmgr" commands in your script)
You should also look at your script and remove any "zoom" and "roam" commands. Leave any "trapsize" commands since they are required.