Radius compensation?

[ger21]

What Josef posted is not an incorrect path, it is the correct path with the algorithm of how G41/G42 has to work, it is not a bug of Mach3.

Then maybe the algorithm is flawed? I'd like to see the code that produces that error.

Can't you check the comp when the g-code is loaded, looking as far ahead as you need to? If it takes time, give the user the option to enable or disable check for errors when loading.

Sorry, but I've been using comp for 20 years and have not seen the issues that you are bringing up.

[ger21]

They just want to make parts not work on CNC machines.

In my world, G41/G42 makes it faster and easier to make parts.

I find the workflow of many people today to be very inefficient. Mainly because they don't know that there are faster and better ways to do things.

[cncdrive]

In my world, G41/G42 makes it faster and easier to make parts.

I find the workflow of many people today to be very inefficient. Mainly because they don't know that there are faster and better ways to do things.

Yes, it is faster to create a path offset with G41/G42 that's for sure, but it has it's limitations/downsides while CAMs can do it much better in most of the cases, because they doing the calculation a totally different way but the process is then slower.

[ger21]

At home I use an AutoCAD macro that I wrote that adds the G41/G42.
Here at work I use AlphaCAM.
Someone posted a trick yesterday on how to get V-Carve Pro or Aspire to do it.

We don't sharpen our own tooling, but have a sharpening service pick up our tooling every week.
And for router use, tolerances aren't so critical. We don't really notice if we're off .003-.004.
But my 0.5" tooling varies from about .45-.50, which does make a big difference. Especially when I run jobs that were programmed 3-4 years ago.