Communicator for BricsCAD - Supported export file formats

Supported export file formats:

Windows

  • 3D PDF: .pdf
  • ACIS: .asab, .asat, .sab, .sat
  • CATIA v4: .model
  • CATIA v5: .CATPart, .CATProduct
  • IGES: .iges, .igs
  • STEP: .step, .stp

    The following export protocols can be specified; AP203, AP214, AP242

  • VDA-FS: .vda
  • XCGM: .xcgm
  • Parasolid: .xmt_bin, .xmt_txt, .x_b, .x_t

    Export to Parasolid format is possible if:

    • pskernel.dll is available in InterOp, e.g. in a folder accessible through PATH enviroment variable.
    • P_SCHEMA environment variable points to the schema folder which can be found next to pskernel in its original installation. The folder name may slightly differ, e.g. in SolidWorks® 2018 it is schema_18.
    • pskernel.dll version is earlier than the major version supported by InterOp, the EXPORTPARASOLIDFORMATVERSION system variable has to be set to a (lower) version that pskernel library supports.

Linux

  • 3D PDF: .pdf
  • ACIS: .asab, .asat, .sab, .sat
  • CATIA v4: .model
  • CATIA V5: CATProduct, .CATPart
  • IGES: .iges, .igs
  • STEP: .step, .stp

    The following export protocols can be specified; AP203, AP214, AP242

  • VDA-FS: .vda
  • XCGM: .xcgm

Mac

  • ACIS: .asab, .asat, .sab, .sat
  • CATIA v4: .model
  • IGES: .iges, .igs
  • STEP: .step, .stp

    The following export protocols can be specified; AP203, AP214, AP242

  • VDA-FS: .vda
Note:
  • When the EXPORTPRODUCTSTRUCTURE system variable is set, you can export a BricsCAD® assembly with mechanical components as a file with product structure.
  • If the assembly contains hidden parts, you can decide how to process the export hidden parts by setting the EXPORTHIDDENPARTS system variable.
  • All other related system variables which controls the export file types are listed in the Related variables.