|
»Click here to display Table of Contents«
|
INSTNCE |
|
|
|
|
|
INSTNCE |
|
|
|
|
|
»Click here to display Table of Contents«
|
INSTNCE |
|
|
|
|
|
INSTNCE |
|
|
|
|
The INSTNCE bulk data entry can be used to define the location of a part in the global structure. Each INSTNCE entry should reference a unique part name.
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
INSTNCE |
ID |
name |
NN |
|
|
|
|
|
|
|
Field |
Contents |
ID |
Set identification number. (Integer > 0) |
name |
Specifies the unique name of a part that is to be attached to the global part (see comment 2). It should match the name of one of the parts defined using the BEGIN, FEMODEL, name entry. (Character String) |
NN |
ID of a RELOC bulk data entry. This field defines the actual location of the part in the final model via the RELOC entry. Default = blank (Integer > 0) |
| 1. | The full model consists of several parts, one part is designated as global and the rest of the parts are attached to the global part using INSTNCE entries. The global part can have an arbitrary name (it is identified by the presence of INSTNCE entries). A minimum of one INSTNCE entry should always be present in the model. |
| 2. | All INSTNCE entries should exist within a global part and no INSTNCE entry can reference the name of a global part on the “name” field. |
| 3. | Each INSTNCE entry should reference a different part name. However, not every part has to be defined using an INSTNCE entry. Such parts are still contained within the full model without any relocation. |
See Also:
