NX 11, Component "Ghost" trips up save-as

[3dr]

I get the following error...
"A File with the same base name already exists"

But it doesn't, not in the folder, not anywhere in the design.

Simply trying to save
156.prt (Current)
156__01.prt (Versioned)

This has happened before and be a real nuisance at times.

I suspect at some point the part was saved as that before and the assembly won't forget it?

Any ideas out there????



Dave
Automotive Tooling / Aircraft Tooling / Ground Support Structures

NX11, Win 10 Pro

 

[jerry1423]

Check if there is a part by that base name buried someplace in your Assembly Tree.

Jerry J.
UGV5-NX1899

 

[cowski]

In addition to Jerry's comment, check information -> part -> loaded parts. Near the bottom of the output NX will list files that are referenced but not loaded. Sometimes an old reference lingers in the assembly, a part cleanup with all the moderate actions checked will usually clear it out. If the part cleanup doesn't do the job, check interpart expressions and wave links for any reference to the old file.

The text of the message makes me think that you are using native NX with part versioning turned on. In the customer defaults check assemblies -> site standards -> part versioning; if any of the fields are not blank, NX might be looking at the file names for revision info. I've only tinkered with this option (never used it for production parts), so I'm not sure how these options might affect saving files.

www.nxjournaling.com

 

[3dr]

Thanks Jerry,
My "Part Find" dialogue doesn't have any of those tab options and seems to have limited functionality.
didn't get anywhere with it.

@ Cowski,
I did find a partially loaded "156" part when it is definitely not part of the design anymore.
We moved on from that part number and obsoleted it since we couldn't version it.

And you're correct... I'm using native NX with versioning turned on.

I have tried the part clean up with as much as I could safely turn on with out risking anything.
All the moderate selections checked.
Just didn't work.

Also tried cloning... that didn't work either.

Also, can't close that part individually because it's not listed in the dialogue.

It's truly a ghost part... frustrating!








Dave
Automotive Tooling / Aircraft Tooling / Ground Support Structures

NX11, Win 10 Pro

 

[cowski]

Other things to check:
Assembly constraints that reference the old part. If the component is used in an assembly constraint and the component is later removed from the assembly, the constraint can hang around and reference the old component (although, part cleanup should take care of this possibility).
Any interpart expressions or wave links may reference the old part.
Sketches can also contain references to other parts. For instance, if you are working in the context of an assembly and dimension or constrain to the edge of a component, a reference to that component part will be created in the work part. These are tricky to find/fix. Are you still using NX 11? I had a journal that would look for these references. Newer versions of NX broke it, but it might still work on NX 11...

www.nxjournaling.com

 

[3dr]

Thanks Cowski,
Let's give the journal a try, I'm still on v11.
It would be a nice tool to have in the box if it works in this version.

This was a tool assembly I imported from step and made limited changes to, it's mostly dumb bodies.
No constraints, some geometry links, no inter-part expressions.

Maybe there's an obsolete geometry link hanging around in there somewhere.





Dave
Automotive Tooling / Aircraft Tooling / Ground Support Structures

NX11, Win 10 Pro

 

[cowski]

http://nxjournaling.com/content/journal-creation-process

An early version of the journal can be found at the link above. It only reports on the objects that the dimensions reference (it doesn't look at geometric constraints). I was working on an improved version when life got busy and I kinda just dropped it and forgot about it... I'll dig up the old code and do some testing.

www.nxjournaling.com

 

[cowski]

I found my WIP code and now I remember why I dropped it. I ran into a bug in the NXOpen API regarding working with sketch constraints. However, I found some similar code from GTAC that had some work-arounds. I'll have to see if I can adapt them to my code to get it working.

www.nxjournaling.com