Stats

  • Replies 4
  • Subscribers 19
  • Views 10665
  • Members are here 0
More Content

Access skill variable in .scr script

olov

Hi,

I'm trying to write a script that will automate the gerber output process. To do this properly I would like to use parameter data (e.g. article numbe for the board) that is stored in a file to control the output files prefix.

When in skill mode I have no problem accessing this information, but now to the problem.

When starting the gerber output I use a .scr file with following content:

setwindow pcb
artwork
setwindow form.film_control
FORM film_control filename_prefix 12345678
FORM film_control select_all
FORM film_control database_check NO
FORM film_control create
FORM film_control cancel

The prefix, e.g. 12345678, I would like to be able to change based on the parameter I can access when in skill mode:

skill Parameters["hq_pcb_article"]

but I cannot fidn a way to transfer this information between these two domains? any ideas?

BR Olov

  • DavidJHutchins

    I would try replacing the line:

    FORM film_control filename_prefix 12345678

    with something like the following:

    skill axlShell(strcat("FORM film_control filename_prefix " Parameters["hq_pcb_article"])))

  • Ejlersen

    Hi

    I would recommend that you stick with SKILL for automation whenever possible. 

    SKILL is more robust across releases than scripting

    Best regards

    Ole

  • olov

    Thanks!

    Works great

    OK, sounds like a good approach. Do you have any input on what skill commands to use to do the corresponding to above, i.e. generate the output gerber files?

    BR Olov 

  • Ejlersen
    in reply to olov

    you would use axlRunBatchDBProgram with artwork command

    Make sure to read documentation for both axlRunBatchDBProgram above and also artwork.txt in folder below which shows the commandl ine options you need to pass when using axlRunBatchDBProgram with artwork

    C:\Cadence\SPB_17.2\share\pcb\batchhelp\

    Best regards

    Ole

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.