linarc$=1 That's what it says.

Will check on that now. Left early yesterday. Thanks for the suggestion guys.

I have looked through the control def and I can find that anywhere. Under the arc page in Cont Defs I have break options. Support arcs XY, XZ, YZ arc center type all set to absolute break at quadrants Arc error check = length of arc = parallel axis motion on quadrant =end point check (round endpoint-break on failure I left a message at my reseller for some help but no reply yet.

Ok Nathan. Will check there. Thanks guys BRB

I am getting a G17 call out in my gcode. But that's in between countless points.

I do not see that in the post at all.

Let me check on that.

We have a brand new POS Hurco which is replacing the older POS Hurco. Anyhow, they same the same post I have will work on this one, but I was writing a quick contour test program on an arc. In the cont defs I have it set to output quadrants arcs in XY and filter in the program parameters to an arc. The post has quadrants and seems like it should work BUT the code comes out point to point. No G2 or G3 anywhere. Am I missing something? Thanks for any help

Bump... I have a new solid file and I am getting the same error. I have tried rough pocket with one set of boundaries and tested a parallel with a different boundary and both give me "unable to extract solid face".

I have an electrode blank in body position. In fact I have many in different files. I have two lines created from mid points of all four sides. They intersect. In V9 if I picked one line near the end and the other line near the end ... the first line would be X and the end I picked would be + and the second would be Y positive. In X I can not get it to orient that way. If the lines are trimmed... it works. BUT That would make another step seeing the lines are centerlines showing origin for layout, and I would have to untrim them or ... regardless its a pain.

Weird... Thanks John.

In previous versions if you slect two lines for a cplane you could pick the + end side of x axis first and the + end side of y axis second to orient the cplane correctly. In X there is no rhyme or reason in the selction method to get it to orient the way you want. Even flipping through the 3 choices they may give you. Every once in a while you get lucky but I have tried every which way selecting and I still have to rotate about an axis to get what I want. Anyone else notice this?

Pete, Yes it seems that after I did the combined view I could no longer write to the two solids. There was only two things that I had done that could call into question. The other thing... I added a few surfaces from a solid face to raise them up .005 to protect a finish cut. I went back to the original geometery and tried to de-select the solids. It wouldn't work or de-select. So I let it go and created a new toolpath with the solids and the new surfaces and that's when I got the error. The solids are not marked dirty. The original "good" toolpaths were not marked dirty. I ended up creating surfaces form the solid to finsih writing the toolpaths.

Also it didn't dirty any of my previous toolpaths.

I was writing toolpaths on these two solid blocks. It was going along fine. I then went to 4 views to see if the printing problem was fixed. (it's not) so I started messing around. I clicked on combine views (no idea why) and since then I can not write on these solids which appear to be clean (no regen needed). I get the error in the subject line of this topic. Any ideas?

or... I finish a complete mold design (maybe 40 hours), print out detail sheets, hand them to the foreman... and about an hour later I get "we have some rough stock in inventory that is smaller than the call out, but I told him to make it out of that and you can change the design." wha wha WHAT?!!!! I told the shop owner, "from now on you guys build the f'n tool and I will design it when you're FINISHED!"

No bonuses here in years as well as raises. I was cutting a .04 rib .800 inches deep about 45 inches long in P-20. Our cutter grinder is a POS so they decided to buy the cutter. I am no genius but if I would to guess I would say buy maybe 8 cutters to be safe. At 46 bucks a piece they decided to go with TWO. Saturday morning I come in and the last of the two was broken. Wouldn't you know nobody was open that sold them. So myself and the operator pretty much came in on a Saturday for nothing. Monday morning..."why isn't that rib finished yet?"

I am with you kinglouie. It does come in handy if you want to insert a semi rough or some sort in the middle.

I am not a post guy, but I would think it is in the post you have. Let everyone know what post you are using and what machine you have. I am sure someone can give you an answer.

I checked out your file. I didn't see any "jittery thing". I see a z level rough (op 4) and a few lifts in Z because of depth variations but not much else that would bother me. I looked at it in X and in V9. Sorry Barb... I said (he) before. Looking at the name Brice. My apology.

So he is using project. That is what I thought. It will jitter on the machine but not necessarily stopping. If the feedrate is up you may get a rumble but that should be it. Been there done that. A more fluid path simulating the edge curve of the surface when projected will get rid of the jitters.

That's what I thought birdman.

I would recreate the problem child.... +1 to Murlin.

Dome shaped... is this a revolved surface? Was it created in something other than MC?

the memory he was referring to is RAM. Database is for surfaces wireframe etc... toolpath alloctaion is RAM dedicated to processing the toolpath. The jittery thing... what type of toolpath are you trying to write? (I believe he is talking about the up and down jagged looking cuts in backplot when you run something like a scallop or project where the surface transition changes per the step over amount. Shoot a screen dump of the backplot to me so I know what you are talking about.