manipulate extrude location in different assembly arrangements
manipulate extrude location in different assembly arrangements
(OP)
Hi,
I am using NX 10. I am working on an assembly which have different arrangements. In part navigator I made an extrude cut on one body by promoting it. Now I want to have different locations of that extrude cut in different arrangements. Is there any way to do it?
Thanks in advance.
I am using NX 10. I am working on an assembly which have different arrangements. In part navigator I made an extrude cut on one body by promoting it. Now I want to have different locations of that extrude cut in different arrangements. Is there any way to do it?
Thanks in advance.





RE: manipulate extrude location in different assembly arrangements
Check out this thread. you may be able to do this using the VB code with expressions to change extrude VIA arrangements.
I think this ER would be great to have an Expression that identifies what arrangement is active.
Hope this helps.
RE: manipulate extrude location in different assembly arrangements
I think it can be done through VB, but I really don't know a thing about VB. Anyways thanks a lot for suggestion. :)
RE: manipulate extrude location in different assembly arrangements
if Active_arrangement = "Arrangement 2" then 2 else 0.
This has more to do with expressions than it does with assemmbly constraints. You can use it for both.
Then you run the VB script on linked site above. Your cut dimension changes per which arrangement is active. (Of course this is after you run the VB code after you switch arrangements.)
RE: manipulate extrude location in different assembly arrangements
RE: manipulate extrude location in different assembly arrangements
The Active_arrangement parameter is part of the expressions that the VB code gets and fills out to tell NX what which arrangement is active after running the VB code.
RE: manipulate extrude location in different assembly arrangements
RE: manipulate extrude location in different assembly arrangements
Since multiple users will be using this file, So we dont want to run the VB code option each time as SDETERS has suggested.