cyclic assembly structure

[cowski]

A coworker ran across a file that will not open, but gives an error "Attempt to load a cyclic assembly structure". It should be a single part in the file and not an assembly, but who knows how it has been abused.

Any tricks to get this to open so we can fix it? Or is this a case for GTAC?

 

[JohnRBaker]

What version of NX is this? And have you tried to Open the part without any components? Also turn off the load interpart data option.

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

http://www.siemens.com/plm

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

To an Engineer, the glass is twice as big as it needs to be.

 

[cowski]

It is an NX2 file that I have tried to open in both NX2 and NX6. I have tried your suggestions but still no luck.

 

[JohnRBaker]

Then you're probably going to have to contact GTAC and see if they help you get this part file usable again.

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

http://www.siemens.com/plm

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

To an Engineer, the glass is twice as big as it needs to be.

 

[jpetach]

Cowski,

(the following assumes non-managed NX .a.k.a native mode)

"%UGII_BASE_DIR%ugii\ugpc.exe" -a interesting_part.prt may help shed some light on the situation. It will output the as-save assembly structure which may help understand the issue. It may be that the aprt had been given a component and that independently (in a different NX session) that component had been added and be given the top assembly as a child.

Also, were there any recent changes to the customer defaults made in the area of version rules? If changes have been made part names that had previously been cosidered unique by NX could now be seen as being versions of the same part number. (it's a long shot but worth mentioning)

(end-of-unmanaged-asumption)


Was the value of the environment variable UGII_OPTION changed?

Looking at the NX log file may also give details which may point at which files are in the "chain" that causes the circularity.

Regards, Joe

 

[hudson888]

Usually it occurs with more than one level of assembly structure, so open the files without loading components and look for what files are called up in the assembly as sub-assemblies. In all likelihood some of them may open on their own but not in combination with the top assembly or other sub-assemblies. You job is to hunt down where the problem occurs and see if you can't make some changes that will fix it.

When and if you exhaust all possibilities then you may still need help from GTAC, but you'll probably either fix it yourself ahead of time or at least identify something more specific for them to solve.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[cowski]

The file won't let me open it no matter what options I use. It should be only a part file (not an assembly), but I do have some coworkers that like to 'temporarily' bring in other components to check things out.

I am currently running in native mode. I tried ugpc.exe and it ran for about 10 minutes but produced no output that I could find. I tried a few different combinations of command line options all with the same result.

Thanks to all for your suggestions. Looks like a job for GTAC.

 

[hudson888]

Turn on load with no components. If that still doesn't work try creating a scratch part file then add your other one to is as a component. If it does neither of those then I'm afraid you're really down to GTAC options, because the error message you're getting is probably just a symptom of some greater type of corruption.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[uwam2ie]

too add HUDSON888
import the corrupt file into a new part.