cancel
Showing results for 
Search instead for 
Did you mean: 

MKE: support for MOM_set_attribute?

Esteemed Contributor
Esteemed Contributor

Is there any schedule to support the newly introduced MOM_set_attribute function in MKE?

Would be nice to avoid creating custom DLLs.

It would be a workaround to overcome a problem where an operation start UDE must be evaluated before the tool change. The UDE is applied through MKE, since the information it represents is hard to get from within the post-processor.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community
5 REPLIES

Re: MKE: support for MOM_set_attribute?

Esteemed Contributor
Esteemed Contributor

A "Tool_Change_Marker" UDE doesn't work for this?

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled


Re: MKE: support for MOM_set_attribute?

Esteemed Contributor
Esteemed Contributor

I have long ago stopped using the markers, since tool change output was always done in initial or first move, where start UDEs of operations are already processed.

I will have a look at the event order, if it has changed, still there are other things where it would be beneficial to provide additional information available in the MKE rules to be added as object attributes.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Re: MKE: support for MOM_set_attribute?

Siemens Legend Siemens Legend
Siemens Legend

Stefan, please provide some more detail of what you are trying to achieve.

We read following in the docs:

"Markers will generally not have any conditions. Markers serve to tell NX where to output an event.

For instance, the Tool Change Marker allows you to specify where you want NX to output the tool

change event. If you insert this marker into the list of Add-ons, NX writes the commands above the

marker to the CLSF before the LOAD or TURRET command, and it writes the commands below the

marker to the CLSF after the LOAD or TURRET command. "

Reinier Capelle

NX CAM Development

NX CAM Machinery and Automation

Re: MKE: support for MOM_set_attribute?

Esteemed Contributor
Esteemed Contributor

Hello Reinier,

the requirement is to distinguish between reamers for blind and through holes, since the cooling outlet is different.

The tool database only contains one reamer, since the important geometry is the same for both tool types.

In the MKE rules I am able to easily tell if I ream a through or blind hole, so I created a UDE with a single Boolean parameter, which is set to true as a start event and to false as an end event.

The post-processor contains the following UDE procedure:

#=============================================================
proc MOM_HAI_is_ThroughHole {} {
#=============================================================
    global mom_hai_is_through_hole

    # OUT mom_hai_is_through_hole
}

The tool change procedure contains the following conditions to add a suffix to the tool name:

    global mom_cutmthd_libref mom_part_material_libref mom_cutter_libref mom_hai_is_through_hole mom_operation_name
    global HAI_is_rough_finish_tool HAI_is_reamer HAI_is_thread_drill HAI_is_through_hole_reaming
    # check if tool is end or ball mill
    set HAI_is_rough_finish_tool 0
    if {[info exist mom_cutter_libref]} {
        set HAI_is_rough_finish_tool [regexp {TL[2-5]\d\d\d} $mom_cutter_libref]
    }
    # check if tool is reamer
    set HAI_is_reamer 0
    if {[info exist mom_cutter_libref]} {
        set HAI_is_reamer [regexp {TL6[34]\d\d} $mom_cutter_libref]
    }
    # check if tool is thread drill
    set HAI_is_thread_drill 0
    if {[info exist mom_cutter_libref]} {
        set HAI_is_thread_drill [regexp {TL6[5-9]\d\d} $mom_cutter_libref]
    }
    # check if operation is through hole reaming
    set HAI_is_through_hole_reaming 0
    if {[info exist mom_operation_name]} {
        set HAI_is_through_hole_reaming [regexp {REIBEN_S\dH} $mom_operation_name]
    }

    # check if cut method is roughing
    if { [info exist mom_cutmthd_libref] && $HAI_is_rough_finish_tool == 1 } {
        if {$mom_cutmthd_libref == "OPD0_00003"} {
            set custom_add_to_tool_name "_SR"
        } else {
            set custom_add_to_tool_name "_SL"
        }
    } else {
        # check if thread drilling brass
        if { [info exist mom_part_material_libref] && $HAI_is_thread_drill == 1 } {
            if {$mom_part_material_libref == "BRONZE"} {
                set custom_add_to_tool_name "_BRONZE"
            }
        } else {
            # check if reaming a through hole
            if { ( [info exist mom_hai_is_through_hole] || $HAI_is_through_hole_reaming == 1 ) && $HAI_is_reamer == 1 } {
                if { $HAI_is_through_hole_reaming == 1 || $mom_hai_is_through_hole == "TRUE" } {
                    set custom_add_to_tool_name "_DGL"
                }
            } else {
                set custom_add_to_tool_name ""
            }
        }
    }
#    OUT mom_cutter_libref HAI_is_rough_finish_tool mom_cutmthd_libref custom_prev_add_to_tool_name custom_add_to_tool_name
#    OUT mom_cutter_libref HAI_is_reamer mom_hai_is_through_hole custom_prev_add_to_tool_name custom_add_to_tool_name

I started with checking the operation name, but that can be changed easily by the user, so I introduced the application of the UDE as start and end event to the operation, since UDEs are not so easy to manipulate by a user.

I will do some further checking and report back with what the solution was.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Re: MKE: support for MOM_set_attribute?

Esteemed Contributor
Esteemed Contributor

@ReinierCapelle  and @Ken_A, sorry the tool change marker doesn't work in this example.

The tool change is output after the UDE procedure is executed, but the custom tool change procedure is still executed before the UDE :'(

This is for a PC post, so things might be different.

I have also contacted the post developer, so he surly knows how to resolve this, since he introduced the custom layer.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Learn online





Solution Information