Question about rotary toolpath display.

Ah, OK, Thanks.
I will try this .

Update - the AXYZ configuration works, but now have the following bug: When open G code and the machine is set in zero machine coordinate, everything looks fine. When do touchoff and set G54 or G55 or other user specified position, the visualisation of the toolpath start deforming. Like a sample, the ring with 30mm diameter looks like a ring with 120mm diameter. I tried AXYZ, XAYZ and XYAZ, always the same result.

Any solutions this?
Hello all, I have the same issue "the visualisation of the toolpath start deforming".It happens when we works in non-zero absolute coordinates, but I think the physical aspect works fine: this issue appears only on visualisation window.

Sorry, no, that is just the way it is. The graphical preview has no way to know where the centre of rotation is relative to your work coordinate system. (Literally no way, this is not an easy thing to fix)

Anyway to define the rotation axis of the displayed tool cone? A least it should be possible to define it in G54 abs coordinates? in my setup the axis for A is parallel to x (ok) but shifted to z=limit_z > 0 which is weird. I would expect rotation about local (y,z)=0, respecting G92 offsets.

master branch:

> 9. Rotations are by default applied with respect to the machine
> origin. Example: GEOMETRY=CXYZ first translates the control
> point to X,Y,Z and then performs a C rotation about the Z
> axis centered at the machine origin.
>
> 10. Rotations applied after translations may use the "!"
> provision to to act with respect to the current machine
> offset. Example: GEOMETRY=!CXYZ translates the control point
> to the X,Y,Z position and then performs a C rotation about
> the machine origin displaced by the current G5x,G92 X,Y,Z
offsets. (Changing offsets may require a program reload).


Ref:
linuxcnc.org/docs/devel/html/config/ini-...tml#_display_section

I wonder how much work it would be to also allow a "magic comment" in the G-code to define the rotation axis?

(ROTATION, 10 20 30)

Or something.

The issue is propagating that info into the preview, I would imagine.