Ok, you have an Intel NIC. That is good!. For ethercat, just use the generic driver.
4.19 is buster and I've never used it. You could adapt the how to and getting linuxcnc doc to Buster by changing a few settings.
Everything I have set up recently has been around Bookworm. A couple of guys I know have got Bookworm working with Mesa devices on 2 core machines with the 6.3 kernel. You probably should add the coalescing settings as shown in man hm2_eth. But ethercat is much more efficient so it performs better than the protocols Mesa use so it might not be necessary.
The other thing you could try is IRQ pinning and pin the NIC interrupt to the one Linuxcnc uses (likely the isolated core) You will hhave to google that but the theory is that if both the servo thread (and perhaps the ethercat master too) and NIC are all on the same core, it will be more efficient
I think your i5 will be fine. I have a i3 that works pretty welll once optimised even with a crappy Realtek NIC.
Hi rod,
there should be some more problems with hooking up of bookworm on the machine with 2 cores ? I tested your hybrid.iso but on my vbox machine with single core it was installed at first shot and ethercat master works ... but there was problem with
For benchtop searching project of controlling servos over ethercat I am still struggling around which hardware should be better for me... Should be better some tiny mini PC from some famous brand as
- Lenovo ThinkCentre M93p Tiny with Intel Core i5-4570T with One gigabit ethernet port, Intel I217-LM (Clarkville)
or
- Rb Pi 4 - b 8GB RAM
I think for digging and struglining around the development a solution for prototype machine should be better that tiny one lenovo with i5 CPU on board but what with Intel I217-LM hardware ... it looks like, it will have e1000 driver or something similar what I read just
here
