Process Simulation File-Based Design Import

File-based design import (FBDI) allows you to import data from V5 into V6 and to save that data in V6. Some previous version entities cannot be imported into V6. In V5, data was stored in product or process documents; the rules for importing each vary slightly.

Simulation State Differences between Versions

What constituted a simulation state has changed from V5 to V6; therefore, understanding the differences between the two entities is important to understanding what happens when the V5 data is imported into V6.

V5 Initial State V6 Simulation State
The following attributes are stored in Initial State for each product / resource:
  • Graphic properties (visibility, color, opacity )
  • Position
  • Applicative attributes (DOF values, attachment offsets, etc.)
 Simulation states have the following attributes:
  • Authored in the Live Simulation environment
  • Contain applicative attributes (DOF values, attachment offsets, etc.)
The initial state is applied whenever you execute a simulation command (Process Simulation, Resource Simulation, Robot Task Simulation, etc.) The active state is applied at the beginning of a simulation
There is only one initial state per process document. Multiple states are supported at each level of the hierarchy

Importing V5 Initial States into V6

The effects of importing V5 initial states into V6 are shown.

Data Type Import Effect
V5 product documents The initial state of the products / resources in the CATProduct document are stored in a single simulation state in V6. The state is assigned to the root product or resource reference.

V5 process documents (initial state of a product)

The initial state of the products under the Product List in the V5 process document, if any, are stored in a single (atomic) simulation state, set as active and assigned to the root product under the PPRContext.

This can be validated by selecting the root product in the PPRContext in V6, getting into Live Simulation workshop (so the root product will be set as ASO) and clicking on the Simulation States browse. There should be an atomic state set as active.
V5 process documents (initial state of a resource)

The initial state of the resources under the Resource List in the V5 process document, if any, are stored in a single (atomic) simulation state, assigned to the root resource under the PPRContext. Also, a composite simulation state is created, set as active and assigned to the root resource under the PPRContext. This composite simulation state points to the atomic state created for the root product and the atomic state created for the root resource.

This can be validated by selecting the root resource in the PPRContext in V6, getting into Live Simulation workshop (so the root Resource is set as ASO) and clicking on the Simulation States browser there should be an atomic state and a composite state (of the state of the products and the states of resources) this last one set as active.

This active simulation state will be applied only when you run simulation at the root resource level (root resource is the ASO). To run imported robot tasks and use the imported simulation state, you will need to display all level tasks in the Behavior browser, select the desired task and simulate it.