Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations The Obturator on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

NX Shop Doc Problem

Status
Not open for further replies.

Jules1968

Aerospace
Dec 24, 2009
4
HI,

I am creating some shop docs using the documentation written by Mark Rief (I notice you are on this forum). I am trying use the command MOM_list_oper_path to capture some UDE variables and whatever I try NX crashes straight away with a runtime error and general fault exception. I have tried copying the examples from the documentation exactly and the same thing happens. Does this command still work in NX 7.5?

Also if I could get it to work, can I use it with the actual full posts for the machine rather that creating the minimal "scratch" posts which the documentation uses for capturing the shop docs?

Regards,

Julian
 
Replies continue below

Recommended for you

Ok. I have fixed this problem; I was missing the "MACHINE UG_CLSF" at the top of the shop-doc def file.

I can now access the UDEs attached to the operations but my new problem is that I want to access a particular UDE which is attached to the PROGRAM group name. I have tried using

MOM_list_oper_path $mom_object_name $my_tcl $my_def

but this gives me nothing. Is it possible to access this UDE?

Regards,

Julian
 
MOM_list_oper_path is only for operations.
You will probably need to postprocess to get the events on the program group.
If you need support in this area, please contact GTAC.

Mark Rief
Product Manager
Siemens PLM
 
Thanks for your reply Mark.

So is it possible to invoke post-processing of the group (or whole program) to an output file from a tcl command in the shop doc program? Then I could open the output tapefile and strip the info that I need from the header?

Regards,

Julian
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor