Does anyone know how to get the Break rotary motion in the md to work?
break rotary rapid in md/cd
Started by
Jeremy Herron@DBS Solutions™
, Jul 12 2012 10:06 AM
8 replies to this topic
#1
Posted 12 July 2012 - 10:06 AM
#2
Posted 12 July 2012 - 11:45 AM
Not sure, but there is another option in the general machine parameters Op feedrate limits axis motion tab, at the bottom, 5 axis rotary motion, a check box for break rotary motion as a combined angle.
Anything look like that in your post?
Anything look like that in your post?
#3
Posted 12 July 2012 - 12:09 PM
I have tried all of these ... and they have no effect on the code.
Attached Files
#4
Posted 12 July 2012 - 12:13 PM
In the first pic, you have use chordal deviation checked, I think that is using the tolerance in the sys config, and sense rapid moves don't have anything to deviate from.......
My GUESS is that none of them will effect your code, but I would try unchecking the use chordal deviation setting, also try a small number like .1 deg (something smaller than the moves in the code) and see if that changes the code at all.
My GUESS is that none of them will effect your code, but I would try unchecking the use chordal deviation setting, also try a small number like .1 deg (something smaller than the moves in the code) and see if that changes the code at all.
#5
Posted 12 July 2012 - 12:15 PM
a fix that comes to mind is 2 conditional statements in the post.
if cabs-prv_cabs > 179.9
cabs = cabs -90
pbld, cabs
cabs = cabs + 90
pbld, cabs
then the second to take care of negative rotations...
not knowing your machine and situation, you may need something to take care of rotations greater than 270 if that would be an issue. (279-90 = 189... still bigger than 180)
if cabs-prv_cabs > 179.9
cabs = cabs -90
pbld, cabs
cabs = cabs + 90
pbld, cabs
then the second to take care of negative rotations...
not knowing your machine and situation, you may need something to take care of rotations greater than 270 if that would be an issue. (279-90 = 189... still bigger than 180)
#6
Posted 12 July 2012 - 01:03 PM
Thanks Kieth. that gives me somewhere to start.
#7
Posted 12 July 2012 - 02:08 PM
Jeremy, sorry but I think you need to post base this verse looking to MD. It might pull the value from the MD, but using it not sure. I would do a look up of the NCI number or variable that is. Then do a search of the post if it is not a psb post and see how it is handling it. If it is a psb post then it may have logic you have no access to. I would be shooting off an email to posts@mastercam.com and see what they say.
#8
Posted 12 July 2012 - 02:23 PM
From X5 nci & param ref....
Hope they haven't changed...
Hope they haven't changed...
#9
Posted 12 July 2012 - 02:54 PM
It was originally an Inhouse post, but I have done a ton to it. I may know someone that has the psm file. ;-) I have access to the section that is outputting the move, so I think I can get around it either way. Thanks guys. :oldforumcheers:
















