Advanced Search

No gigabit is not required, the mesa boards do not support this speed.
As no based thread is required jitter is not a major issue, under 100000ns will work.

Stop overthinking.
With mesa hardware you don't need a base thread, only a servo thread is required. With that, latency isn't such a huge issue either. Trying to get an extra bit here and there does nothing.
The pre made image Rodw recently linked to is perfectly fine to run a machine, the only exception would be if you are using the RPi 5 spi interface to talk to a 7c81 or 7c80 as this requires a driver that isn't included in Rods image , this is not required for ethernet.
Invest more into learning the ins and outs of hal . This is more important that fussing over software as the images provide what is required, remember the only task these images are meant for is running a CNC machine.
If one reads the online docs one will fine some simple exercises that do not require a CNC machine.

Dear jjdege.
How can you solve the error when you install the ethercat package by command "sudo apt install -y linux-headers-(uname -r) ethercat-master linuxcnc-ethercat?

I think we would have to add the motion color into the plot point.
(qt_mismach.py line 287 ish)

Dear jjdege.
How can you solve the error when you install the ethercat package by command "sudo apt install -y linux-headers-(uname -r) ethercat-master linuxcnc-ethercat?

Good day! Tell me, is a gigabit port absolutely necessary or is 100Mb enough? How important are the jitter readings in the test?

I read your post and it took a while to sink in how well running the native RaspianOS with the 6.12 kernel for what I want to accomplish.  I'm guessing that 6.12+ might be a real game changer across the board but I remember discussions about certain run-time flags being used to determine if PREEMPT_RT was part of the build and people commented that some don't match up yet.

Do you think that might be a hurdle in the short / mid  term?

Do you think someone familiar with the run-time testing code might already be working on a fix to any of those problems?

Ok, I decided to complete a complete re-installation and work from clean. However getting the following:

abcabc@192-168-1-???:~$ apt --fix-broken install
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
I definitely did not put a root password in. So ideas?

Ok, sorted ran sudo apt --fix-broken install

That's awesome - as always!

I've already starting to dig through it.