Showing results for 
Search instead for 
Do you mean 
Reply
Solved! Go to solution

Rapid Move XYZ Sequence in NC Program different from that in PostProcessor

Hello,

 

In my post processor, for the rapid move, I set X and Y to be output first and Z after that. Picture is attached. However, when I post operations and get NC programs, sometimes X and Y are in front of Z, sometimes they are after Z. I was wondering why it is like that.

 

Thanks,

Kai

 

 

 

3 REPLIES
Solution
Solution
Accepted by topic author Kai_Xue
‎02-09-2016 12:00 PM

Re: Rapid Move XYZ Sequence in NC Program different from that in PostProcessor

Somewhere on that dialog (below what you show) is a check box "Work Plane Change"

 

What this does (assuming the tool axis is "+Z")

- if you are going DOWN in Z, it does all other axes (X/Y/4th/5th) Then Z

- if you are going UP in Z, it does Z first (to clear the part) then the other axes (X/Y/4th/5th)

 

So this is usually the "safest" way to rapid between points (the X/Y/4th/5th motion is done as high as possible)

 

If you have "head" (vs. table) rotary axes, this may or may not be true (depends if you rotate the work plane with the tool - i.e. is "+Z"  *always* pointing UP the tool?)

Ken

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: Rapid Move XYZ Sequence in NC Program different from that in PostProcessor

Thanks, Ken.

 

I found my problem. I used "MOM_output_literal "CALL LBL 100" " to let the tool go home, but the system doesn't know that the Z value has been changed. So after homing, the tool is going in the -Z direction, but because the new Z value is larger than the Z value before the tool went home, the system assumes the tool is going up.

 

Kai

Re: Rapid Move XYZ Sequence in NC Program different from that in PostProcessor

[ Edited ]

Yup, if you have the post output something that "moves" the tool location, you DO need to let the post know it moved.

For those that can't figure it out on their own, typically something like:

global mom_last_pos
global mom_prev_pos

set mom_last_pos(...) $new_value
set mom_prev_pos(...) $new_value

MOM_reload_variable -a mom_last_pos
MOM_reload_variable -a mom_prev_pos

where the (...) is the axis/axes involved, i.e. (0) = X, (1) = Y, etc.

 

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