Export Model

Produces a STEP Physical File representation of an EDMdatabase model.
The STEP Physical File format is defined in ISO 10303-21: Clear text encoding of the exchange structures. A STEP Physical File is also referred to as a Part 21 file.
This is one of the implementation forms of ISO 10303, and can be used to exchange data between two EDMdatabases or between an EDMdatabase and any application that conforms to ISO 10303-21. The produced file can also be used for long time archiving of the data.
The Header Section part of the STEP file can be produced from an existing header model in the EDMdatabase or a default Header Section can be produced by this command. A header model is a model of the HEADER_SECTION_SCHEMA defined in ISO 10303-21. The default Header Section can be configured by setting the EDM system variable EDM_STEP_FILE_AUTHOR.
For information on the format of the file in argument <short names file>, see Short names in the User Guide.
Arguments:

Repository:

Specify the name of the repository holding the model to be exported. Repository names are case sensitive.
When activating the Select button, the name of all open repositories will be displayed in the related selection list.

Model:

Specify the name of the model to be exported. Model names are case sensitive.
When activating the Select button, the name of all open models located in the repository(ies) specified by the <Repository> argument will be displayed in the related selection list..

STEP Header Model:

Specify the name of the STEP Header Model in EDMdatabase that will be mapped to the Header Section in the resulting STEP file. STEP Header Model names are case sensitive.
All instances in the specified <STEP Header Model> will be mapped to the STEP file Header Section as is, except that the attribute FILE_DESCRIPTION.IMPLEMENTATION_LEVEL is set according to the mapping method specified. The actual mapping method is specified by activating one of the following options: [conformance class 1], [conformance class 2], or [EDM private format]. The attribute FILE_NAME.TIME_STAMP is set to the current date and time, i.e., the date and time when the STEP file is produced.
When the [no header change] option is set, the specified header model will be mapped as is, i.e., also the three attribute values described above will be mapped from the specified header model to the STEP file.
When the <STEP Header Model> argument is blank, a default Header Section is produced. This default header section can be configured by setting the EDM system variable EDM_STEP_FILE_AUTHOR.
There are several ways to customize one or more STEP Header Models in EDMsupervisor, among others the 2 following ways:
1) Edit an existing STEP file an import this file by the command Data>ImportModel.
2) Create a STEP Header Model by the command sequence:
Data>Create>Model , Data>Open>Model , Data>Create>Instance , and Data>Close>Model .
When activating the Select button, the names of all STEP Header models in the EDMdatabase will be displayed.

STEP file:

Specify the name of the file that will hold the resulting STEP file. Default file extension is ".stp".
If this argument is left blank, the resulting STEP file will only be displayed in the EDMsupervisor output window, i.e., no permanent copy of the actual model in STEP Physical File format will be produced.
When activating the Select button, a window is opened to allow browsing the directory structure and select the desired file.

Diagnostic file:

Specify the name of a file that will contain diagnostic information generated in the creation of the STEP Physical File. If this argument is not presented with any value, the result will be displayed in the EDMsupervisor main output window.
When activating the Select button, a window is opened to allow browsing the directory structure and select/specify the desired file.

Real precision:

Specify the number of significant digits after the decimal point in a REAL number in the resulting STEP file.

Short names file:

Specify the name of the file containing the mapping matrix between full entity names and its unique short name. This argument is effective only when the [short names] option is set.
For each STEP AP, a short name file is provided by ISO TC184/SC4 and can be downloaded from

http://www.steptools.com/short_names/index.html

.
When activating the Select button, a window is opened to allow browsing the directory structure and select the desired file.

Options:

accumulating command output:

A global option that appends the command output to the EDMsupervisor output window. Otherwise the output window is refreshed and only the last command output is displayed.

match selected input:

A global option that specifies that only items that partly or exactly matches the string in the related argument input field when activating a Select button, will be in the selection list. An empty (blank) string will match all items.
This option has no effect on file name arguments.

conformance class 1:

Enforce the file to be exported according to ISO 10303-21:1994/TC1 conformance class 1. Identification of the format is written to the Header Section of the resulting STEP file.
The options [conformance class 1], [conformance class 2] and [EDM private format] are mutually exclusive, i.e., only one of this options should be activated in one execution of the Data>Export>Model command.

conformance class 2:

Enforce the file to be exported according to ISO 10303-21:1994/TC1 conformance class 2. Identification of the format is written to the Header Section of the resulting STEP file.
The options [conformance class 1], [conformance class 2] and [EDM private format] are mutually exclusive, i.e., only one of this options should be activated in one execution of the Data>Export>Model command.

kept STEP identifiers:

A STEP Identifier model will be created and connected to the data model created by this operation. The STEP Identifier model will keep the correspondence between the STEP file entity instances and the EDM instanceID. The command Data>ShowStepIdentifier can be used to display the stepID corresponding to an EDM instanceID and vice versa.
The EDMmodelChecker can optionally output the stepID of failing instances on the validation report.

short names:

Specifies that short names specified in the <Short name file> argument will be used for entity names in the resulting STEP file.

EDM identifiers:

Specifies that the EDMdatabase instanceID will be used as instance identifiers in the STEP Physical File such that it will be easy to find the correspondence between a mapped instance on the STEP file and the same instance in the EDMdatabase.

no header change:

Specifies that the header model specified by the <STEP Header Model> argument will be mapped to the actual STEP file without any changes. Normally the mapping method, time stamp, and schema name will be provided by the EDMstepHandler function. No information will be provided by the EDMstepHandler when this option is set. This argument is only effective when a header model is specified in the <STEP Header Model> argument.

no string encoding:

Specifies that no encoding will take place when mapping a STRING data type to the STEP file. The ISO 10303-21 specifies that all character in a STRING data type that have an ASCII value less than 32 or greater than 126 should be encoded in a STEP file.

no line breaks:

There will be no line breaks within an instance on the resulting STEP file.

show step file in html:

Specifies that the resulting STEP file will be written in HTML format to a temporary file and the EDMsupervisor default Internet Browser will be activated to display the STEP file. The temporary file holding the HTML representation of the STEP file will be deleted after this command is terminated. The command Data>STEPfileToHTML should be used when a more permanent HTML representation of a STEP file is wanted.