Advanced Search

gsoft2 is great for config, I'm just using FOR and REV commands. I tried to work out the pulse train on the gs20, but it wants 24v pulses and the mesa hardware I have requires um more electronics skill then I have. I considered using the 15 preset frequency via the DI3-6, but got the analog out card working so I think just a basic PID will do all I need.

I would call it a Preempt-rt kernel bug since the r8169 driver is a FOSS kernel driver
that fails in RT environments. Unfortunately it looks like very little if any RT work has been
done on network drivers (looking at the RT patches)

It looks like the main driver related RT patches are for video drivers...

EDIT Nov. 3 2024. THERE IS A WIRING ERROR IN THE PICTURE BELOW. THE OE LINE NEEDS TO BE CONNECTED TO 3.3V OR AN OUTPUT. WILL CORRECT THE DRAWING AND UPLOAD AGAIN ONCE TESTED.
This one is actually how I want to connect the joints. I have a total of 4 joints (dual Y axis motor), but only draw joint 1 and 2 for the moment.

 

BaxEDM wrote:

Ah yes! After switching off EEE and aspm, I ran the machine for over 3 hours straight without encountering any servo following errors. I captured everything I did in order to do a full problem free installation in this procedure for my customers, this might be useful for others as well:

baxedm.com/linuxcnc-installation-for-edm...-on-linux-debian-12/
 

Nuce writeup. I hope you don't mind but I added it to my Debian 12 document
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

Ok, so do I have the wrong W5500? I was planning to use it like in the attached picture.

Lcvette wrote:

PCW wrote:

Lcvette wrote:

@PCW who would be the person group best suited to fixing it, and do they know about it? is this a linuxcnc thing or a debian thing?
 
Honestly its a Linux thing (broken driver) but would be easier to fix in a non debian compliant ISO
Ultimately it should get fixed in the kernel driver so the proprietary Realtek driver is not needed.

Interesting, would it help the intel adapter performance as well? bring it back to the 4.9 kernel day performance?  i miss those days...lol

I don't think this is a kernel bug but related to some decisions made with the kernel inclusions for realtek NIC drivers. The R8169 driver is a generic NIC driver for the Realtek cards but it fails in a Real Time environment on the R8168/R8111 hardware (And also the Realtek R8125 driver). I suspect it is related to restrictions on the code licencing of Realtek binaries  and FOSS.

Pre kernel 5.10 (Bullseye), you had to download the driver sources from Realtek and build your own driver but this was kernel specific. Users of the Odroid H2+ will remember having to compile the R8125 driver. It was hard to find a working version for your kernel. Somewhere around kernel 5.9, I think the  Realtek code was separated into different drivers and the R8169 was included in the kernel. But the non-FOSS code from Realtek was separated out into DKMS driver modules. DKMS allows kernel modules to be distributed in source code and built for a specific kernel automatically. This  is recompiled if you upgrade your kernel.

So here is the problem. the R8168_dkms driver is not part of the kernel so its not considered a kernel bug. the RT project does not see it as part of their remit as a driver is available.

I have tried reporting Bugs with Debian and the RT kernel team but it is exhausting and non productive so I gave up.

It does get a bit worse as because the R8168_dkms driver not a kernel module, the dkms driver is not included in the Debian non-free-firmware module so your sources.list specifically still requires the non-free module. (We add this for you in the Linuxcnc ISO).

Can you post the .pnconf file that causes the error?

@rodw, mb2hal also works with TCP/IP:
 

 

linuxcnc.org/docs/html/gui/gladevcp.html

Isn't MB2hal require a  RS485  connection (serial port)? In that case, you need a RS485 port (like a USB to RS485 interface) 
Ethercat master requires a network port
These two interfaces are totally different