Running AnsTranslator on the Command Line
The format for running AnsTranslator on the DOS command line is:
AnsTranslator <input> <output> <switches>
Where:
AnsTranslatoris the complete path to AnsTranslator.exe<input>is the required path to the design to be translated<output>is the optional path to the edb directory. By default, the export type is edb. If no<output>is specified, the edb design is created in the same folder as the<input>file/folder.<switches>are any of the following options:-i=inputFormatSpecifies the file format for translator input. If not specified, the file type is deduced from the file extension. Gerber designs must be explicitly specified though this option.
Options: AutoCAD, GDSII, Extracta, IPC2581, ODB++, Gerber, or anfv2
-o=outputFormatSpecifies the output format. The default output is edb.
Options: edb and ControlFile
Note:An IPC2581 rev.c exporter has been introduced as a beta feature in Anstranslator. To use this functionality, enter [design file].aedb [IPC-2581 file].xml -i=edb -o=ipc2581 at the command line. Flex and multi-zone designs, non-laminate designs, and backdrills are not currently supported, and padstack instances that include backdrills will be exported without them. Designs are flattened during export. Circular, square, and rectangular pads are exported as intended, while all other pad shapes are converted to polygons, except thermal pads, which are ignored and not exported. Circular and square holes in the design’s padstack definition are exported as intended, whereas all other hole shapes are converted to polygons and exported as a rev. 4 *.xml.
-c=controlFileNameSpecifies the path to a control file (*.xml). If not specified, the control file is still used (*.xml) as long as it has the same name and path as the
<input>file/folder.Note:To generate nets during import, enter:
<GDS_CELL_RULES>
<WHITE_BOX_CELLS>*</WHITE_BOX_CELLS>
</GDS_CELL_RULES>
This will automatically generate all nets.
-l=logFilenameSpecifies the path to log file (*.log). By default, the log file is created in the same folder as the
<output>edb file.-w=workingDirectoryNameSpecifies the directory to use for any file manipulation needed by the translation. If not specified, the directory for the input is used as the working directory.
-t=technologyFileSpecifies the path to a technology that defines a stack up. The file can be *.layermap, *.ircx, *.vlc.tech, or *.itf. *.itf must have a mapping file specified with them. Use this switch when a technology file is provided. Users should specify either a control file (-c) or a GDS layer mapping file (-g).
-f=filterfile.textUse to specify all signal layers to import into the design as a list of layer names separated by end of lines. Via layers will only be imported if both the start and end layers are included in the list. The file can be *.ircx, *.itf, or *.vlc.tech. Requires a technology file (-t) switch.
-g=gdsMappingFileSpecifies the path to a GDS layer mapping file (*.map).
-vSpecifies verbose logging (without this option, only warnings and errors are logged).
-a(nfcmp)Optionally used for ANFV2 import to specify a *.cmp file
A new OASIS translator (i.e., Open Artwork System Interchange Standard) has been introduced as a beta feature in Anstranslator. To use this functionality, enter -i=oasis at the command line. All arguments that are valid for GDSII files should work with OASIS (*.oasis) files. The GDSII Import window in the Ansys Electronics Desktop (AEDT)TM electronics systems design platform now supports importing OASIS files.