Something seems odd there, Maybe one of the Okuma Apps guys can create a program in there PC version of IGF so we can check we have the format correct

I haven't seen a 700 control for a long time, if I remember correctly we should only have a value in X or Z not both

Remove the G52 from the BT=1 line, Also try it with and without the G127 block, If you are cutting on the face of the part we should not need to rotate the coordinates with G127 M403 TL=5252 BT=1 SB=1800 M13 M404 G21 HP=4 G138 Y0. G17

I am a Tornos fan

A company I do some work for just purchased a new Flexicam XL router, Cuts Ally no probs http://www.flexicam.com/en/component/content/article/34-products/routers-3-a-4-axis/50-flexicam-xl.html

How did you go?

Rolldie Chook works pretty well for this sort of thing as well

Hard to know without seeing eveything but matb8$ : -1 Is not very commmon

You need to start here mtype : 0 #Machine type (Define base and rotation plane below) #0 = Table/Table #1 = Tilt Head/Table #2 = Head/Head #3 = Nutator Table/Table #4 = Nutator Tilt Head/Table #5 = Nutator Head/Head Sounds lke you have #3

Is it an old post that has been updated? Can you share it?

either in the post or the machine def, it depends on how old your post is

yes, lathe or mill?

^^ I guess that is one way ^^

is that for all arcs or just helical cut holes? You will need to force the K output in the post probably from parc if (plane$ = 0 & arctype$ < five) | (plane$ = 1 & arctypeyz$ < five) | (plane$ = 2 & arctypexz$ < five) | full_arc_flg$ | arc_pitch$, [ #Arc output for IJK # If you do NOT want to force out the I,J,K values, # remove the "*" asterisks on the *i, *j, *k 's below... if plane$ = zero, *iout, *jout, *kout #XY plane code - G17 if plane$ = one,*iout, *jout, *kout #YZ plane code - G19 if plane$ = two, *iout, *jout, *kout #XZ plane code - G18 !i$, !j$, !k$

Looking at the website it is essentially a 6 axis robot. Does the machine work like a standard robot? where you define points? CONST robtarget pickup:=[[-625.59,229.00,573.33],[0.715995,-0.00576595,-0.698058,0.00574628],[1,1,0,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]]; !Part Pickup Pos CONST robtarget p30:=[[-115.80,260.06,826.95],[0.607585,-0.35808,-0.576312,-0.412896],[1,-1,1,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]]; CONST robtarget p40:=[[-168.06,227.00,648.60],[0.323109,0.0583716,-0.896839,-0.296433],[1,0,1,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]]; CONST robtarget p55:=[[-141.40,182.74,529.88],[0.185192,-0.469153,-0.859244,-0.0854328],[1,-1,2,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]]; Then use the points for a program? PROC MoveHomeBucketSide()!move back to mori chute from bucket SetDO doGrip, 1; !gripper open MoveL p200, v200, z50, tgrip; SingArea \Wrist; ConfL \Off; MoveJ p370, v200, z50, tgrip; MoveJ p380, v200, z50, tgrip; ConfL \On; MoveL Offs (pickup, 400,0,0), v150, fine, tgrip\WObj:=wobj0; SingArea \off; !Move to 400 above part ENDPROC If yes then it should not be too difficult, if no then a 5 axis curve toolpath may give you the result with some hand editing of the 6th axis, or maybe something more aimed at robots in general. Robotmaster etc.

Maybe an engraving macro that self counts, what control do ewe have?

I don't think that is a video card error, my hunch is something has gone wrong within the veiw matrix in mastercam itself, send the file to QC, see what they say

You could use this http://www.cenic.fi/english/ropecam/

The error comes from your offset call TL=5252 BA=90. A Macturn has 2 offset sets BT=0 BASE-A and BT=1 BASE-B BT=0 is the default so if nothing is programmed then we use the horzontal BASE A BT=0 offset. This is why you need the G52, to recalculate the offset at the BA=90 angle. I think it will work better if you use the BASE B offsets Please try TL=5252 BT=1 with NO G52

Do you have a 5 axis machine?

In the format statements fmt "X" 2 xabs #X position output fmt "Y" 2 yabs #Y position output fmt "Z" 2 zabs #Z position output fmt "X" 3 xinc #X position output fmt "Y" 3 yinc #Y position output fmt "Z" 3 zinc #Z position output relates to fs2 2 0.4 0.3 #Decimal, absolute, 4/3 place fs2 3 0.4 0.3d #Decimal, delta, 4/3 place You are better off creating a new statement, if you change fs2 everything that uses fs2 will then be 4 decimal places

Easy fix, Read and follow the instructions or LEAVE

Do you have a 500 or a 96 offset machine? Look like the TD and the MT blocks are not right, could be a post error or it could how you have setup the tool in mastercam. my hunch is you have the tool setup differently to what the post is expecting

What makes it even more expensive is that fact that the CAD is so useless, you are forced to but a standalone CAD pakage as well

ESPRIT does some nice stuff, but it is just way overpriced. Like Gcode said The CAD side is really only one step past typing APT.