It's the gouge check. As soon as I un-checked that box it worked fine. I never use gouge check so that explains why you have different results than I.

Works just fine here. Have you tried changing the radius or length of the line? Maybe i could recreate it better if i knew your perameters? Tool dia:? Line length:? Arc radius:? and I'll try it again.

quote: What tool, RPM and what material?And what depth of cut and step over? Just trying to figure out Cubic inches per minute.

I'll have to do some digging in my post but our Okuma post are set up to calculate shortest distance for rotation since they require M15 and M16's to tell them wether to rotate Clockwise or Counter clockwise.. Example if I'm at B5 and need to got to B0 and the program doesn't tell it M16 then the dang tombstone will rotate 355 deg's instead of -5. Give me a lil time I'll post something this afternoon if no one else has.. My break has ended.

Until this is changed you could always do the old fashioned Convert to STL instead of Boolean add. Works great for verifying multiple parts that are not touching, and or tooling. [ 01-12-2008, 12:09 PM: Message edited by: Slepydremr ]

Yes i have had the same trouble with no 1 on your list. It's quite a PITA. I used to have trouble with losing surfaces. Then i figured out what seems to cause it. DO NOT modify a surface used in a toolpath unless you plan on reselecting it. Even if you simply extend the surface .05 to go past the EOP it will no longer be in the operation. Weird, I know but that used to happen to me also, until i figued out what seemed to cause it. and yes to no. 4 also the bigger the file the more troubles on mirroring, but that is about it. Other than X2 seeming to slow down if you have the large file open for too long. at that point i simply save the file, exit and then re-open x2 Hope that helps alittle, I wish I could figure out what to do about #1. Since almost every part I make I have to mirror. And we prefer to actually mirror the file so that the tooling and part appear correctly in the setup sheets. That is why we don't use transform toolpath mirror. Incase anyone was wondering. I do not have the no. 2 problem you seem to have.

quote: READ THE RULES BEFORE YOU ASK QUESTIONS. Read the post before you flame.... Especially in all caps.... As far as mtol I don't have any advice sorry.. Welcome to the forum.

BACP's can usually be purchased parts, but you can also make them yourself. Think of nutplates only diffferent. The one's we have made are Pins, small extrusion type clips, and flat pattern stuff. The spec defines the part as in one of the letters after the bacp is length, one is width, and so on. This helps to make several parts that are all basically the same configuration, but just slightly different sizes. HTH

I've seen BACP standards, but I dont have the one, or access to the one you need sorry. I always have to get those from my buyer.

Screen, configure, screen tab it's a pull down menu Levels dialog display

Try putting a # in front of your format values and change the *day to day$ Works for me and i have not Day format variables. oops sorry, let try ver 9? here is my line form 9 post code: "( DATE= ", smonth, "/", day, "/20", year, " TIME=", time, " )", e Still no format variables except for the smonth. HTH

Right click anywhere on the toolbar It should be shown in the drop down list.

control definition NC output / page post debug information / button

Turn on debugging, and repost this program again. That should give you an idea where to look.

When you find out let Bruce know. J/K It's kinda a bug, and has been discussed alot. Here

I think what you are looking for is under: screen/ configure/ NC settings/ tab Operation/ button Job setup/ button tool offset register / box add 0 length 0 diameter

Uh-oh sounds like someones in trouble.

Could you (just for fun) post up more of the program. Like 20 or so lines after where you're getting the error. Like Ralph said maybe it's something the read ahead is seeing.

You're machine really ought to be able to do that. Look for a G18 or G19 before that G3. It should be running G17 (XY Plane). edit: Try inserting a G17 before the arc and see if it runs. That would be easier than searching.

Oh, I see. Well then you're over my head. But if you did use change at point at least it would output the code right if you ever had to repost. Then you wouldn't have to remember to edit the program every time. Sorry I wasn't of more help.

You've hard coded it into your post. That's not gonna work. Try using the canned text and insert before. It's on the operations parameters tab. Should be the first one available.

here just try this code: prapidout #Output to NC of linear movement - rapid pbld, n$, pccdia, e$ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, e$ pbld, n$, sgcode, pxout, pyout, pzout, strcantext, e$ # pbld, pcout, pindex, strcantext, e$ it appears you don't need the index call here.

Hmm, I will look at it again. It's really not a problem, I'm just swamped with work.

Sorry, I've been busy here try this change code: prapidout #Output to NC of linear movement - rapid pbld, n$, pccdia, e$ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, e$ pbld, n$, sgcode, pxout, pyout, pzout, pcout, pindex, strcantext, e$ to code: prapidout #Output to NC of linear movement - rapid pbld, n$, pccdia, e$ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, e$ pbld, n$, sgcode, pxout, pyout, pzout, strcantext, e$ pbld, pcout, pindex, strcantext, e$ I think you need to break the xyz and rotary moves.

David, Here's a short and easy way. code: pdrlcommonb #Canned Drill Cycle common call, before add this line--> dwell$=dwell$*1000 if sav_dgcode = 81, I'm sure someone else knows a more proper way, but this works for me.