problem with illegal arc at . . .

[Code_Breaker]

I need a little (lots) of help. I have been at this for about two hours.

 

 

This works fine:

[*]I am using a 1mm BEM with Surface Rough Pocket with "Rough" turned off and "Finish" turned on. I am only want to do the walls. The tolerance is .0008 (filter 2:1, one way, only arc in XY) and step down .005. Plus .002 stock.

This one doesn't work, but getting illegal arc warnings.

[*]I am using a 1mm BEM with Surface Rough Pocket with "Rough" turned off and "Finish" turned on. I am only want to do the walls. The tolerance is .0001 (filter 2:1, one way, only arc in XY) and step down .0005. Plus .000 stock.

I have played with the filter, tolerance and step, but to no avail.

 

QUESTION Is there something missing here?

 

Code_Breaker

[Teh Bear without Brains kinda idiot]

Code_breaker I had it with DMC63V And Sinumeric810d

The solution is change your way of arc writing from

R to I and J and you `ll be fine

.

I have more too say but I am busy and I think that`s enough .

[Code_Breaker]

Winnie,

 

I am using I & J (seven places in NCI), our machine won't take R. I am getting this in backplot.

 

Also, if I change to Surface Finish Contour with same filter, tolerance and step == problem solved for this project. However . . .

 

I know they are basically the same, but something is causing the problem.

 

Code_Breaker

 

 

[Teh Bear without Brains kinda idiot]

Are you OK when you turn your filter off completly ?

[Code_Breaker]

no, I still gets the warning. I used limits that had arcs. But, I changed it to all lines, filter off and it still gave me arcs in the toolpath and the error message.

 

Code_Breaker

[cadist]

code_breaker, we used to get that error in version 9 all the time but it went off in 9.1sp2. I know you must be having 9.1sp2 but has it happened for the first time or earlier also.

Have you ever tested your program in controller's test run? In our case illeagle arc always worked fine on machine.

[gcode]

Don,

make sure you are using the newest MP.DLL. (v9.18)

You can download it from the patches page here.

[cadist]

Illeagle arc warning.

HTH

[Teh Bear without Brains kinda idiot]

Code_Breaker.

 

Do not want to sound like dumbA&& but I personally would use surface->contour ,far too better .

 

Talking `bout Ur probs I would like to see your file !

Can you put it on ftp .

+1000 to Cadist ,I saw this thing before SP2 too

[Code_Breaker]

Winnie,

 

As posted ealier, that's what I did, but just to see this problem get solved.

 

Tom,

 

My MP.dll file version is 9.1.9.19

 

Code_Breaker

[foolsh]

do not use mp.dll ver 9.19,i used it,and it caused a big overcut on my closed chain 2D contour.when i downgrade to mp.dll ver 9.16,everthing's ok

[Mick]

foolsh,

 

Can you put the file you had the big overcut on, up to the FTP? I just upgraded to MP 9.19 and it seems to work ok. I'd like to see if I could replicate the error.

The posted code worked fine.

 

Cheers

[foolsh]

but the funny thing is it could not be seen on backplot or verify,but caught on vericut

[Teh Bear without Brains kinda idiot]

Illegal arc can be thing like this :

if your start point ,end poin and center of the

arc are on one line and in this order :start point ,end point and center or end point ,start point and center .

What can cause it - a loop .

Check your geometry :

analize surfaces for internal sharp corners ,overcrossing and look for very little surfaces .

Check your check boundary for overlapping entities and gaps

If you created spline and use it for check boundary and there were gaps or overlapping entities you have prelly good chanses to happen this .

or if the chain was not closed and you add the tolerance for not closed chain in chain options .

IOW ,check good your geometry !

also ,look for points in check boundaries geometry

HTH

WTHH

[crazy^millman]

I have found file size leads to this as well. Take the question geomety and do a save as. Then try to do the toolpath again and see if it makes a difference.

[Teh Bear without Brains kinda idiot]

+1000 but ...

Ron ,this is not a file size ,that`s because when save as saves your geometry ,it writes the brand new database ,and this can be related .

The same result you can achieve with Ramsaver command .

 

Your humble servant

WTP ,bearwolf

[foolsh]

to Mick,

i have downloaded a file named contourovercut.you can post and try on your machine to see whether there is the overcut!