G Code Generation for Camshaft grinding

I would set the spindle axis as axis A and the axis of the grinding wheel as axis Y

Well at the end it is not that important which axis name I give the individual axis
whether I call it A, X or Y.

The G33 can only synchronize movements between a spindle (S) and any other axis.
But a spindle has some limitations (e.g. move to position and hold), so the G33 does not really work

I think that coordinated moves in angular and linear axes is probably the way to go, and you probably do want to configure the rotary axis as the Y, as this should allow the trajectory planner to blend it.

Which version of LinuxCNC are you using? 2.7 should bland the moves rather better than the previous versions.

Hi,

Currently I'm using 2.7.9. I updated recently from 2.7.5.
With this update I did not notice any increase in performance.

Currently I'm configured two linear axes. Do you expect any better performance if the rotary axis is configured as a rotary axis?

TobiasKa wrote: Currently I'm configured two linear axes. Do you expect any better performance if the rotary axis is configured as a rotary axis?

No, I would expect worse performance with a rotary axis as the path-blending in angular-linear moves uses a single segment lookahead whilst linear-linear uses a many-segment lookahead.

Do you know if your axis acceleration limits programmed for the axes are anywhere near the physical/mechanical limits?

Ok, so I will stay with the "double linear" configuration.

I tried several acceleration values for the linear axis.
There I have not seen any improvement nor deterioration.

I have looked through the documentation, but I have not found any detailed information how the acceleration values are taken into account during a synchronized G01 movement.

Anyway I have just wrote down how I calculated the desired velocity of the system:


Maybe someone can point out where the flaw is in the calculation process?