Advanced Search

The Pi4b was marginal, sometimes requiring a slower servo thread but one guy I know says the Pi5 is flawless on real machines
I'd probably pair it with a mesa ethernet card. A Mesa 7i76eU has 5 axes, 16 outputs and 32 inputs but is extensible beyond that.
Linuxcnc supports 9 axes and 32 motors
Arduino is not useful for linuxcnc
There are several GUIs that support lathes but its always best to start with axis until you get everything functional.
Of course we are friendly!
You can mess with everything!
Check the docs as they list the GUI's available but you can write your own. Some support portrait mode.
I checked the other day, there's is over 1800 pages of docs but I always refer to the online docs.
There are no limits to motor size and it will control Ethercat and analog servo motors not just step and direction.
Linuxcnc is far more flexible than Centroid and is complete as opposed to Centroid where additional upgrades are required.
But it may require more effort from you  because there are probably more decisions you need to make becsause of LinuxCNC's flexibility

Re Youtube not sure on Lathe specific videos but I have a channel which is trying to produce tutorial type material.
This one is designed to be a general introduction describing the various pathways through Linuxcnc 

I'm currently working through a series of videos building a control panel from scratch using a parallel port (3rd one to be released tonight) with a couple more planned. Once fully functional, my plan was to replace the parallel port with other controller options. Sounds like I need to include a lathe walkthrough too!



 

easisest way would be to create seperate configs for each option

What is "the auto tool probe remap"? I mean I know what remap is in general, but it sounds like it is a name of something specific. Is it something one can download from somewhere? A quick googling didn't come back with anything specific.

In the meantime I studied the documentation and the source code a little bit, and I think I now have a clue what's what, and there are multiple ways to achieve tool offsets (G10 L2 vs. G10 L20 for instance). What I was looking for was a simple way and a sequence of click here, enter there kind of set of instructions.

I eventually managed to make the standard tool touchup work. The one where you enter the the tool height in the settings tab, enter the workpiece height in the offsets panel on the main screen, and you just click on the tool sensor button, which will calculate the Z value for the current WCS and sets it with G10 L20 (after touching the sensor with the loaded tool).

Tried again and now thinking some kind of network error.  Will try again later.

Seems likely since that was common on 2 pc's....Did not try live yet...found another hard drive..Thanks!

Not at shop now but pretty sure it is read only...message shows while still running gcode..seems triggered when I pause and change an axis touch off....after a little while all communication stops have to restart..have everything now on a different pc as well as different hard drive (not ssd) only ran for an hour or so.. seemed ok..will check again tomorrow...Actually I got the read only when running the dmesg many times in terminal...that should have nothing to do with mesa right?...so looks like bad ssd...unless I get a surprise tomorrow...i will have to see how to check power supply to mesa I guess...Thanks all for your help!!...this kind of stuff always seems to come when deadline pressures are in play..

Someone with experience in Debian Linux admin probably knows what this means and how to fix it.  Sadly that's not me.

Installed LinuxCNC on a plasma table a few months ago.  Been a few weeks since I had it on due to travel.  Tried to do a package update today and got the following:

Notice: Repository 'xxxxxxxdeb.debian.org/debian trixie InRelease' changed its 'Version' value from '13.5' to '13.6'
Error: The repository 'xxxxxxxrepository.qtpyvcp.com/apt develop Release' no longer has a Release file.

Guessing it's something simple?  Machine works but I like to keep things updated so would like to resolve it.

Thanks! 

-Dave

cnc@linuxCNC:~/Desktop/test_plasma_1$ uname -a Linux linuxCNC 6.12.86+deb13-rt-amd64 #1 SMP PREEMPT_RT Debian 6.12.86-1 (2026-05-08) x86_64 GNU/Linux 
 

PCW wrote:

"Error finishing read" on Mesa Ethernet hardware indicates too many timeouts waiting for returned read data.

Most commonly caused by excess network latency.
 

I got "Error finishing read" even after few hours of stable work without any latency.
I don't know why, but the problem is in kernel version and/or network card driver.
 

Nice, thank you.

"Error finishing read" on Mesa Ethernet hardware indicates too many timeouts waiting for returned read data.

Most commonly caused by excess network latency.

RLA wrote:

Just went to run dmesg again....after it finished...stretched terminal window...went blank...opened new terminal fullof read only errors??

SSD's will do that when they are failing.
Did you try booting from usb?

PCW wrote:

(which indicate network latency issues)
 

This indicate break connection, not latency issues.

By read only errors did you mean "error finishing read" errors
(which indicate network latency issues)

Thanks a lot, that is now working as it should.
Cheers,
Mark

in case anyone is curious, have some cad and pictures 
ignore the messy home shop