LinuxCNC on Raspberry Pi 5
16 Jan 2024 08:09 - 16 Jan 2024 08:10 #290838
by Jiyar
Replied by Jiyar on topic LinuxCNC on Raspberry Pi 5
Hi,
Here is a YouTube link that may be useful.
Here is a YouTube link that may be useful.
Last edit: 16 Jan 2024 08:10 by Jiyar.
Please Log in or Create an account to join the conversation.
22 Jan 2024 20:04 - 22 Jan 2024 20:05 #291364
by acondit
Replied by acondit on topic LinuxCNC on Raspberry Pi 5
I found a sweet spot for a moment. github/raspberrypi/linux rpi-6.6.y was at 6.6.12 (rpi-6.6.y is now at 6.6.13). I used patch-6.6.12-rt20.patch.xz The patch applied with no problems.
uname -a
Linux RaspberryPi5-1 6.6.12-rt20-v8-16k+ #2 SMP PREEMPT_RT Mon Jan 22 08:35:10 CST 2024 aarch64 GNU/Linux
I haven't done any testing yet. If it looks good I will try to create a release for the .debs on github.
uname -a
Linux RaspberryPi5-1 6.6.12-rt20-v8-16k+ #2 SMP PREEMPT_RT Mon Jan 22 08:35:10 CST 2024 aarch64 GNU/Linux
I haven't done any testing yet. If it looks good I will try to create a release for the .debs on github.
Last edit: 22 Jan 2024 20:05 by acondit. Reason: correct a run together line
Please Log in or Create an account to join the conversation.
12 Feb 2024 04:41 - 13 Feb 2024 23:35 #293125
by RNZ
Replied by RNZ on topic LinuxCNC on Raspberry Pi 5
I now have a RPi 5 8 GB model and Mesa 7i96S card. I have downloaded and installed onto a 32 GB micro SD card "LinuxCNC 2.9.2 Raspberry Pi 5 OS based on Debian Bookworm Raspberry Pi 5 Uspace compatible with Mesa Ethernet and SPI interface boards."
I have the Pi (10.10.10.1) talking over ethernet to 7i96S (10.10.10.10) following a W5 jumper change on 7i96S and Linux command:
sudo ip address add 10.10.10.1/24 dev eth0 /* this will work but DON'T USE THIS as it will not persist after a reboot */
ping 10.10.10.10
To ensure the settings persist after a reboot, AND noting that Linux networking commands seem to have recently changed, the following works:
nmcli con show /* this will show the RPi 5 wireless and wired "ethernet" connections, and the NAME e.g. "Wired connection 1" for TYPE "ethernet" */
sudo nmcli con mod "Wired connection 1" ipv4.addresses 10.10.10.1/24 /* dunno where this gets saved in RPi OS */
Test if persistent by rebooting, then typing again:
nmcli con show /* DEVICE should now = "eth0" */
ping 10.10.10.10 /* ping the Mesa 7i96 card -- I get a ping time of 30-40 us */
This editor is ghastly
I have the Pi (10.10.10.1) talking over ethernet to 7i96S (10.10.10.10) following a W5 jumper change on 7i96S and Linux command:
sudo ip address add 10.10.10.1/24 dev eth0 /* this will work but DON'T USE THIS as it will not persist after a reboot */
ping 10.10.10.10
To ensure the settings persist after a reboot, AND noting that Linux networking commands seem to have recently changed, the following works:
nmcli con show /* this will show the RPi 5 wireless and wired "ethernet" connections, and the NAME e.g. "Wired connection 1" for TYPE "ethernet" */
sudo nmcli con mod "Wired connection 1" ipv4.addresses 10.10.10.1/24 /* dunno where this gets saved in RPi OS */
Test if persistent by rebooting, then typing again:
nmcli con show /* DEVICE should now = "eth0" */
ping 10.10.10.10 /* ping the Mesa 7i96 card -- I get a ping time of 30-40 us */
This editor is ghastly
![:-( :-(](/media/kunena/emoticons/sad.png)
Last edit: 13 Feb 2024 23:35 by RNZ.
The following user(s) said Thank You: flyingbrick
Please Log in or Create an account to join the conversation.
- flyingbrick
- Offline
- Junior Member
-
Less
More
- Posts: 30
- Thank you received: 11
13 Feb 2024 05:08 #293195
by flyingbrick
Replied by flyingbrick on topic LinuxCNC on Raspberry Pi 5
Yup, I find it kinda funny that a site catering to technology uses such a terrible editor :-D
I have used a lot of forums but never seen one this bad :-D
If it wasn't for the great people here it'd just be too painful hahahah.
I have used a lot of forums but never seen one this bad :-D
If it wasn't for the great people here it'd just be too painful hahahah.
The following user(s) said Thank You: RNZ
Please Log in or Create an account to join the conversation.
13 Feb 2024 09:24 - 13 Feb 2024 09:25 #293207
by RNZ
Replied by RNZ on topic LinuxCNC on Raspberry Pi 5
The good news is that the RPi and Mesa 7i96s are communicating and appeared to be doing so reliably using the Dragon GUI until a string of these messages appeared:
hm2/hm2_7i92.0: error queuing read! iter=xxx
hm2/hm2_7i92.0: error finishing write! iter=xxx
If I run the following, there appears to be dropped packets:
sudo chrt 99 ping -i .001 -q 10.10.10.10 /* forum.linuxcnc.org/27-driver-boards/4837...rite?start=20#266420 */
About 25% were dropped when using a 30 cm CAT cable (not sure what type, shown in photo above). Changing to a longer CAT 5e cable resulted in a tiny percentage of dropped packets. Nevertheless, the errors keep appearing when running Dragon GUI -- I'm not suggesting that Dragon GUI is the issue here.
hm2/hm2_7i92.0: error queuing read! iter=xxx
hm2/hm2_7i92.0: error finishing write! iter=xxx
If I run the following, there appears to be dropped packets:
sudo chrt 99 ping -i .001 -q 10.10.10.10 /* forum.linuxcnc.org/27-driver-boards/4837...rite?start=20#266420 */
About 25% were dropped when using a 30 cm CAT cable (not sure what type, shown in photo above). Changing to a longer CAT 5e cable resulted in a tiny percentage of dropped packets. Nevertheless, the errors keep appearing when running Dragon GUI -- I'm not suggesting that Dragon GUI is the issue here.
Last edit: 13 Feb 2024 09:25 by RNZ.
Please Log in or Create an account to join the conversation.
13 Feb 2024 09:28 #293208
by rodw
Replied by rodw on topic LinuxCNC on Raspberry Pi 5
Its a hardware issue. please read my tutorial here
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing
The following user(s) said Thank You: RNZ
Please Log in or Create an account to join the conversation.
13 Feb 2024 09:39 #293209
by RNZ
Replied by RNZ on topic LinuxCNC on Raspberry Pi 5
Thanks, I will give that a try tomorrow and report back.
Please Log in or Create an account to join the conversation.
13 Feb 2024 09:56 #293211
by RNZ
Replied by RNZ on topic LinuxCNC on Raspberry Pi 5
Hey Richie, how did you go with the RPi 5? I have the same + Mesa 7i96s in Blenheim…
Please Log in or Create an account to join the conversation.
13 Feb 2024 23:33 - 15 Feb 2024 01:03 #293277
by RNZ
Replied by RNZ on topic LinuxCNC on Raspberry Pi 5
Running this on RPi 5 8 GB with Mesa 7i96s:
latency-histogram --nobase --sbinsize 1000
With essentially no load on the Pi, have after about 400 seconds:
min (us) = -18.8
max (us) = 19.2
sdev (us) = 0.9
With 1x Glxgears, after about 80 seconds:
min (us) = -16.6
max (us) = 14.5
sdev (us) = 0.9
With 2x Glxgears, after about 80 seconds:
min (us) = -20.4
max (us) = 15.2
sdev (us) = 1.6
With 3x Glxgears, after about 80 seconds:
min (us) = -18.6
max (us) = 16.5
sdev (us) = 2.2
With 4x Glxgears, after about 80 seconds:
min (us) = -17.2
max (us) = 18.3
sdev (us) = 2.6
With 5x Glxgears, after about 80 seconds:
min (us) = -21.6
max (us) = 20.6
sdev (us) = 3.0
With 6x Glxgears, after about 80 seconds:
min (us) = -16.5
max (us) = 18.1
sdev (us) = 3.1
With 10x Glxgears, after about 80 seconds:
min (us) = -23.8
max (us) = 16.6
sdev (us) = 3.5
Seems that the 7i96s ethernet connection to the Pi has died again during these tests.
======================
Repeating the 10 gears version on HP i5 8100 Elite SFF x86_64 6.1.0-13-rt-amd64 2.9.1 3.6 GHz
With 10x Glxgears, after about 200 seconds:
(1000 us servo thread)
min (us) = -80.8
max (us) = 79.3
sdev (us) = 1.5
(25 us base thread)
min (us) = -24.9
max (us) = 42.4
sdev (us) = 0.8
latency-histogram --nobase --sbinsize 1000
With essentially no load on the Pi, have after about 400 seconds:
min (us) = -18.8
max (us) = 19.2
sdev (us) = 0.9
With 1x Glxgears, after about 80 seconds:
min (us) = -16.6
max (us) = 14.5
sdev (us) = 0.9
With 2x Glxgears, after about 80 seconds:
min (us) = -20.4
max (us) = 15.2
sdev (us) = 1.6
With 3x Glxgears, after about 80 seconds:
min (us) = -18.6
max (us) = 16.5
sdev (us) = 2.2
With 4x Glxgears, after about 80 seconds:
min (us) = -17.2
max (us) = 18.3
sdev (us) = 2.6
With 5x Glxgears, after about 80 seconds:
min (us) = -21.6
max (us) = 20.6
sdev (us) = 3.0
With 6x Glxgears, after about 80 seconds:
min (us) = -16.5
max (us) = 18.1
sdev (us) = 3.1
With 10x Glxgears, after about 80 seconds:
min (us) = -23.8
max (us) = 16.6
sdev (us) = 3.5
Seems that the 7i96s ethernet connection to the Pi has died again during these tests.
======================
Repeating the 10 gears version on HP i5 8100 Elite SFF x86_64 6.1.0-13-rt-amd64 2.9.1 3.6 GHz
With 10x Glxgears, after about 200 seconds:
(1000 us servo thread)
min (us) = -80.8
max (us) = 79.3
sdev (us) = 1.5
(25 us base thread)
min (us) = -24.9
max (us) = 42.4
sdev (us) = 0.8
Last edit: 15 Feb 2024 01:03 by RNZ.
Please Log in or Create an account to join the conversation.
14 Feb 2024 00:02 #293279
by rodw
Replied by rodw on topic LinuxCNC on Raspberry Pi 5
Being new hardware, its possible you are a victim of enegy efficient ethernet.
ref: www.juniper.net/documentation/us/en/soft...e%20link%20is%20idle.
Could you try disbale it by adding
igb.EEE=0
to your boot parameters (where you put isolcpus) I think its boot.txt on the pi
I have no idea if this will work!
ref: www.juniper.net/documentation/us/en/soft...e%20link%20is%20idle.
Could you try disbale it by adding
igb.EEE=0
to your boot parameters (where you put isolcpus) I think its boot.txt on the pi
I have no idea if this will work!
Please Log in or Create an account to join the conversation.
Time to create page: 0.109 seconds