- Check your design.
- Specify mandatory checks of specified attributes.
- Establish the parameters for certain checks.
These are explained below.
The validation checks are.
Bending - Bend radius does not match what is specified by the bending rules. The criteria, which can be changed by users, are defined in the Bending Design Rule.
Bending - Bends that cannot be processed by given bending machines: The bend cannot be recreated by a manufacturing machine. The criteria, which can be changed by users, are defined in the Bending Design Rule.
Bendable Maximum Bend Angle Violation: The maximum specified bend angle has been exceeded. This is a value specified by the user in the file DesignValidationInputCriteria.txt. See Step 3.
Bending - Bend angle more than maximum allowed: The minimum specified bend angle has been exceeded. This is a value specified by the user in the file DesignValidationInputCriteria.txt. See Step 3.
Bending - Grip length less than minimum allowed: The minimum specified grip length has not been met. The criteria, which can be changed by users, are defined in the Bending Design Rule.
Bending - Tangent length less than minimum allowed: The segment length is less than the minimum specified tangent length. The criteria, which can be changed by users, are defined in the Bending Design Rule.
Bending - Flow defined on extremity connectors is inconsistent with node creation order: The application checks that the flow direction is from Connector 1 to Connector 2 on a bendable or stretchable - Connector 1 should have IN flow, while Connector 2 should have OUT flow. All other settings will result in an error.
Connection - Connected parts are not aligned
Connection Incompatible: The connector specifications between two connected parts do not respect the Design Compatibility Rules.
Connection - More than one part connected to a part: A connector is connected to more than one object.
Connection Open Connector: A connector is not connected to any object.
Connection - Connected parts are not clocked/oriented correctly: The orientation of two connected connectors does not match – the up direction of the two connectors is not the same.
Connection - Two connected parts have a gap between them: A logical connection exists between two objects, but the objects have become physically separated.
Duplicate - More than one part found with the same name: More than one object has the same ID or name.
Duplicate - More than one Run found with the same name: There are two or more runs with the same instance name.
Instance ID Inconsistent: An object has an ID that does not comply with its defined object naming rules.
ISO Symbol Name Inconsistent: This check ensures that the symbol name for isometric drawing generation is properly set. The symbol name must be one of the symbols that are allowed for isometric generation. The allowed symbols are defined in the symbol mapping file.
Mandatory attribute values undefined for parts: A mandatory check of an attribute (on a part) has been specified, but that attribute has no defined value.
Mandatory attribute values undefined for connectors: A mandatory check of an attribute (on a connector) has been specified, but that attribute has no defined value.
Non-Spec: The object does not have a specification defined, but belongs to a logical line that has a defined specification.
Out-of-Spec: The object has a specification defined that is different from the specification defined for the logical line it belongs to.
Pipes with insufficient slope: The slope is less than the specified minimum. This is a value specified by the user in the file DesignValidationInputCriteria.txt. See Step 3.
Pipe/Tube length more than maximum allowed: The total length of the bendable is longer than specified. This is a value specified by the user in the file DesignValidationInputCriteria.txt. See Step 3.
Runs that contain a bend radius more than maximum allowed: The bend radius is checked relative to adjacent run segments. If the radius is larger than what is geometrically possible for the segments then an error is displayed.
Runs that contain broken segments: A run segment is broken.
Runs that are connected have a gap between them: A run, and equipment or part, have a logical connection but have become physically separated.
Runs that are connected to another run with a gap: A run, and another run, have a logical connection but have become physically separated.
Runs where part are placed and a part hole connector is not aligned with the run: A hole connection and the run to which it is connected are not aligned.
Runs that contain a segment with a length less than allowed: A segment is shorter than the minimum segment length defined for that run.
Runs that contain a bend radius that does not match what is specified by the bending rules: A run turn radius is not consistent with the Turn Design Rule specifications.
You can specify that the values associated with certain attributes always be checked when a design validation is done. This check only determines whether or not a value has been assigned to that attribute. To do this, you need to enter the attributes you want checked in a file.
The file name is DesignValidationMandatoryAttributes.txt, and the sample file provided with this application is located in the directory ...startup\EquipmentandSystems\MultiDiscipline\SampleData. Make changes using a text editor, and follow the existing format.
There are some validation checks that require users to specify values. These checks are:
- Slope: The slope of a routable. Enter the value in percent. Any slope less than this value will be flagged as an error.
- Maximum total length: The maximum possible length of one bendable. This totals the length of all the segments in the bendable. You must specify the unit.
- Maximum bend angle: The maximum possible bend angle in a bendable, in degrees.
- Minimum bend angle: The minimum possible bend angle, in degrees.
The values should be entered in the file DesignValidationInputCriteria.txt. The sample file provided with this application is located in the directory ...startup\EquipmentandSystems\MultiDiscipline\SampleData. Make changes using a text editor, and follow the existing format.
