Object ID

[Mrbharti17]

Hello Everyone,

I was doing some research with NX 9.0 and NX 10.0. Just wondering that when we combine two blocks together with unite feature and subtract the third block (or any shaped feature) using subtract, and then when we switch the target and tool in unite operation (which was done in previous unite operation)then it shows an error of "Unable to perform Boolean operation", that's because the object's ID was changed but my question is that "Is there any way we can automate this thing in NX that it will automatically find the new Object ID by itself?"

for the clear picture I have attached an Image file

 

[Mrbharti17]

 

[cowski]

I can't see your images (they are blocked where I am), but from your description I ran a quick test. I was unable to reproduce the error you describe, I'm running NX 9.0.3.4.

Can you post a sample file where this error occurs?

www.nxjournaling.com

 

[JohnRBaker]

There's not much that can be done since this is how NX keeps track of object ID's. During your example, when the Boolean Unite is performed, the new unified body inherits the object ID of the 'Target' body. Now it's true that we could have simply created a totally new object ID but that in itself can be a problem since the rule has always been that the body characteristics of the Target are always inherited by the final result, such as color, attributes, etc. And those characteristics are tied to the object ID's as the scheme we use to collect and relate this sort of data.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

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

 

[Mrbharti17]

But the thing is it worked before for few times that's why I was confused if this is an update in the software or something. what happened was it didn't show any Boolean error and after few trials it started showing the error. Can you suggest me the possible reason for why it was doing it?

 

[JohnRBaker]

In what version(s) do you think that you saw this working as desired?

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

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

 

[JohnRBaker]

I just went back and tested NX 5.0 and it behaved the same as what you found using NX 9.0 and NX 10.0. Note that if I need to I could probably test this back to UG V17.0 (it would take me a bit to get my license server set-up first for anything older than NX 5.0).

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

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

 

[Mrbharti17]

It worked in NX 9.0 but when i tried next day, It didn't work. So I just wanted to make sure if this is an updated feature in NX.

 

[Toost]

Why would you want to replace the target body in the Unite feature ?
As john explains, the target body ID is the method NX uses to keep together the feature history, messing with the ID is ?....
Of course you could for some special purpose design an algoritm that searches geographically for a suitable body to use as the target, but for general modeling ?


Regards,
Tomas

 

[cowski]

I've seen the pictures now and while I don't have a solution for you, at least I know why my test didn't fail. I tried to subtract the third body from the two that were united rather than subtracting the united bodies from the third body. I see the same issue now; but, like Toost, I have to wonder why you would want/need to switch the target and tool body definitions?

www.nxjournaling.com

 

[Mrbharti17]

There was no particular reason behind that but all I wanted was to have a clear picture on this topic rather than just ignoring.

Thank you Mr. Jones, Mr. Cowski and Mr. Tomas for sharing your knowledge. It was helpful