NX 5 Move Command

[Andy512]

We upgraded from 3 to NX5 and now the "move" command available from the right click menu will take about 10 seconds to display the dynamic positioning tool. Even worse, if the command is canceled it takes even longer.

When it is "thinking" about this operation ugraf.exe is using 99% cpu and the memory usage just barely trickles upward.

We use dual core cpu's, XP64, 3G ram, quadro 1400, NX 5.0.3.2.
Any suggestions?

 

[JohnRBaker]

Exactly which MB3 menu option titled 'Move' are you talking about? Is this a pop-up menu or after a select-MB3, either from an object or a Navigator?


John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[Andy512]

From MB3 over a component or from pressing the Move Component button in the assembly toolbar. Same result.

 

[JohnRBaker]

You must be using the New Assembly Constraints, because if Mating Conditions was your default, there is no 'Move' Component option (it's titled 'Reposition').

That said, is your assembly large? Now I just tried this using NX 5.0.4.1 on an assembly with over 11,000 components and while it did take perhaps a second or two longer for the dialog to come up than when I tested this on an assembly with only a dozen of so components, it was still fast enough that I wouldn't have thought twice about it. Now there is one issue, if it is a large assembly with a really deep tree (many sub-assemblies inside sub-assemblies inside sub-assemblies, etc,) when you move a selected component that is part of a sub-assembly, the system has to first set that sub-assembly to be the Work Part, which can take a little extra time, but again, in my 11,000 component assembly, even if I pick as deep as I can (at least 4 levels down), it still only adds a second or two at most to the dialog coming up.

One more thing that it might be. If you have lots of inter-part relationships and you're using Partial Loading and you're NOT loading inter-part date, if you are selecting components several levels deep in the assembly structure, it is possible that when they set the sub-assembly to be the Work Part they extra time will be taken to fully load and perhaps even update inter-part links that will also get loaded at that instant under those conditions.

Anyway, unless it's some sort of inter-part updating thing, I can't think of anything that would case a 'Move Component' command to be anywhere near as slow in coming up as you seem to be telling us that it is.


John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[MCGNX]

NX5.0.4.1!!

When does it hit the streets and what's new?

 

[JohnRBaker]

NX 5.0.4.x will be released in April.


John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[doc1955]

I've found if the assembly has components within it with inter-part links and the linked part has moved to a new directory or changed in some way the reposition of a part takes up a lot of resources trying to do updates. Once the links are fixed or removed things went back to norm. This problem also created trouble on the manufacturing side also. You could create your program save and close and the next time you opened all your cut paths would be bad. It seems UG will load the assembly different each time you reopen due to the bad inter-part link.

Doc

http://www.goodrich.com

 

[hudson888]

Doc,

If you have the links set to update automatically try turning on delayed update and see if that helps. It may not do anything or be only a partial solution, but the thread reads like until 5.0.4 there is every reason to proceed cautiously.

Best Regards

Hudson

P.S. I'm not observing the same thing testing smaller assemblies under 5.0.3.2 on Xp 32Bit.

 

[doc1955]

I have already gone that route with no luck. The way I fixed it was to trace down the bad links and relink them then things were good again.
You need to realize when using inter-part links you need to make sure it is a solid model and will not move or be deleted, renamed or the like.


Doc

http://www.goodrich.com

 

[hudson888]

Yes well the only other comment I could make is that you don't want to be doing this running under Teamcenter the path of removing and recreating links can be more tortuous. I have found on occasion that the only way to do so is to first remove the affected components from all the assemblies then save, then delete the links, and then start all over again.

So if there is any way to determine whether a bug does exist that can be addressed I would really encourage PLMS to get on to it. I'm not in a position to test it myself nor do I know whether problems that some posters are reporting can be reproduced. Maybe if those of you who do have the problem can send in your parts to GTAC we're all going to thank you for doing so in the long run. All I know is that problems with Wave Linked geometry are pretty much your worst nightmare in NX.

Best Regards

Hudson

 

[doc1955]

I believe our IT department has turned it in to GTAC.
We are in the process of uploading and turning on Team Center.

Doc

http://www.goodrich.com

 

[hudson888]

I hope that you're given all the help and training that you need to implement Team Center. A few places that I have seen make a start and stop short of fully implementing things like workflow. Half implemented it is a line call as to whether it really provides enough of the benefits that it could. Not a few people can talk about how powerful it is, but when you look at it if you don't have it well implemented then you're just using more memory and trading away some of the flexibility that you may have enjoyed using native systems. Which is a pity because I wouldn't mind getting involved with doing that sort of thing myself if a company were really prepared to get the most out of it. That sort of training and implementation process could be an interesting ride.

Good Luck

Hudson