Move Increment to Move Point Conversion Script?

hi,

I don't understand the use of the bMOVE_CLEARP variable?

I think you missed something. This variable is only set to FALSE after a new "hit", ie only where it is relevant for this task.
if it doesn't work for you in your test, I'll look at it again

What do you mean by fancy alignments?

If the "Clearance Planes Definition" is NOT set after a aligment change, Then it sticks to the previous alignment, the script doesn't know that and calculates the point incorrectly
i have to trace the changes between every Aligments that not reset the "Clearance Planes Definition", I admit that it was too difficult for me

what happens if there is a moving point, flow control command, or avoidence move preceding the Move increment?

I didn't think of that, it will be calculated incorrectly, but it should be possible to patch that

I'm guessing to make this work with imperial one would just divide the vDESTI_POINT_X, vDESTI_POINT_Y, and vDESTI_POINT_Z variables by 25.4 before passing them into the new command?

maybe he already outputs the values correctly, otherwise just convert them, yes
have not tested it in inches


->
When I think about it then the script is very useless at the moment because it doesn't even consider two increment movements that follow one another
sorry

hi,

I don't understand the use of the bMOVE_CLEARP variable?

I think you missed something. This variable is only set to FALSE after a new "hit", ie only where it is relevant for this task.
if it doesn't work for you in your test, I'll look at it again

What do you mean by fancy alignments?

If the "Clearance Planes Definition" is NOT set after a aligment change, Then it sticks to the previous alignment, the script doesn't know that and calculates the point incorrectly
i have to trace the changes between every Aligments that not reset the "Clearance Planes Definition", I admit that it was too difficult for me

what happens if there is a moving point, flow control command, or avoidence move preceding the Move increment?

I didn't think of that, it will be calculated incorrectly, but it should be possible to patch that

I'm guessing to make this work with imperial one would just divide the vDESTI_POINT_X, vDESTI_POINT_Y, and vDESTI_POINT_Z variables by 25.4 before passing them into the new command?

maybe he already outputs the values correctly, otherwise just convert them, yes
have not tested it in inches


->
When I think about it then the script is very useless at the moment because it doesn't even consider two increment movements that follow one another
sorry