The Create Coincident Mate Generation Task will create a Coincident Mate, in an Assembly, between reference Planes in each Component.
With this Generation Task you can use any Plane and although naming your Planes is not necessary to make this Generation Task work it is advised as good practice. See How to Name and Write Rules for a Face or Plane in a SOLIDWORKS Part for more information about Naming and Writing Rules.
|(Name)||The unique name for this task.|
|Aligned||The alignment type (True = Aligned, False = Anti-Aligned).|
|First Plane||The name of the first reference mating plane.|
|Second Plane||The name of the second reference mating plane.|
When this Generation task is added the properties are Dynamic by default.
|Property Name||Example Rule||Example Result||Meaning|
|Aligned||FALSE||FALSE||The Alignment type. TRUE for Aligned and FALSE for Anti-Aligned.|
|First Plane||"Top Plane@Bracket " &DWSpecificationId&"-1"||Top Plane@bracket 9999-1||The name of the First reference Mating Plane.|
|Second Plane||"Plane1@Rib " &DWSpecificationId&"-1"||Plane1@Rib 9999-1||The name of the Second reference Mating Plane.|
When building the rule for the plane names, they must reference the generated file name and not the master. The rule must be built in the form: [Plane Name]@[Generated model name]-[Instance number].
If the plane is in the top level assembly, only the plane name is required.
The rule must include the instance number, even if there is only one instance of the component in the assembly.
Mating planes can only be one level deep. For example, the rule: [Plane Name]@[Generated model name]@[Generated sub assembly name] would not be valid.
When filling out the Entity Names it is important to remember to add a space after the end of your model name before your quote otherwise the task will not work. For example "Part "&DWSpecificationId .
For more information about Mate Alignment see Mate Alignment in the SOLIDWORKS Help file.
DriveWorks Tech Tips Portal
Insert Component Generation Task
This project demonstrates how to insert and define a component using Generation Tasks, and also how to use Looping to insert multiple components.