Posts tagged with 'Import/Export'

Supported Formats for Import/Export

Format Import Export
ODB++ x x
GenCAD 1.4 x x
CC/CCZ x -
Fabmaster (Cadence Allegro Fabmaster, or FABmaster) x -
Eagle x -
IPC-2581 a/b x x
Gerber RS-274-X x x
DPF x -
IPC-356 x x
DXF x x
IDF x x
Sieb & Meyer x x
Excellon 1,2 x X
Image files
x x
(e.g. MS Excel, Txt-Lists)
x x
AVL x -
PDF x x
3D formats:
Google SketchUp files
3Ddata as obj files
x -
STEP x x
3D PDF - x
WebGL - x
Many Machine Formats - x
Any ASCII Format - x



CAD and CAM systems are often produced by different companies, so, it is necessary to agree on a CAD-to-CAM data exchange format. ODB++ is such a format and arguably the closest to a global industry standard. Developed and released by Valor Computerized Systems, Ltd. in 1995, it was and still is continuously improving to meet the evolving needs of PCB designers, fabricators, and assemblers.

In 1997 together with component names the ++ suffix was added in reference to C++ and in 2000 development of an XML version started, which ended in 2008 when this new ODB++ format, called ODB++(X), was donated to the Association Connecting Electronics Industries (IPC) in an attempt to merge GenCAM (IPC-2511) and ODB++ into a new format called IPC-2581. ODB++ is the de facto standard for intelligent PCB data exchange containing all data necessary to fabricate, assemble and test in a single hierarchical file structure which makes it superior to the only format more popular: Gerber.

Some of the major benefits of ODB++ include:

  • minimization of supply-chain risks related to data transfer errors and potential introduction of errors through integration of data from different sources (both occurring because of different interpretation of various file formats)
  • enabling shorter processing times and the highest-possible levels of automation
  • supported by all major vendors of CAD, DFM and CAM tools

The aforementioned reasons explain why ODB++ is the standard format of PCB-Investigator, which is always used internally even if the data were imported in a different format.


AutoCAD DXF (Drawing Exchange Format) is a widespread file exchange format for CAD data developed by Autodesk, Inc., that enables vector data exchange as well as 2D and 3D graphics drawing. Originally introduced in December 1982 as part of AutoCAD 1.0, it was intended to provide an exact representation of the data in the AutoCAD native file format DWG (Drawing), but since Autodesk didn't publish its specifications until many years later, correct imports of DXF files have been a problem since the beginning. Another problem is that DXF typically is dimensionless meaning it doesn't provide all necessary information to permit interoperability with other programs. That's why it's essential that the viewer knows the unit that was used to produce the drawings. With AutoCAD supporting more complex data types over the years, DXF has become less useful but due to its good documentation and with being the lowest common denominator of all CAD based systems, it is still quite popular and therefore also supported by PCB-Investigator.


Among ODB++ and IPC-2581 GenCAD is one of the most important file formats for PCBs. The primary focus of the GenCAD standard rests on fabrication and testing. GenCAD contains all information about a PCB ranging from net, component and route information, to complete layer setups in a single file which provides additional protection from data loss.

In some software you have export options, for a good result (e.g. for bottom side components) use e.g. this setting in target software:
How to set GenCad output options in target to get valid file for PCB-Investigator
(angle counter clockwise and no flip option)


The Intermediate Data Format (IDF) is a 3D CAD data exchange format which is specifically designed for the import and export of PCB data. It consists of two files, a component library (* .emn) and a layer assembly file (* .emp). The component library file contains information about the PCB dimensions (PCB outline), the position and orientation of the components, the position of the mounting holes, cutouts and the barrier areas, the layer assembly file contains information about the file dimensions and the height of the individual components.

Gerber RS-274-X

Gerber is an open ASCII vector format for 2D binary images, which allows a smooth data exchange between CAD (development) and CAM (production), since it can be imported as well as exported by all current CAD and all common CAM programs. It is particularly used to output the layout data for printed circuit boards. However, it must be noted that the Gerber format can only contain one layer per file, so multilayer PCBs must be recorded in several Gerber files. The RS-274-X extension is a two-dimensional bi-level vector-oriented image description format that includes coordinates and commands and contains a complete, unambiguous description of a circuit board. Since the format does not describe which position is displayed, it is recommended making the filename visible in the layer function . Although the export of the format provides a list of all component connections to networks and bores, no components and network data are supported. This deficiency can, however, be offset by using the IPC-D-356 network list.

If you search for instructions how to modify gerber data to run analysis and exports see this page.

Sieb & Meyer

The Sieb & Meyer format - as well as the Excellon format; they only in a few details - was created to operate CNC drilling and milling machines. Therefore, it supports only simple attributes and drill tool definitions and is primarily used to output drill information, like for example the diameter of the holes. As a rule, each drill file also requires a separate tool file, which indicates the diameter of the tool used.

Reports in TXT, Word, Excel, HTML

In many cases PCB-Investigator offers the possibility of exporting data in different file formats - e.g. as lists for MS Excel, TXT, as well as detailed descriptions in MS Word or HTML - as reports. Though no real output format, reports contain valuable information for identifying potentially problematic areas. Please refer to the plugin description section in this manual for further information.


IPC-2581 ("Offspring") is the result of the aforementioned attempt to merge GenCAM with ODB++(X). Like its predecessor ODB++(X) too is XML based. Contrary to ODB++ however IPC-2581 is a common free format which is developed by 40 enterprises under the leadership of Cadence Design Systems and which specifications can be downloaded freely. In 2011 an industry consortium was created to support the development of IPC-2581, a step at least partly motivated by the fear the more popular ODB++ format could be vendor locked by Mentor at some point. These 40 companies include big names like Fujitsu, Nvidia, Cisco,... which see the big potential of the standard to prevent data transmission errors and of course save costs. Even Ucamco, the owners of the Gerber format, and finally also Mentor, the current owners of ODB++, joined the consortium.

IPC-2581 contains data about the layer structure, copper structures per layer, assembly order, material information, drill data and test points with the names of their corresponding network names and components including coordinates and rotation values for the placement. Furthermore, IPC-2581 promises to be able to document all necessary steps in one consistent record.


IPC-D-356 is an electrical test format, traditionally used to supplement Gerber files with netlist descriptions. It was originally designed to define a standard netlist format by which bare board test information can be represented. That means storing netlist information along with XY coordinates as well as referencing pins and other components. Done right IPC-D-356 contains all information a test system would need to perform a bare board check in a single consistent file.


The AVL (Approved Vendor List) is a supplement file, which contains a list of all approved and debarred manufacturers of all PCB components. There can be multiple approved manufacturers for one component. The various approved manufacturers are usually determined by strict criteria (e.g. quality, delivery capability, delivery times, cost intensity,...) defined by the purchasing department.


STEP (short for "Standard for the Exchange of Product model data") is a popular exchange format connecting the world of electronics and mechanics. Usually it is used to share 3D models between users with different CAD systems. STEP goes beyond the simple exchange of gemoetry like DXF and IGES. You can integrate all forms of CAD data models (wire, surface and volume models) in the geometry description.


Eagle (short for Easily Applicable Graphical Layout Editor) is the native format of Autodesks schematic editor (also named Eagle) for designing PCBs. 

Net Groups

The NetGroup Wizard can be used to create net groups and to add or remove nets to them.

Open the NetGroup Wizard with clicking the "Net Groups" button.

The following dialog will show up.

1. The two important tabs contain the following options.

The net groups are always stored within the ODB design. Sometimes, you want to import net groups from another design. Prior to that, export the current net group to have a backup of them. In the import you can select between different file formats (xml, txt, dcf, dcfx, csv, rulf) to add net groups from other software (e.g. Xpedition or Zuken) or if you select xml from other PCB-Investigator exports.

Import Format List:

Show Import Formats for Net Groups

The "Tools" tab has three important functions.

  • Analyse (see next chapter): Clicking the analyse control, a new dialog will open.
  • The PCB Stack-up Calculator is a calculator for the PCB stack-up.
  • Generate Net Groups: If you want to generate net groups automatically, you can use the "Generate Net Groups" contol. Clicking this option, will open the following dialog.

To create net groups, the net names will be used. The number is the number of letters to be tapped. All nets with the same beginning will then be added to the net group. The net groups names depend on the tapped letters.

2. The summary of controls allow you the following operations:

  • Select: The "Select" control can be used to focus the selected net group.
  • Unselect: If you selected multiple net groups, you can deselect one or more net groups to isolate the net groups you want to inspect.
  • Activate Layer: This allows you to see the layers nets of the net groups when selecting a group.
  • Include Components: "Include Components" also shows you the connected components to net nets of the net groups that you are selecting.
  • Apply all Colors: If the net group has been colored, the "Apply all Colors" button allow you to color all nets with the same color.
  • Optimize View: With this option you can zoom to the area of the net group and all included nets.

3. The button "Create Group" allows you to create you own groups with the desired group name.

4. This control contains all net groups which are deposited in the ODB dataset. More options to edit net groups can be found by right clicking on a net group.


  • Rename: Here, you can rename the net group
  • Add Description: You can add text that will be shown behind the group name in the extra tab.
  • Assign Color to Group(s): Using this functionality, you can assign a color to the group within the list. It won´t assign color to the nets on the design.
  • Apply Color in PCB-Investigator: If you assigned a color to the group, you can now assign this color to the nets included in the net group. Now, the nets will be shown in the design with the same color.
  • Zoom to the Net Group: Here, you can zoom the net group. If you double left click a net group entry, you will also zoom to the net group.
  • Remove Color Assignment: Use this function to remove color assignments.
  • Delete/ Delete All: You can either delete the selected net group or all by using either "Delete" or "Delete All".

5. Every net of the net group will be shown here, if a group in the group view (4) is selected. To remove a net of the net group, right click the net you want to remove and click remove.

6. If y net group (4) is selected, you can add single nets to the net group with clicking a net in the view with the number 6 and clicking the add button. There are two different add buttons:

  • The upper add button will just add nets which are selected on the design. If no net is selected, the button can´t be used.
  • The button below adds the nets you select in the bottom right net list.

For more details have a look to this short video:


CC/CCZ is the native format of CAMCAD Professional


A '.fab' file is the native format of 'Cadence Allegro Fabmaster', or of 'FABmaster'.  Both tools export '.fab' files, but with different content and definitions. PCB-Investigator can import both.

OIB Server Manager

When you open the "SIPLACE OIB Connector" (in the 'Machine Export' menu) the first time, you have to first enter your OIB server settings by clicking on the gear button (1)

Following dialog will open:

In this server manager, you can organize multiple OIB servers. To create a new one, please press on the little green "+" button and enter a name.
Afterwards you'll have to specify the OIB server adress by entering an IP/Hostname + Port, or directly enter the 'net.tcp://...' adress (1).

When this is done, you'll have to specify two server directories by clicking on the small browse button (2):

  • "Component Main Path": This is the OIB directory, where your part library is located. Parts in this directory are only read, but never written or changed.
  • "Component User Path": This is the OIB directory, where parts, that do not exist in the main path yet, are created by PCB-Investigator. The user has to complete the information of those parts in the SIPLACE Software and can then move them to the main path later.

Click "Save" and close the dialog to preceeed.

Placement List Creator

To start, please select a server and click "Connect" (1).

With the "Placement List Creator" tab, you can create placement list elements for each component side on the OIB server.

To start, you have to do a few settings in block (2):

  • 'Current Step': Select the board step, for which placement lists should be created
  • 'Group Components by': Choose whether to use the internal 'Part Number' or any other Property in your CAD data to get the list of part numbers. These part numbers are the 'key' to search for parts on the OIB server.
  • 'Component Type Filter': You can filter components by the '.comp_mount_type' attribute, e.g. to get only SMT components

Always when you change settings in (2), you will have to 'Refresh' the list and 'Match Parts via OIB' again (3).

When the matching process is done, you will see all your filtered parts in the list (4), including an overlay of the matching OIB part definition on the selected server. Found OIB parts are centered on the CAD package center. Details of the found OIB part and the fitting state are listed on the bottom side (5).
The 'Status' column indicates, whether a OIB part was found or not, and if the found part fits onto the CAD package. The condition for fitting is, that the pin definition of the OIB part must at least partly overlap the CAD package pin.

If the found part does not fit, you have the possibility to shift its position or to rotate it until it fits (6). With the two buttons in this block on the right, you can open the property dialog of the CAD component or zoom to it.

If the OIB part has a polarity definition, this polarity marker is visualized in red. The fitting alorithm then also uses the polarity information, to recognize if the component is correctly rotated (CAD polarity pin is same as OIB polarity pin).

Example of the fitting process (6) (by rotating 90° clockwise):



When clicking the 'Create Placement List via OIB' button (7), you are asked to select a folder on the OIB server and enter the name for the placement list(s) for top and/or bottom side. Afterwards, the placement lists are created via OIB. Missing parts, that where not found during the matching process, are automatically created in the 'Component User Path' (see 'OIB Server Manager'). Those created parts are dummy parts without any real outlines or pin definitions. Their information must be completed by the user in the SIPLACE Software afterwards. Components that have the ".comp_ignore" attribute are marked as 'omitted' in the placement list.

Here is a screenshot of the result in the SIPLACE Software:

Board Creator

After having created the placement list of the single board(s), you can create the panel data with the "Board Creator" tab.

To start, you have to select the panel step that should be created (1). It is also possible to create panels in panels (recursive), when the most outer panel is selected.

For the given panel, the included single board(s) is/are listed unter (2). Here an already existing placement list on the OIB server must be selected per board and side. If the placement lists where created before in this session with the "Placement List Creator", the information is already prefilled. If not, you can click the small browse button and select the right placement list.

In the block (3), there are different options available:

  • "Export Board Outline": if checked, the complex board outline of the CAD data is exported. This may need some time. If not checked, the bounding box is used
  • "Export Fiducials": if you want to export objects with ".pad_usage=gfiducial/lfiducial", please check this box and select a fiducial type from the OIB server by clicking on the little browse button
  • "Export Inkspots": if you want to export objects with ".board_mark=bbm" (Bad Board Marker), please check this box and select a fiducial type from the OIB server by clicking on the little browse button
  • "Requires trace information": This field on the OIB server can be set or not here
  • "Requires PCB barcode verification": This field on the OIB server can be set or not here
  • "Default processing orientation": 0/90/180/270° for Top or Bot (sets the corresponding fields on the OIB server)

In the block (4), you can choose which CAD layers should be exported and imported in OIB for this board per side. It is mainly thought for paste/mask layers.

When clicking the 'Create Board via OIB' button (5), you are asked to select a folder on the OIB server and enter the name for the board entry. Afterwards, the board is created via OIB.

Here is a screenshot of the result in the SIPLACE Software:




With the "SIPLACE QD Exporter" tool, you can create '.qd' files including placement lists and board information for ASM machines.

To start, you have to do a few settings in block (1):

  • 'Current Step': Select the board or panel step, that should be exported
  • 'Group Components by': Choose whether to use the internal 'Part Number' or any other Property in your CAD data to get the list of part numbers. These part numbers are the 'key' to search for parts in SIPLACE.
  • 'Component Type Filter': You can filter components by the '.comp_mount_type' attribute, e.g. to get only SMT components

Always when you change settings in (1), you will have to click at 'Refresh' to update the list. In the list (2), you will see all packages and the corresponding parts for each step or sub-step of your selected (panel) step.

It is then important so select list entry by list entry to check the rotation correction. If a entry is selected, you'll see the package drawing on the right side. You have to rotate this package to be displayed in exactly the same way, as it is defined on the ASM machine ('make it ASM conform'). You can confirm this by checking the "User Confirmed" checkbox in the list's last column. The rotation can be done by using the buttons in (3). Here, the rotation can also be reset and with the two buttons in this block on the right, you can open the property dialog of the CAD component or zoom to it.

In the block (4), you can choose which CAD layers should be exported as gerber files next to the '.qd' file. These gerbers can then be also imported in SIPLACE. The mirroring/translation of the bottom gerber is already done in the gerber itself, so that you do not need to transform the layers in SIPLACE.

In the block (5), there are different options available:

  • "Export Fiducials": if you want to export objects with ".pad_usage=gfiducial/lfiducial", please check this box and enter the fiducial path/name that is defined in SIPLACE.
  • "PCB Height": here you can enter the height of the PCB in the given unit.
  • "Project name": this name of your project, will be exported also to the '.qd' file
  • "Export Top Side": if checked, you'll get a '.qd' file for the top side of your PCB
  • "Export Bottom Side": if checked, you'll get a '.qd' file for the bottom side of your PCB

When clicking the 'Export QD File(s)' button (6), you are asked to select a folder where the files are exported to.


Here are some screenshots of the result in the SIPLACE Software:



Message System

You can address various exports with different MessageIDs.
For this you must use the function:
→ bool parent.SendMessage(string ReceiverName, string SenderName, int MessageID, List object Params).
Insert the ReceiverName given in this page and the desired MessageID of the export. Please pay attention to the parameters you have to pass for the export files!
  • "PCBI_GenCadImport.PCBI_GenCadExport"
    • ID: 1 Import GenCad file

      Params: string importPath

      ID: 2  Export GenCad file

      Params: string exportPath

      Example: parent.SendMessage("PCBI_GenCadImport.PCBI_GenCadExport", "script", 2, new List object(){ newGenCad })


  • "PCBI_IPC2581B.PCBI_Connection"
    • ID: 1 Import IPC2581b file Params: string importPath
      ID: 2 Add or modify Stackup Params: string/IFileData exportPath
      ID: 3 Export Stackup Params: string/IFileData exportPath
      ID: 4 Export to IPC2581b file Params: string/IFileData exportPath
      Example: parent.SendMessage("PCBI_IPC2581B.PCBI_Connection", "script", 4, new List object (){ newIPCF })


  • "PCBI_DXFImport.PCBI_Connection"
    • ID: 1 Import DXF file

      Params: string importPath

      ID: 2 Change Settings as XML

      Params: stringimportPath

      ID: 3 Save DXF file




      IFileData filedata

      Dictionary<double, List PCBI.MathUtils.PointD> outputElements

      IStep step

      string outptLayerName

      bool? unitInch

      bool unitInch


      ID: 4 Export file Asynchronus




      string name

      XMLSettingsOutput outputSetting

      List ILayer outputLayers

      IStep step

      bool param


      ID: 5 Export in DXF format




      string exportPath

      IStep step

      List ILayer outputLayers

      XMLSettingsOutput outputSetting

      bool param

      Example: parent.SendMessage("PCBI_DXFImport.PCBI_Connection", "script", 2, listParams);


  • "CncExport.PCBI_Connection"
    • ID: 1 Export SiebUndMeyer



      string exportPath

      PointD zeroOffset

      double settingDouble

      bool settingBool

      Dictionary<double, List PCBI.MathUtils.PointD>


      MoveRoutingDirection routingOptionDirection

      XMLSettings _settings

      string layerNames


      ID: 2 Export Excellon2



      string exportPath

      PointD zeroOffset

      double settingDouble

      bool settingBool

      Dictionary<double, List PCBI.MathUtils.PointD>

      MoveRoutingDirection routingOptionDirection

      XMLSettings _settings

      string layerNames


      ID: 3 Export Posalux

      PointD zeroOffset
      double settingDouble
      bool settingBool
      Dictionary<double, List PCBI.MathUtils.PointD>
      MoveRoutingDirection routingOptionDirection
      XMLSettings _settings
      string layerNames

      Example: parent.SendMessage("CncExport.PCBI_Connection", "script", 1, listParams);


  • "PCBI_MachineFormats_ImportExport.PCBI_Connection"
    • ID: 1 Export Viscom SI Params: string exportPath
      ID: 2 Export Viscom XML Params: string exportPath
      ID: 10 Export Parmi Params: string exportPath
      ID: 11 Export Goepel Params: string exportPath
      ID: 12 Export Modus Params: string exportPath
      ID: 13 Export Yamaha Params: string exportPath
      ID: 14 Export Tri Params: string exportPath
      ID: 15 Export Mycronic Data Params: string exportPath, bool exportTHTs

      Example: parent.SendMessage("PCBI_MachineFormats_ImportExport.PCBI_Connection", "script", 1, listParams);

  • "PCBI_Step_Export.PCBI_Connection"
    • ID: 1 Export Step file


      string outputStepName
      List string exportOptions
      ExportOptionAll expOptionAll

      Example: parent.SendMessage("PCBI_Step_Export.PCBI_Connection", "script", 1, listParams);
  • "PCBI_AOICheck.PCBI_Connection"
    • ID: 1 run check without gui Params: string param
      ID: 10 open dialog and show it Params: string param
      Example: parent.SendMessage("PCBI_AOICheck.PCBI_Connection", "script", 1, new List object() { newAOI })


  • "PCBI_BareBoardDRC.PCBI_Connection"
    • ID: 1 open result file Params: string param
      ID: 2 show DRC dialog Params: string param
      ID: 3 run check and save result file Params: string fileName
      Example: parent.SendMessage("PCBI_BareBoardDRC.PCBI_Connection", "script", 1, new List object() { newDRC })


  • "PCBI_ComponentsAnalysis.PCBI_Connection"
    • ID: 1 Export HTML with all options Params: string exportPath
      Example: parent.SendMessage("PCBI_ComponentsAnalysis.PCBI_Connection", "script", 1, new List object(){ newAnalysis })


  • "PCBI_CreepageDistances.PCBI_Connection"
    • ID: 1 Export result in user DIR with given Nets Params: 

      string outputPath
      PCBI_NetGroups.NetGroup netGr
      PCBI_CreepageMeasure.XMLCreepageSettings settings

      Example: parent.SendMessage("PCBI_CreepageDistances.PCBI_Connection", "script", 1, listParams)


  • "PCBI_HazardAnalysis.PCBI_Connection"
    • ID: 1 Open the Dialog Params: string fileName
      ID: 2 Save FilePath Params:

      string fileName
      bool saveBothFormats

      Example: parent.SendMessage("PCBI_HazardAnalysis.PCBI_Connection", "script", 1, new List object() { newHazard })


  • "PCBI_TombstoneAnalysis.PCBI_Connection"
    • ID: 1 Export CSV in User Dir Params: string fileName
      Example: parent.SendMessage("PCBI_TombstoneAnalysis.PCBI_Connection", "script", 1, new List object() { newTombstone })
  • "PCBI_IDFFilter.PCBI_ConnectionImport"
    • ID: 1 Import IDF file

      Params: string importPath

      ID: 2  Export IDF file

      Params: string exportPath

      Example: parent.SendMessage("PCBI_IDFFilter.PCBI_ConnectionImport", "example", 2, new List object(){"path"}

  • "PCBI_NetGroups.PCBI_Connection"
    • ID: 1 Add Rule File

      Params: string importPath
      strong> IFileData importFileData

      ID: 2  Run rule check

      Params: string resultPath
      XMLSettings settings
      NetGroupList all net groups to check
      double first double is distance min outer, second double value is distance min inner and third double value is distance min 3D

      ID: 3 Open net group dialog

      Params: string info string

      ID: 4 Open net rule dialog

      Params: string step name

      Example: parent.SendMessage("PCBI_NetGroups.PCBI_Connection", "example", 4, new List  object(){"stepname"}

7) 365 Explorer

365 Explorer to check all files in the storage, including designs and all additional files

    365 Explorer with all data in all storages

1) Open PCBI 365 design tree

Open PCBI 365 design tree
    Show PCBI 365 Open Designs

2) Add current design to the 365 cloud

Add current design to the 365 cloud

    Show the add to 365 dialog

Select path to 365 group and add the open design.

5) Design Explorer

With the Design Explorer you have an overview all additional files for this data stored. E.g. additional BOM files, Images, schematics, exportes and notes

    Show Design Explorer for 365 with sub documents

6) Design Properties

Design Properties to find the design later again (including comments, design size, layer count)

    Show design propertes

4) Upload Data

Upload data to update the design online

Template Manager

Panel Builder brings an template manager with it, there are options to store panel templates and an coupon library online or local.

With the templates you can use standard panel sizes with fix drill and marker positions. It is possible to store templates for each layer count, depending to the size of the useable area it calculate the amount of single PCBs in the template.

Overview template manager

1) Add Template from the list on the right side

2) Change to Admin area

3) Options for distance in fix values

4) Option to fit single pcb with percent distances


Admin Area

Admin area with explaination for the important buttons

1) Add the current design as template to the list.

2) Remove the selected template from the list.

3) Open the update dialog with many more options (useable ares, copper layer count, path to the template and step name)


Coupon Library

Coupon Library for template manager


1) Add the selected coupon to the panel.

2) select "Test Coupon on Layer" to add the loaded coupon entry on one layer.

3) select "Test Coupon ad Step" to create an new step with all coupon information (recommended for coupons with components and net information)

4) select "Synchronize Layer" to fit the coupon data on the panel layers.

5) Edit the coupon entry, e.g. change image or path to the coupon.


HTML Export

Here is an example how the report can be organized, with extra tab pages for each exported analysis:

Example output html report

The report begin with an overview for each step with e.g. design size, component count and the stackup information (signal layers, step count, layer count, net count,...)

With the extended design report you can use customization to change colors and images, you can also add own reports and pages. The report has an open Interface to automate it and create complete reports for all made analysis/checks.



Export Parmi Files for SPI

Export Dialog for Parmi Files

1) options for output digits and transformation (e.g. export your board with 90 degree rotation)

2) Select the output panel

3) export Top and/or Bottom side with extra layer for the paste definitions

4) use filters e.g. for THT components or ignore unplaces components

5) change the fiducial definitions and options

6) Export the Parmi PADX File(s)


Export Viscom vVision and older Formats for AXI, AOI and SPI machines

Viscom export dialog

1) Export Type and generall settings

2) Export Panel and options for sides (for AXI combined file for both sides possible), you can also select the paste layers for top and bottom side here

3) Set component Attributes, many output elements need further information e.g. you have to define the package group to export BGAs, SOICs and CHIPs in simple form

4) Define the output project name

5) Filter components e.g.g export only SMT components

6) Define Fiducials and Bad Marks or change there definitions

7) Optional use of global output libraries

8) Depending on the machine type you can add camera marker

9) Depending on the machine type you can add laser marker

10) Export SPI or vVision format


The Viscom export has many option e.g. for specific viscom machine types with laser marker or camera marker, it supports mapping files aswell as library structur for cle and cad files.

Here is the list of all export options you can modify for viscom files:

Overview available expert options for viscom format

1) generell options like output digits in the files or use naming confentions for package group footprints in cle files.

2) tolerance and file/folder naming

3) copy default files for specific cases e.g. copy par or si_lpos files and alias files handled different for AOI/AXI and SPI

4) use mapping and update the file

5) fiducials replaced by rectangles or TAR files for AOI/AXI and SPI

6) many options for output files like output folder in SI structur, SPL Files for splitter definition or the rotation system.

7) specific options for vVision (xml) files like automatically library update with lead information, use mpn packages from library or replace step names by numbers and some more


The expert options contain many options that you define once and cannot change later. You must have a certain amount of background knowledge to be able to use some of these options!

Siplace QD/OIB

Export Siplace QD Data or connect ot OIB machine

more details for OIB here:

and more details for QD here:



Export Mycronic MY300 format with connection to the machine or with csv library, you have information for pin fitting and polarity pin.

You can filter for technlology like SMT and define export sides and some more:

show mycronic export dialog


Export Modus format

Export Dialog for Modus Format

1) Export File selection for components and pins

2) Export Sides (TOP and/or BOTTOM)

3) Filter components e.g. for THT/SMT technology

4) Fiducial definition and overview

5) Export the Modus file(s)


Export TRI Format in one file without specific exta options.


Export Göpel Standard oder CASCON format

Goepel export dialog

1) Change Output digits or PA Name Attribute (default is package, but in some cases this can be different)

2) Select the output step and the paste layers to export

3) Filter components

4) Define the fiducial markers

5) Change output handling in one or more files and with mirror for bottom side

6) write file(s) for göpel export


This machine export supports the SPI machine aswell as the jtag machine (CASCON).


Export and Import Yamaha AOI and PTool format

Yamaha export dialog

1) Select Export Type (AOI or P-Tool) and change global settings

2) Define the board and add comments and names

3) Select export layer and side

4) Filter components e.g. technlology SMT

5) Define the fiducials and select output options

6) You can select the Part Name property, in case you want to use internal properties you can just select a other property.

7) Save the Yamaha export

In both formats all important information for components, fiducial markers and meta data for the board available. The P-Tool format is a assembly format to place the components. The AOI format is to check the places components are available in the automatically optical inspection.


Export NDF Format for AOI machines.

The NDF file contains component references with position, Rotation, Placement Side, PartName and Package.