NX command creation

[Maddy02]

Hi, All

I know Siemens has given NX OPEN API supporting various programming languages through which one can automate and customize NX. Heard from someone that almost all command can be automated and customized.

What I would like to know is there any way that one can recreate a command to be associative (basically the commands which are non-associative) like for eg: if we use "Divide Curve" to split a curve with a point or a plane then result won't be associative (and it won't be displayed in the part navigator.

so, if one knows the way how this command should/has to be created (program generation), then
is it possible to make it
1. Associative.
2. Appear in the Part navigator. will be easy to edit it later.

So, summing it up "a command which creates a result which is non-associative, and replicate the same command to be associative as well as it should appear in the navigator tree..."

Thanks in advance,

Regards,
Maddy

Regards,
Maddy

 

[JohnRBaker]

With a LOT of work, perhaps, but I suspect not like you'd expect it to work.

A 'Feature' is the sort of thing that shows up in the Part Navigator (BTW, not all features are 'associative') and participates in updates and internally we have developed what's called a 'feature method' which describes how it works, what can be edited and what is the associative behavior, etc. If a current NX object does not behave like a 'feature' that means that there is no 'feature method' constructed for this object and it's not something which can just be conjured-up by a user using NX Open. Now there are tools to create what we call 'User Defined Objects' using NX Open tools and as part of defining a UDO, you can describe how an object updates, is edited, etc, much like our developers do when they create an actual NX 'feature', but you have to basically start from scratch, you can't just take some existing NX non-feature object and give it a new 'soul' as it were, at least not easily.

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

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

 

[Maddy02]

Hi, John,

First of all thanks for your kind explanation...
My apologies if I didn't made myself clear about what I wanted to know. I can understand that
no software developers will allow to change the tools they've developed by someone from outside.
I just wanted to know is there any possibility of creating an alternative command which gives the
same result as the one software is providing the user - which you made clear (UDO).

So basically it's like creating the same command from scratch. Of course, developer has to take care of
all the aspects related to that particular command.

If one has to create an UDO object then how he needs to proceed.
If you can guide me on this, it will be helpful (perhaps a brief will do the needful or any material which I can find).

Thanks and regards,
Maddy

Regards,
Maddy

 

[JohnRBaker]

I'm sorry, but I don't program, at least not with anything that supports UDO's. Perhaps someone else with more classic NX Open experience can chip in and offer some advice on how to get started.

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

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