Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Creator
Creator

Hello,

 

have the same problem with Heidenhain.

I changed the parameter MP7431to 0,01mm in the machine parameter.

It is the arc end-point tolerance and default setting is 0,005mm.

Have not tested it if it´s better now!

 

Kind regards,

Martin

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

hello,

is there any update on this topic?

 

Ive seen comments about circle end point but "radius too large" is something different.

Radius to large:

Ive tried cycle32, M120 LA ... no efect. Still get error.

 

still any idea how to fix it?

 

thank you

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Hi, 

 

Any update on this topic? 

 

I get the same problems in some customers. 

 

Best Regards

Ivan

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

I am facing now this problem quite often.

It is not about only circles in the code.

It is happend when ou are using RR/RL cutcom on path with multiple smaller lines or cicles.

For the first time I met this problem with machning shape like wing profile and then in simple opened cavity.

Our heidenhan "JEDI" tell us to use M120 LA3 - but it helps only in few cases.

Somebody tolds me that they never get such error with solidcam.

 

I will do more tests but I get it in floor wall and cavity mill operation.

I am trying to find some nx setting like tighter tolerance or tolerance only outtol not intol, etc....

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Valued Contributor
Valued Contributor

When I'm using contact counter I try to use ZLevel Profile, I seem to get less errors with this operation.

It don't happens to often anymore, but when it does I use the smooth corner option. 

When the error occoures because the radius is to small you get a sharp corner, you have to use a smaller tool or you can set the smooth corner option to 0,1mm.

If it occures because of a profile thats not "clean" and you get sharp connections you also can solve that with the smooth corner option.

 

image.png

 

I also tried differend tollerances and more decimals but my experience is that this is not a solution that always get's a good result.

Its mostly becausee there is a sharp connection in the profile or the mill you're trying to use is to large.

Both of the problems can be solved with corner smoothing.

 


Regards,
Sven

NX11.0.1

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Creator
Creator

Since I changed the Machine setting it works really fine.

The only thing I have to take care is, if I use cutcom on the min angle must be 90°.

Cutcom_setting.PNG

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

I suppose this angle setting is for engage cutcom only , it change only engage angle or cutcom length in engage move. It doesnt change character of the path.

Our problem is in the middle of the cutting paths where are tiny linear/circular moves exists.

 

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

I'm wondering if any of you get this errors when "Output Contact/Tracking Data" option is turned off? I mean still with cutter compensation active, but compensating only tool wear?

 

Marek Pawlus, NCmatic

Development: C#, Tcl/Tk, CSE

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

Maybe we will test it, but you have to have  zero tool radius in machine tool table.

But it also means no real simulation on the machine

Machine has ability to have radius defined so most of customers use it.

So workaround with no output contact tracking data is not usable (if even it will works).

 

I am preparing to send it to gtac as soon as I will have nc code and to be sure it is not working.

But I am skeptical of this.

 

---------------------------------------------
#♫ PB, 5ax, itnc, nx, vericut ♫ #

Re: Tool radius too large (Postprocessor / Heidenhain / contact counter)

Legend
Legend

Hi, Juraj!
Have you solved this problem? A year passed after your last message.
I met the same thing working with iTNC640. Only "M120 LA3" helped me in my Z-level operations.

Learn online





Solution Information