Migration of Robot Tasks in Product DocumentsWith the correct settings, it is possible to define tasks in product
documents. Tasks, like controllers, are copied whenever the document
containing them is instantiated into another document. Only the copies
in the document are displayed to the user when that document is open.
All copies of tasks are imported to ensure that no task data is
lost. To allow tasks to be differentiated, tasks imported from product
documents have the document name appended to the task name. Tasks
that come from process documents, even if they are copies of tasks from
product documents, never have their name altered. In the above example, the task and tags were created when the line document was open. The line was then parented under the zone. This created a copy of the task in the zone document. During import, two tasks are created in V6, one from each document. Migration of Robot Motion ActivitiesFour kinds of robot motion activities are migrated:
For each, the name, target, and sequencing migrate. The above diagrams for robot task migration also show how robot motion activities are migrated. Migration of Device Move ActivitiesDELMIA V5 Workcell Sequencing allows for MoveDevice activities to be defined in the tree for an inverse or forward kinematic device. DELMIA V5 Assembly Process Simulation allows for a MoveCartesianActivity to be defined for an inverse kinematic device, and MoveHomeActivity and MoveJointsActivity activities for an inverse or forward kinematic device in the tree. For inverse kinematic devices:
For forward kinematic devices:
Migrating Tags and Tag GroupsV5 tag groups can be created in V5 process documents under the Resource/TagList. With the correct settings, tags can also be created in product documents. The above diagrams for robot task migration also show how tags and tag groups are migrated. The rules for tag and tag group migration are:
|