Assembly Process Simulation and Fitting Simulation File-based Design Import | ||
| ||
Importing Track Data
This describes importing track data.
To import data, you select a V5 document to be imported. Any tracks stored in the applicative data containers of selected product documents or in product documents related to the selected documents will be imported to V6. The imported tracks will be created in behavior representations that are children of the V6 version of the products the tracks they came from.
| V5 | V6 |
|---|---|
| General Track Data | |
| Name, Time, Speed, Mode (Time/Speed) | Imported |
| Tracks | |
| Location of the path relative to world and father of the moving object. | Imported |
| Non-mapping track path data | When moving some types of objects, V5 tracks use a shot data format that is not supported in V6. If these types of tracks are encountered during migration, a warning will be displayed and the track will not be migrated. |
| Multiple instance tracks such as tracks that move cameras | Not imported. All imported tracks will be single, separate entities. The name for imported tracks is always the instance name. |
| Visualization properties of a track's path (Line color, type, and thickness. Hide/show status.) | Not imported |
| Shots | |
| Position, compass offsets, durations | Imported |
| Shot Flags | Partially Imported. Shots generated by the pathfinder command when collisions are disabled are marked with a flag and are rendered in red. This flag (and the red coloring) will not be imported into V6. |
| Moving Objects | |
| The Products or Shuttles moved by the track. The offset of the objects from the track. | Imported |
| Shuttles as objects | Not imported.
There is no object in V6 that is the equivalent to a Shuttle. If a track moves a shuttle, the track will directly move the product children of the shuttle. The offsets between the shuttle and its children will be respected. If the V5 track moves a shuttle and that shuttle has a referencing shuttle, the referencing shuttle (and its children) will not be migrated. This is because referencing shuttles provide relative motion, which is not supported by the V6 tracks. |
| Motion interpolation | |
| Linear interpolation | Only linear interpolation is supported in V6. All migrated tracks will use this mode. |
| Non-linear interpolations | If a V5 track using a different interpolation is migrated, a warning will be displayed and the interpolation type will be set to linear. |
| Relations to non-product objects | |
| Relations to the following types of objects will not be imported. A warning will be displayed when this happens. Section planes: both moved and associated Bound analysis (clash/distance) Lights | Not Imported |
| Log Data | |
| Log data and attributes | Not Imported |
| Operations such as Split and Join generate a new track while
keeping the original track as a Log that is the child of the new
track. Any track that is only displayed as the log of another track
is not imported into V6. A warning is displayed in the log whenever
this happens.
The Mirror operation is the exception to this rule as Tracks that are the source for a Mirror operation are still displayed as children of the 'Tracks' node in the tree. |
Partially Imported |
| Special Cases | |
| V5 CATPart documents | V5 CATPart documents are migrated into a pair of objects: a V6 Product object and a 3D Rep object. If a V5 Track moves a CATPart, the migrated V6 track will pointing to the generated product object. |
| Lights | V5 tracks can move lights. Although the same double transform shot is used in this case, the shots are interpreted differently when interpolating the light along the track. When a V5 track with a light is migrated, the relation to the light is not migrated and the shot data is copied directly. Because the V6 track does not consider the data a special case, the V6 track path may not look like the V5 track. |
Process Document Data
This describes how to import process document data.
To import process data, select a process document to be imported. These activities stored in the main process of that document will not be imported to V6.
| V5 | V6 |
|---|---|
| Predefined Move | Not Imported |
| Grab | Not Imported |
| Release | Not Imported |
| Hyperlink | Not Imported |
| Pause | Not Imported |
| Delay | Not Imported |
| Device Move | Not Imported |
Track Links Management in a Work Plan
This section describes how track links are managed in a work plan.
These activities will not be imported to V6.
| V5 | V6 |
|---|---|
| Predefined Move | Not Imported |
| Grab | Not Imported |
| Release | Not Imported |
| Hyperlink | Not Imported |
| Pause | Not Imported |
| Delay | Not Imported |
Cartesian Track Rules for operation:
- A track is only created under an operation
- A track can be linked to nothing ( case of track defined for all object implemented by operation)
- A track can be linked to 0 to N operations if
:
- Operation has been performed before the current operation ( according Time Constraint)
- Operation has implement links to a process
- A track can be linked to 0 to N systems if :
- System has been performed before the current operation (according Product Flow)
- System has a scope with a process
- Semantic Relation used for operation/system links are created in context of the first upper system scope
Cartesian Track Rules for resources:
- A track can be linked to 0 to N resources if:
- Resource is defined as With resource for the operation
- Semantic Relation used for resource links are created in context of the first upper resource in scope with the first upper system
Kinematic Track Rules for operation:
- A KIN track is only created under an operation
- A track is linked to one Mechanism Rep if :
- Mechanism Rep is under a product in scope with a process which is in scope with the first upper system scope of the operation
- A track can be linked to 0 to N Kin Commands
- Semantic Relation used for product links are created in context of product scope