cancel
Showing results for 
Search instead for 
Did you mean: 

Need help with mom_cycle_tool_axis_change variable

Pioneer
Pioneer

Hi

 

Need a small help with the variable mom_cycle_tool_axis_change  which usually gives output in either 1 or 0.This variable is basically used in cycle plane change. I am currently working on a 5-axis mull-turn machine and need to understand the use of this variable if it could be helpful.

 

Kindly help me to understand its usability and the basis of its output (0 or 1).

 

Thank You.

10 REPLIES

Re: Need help with mom_cycle_tool_axis_change variable

Phenom
Phenom

hi,

 

maybe you are not the first who wants to know that.

I dont know the rules of calling cycle plane change procedure.

What you want to do (why)? Or what problem do you have?

 

I have some template blocks in cycle plane change section and one CMD.

Also I use only one setting for checking tool axis (check boxes below)

The CMD I have there - if postprocesing do "cycle plane change" CMD do its job.

If postprocesing dont jump there - It wont. So I count with both situations to get good nc code.

I dont care when "cycle plane change" event is present, but if it is, you can handle it.

If you want you can also abort this event.

 

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Need help with mom_cycle_tool_axis_change variable

Pioneer
Pioneer

Well i am currently not facing any problem but just to understand the functioning of variable i have put up the query.Was wondering if it could help me in some way to ease up my work.

Re: Need help with mom_cycle_tool_axis_change variable

Phenom
Phenom

Documentation:

 

NX outputs an event (MOM_cycle_plane_change) to allow you to process work plane changes. A Work Plane Change occurs when the next tool position is higher, relative to the spindle axis, than the current position. The system uses the event mark Cycle Plane Change to output a move, if desired, to a higher plane before the next cycle is executed. You may attach a block or call a custom command to output the work plane change move. The mom_variable, mom_cycle_clearance_pos defines the X, Y, Z position.

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Need help with mom_cycle_tool_axis_change variable

Pioneer
Pioneer

It gives an output of 1 before the start of drill cycle and an output of 0 after the drill cycle.

I am printing the output from cycle plane change.

 

OutputOutputProc in cycle plane changeProc in cycle plane change

Attached is an ouput image and the proc from where i am printing the value.Ignore the B value.Output is for drill at an angle with a moving head and table.

 

Kindly help to identify how it gives the output of 0 or 1

Re: Need help with mom_cycle_tool_axis_change variable

Phenom
Phenom

documentation

 

.....The system uses the event mark Cycle Plane Change to output a move, if desired, to a higher plane before the next cycle is executed........

 

R in your cycles is the same,  there is no output of cycle plane change - 0, so where is the problem ?

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Need help with mom_cycle_tool_axis_change variable

Pioneer
Pioneer
This output is of the cycle_tool_axis_change. Drill cycle invokes it from the cycle plane change . I am asking about the output underlined in red, 0 & 1.

Need clarification over that.

Thanks

Re: Need help with mom_cycle_tool_axis_change variable

Phenom
Phenom

output 1 - I am surprised that cycle plane change event is invoked before first hole.

(If your attached picture of pb_cmd is from cycle plane change.)

I suppose you are using librabry post fanuc.

I really dont know why is this variable 0 and 1 and when.

Ive never use it.

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Need help with mom_cycle_tool_axis_change variable

Pioneer
Pioneer
ok.thanks for your views.i will try to identify it further on.

Re: Need help with mom_cycle_tool_axis_change variable

Esteemed Contributor
Esteemed Contributor

I'm not sure about the "1" either.

Did you just post this ONE operation?

Or did you post a bunch of operations, and only show us the output from the one op?

- if so, what Z values were used in the proevious op?

 

Also, where are the machine "0" points defined to?

Could be after a tool change NX thinks the tool is at Z0, so Z275.xxx is really "up" from the prior position?

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


Learn online





Solution Information