Nest Move (dcu_NestMove.dll)

<< Click to Display Table of Contents >>

Navigation:  User DLLs > Add-In DLLs > Extra DLLs >

Nest Move (dcu_NestMove.dll)

The purpose of this routine is to locate an object to a target, in which one or more features simultaneously establish the primary locating plane. Consideration of the center-of-gravity will stabilize the object to the target primary plane.

 

Nest move operates only on the primary mating faces in the sense that it cannot float a pin/hole for secondary or tertiary. Therefore the Nest move requires a preceding move to position for the secondary and tertiary locators.  For instance, using a preceding step-plane move is good because it locates in all 6 degrees of freedom.  Then the following Nest move "over-writes" the primary location with a new position of the primary mating faces based on 3 high-point contact.

 

Background:

The "Nest" move is very similar to the Autobend Move in its High Points mode, operating only on the primary mating surfaces, except Nest move also considers the center-of-gravity (or force direction) when mating faces.  

Of two mating faces that have multiple point pairs, it mates the faces based on the 3 "highest" point contacts between the faces, and searches for the 3 highest points based on the location & direction of a force/gravity.

The nickname "keystone" comes from its first conception as a routine to assemble an intake manifold on a V-configured engine; it has the general shape of the keystone in a classical architectural arch but can be used in several other applications.

For one example, it can be used to position an Oil Pan onto three parts, across two mating T-joints. That is, the Oil Pan has to mate to the engine Block, and the Engine Front Cover, and the Engine Rear Cover. Nest move can be used to select the 3 high-points to mate across all the components.

Another example, Nest move can be used to position an angle bracket to a block.  Here it considers two skewed faces as the primary mating faces.

 

Within this Section:

Objective

Inputs

Assumptions and Limitations

 

 

hmtoggle_arrow1 Inputs and Requirements:

 

hmtoggle_arrow1 Assumptions and Limitations:

 

Notes:

Requires a minimum of at least 4 ObjPts, at least 3 TgtPts, 1 Dir, and 1 object.

Alternative argument lists:  

If there is only one (1) direction in the direction list, then the routine will use D1 for all target surface points, and as the force/gravity direction DF.

If there are only 2 directions in the direction list, then the routine will use D1 for all target surface points, and the second direction for the force/gravity direction DF.  

If there are more than 2 directions in the directions list, then the routine will associate each target point-pair to a separate direction D1 D2 D3 …Dn.  The number of directions must be the number of target-point pairs plus one for DF.