<< Click to Display Table of Contents >> Navigation: Features and Operations > Validation > Compliant Validation |
Select the Validation icon to check if any errors are in the model. Users can also Validate their model when running a Simulation. The errors shown below are some that can affect the model Simulation and cause failed builds.
|
Compliant Model Status *Error will indicates that this type of error found in the run log causes a failed assembly condition
|
|||
Move Type |
Status |
Message |
Solution |
All Moves |
Error |
Empty Part List |
Add a Part(s) to the Move Parts list |
Not Enough Object/Target Points |
|||
Invalid Object/Target Primary Plane |
|||
|
|||
Warning |
Move is Inactive |
||
Object/Target Points not Within |
|||
Object Points not Within Move Parts |
|||
Check the move to see if a feature was selected in two or three primary fields. If one feature has two or more locators, create points to represent different locators. |
|||
Bend Condition Points not Within |
|||
Bend Condition Direction Points not Within |
|||
Direction(#): Points Not Within |
|||
Direction(#): Not Enough Points Selected, Using (0,0,1) |
|||
...has Inactivate Points |
|||
|
|||
User-DLL Move |
Error |
Cannot find file 'Name.exe' |
3DCS Cannot locate the file used in the User-DLL function. Please check the file's location and file path. |
No User Function Specified |
The User-DLL function is not loaded. Load the missing User-DLL into the DLL Load function. |
||
Cannot Find User Function 'Name' |
Check if the User-DLL is loaded. If the DLL is loaded, check the move with the missing User-DLL function, the function may have changed names or position in the list. |
||
|
|||
Match Move |
Error |
MatchLine (err=0.021504) Calculation Fail |
|
|
|||
Conditional Move |
Warning |
Condition (MeasX) uses Relative Specification Limits |
Compliant Model - Points and Stiffness Matrix Status *Error will indicates that this type of error found in the run log causes a failed assembly condition
|
|||
Type |
Status |
Message |
Solution |
Stiffness Matrix file |
Warning |
The stiffness files of object and target parts have different DOF numbers. |
|
|
|||
Points (ASET) |
Warning |
Modeling Pt(s) "Point Name" do not have a saved link to any FEA (ASET) node. |
1.Open the FEA Point Linking dialog, select the part, click "Refresh Mesh" and Nominal Build. 2.Or utilize the "Refresh ASET Links" function when loading the Mesh in the Load FEA Data Move and Nominal Build. 3.Or regenerate the FEA Files with StiffGen. |
Compliant Model - Creo users only
|
|||
Type |
Status |
Message |
Solution |
3DCS/Creo Message |
Error |
dcsErr: Part tessellation returned no points for partBASE. Check for and repair part/import feature's missing surface and/or edges. |
This issue will not occur a lot with CREO and 3DCS. If so, here are some solutions to help fix the issue. 1.Use native Creo parts, instead of importing IGES or STEP files 2.Try to improve the geometry by modifying and saving the part. 3.Use the Data Doctor provided by PTC. |