Advanced Search

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

I did find those files in lib/python3/dist-packages/gladevcp

Yes, those are the files you need to edit.

Over the last year I have been building a gantry plasma table with leadshine el8 servos and Beckhoff modules for I/O, I struggle a lot with software but have managed to get the motion going and calibrated in the axis interface following the guide below, the config files that worked are also below in a zip file.
The thing I need help with is how to integrate all of this into QtPlasmaC and how to map the I/O of the Beckhoff modules into the software.

I have a EK1100 coupler, an EL1008 digital input, an EL2008 digital output and EL3102 analog input to read the divided arc voltage.

Can anybody give any help, or tips on how to do this?
 

 I was out on a business trip this week and only just got to try this. I don't have a lib/python/gladevcp folder.

I did find those files in lib/python3/dist-packages/gladevcp. Would it help to edit them there, or should I leave those versions alone and look for them somewhere else?
Cheers,
Mark