About Harness assembly reports: Guidelines for using configuration files

Several standard report types, such as wire run lists, parts list, and connector tables, can be run on a harness assembly. To create a report you activate the harness assembly to report on, select a configuration (.cfg) file to process the data, and then generate the report. You can also create your own configuration files or rename and customize the sample configuration files. When a report is generated, the output file is saved to a specified location, and one or more reports are displayed in the Report Generator document window for viewing. Configuration (.cfg) files are used for reports and the import and export of wire library data. These .cfg files differ in both format and operation.

Sample configuration files for each of the main report types are provided in the Tutorial Files\Cable&Harness\Report Generator directory where you installed Autodesk Inventor. Autodesk recommends using these sample files as a starting point to save time used for data entry and to reduce input errors. To create a new configuration file or modify an existing configuration file, use Edit Configuration file on the Report Generator toolbar.

How do configuration files for reports and import/export differ?

Sample Configuration Files

The easiest way to create a report is to use one of the sample configuration files installed with the application. If the sample file does not meet your needs, use the sample file as a base. Modify and organize the data to include the information you need, and then save the file using a unique name.

The following are sample files and their output:

What checks are done on report output?

A data type consistency check is performed for all properties on every harness object that is associated with the active harness assembly file. For each property used on an object in a harness assembly, only one data type can be associated with the property name. For example, a data type inconsistency can occur when a connector part with a specific property and data type is placed into a harness assembly that has an existing wire or segment with the same property name, but a different data type.

These inconsistencies do not affect the creation of the harness, and only affect the output report under certain conditions. If the data type is text or has no units, or the property value has no associated numerical operations or units, then the report output data is not affected. However, if the value requires units and numerical operations such as conversions, then the data type for a given property name must be consistent among all its occurrences in the harness assembly to ensure data integrity.

Where are .cfg files stored?