Advanced Search

That is because the PP uses G18 to rotate the coordinate system for milling.
Have you tried setting the rotational axis to Z as suggested here:
forum.linuxcnc.org/10-advanced-configura...hine?start=50#327942

The underlying problem is that linuxcnc applies the x-,y-z- tool-offsets internally, so the tool-length is automatically subtracted from the Z position shown in the DRO. That is why the kinematic model for milling has the tool spindle pointing in the negative machine Z direction and the model for turning has it pointing in the negative X direction.
While it might be possible to remove the tool-offset as linuxcnc applies them and add them to different axes in the kinematic I'm rather skeptical that it is worth the effort.
You need to remember that the planner currently has no information about the custom kinematic used, neither does the preview. The nice thing about TWP is that you can load any G17 XYZ milling toolpath and it will be displayed correctly in the screen.
Generally speaking limit violation checking and tool path preview will only be of limited use for more complex kinematics.

Note though that limit values can be changed when changing kinematic modes. For an example see:
github.com/LinuxCNC/linuxcnc/tree/master...xis/vismach/millturn

The actual values are changed using executable Mcodes:
github.com/LinuxCNC/linuxcnc/tree/master...mach/millturn/mcodes

Thanks for your interest! I made several modifications to qt_auto_probe_tool.ngc to improve tool length offset management and work coordinate independence.

Changes Made:
Separated tool length offset (G43) from work coordinate systems (G54/G55), making the tool table more intuitive.

The probe height was defined in machine coordinates and probed at the tip of the spindle.

Ensured tool length offset remains consistent regardless of WCS changes.

Thanks!

Hi all,

It’s been (far) too long since I last had time for CNC projects. Fortunately, things have settled down a bit lately, and I’ve been able to pick up the hobby again. However, getting my machine up and running has proven to be more of a challenge than expected.

My old Intel setup (with a 4790K) had both a faulty motherboard and RAM, so I replaced it with an ASUS AM4 board and a Ryzen 5600 CPU. Since then, I've been struggling with what seems to be very high latency.

To make matters worse, I used to run LinuxCNC 2.4, but I’ve now reinstalled everything using the latest stock ISO (2.9 with the PREEMPT-RT kernel). Unfortunately, this means my old configuration is no longer compatible.

I’ve uploaded my current settings, including the BIOS changes I’ve made in an attempt to reduce latency. At this point, my first goal is simply to get the axes moving at a reasonable rate. Right now, I can’t get it to move faster than about 1 mm/sec (rough estimate) before I run into either a joint 0 following error or an error about the base thread timing.

If anyone has tips or suggestions based on my setup or config files, I’d really appreciate the help. The machine used to run at a speed much faster than the tool could handle, so I know it's capable — I just need to get the configuration right again.

I’m aware that my .hal and .ini files likely need significant changes. I've done my best to port over the old configuration, but clearly, it’s not quite there yet.

Thanks in advance for any insights or advice!

The images are from 1 to 12, replace the number in the URL. I cant post that many links
www.doingcode.nl/images/linuxcnc/1.jpg

Hello Aciera,

i spend more time with it and found one more challenge.

While working with TWP i saw a problem, that it does twist the workplane perfectly but it also changes the axis definition.

Z Integrex is becoming X (Conventional)
X Integrex is becoming Z (Conventional)

Y stays Y

While this behavior can be surely handled in the PP, its a bit of a mess in LCNC. Soft limits are fairly difficult to define and in AXIS GUI it also looks a bit messy. The Doosan PP also does not change Z/X definition, when G368 is posted. And of course the key binding is also off in TWP mode.

The question is now: Can G68 keep the original Integrex Axis definitions ?