Connector Export

Learn about exporting connector files.

The following file types can be exported:
  • ASCII: The very basic format. The data labeled in a header line for one connector are in a row and separated by "::". This format outputs the information of connector id, layer, position, config, and link and is only for spot connectors.
  • XML1.0: The Altair 1st version of xml format and can be used as both a standalone file or embedded in a solver deck. This format outputs all information about different types of connectors except realization state and FEs, which are only output together with a solver deck. Connectors are organized based on links in an xml file of this format.
  • XML 2.0 (default): The Altair 2nd version of xml formats. Compared to XML 1.0, it is a more flexible format and there are two differences: individual connector structure and connectors are not grouped based on links. Most data are written in the format of name-value pair.
  • MCF (version A): By default, HyperMesh will export the bolt connector vector that was dynamically identified during realization. The vector can be exported with or without the bolt. If a bolt connector vector is not identified after you import the connector, HyperMesh will search for the dynamic vector again. If a vector is already defined on the connector, HyperMesh will use that vector for realization.
  • MCF (verion B): Only output limited information of connectors, like links and positions. Version A and version B have some subtle differences, for example, version B only supports component links whereas version A supports both component and property links.
  • VIP: Very simple column data format for spot connector only, includes connector id, position and link IDs.
  • xMCF: An advanced xml format, it is a standard that is currently being established between different software vendors for CAD, FEA and Fatigue. Compared to MCF (version A) and MCF (version B), this format outputs more details.
Note:
For XMCF files, the following types of connectors and features are managed:
  • 0D: Spotweld, bolt, screw, gumdrop, clinch, rivet (blind, self-piercing, solid, swop), robscan, contact_list, threaded connection, heat stake, clip, nail
  • 1D: Sequence connection 0D (spotweld, gumdrop), seamweld (butt_joint, corner weld, edge weld, i_weld, overlap weld, y-joint, k-joint, cruciform joint, flared joint), adhesive-line, hemming, contact list
  • 2D: Adhesive face
  • Custom attributes are managed.
  • Appdata is not managed.