shop doc documentation 1

[berri]

Hi guys:

I am customizing, my own shop doc html for CNC operator.
Can anybody help me with the code. For example I need to know,how can I create the part name on html, the weight,the origin of the tool, tipo of machine for simulation, the total machining time, how is the rutine to send photos to html. I need to know this rutines.

Thanks.

 

[DynaVox]

Berri, a lot of $mom_... variables can not be extracted when you need them in shop docs. I report this on GTAC 2 years ago.

 

[berri]

I am using NX6, I so new user on NX CAM.

This documentation is imposible to customize?

Thanks.

 

[berri]

This variables of MCS axis can be put on shop doc??
I am searching...

global mom_mcs_origin
global mom_mcs_matrix

OBJ_title "Machine Coordinate System"
OBJ_info "Origin" $mom_mcs_origin(0) \
$mom_mcs_origin(1) $mom_mcs_origin(2)
OBJ_info "Matrix" $mom_mcs_matrix(0) \
$mom_mcs_matrix(1) $mom_mcs_matrix(2)
OBJ_info " " $mom_mcs_matrix(3) \
$mom_mcs_matrix(4) $mom_mcs_matrix(5)
OBJ_info " " $mom_mcs_matrix(6) \
$mom_mcs_matrix(7) $mom_mcs_matrix(8)
OBJ_info " "

OBJ_info "Intol" $mom_inside_outside_tolerances(0)
OBJ_info "Outtol" $mom_inside_outside_tolerances(1)
OBJ_info " "

 

[FrankMalone]

Give a shot to the command MOM_list_oper_path.

My solution to obtain data from the operations path is to run a simple postprocessor from shopdoc, this very simple postprocesor outputs a file with lines like:
set variable value
set variable2 value2
...
then, make a source of this file and you can get every data like a normal postprocesor can get inside the shopdoc.
For example:

proc MOM_OPER_BODY { } {

global mom_source_directory
....

set list_tcl "$mom_source_directory\post_list.tcl"
set list_def "$mom_source_directory\post_list.def"
set file_tmp "lop.tmp"
MOM_list_oper_path $mom_operation_name $list_tcl $list_def $file_tmp
source $file_tmp
....
}

 

[berri]

Ok I am going to try this.

Thanks

 

[markrief]

a lot of $mom_... variables can not be extracted when you need them in shop docs.

Mom variables are available for almost all operation parameters. See the help for instructions on turning on the review tool, then you can see all of the available variables.

There are a few that are not available because they are generated by the postprocessor. For these, you can use MOM_list_oper_path as mentioned above, or generate the shop docs from your postprocessor.



Mark Rief
Product Manager
Siemens PLM

 

[DynaVox]

Thank you markrief and FrankMalone. I will try this.

 

[berri]

Setting File Extensions, on shop doc

PDF can be other format? or only can be on txt and html?

global mom_sys_output_file_suffix
set mom_sys_output_file_suffix "txt"
Open_Files
}

thanks.

 

[markrief]

The output is ascii text.
Changing the file extension does not change the file format.

Mark Rief
Product Manager
Siemens PLM

 

[wmalan]

"Mom variables are available for almost all operation parameters. See the help for instructions on turning on the review tool, then you can see all of the available variables."

"There are a few that are not available because they are generated by the postprocessor. For these, you can use MOM_list_oper_path as mentioned above, or generate the shop docs from your postprocessor."

Does this mean that MOM_operator_message can be output in shop docs if it's run from within a post? I tried a while back to use the modified default pulldown Postprocess, Tool_List (HTML) but was later told that mom variable was not available.

--
Bill
NX 6.0.4

 

[berri]

I only want this mom variables, on shop doc.

mom_date, for date
mom_part_name, part name
mom_part_material_name, I don't know if this variable is ok,
because some similar ones are taken from machining library, material hardness etc.
mom_msys_origin, origin of tool
mom_machine_name, name of the machine
mom_machine_time, time expenden on milling etc
mom_operation_name, name of the machining operation
mom_tool_name, name of the tool
mom_cutting_time, cutting time on a particular operation.

I think, that this variables a so common to customize a .tcl archive for shop doc. I prefer to build shop doc independet from the postprocessadors.

thanks.

 

[markrief]

Does this mean that MOM_operator_message can be output in shop docs if it's run from within a post? I tried a while back to use the modified default pulldown Postprocess, Tool_List (HTML) but was later told that mom variable was not available.

The mom variable may not be available. You would have to catch the output in the proc in the post. In general, for any UDE, you need to capture the OUTPUT from it, and that does not happen until you post.

Mark Rief
Product Manager
Siemens PLM

 

[berri]

Hi Mark,

You mean,to create a simple post with the MOM variables that I want to see, postprocess and see the internal code of them.

Later put this code on the shop doc tcl archives, that I want?

Thanks.

 

[markrief]

I don not understand your question. Only if you want to capture UDE output do you need to use a post.

When you tried to output the mom variables, which ones were missing?

Mark Rief
Product Manager
Siemens PLM

 

[berri]

I don't know if it's possible put mom variables on a .tcl archive to generate a shop doc html document.

 

[wmalan]

"The mom variable may not be available. You would have to catch the output in the proc in the post. In general, for any UDE, you need to capture the OUTPUT from it, and that does not happen until you post."

Mark,
Ok. That makes sense. I guess what I need is an example of capturing the event. I would assume it would store it in some buffer after cycling through. I'll poke a bit in the samples to find a similar technique.

I've been editing the post_operation_list_html.tcl and trying to simply replace either mom_operation_name or mom_operation_type. I can see now since those are NOT ude's that would not work. (yes, I know, the Customization class..<g>)Thanks for the info.

Btw, how do you reply with that formatted "Quote" on this board?

--
Bill

 

[markrief]

Bill, if you can post a request on the nx.cam bbs forum, or log a call with GTAC, I can send you an old shopdoc sample for catching UDE output.

For quoting - (w/o spaces):
[ q u o t e ] blah [ / q u o t e ]

Mark Rief
Product Manager
Siemens PLM

 

[berri]

I don't understand how can I get old UDE output,

with an old shopdoc sample. Seen internal code?

with ultra edit or other soft??

Thanks.

 

[wmalan]

Bill, if you can post a request on the nx.cam bbs forum, or log a call with GTAC, I can send you an old shopdoc sample for catching UDE output.

Will do. Thanks.

--
Bill