This chart below outlines the differences between the various methods of model generation in DriveWorks.
There are 3 types of model generation in DriveWorks Pro
DriveWorks Autopilot will give generation priority in the following order:
Components Released before DriveWorks 15
Any components released before installing DriveWorks 15 will be generated before anything released after installing DriveWorks 15.
|OnDemand (Real Time Preview)||Manual/Queued Generation
and Automatic/Queued Generation (Autopilot)
|File Names||Temporary file names allocated||Permanent file names allocated in line with rules applied|
|File Location||Temporary folder||Permanent folder in line with rules applied|
|Static Replacement Files||Temporary file created||Replacement file used|
|Driven Replacement Files||Temporary file names allocated||Permanent file names allocated in line with rules applied|
|Component Deletion||Suppress component||Delete component|
|Feature Deletion||Suppress feature||Delete feature|
|Unused Configuration Deletion||No effect||Delete unused configurations|
|In Context References||Not supported||One level|
The following table provides information on the steps DriveWorks will take to generate a model, based on its current state.
Each time DriveWorks tries to generate a model, it sets the Generating flag so that if SOLIDWORKS crashes or is terminated, then the next time the model is attempted to be driven, DriveWorks knows that it failed.
The Generated flag is set when DriveWorks successfully generates a model.
The Failed flag is incremented whenever DriveWorks fails to generate a model, e.g. if the master file doesn't exist, or if a problem occurs during generation..
The Exists column refers to whether the target file actually exists in the file system.
Based on the combination of the model state, the Behavior column indicates the action DriveWorks will take.
|2||No||No||No||Yes||Using existing model, mark as generated, and log warning.|
|4||No||No||Yes||Yes||Delete existing, and retry generation.|
Log warning, clear generated flag, and retry generation.
|6||No||Yes||No||Yes||Use existing file.|
|7||Yes||No||No||No||Mark as failed, and try #3|
|8||Yes||No||No||Yes||Mark as failed, delete the existing file, and try #3|
1. The failed flag keeps track of the number of times that a given component fails, if the model is being generated by DriveWorks Autopilot then the administrator can decide how many times DriveWorks Autopilot will try to generate the model before giving up until the administrator has intervened. An administrator can use the data management tool to mark a model that has failed the maximum number of times for regeneration.
|Knowledge Base Article Ref:||KB12121006|