Cutter Radius Compensation Warning

[Titaniumboy]

Hello,

I received the following message when loading a GCode program that I generated in Solidworks CAM (CamWorks).

Warn code 2: Approach angle too low. angle < 180 deg. On row: 8

I’m not sure where to find Row 8? The program seems to run without any obvious problems observed during machining.

Thanks for any help.

Titaniumboy


P.S. How do I upload files in a message? I have been unsuccessful in attempts to upload both xml and txt files. I get a notice from the forum that says "The upload was rejected because the uploaded file was identified as a possible attack vector."

[dezsoe]

Row 8 is line 8. Check your g-code. (Note: the line numbers begin with 0 in UCCNC.)

(You can upload txt files. XML is not used by UCCNC.)

[Titaniumboy]

Thank you for your help.

My line 9 (your Row 8) is G17 X0 F13.7615. No G41 in sight.

This part of the program (about 480 lines) was running perfect and contained no G41 cutter comp. The Cutter Radius Compensation Warning only started being displayed when I added gcode past the original 480 line program. This added gcode was the first code that utilized G41 cutter comp in my program.

This is why the Row 8 location confused me. I would have thought the error would be somewhere higher than line 480 since that is where the first G41 cutter comp code shows up in my program.

Titaniumboy

[dezsoe]

When you start the cycle is G40 active? Maybe the compensation is already on when you start.

[Philippe Allemant]

When you start the cycle is G40 active? Maybe the compensation is already on when you start.

Hi there,

I have the exact same error, 'angle approach too low at row xx' , line number may vary but never makes sense, usually a line with no radius comp being called at all(got one with line saying : G90 G0 X14.55 Y-0.6)

Made sure G40 was active when loading the code into uccnc, that doesn't change anything, and you can type g40 in mdi console all day, close and reload the code, the error still appears, and always with a goofy line number(the code does indeed have radius comp called at some point, but not at such lines, ofc).At this point I don't know what causes this and it sure looks like a bug.

Besides, radius comp seems globally buggy on my end, I don't know if there is any workaround but if I choose 'In control' (this is when you have to type the actual diameter of the tool in tooltable, the cam soft generates an exact centered toolpath)in Hsmworks the uccnc controller gauges the part 50% of the time, usually in lead ins/ends of the tool in material, as it then deviates from the tool path drastically.Using 'Wear' seems to be safer(with wear the cam compensates the toolpath with a set diameter for tool but stiil outputs G41/42 commands for you to use, you input '0' in tooltable as a diameter and can then later input say for example '-0.1' to decrease diameter by 0.1mm). Problem and gauging is the same in 1.2111 and 1.2113.

What Am I missing?