Extract Moves

<< Click to Display Table of Contents >>

Navigation:  Features and Operations > Extract Functions >

Extract Moves

ExtractMoveIconExtract Moves: This command is available under Extract GD&T which will extract the CAD Constraints and create Feature Move in 3DCS. It creates primary, secondary and tertiary move features by combining the constraints created in between 2 CAD Parts. The Feature move is also created in the same order how the constraints are defined in the CAD.

 

Extraction

Features: The object and Target features are extracted from the CAD Constraints in the order how it is defined in the CAD

Orientation Control: The matting orientation for primary and secondary features gets extracted.

Offset: CAD Offset/Distance constraint will get extracted along with the defined offset value that will be displayed in the offset field in the Feature Move dialog

Move Part: The object part will be extracted as Move Part.

 

Logic - Rule1

Combine the Primary, Secondary and tertiary features from the defined Constraint between 2 Parts in the given Order.

DVM_Move_Extract1

 

 

Rule 2

Fixed Part will always be the Target even though if it is picked to be the object in the CAD. This is to match the CAD behavior to retain the fixed Part Position.

 

DVM_Move_Extract2

 

 

Limitation of Rule 2:

The Fixed Part will always not retain the position if the user defines a move order as shown below

 

DVM_Move_Extract7

 


Now the extracted feature move will have Part_B to be the Target but as the last move in the CAD moves Part_B to Part_C the 2nd Feature move extracted will have Part_A also in the move part list along with Part_B this will not break the previously defined Move. This will break the fixed part position in CAD.

 

Rule3

If an object part is previously constrained to a part, both those parts need to be in the Move Part list.

DVM_Move_Extract7

 

DVM_Move_Extract3

For this order of Moves, Part_A to Part_B will be Feature move 1, Part_B to Part_C will be Move 2 in which both parts, Part_A and Part_B will be in the Move Part List.

Rule 4

From the previous case if any of the carry over part (in the Move Part List) is directly or indirectly linked with the Target Part of the current Move then ignore the Rule 3 and combine this move to the previous Feature Move.

DVM_Move_Extract4

 

 

In this move order Part_A to Part_B will be extracted as 1st Feature Move, Part_C to Part_A as 2nd feature move and now if the Part_C to Part_B extracted as the 3rd move it will look for the parts Part_C is linked to and add that in the move parts for the 3rd move but Part_A is already constrained with Part_B it cannot add this in the move part list and hence combine it to the previous (2nd) Feature Move in the secondary field.

 

 

Limitation of Rule 3 and 4

There are few cases that conflict with our logic and we cannot extract them correctly.

For the below mentioned constraints order,  Part_C to Part_B will be the 1st move, Part_A to Part_B will be the second move with all pri/sec/ter defined. Part_A to Part_C should be the third move but as Part B is previously constrained to Part C Rule 3 cannot be implemented here and also the previous feature move created between Part A and PartB have all pri/sec/Ter field filled Rule 4 also cannot be implemented which will leave this case to build wrong

DVM_Move_Extract5

 

 

Rule 5

From Rule 4, if the last move that need to be merged to the previous move have obj and Tar in different order, we automatically swap it to get the object and Target to match the primary and secondary order.

 

DVM_Move_Extract6

 

 

 

Constraints Supported in CATIA

3DnnszfGTL7VcbFReNIXFi9CBgH5o8LdE5g85svfX7Z5bet4LOKRZ43foQJEg-gVZLIi25CyptX5KG9cQkrUgqPSD5X4Y7lnbYR-x_6P6iby3-68I5wdqzuED4cqGpM_utzW676zaYACoincidence

SrHqQdMI2pkcT-q5ubGKES81D5QApjkDHivRQuUinwKhj8YvV7QQn2L-ANoMuvgg5zw0AfemT-mEsGt5t86VRbRw2zhk6LCRPouhFD6S5Cvnk0aWBCs31H4X4ixWcJ45VHMEV5oztQQContact

c0P98nRWefKFDIK44NEa-q6IJRbftnKdOQhI72YjQJG3KqVNuVrFTD80Li6zdKpU0ujgeLk62g1Ez3oua0czT0hOCiaB9d3lJJ3h_QijX8hUgb9BaELiT4cgCHnbsdlHUUf2i4XqLm8Offset

 

Constraints supported in Creo

 

cckyRBQR3TbcQg6UTNsQLnWVnQ5Vo12OLTOem4QNOhc4f4lu32UnQw8xG3IU6PVVuxjSWEygY7x5Ngy6PlvcrIJYr7cDN-eZC-4ucqC36nTPZ7jo_-VZd-eu0wVYrfcimPdR8z59WoMCoincident

rzr5Ea-CtmUiHzjeFSd4jIedCE4yi4IZ6FY3y8RCv-5oVzP-ylmqa6lfOI43y05PAuNrGhaINR-3v9eGs0tqFIL-tfgZlSYUmVe9xxI-IL_wEilHgKPZv-wmQWtlCJeuGwmpIM-1G5MDistance

WET4U6_ZGwIWqdsOHBIJh2kTbFN1rOkQpNlaoPnT8zun07fn1jfTcdjehyK8eMKdqiGufpSDxpGzjtdlRHk2TStmuggR0gxhquSOZIuyIU4LdaAErgb4nwWFmRqXrYLUgaPFeJLdMCcCentered

 

Constraints supported in NX

 

5LGlzECPHrfc72-J3J-F0JFy5BAHxe4fCo6ccoeC0KRLGCioYq9NA3bL3qEg0TgX8wu_itFroV1EGwTxV6IvkhDfhHLlKdLQQwoumCHOI4jiahawAcqVJo7ioM2F44kAvw4XUDW50P0Touch /Align

ZNTWYrKGCgiJWKKgecQE1Eu3D-etr2SjMNvgRfxBt9jDyAB4vZNJFSQdr1KQz4nAF0EcVS3_NpJaxZ0YKqYGnU8fyGP5adSWNTb1o7gm_OlxRrI8xpMBQf9uLxF6_CRmlWkSEYCjP5IDistance

gUTlxIRtSyoa5g_b4S_7i2Ijq6HrNSQDgSQ1eFuOU1P5DhWu-4IHcVg79GWwaVm6LnnhuTN5_2f4oK7k6MuxUqVaY3uaPZoYAO4qQqtQMyIErtU_UF-lrws0m1vTwoAxSp_yHgypGa0Align Lock

Bz-PsKu6vrMACJC-cQBeSfpG_5a_BH1FsiZpx1bsOJoX2JOm4ug1KMzXyUegIW1Ep9XZxYfrQCB_fpR0XmCr9hRAhki_Uf79vtJWiY9N343eFMGxZh4gQm1bZMYWGVE6HgDVUXq7zQcCenter

 

Constraints supported in SW

 

HQhfO_wgSiylu51MgdytaZVwza1kQ3yeXCL00Oz-aYpStnHntC3HnamrIBfoh1E0BddI2fKbBlyowgtsp7eGDXItGaJbyR3cRIijG_K51u3zqSY4z1EzUefZgFw1x2O2VYX_B2C1jPgCoincident

rwnKjV4aeirmWZdRjMDSczQmRpR6aJSlzkNJVRDUDRHPm7vXEtivDZ7K1JIaU_F690DEyuthv2twd7jzWMLQw5Rgr2HFHDJ4qNu59JlXknlNwc3woqIT9YIO26wNrfWpu4HAB1M-IE8Concentric

Z8_3hiDjXWBkEPU8JhGoNJqgvym-oGhOsKDKVGyJ981GSq-Iqec7ux4CcHXT-e7isoa52Bd83Tz88QpOxO0jriRZ5e2TLdlW24XxQfygDNgWHZchJ2mKcRD8Qfi-aQsrgPMUdoRXzNgDistance

 

Limitation on Offset Constraint

Offset Values extracted will not always build correctly because as per Feature move logic the build position differs depending on which is the Target Part.