Cancel
Showing results for 
Search instead for 
Did you mean: 

Zlevel Depth per Cut Variable

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Hi, 

 

Someone knows that variable corresponds to the yellow parameter (Zlevel Depth per Cut), in the attached photo, within the streamline operation?


streamline_operation.JPGvariable_ap.JPG

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Best Regards 

Ivan

9 REPLIES

Re: Zlevel Depth per Cut Variable

Esteemed Contributor
Esteemed Contributor

Are you looking for this variable in the post or shop docs, or somewhere else?

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: Zlevel Depth per Cut Variable

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Is for post, I searched with the debugger  but I can not find it.

 

 

Re: Zlevel Depth per Cut Variable

Esteemed Contributor
Esteemed Contributor

You cannot access all operation settings from MOM in some cases you need to create a custom DLL to collect this information on your own.

I doubt that settings of the various drive methods of fixed and variable axis operations are even planned to be available in MOM.

The surface contouring operations are much more complex than the level-based operations.

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: Zlevel Depth per Cut Variable

Esteemed Contributor
Esteemed Contributor

Did you try setting it to a "unique" value (e.g. "5.01234")?

Then search for one digit less (for my example, search for "5.0123")

 

When you searched the debugger - did you look in the TK dialog for the debugger, or in the text files that get created?

 

You could also try the "Moog_Show_Globals" proc (search this forum for thread with proc code & how to use), it could be the variable is set but Siemens doesn't report it. 

 

But as Stefan says, this may not have a mom variable created for it.

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: Zlevel Depth per Cut Variable

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Thank you for everybody. 

 

I have tried the function but it seems that this variable doesn´t exists. 

 

Maybe with a .dll I could take it. 

 

Best Reagrds

Ivan

Re: Zlevel Depth per Cut Variable

Esteemed Contributor
Esteemed Contributor

If you need help writing the DLL...

The tcl command in the post is MOM_run_user_function

The Ufunc call is UF_MOM_extend_translator

There are examples in the "Solutions" database (https://solutions.industrysoftware.automation.siemens.com/), search on either of the above 2 functions.

 

 

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: Zlevel Depth per Cut Variable

Esteemed Contributor
Esteemed Contributor

I didn't want to post until I found it...

I also did a presentation on this at the 2010 PLMworld conference.

You'll need to become a PLMworld member, but it is available at:

 

http://www.plmworld.org/p/do/sd/sid=1025

 

Concentrating on C/C++, but there's some useful info for any language.

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: Zlevel Depth per Cut Variable

To confirm, not every operation parameter is output as a mom variable. If a parameter is not output (such as this one), then you need to use the API to read the parameter from the operation.

Mark Rief
Retired Siemens

Re: Zlevel Depth per Cut Variable

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Ok, thanks to all.

Learn online





Solution Information