Coordinate system problems when importing parasolids

[Airasj]

Hi

I have the following problem:

In a large assembly I export a parasolid from a subcomponent. I then import this parasolid into another subcomponent. The parasolid will not stay in the global or absolute coordinate system. The problem was traced down to the following. Whenever the sub assembly file into which the parasolid is imported, was not ever moved, it falls into the correct position. If the sub assembly file was moved ( move component) the parasolid will show up at that position relative to the absolute coordinate system. As the move becomes unknown in a big assembly where different people brings in components, it is impossible to get the parasolid into the correct position.

This is driving us crazy. we are working in a large assembly and subcomponents are often not linked with assembly constraints, but are rather left in the absolute coordinate system.

Is there a way to make sure that the parasolids coordinate system always stay relative to the main assembly absolute coordinate system. I have tried to set WCS to absolute in all files prior to export and import, but that have no effect. Somehow I think I misunderstand to way NX works with coordinate systems. Thanks for the help.

Attie

 

[cowski]

The main thing to remember is that the display part controls the coordinate system. Let's say that you are working with the assembly set as the display part; the exported parasolid body will be relative to the assembly coordinate system. If you make the component part the display part before exporting, the parasolid body will be relative to the part file coordinate system.

www.nxjournaling.com

 

[jerry1423]

When I export a parasolid from one file and then import to another I verify that the WCS is oriented the same way, and directly on top of, the Absolute Coordinate System, and it work fine for me.

 

[Xwheelguy]

For clarity, Source Asm = Asm A, Source Sub-Asm (Parasolid) = Asm B & Target Asm = Asm C.

The problem was traced down to the following. Whenever the sub assembly file into which the parasolid is imported, was not ever moved, it falls into the correct position. If the sub assembly file was moved ( move component) the parasolid will show up at that position relative to the absolute coordinate system.

Well, yes, that's how it works. If Asm C is moved around and then one imports a Parasolid or even adds as a component Asm B, it's NEVER going to be in correct the position. What you're saying, to me, is that Asm C may get moved 10000mm in X and you expect Asm B to know that Asm C was moved 1000mm in X. Nope, doesn't work that way. Move/Reposition is the only alternative at that point unless you're really good at manipulating the WCS and saving CSYS and copy/pasting them between asm's to use as reference for relocating the WCS prior to exporting the Parasolid.

Tim Flater
NX Designer
NX 9.0.3.4 Win7 Pro x64 SP1
Intel Xeon 2.53 GHz 6GB RAM
NVIDIA Quadro 4000 2GB