Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »


 
SYNTAX:
 
xpxWriteStepFile(repositoryName, headerModelName : STRING,
                 modelName, STEPfile             : STRING,                 diagFile, shortNamesFile        : STRING;                options, realPrecisision         : INTEGER;
                 VAR nWarnings, VAR nErrors       : INTEGER;                VAR sdaiError                    : INTEGER)
                status                           : INTEGER;
 
The xpxWriteStepFile function can be used to produce a STEP Physical File (Part 21 file) of specified model. The arguments in the xpxWriteStepFile have the following meaning:
repositoryName:
Name of the repository where the actual sdai model is located.
headerModelName:
Name of a sdai model of the STEP Physical File Header Section that should be mapped to the Header Section of the actual STEP Physical File. The actual sdai model of the Header Section must be located in the repository specified by the repositoryName argument. This argument can be specified as an empty string or as indeterminate (question) meaning that the Header Section of the actual STEP Physical File will be produced according to a standard procedure.
modelName:
The name of the sdai model within the repository repositoryName that will be mapped to the actual STEP Physical File. A sdai model is uniquely identified by the repositoryName and modelName arguments.
stepFile:
Fully qualified name of the file that will receive the actual STEP Physical File.
diagFile:
Diagnostic file. The xpxWriteStepFile function will record all diagnostics found during mapping of the actual sdai model to the actual STEP Physical File on this diagFile. When the diagFile argument is set to an empty string or to indeterminate (question), then no diagnostic recording will be produced.
ShortNamesFile
Short Entity Names file. When the xpxShortNames option is set, the xpxWriteStepFile will use the short entity names found on the specified shortNamesFile argument instead of the entity names found in the underlying schema of the actual sdai model mapped to the STEP file.
For information on the format of the file in argument <short names file>, see Short names in the EDMsupervisor User Guide.
 
options:
The options are equivalent to the options used in the EDMinterface function edmiWriteStepFile except for the XPX prefix.
Available options for the xpxWriteStepFile function is:
xpxShortNames:
Use the short entity names if available.
xpxEdmId:
Use the EDMdatabase instanceId's as entity names on the STEP file.
xpxLogToFile:
Log to the file specified by the diagFile argument.
xpxLogToStdev
Log to standard output file.
realPrecision:
Specifies the precision of the REAL data type on the STEP file. Default value is used when realPrecision argument is set to zero.
nWarnings:
This argument will receive the number of warnings detected during the xpxWriteStepFile operation.
NErrors
This argument will receive the number of errors detected during the xpxWriteStepFile operation.
sdaiError:
If the xpxWriteStepFile operation is terminated due to errors in accessing the database, the argument sdaiError will receive the actual sdaiErrorCode causing the termination of the xpxWriteStepFile operation.
This function is equivalent to the EDMinterface function edmiWriteStepFile

  • No labels