' Create a mate constraint in the assembly.ĭim asmDef As Assembl圜omponentDefinition ' Create proxies for the two work planes.Ĭall cylPart.CreateGeometryProxy(cylinderPlane, cylPlaneProxy)Ĭall rodPart.CreateGeometryProxy(rodPlane, rodPlaneProxy) ' component definitition returned is the same as if you ' This leaves the context of the assembly because the ' Find the origin work plane in the cylinder part. Set rodPart = (SelectionFilterEnum.kAssemblyOccurrenceFilter, 'Select the rod part.') Set cylPart = (SelectionFilterEnum.kAssemblyOccurrenceFilter, 'Select the cylinder part.') ' Select the cylinder and rod occurrences. Here's some VBA code that demonstrates the entire process. In this case you have the occurrence but need to go into the part to get the correct plane (this assumes they've been named) and then create proxies of the planes to be able to use them in the context of the assembly. For example, in your program it would probably more convenient to ask the user to select the cylinder part and then select the rod part, instead of having to select specific work planes. This is when you have a reference to an entity in the context of the part or subassembly but then need a reference with respect to the top-level assembly. However, there are cases where you do need to create a proxy. When you select something in an assembly you're getting the proxy for that object so the entities you're getting back from the Pick method can immediately be used to create a constraint because they're already a proxy in the context of the top-level assembly. It's not clear what exactly you're workflow is but here are a couple of things that will hopefully help.

Autodesk inventor 2015 work plane