Advanced Search

Always wonder why you use such a low servo thread, which isn't a real world scenario, and don't show a 1ms servo thread and a base thread.

It would be interesting to see a 1ms servo thread without isolating any cpus. And the aforementioned 1ms servo thread & base thread isolating the required cpus to get a real life scenario. Some users can judge whether it would suit a real life setup without having to go through buying a RPi5, installing Linuxcnc and running the latency tests. Something that would give them confidence in a particular setup.

LinuxCNC 2.9.2 auf RPi4 (RPi 400) + MESA 7i76e
Nachtrag:

Inzwischen habe ich das Komando <menu-config> gefunden.
Dieses ist im <.img.xz> enthalten und ist vergleichbar mit <raspi-config>.
Somit kann der Abschnitt mit <raspi-config> entfallen.
<menu-config> zeigt nach Beenden einige nützliche Infos an.


cnc@raspberrypi:~$ menu-config
Generating locales (this might take a while)...
de_DE.UTF-8... done
Generation complete.

Current default time zone: 'Europe/Berlin'
Local time is now: Wed Mar 13 00:34:39 CET 2024.
Universal Time is now: Tue Mar 12 23:34:39 UTC 2024.

Debian GNU/Linux 12 (bookworm) 6.1.54-rt15 #1_RT Fri Nov 17 17:02:27 AEST 2023
aarch64
Raspberry Pi 4 Model B Rev 1.5
== DISK
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 28G 3.6G 23G 14% /
/dev/sda1 508M 89M 419M 18% /boot/broadcom

== NETWORK
Hostname: raspberrypi
Wired: eth0 UP 192.168.0.132

== SYSTEM
Processor: Cortex-A72 @ 1800MHz 35.5°C
Online: 0-3
Governor: performance
Memory: 3.7G 482M
Entropy: 256
Uptime: 00:35:27 up 8 min, 1 user, load average: 1.01, 0.98, 0.62

sudo apt update && sudo apt full-upgrade
sudo reboot

Weitere System-Infos kann man mit diesen Komandos erhalten:

uname --help
uname -a
(Kernel-Version)

hostnamectl -h
hostnamectl
(System-Info)

df --help
df -h
(Dateisystem-Info)

lsusb -h
lsusb
(USB-Info)

rpi-eeprom-update
(Liste mit EEPROM-Info)

stz60

Looks good. It would be interesting to retry using the debian kernel rather than your compied one and compare latency results. I suspect what you have will be better.sudo apt-install -y linux-image-rt-arm64 linux-headers-rt-arm64

I recently noticed that the Raspbian update on Pi5 installs version 6.6.20+rpt-rpi-2712.

Therefore I thought about updating the PREEMPT_RT version

So I started with a fresh installation of the Raspberry Pi OS 64 bit via Raspberry Pi Imager.
I updated to version 6.6.20 with the usual commands:
sudo apt update
sudo apt upgrade
and I rebooted.

The uname -a command now returns the following indication
Linux raspberrypi5 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/

I then compiled a new version of the Raspbian OS that included the PREEMPT_RT
For convenience I used the procedure here
forums.raspberrypi.com/viewtopic.php?t=343387

The kernel with the PREEMPT_RT is kernel-6.6.21-v8-16k-elv.zip
and can be downloaded from here
drive.google.com/file/d/1FKLQIBdXTh43kjC...48d/view?usp=sharing

To install it, just copy it to /tmp and then run these commands

cd /
sudo unzip /tmp/kernel-6.6.21-v8-16k-elv.zip
overwriting all files with the All option

So I edited the cmdline.txt with
sudo nano "/boot/firmware/cmdline.txt"
adding the following commands to the end of the line
   isolcpus=2.3 rcu_nocbs=2.3 nohz_full=2.3 max.processor.cstate=1
   
At the next reboot the uname -a command reports the following indication
Linux raspberrypi5 6.6.21-rpi999-rpi-2712 #1 SMP PREEMPT_RT Tue Mar 12 15:59:56 CET 2024 aarch64 GNU/Linux
   
To install linuxcnc simply type the following commands
 sudo apt update
 sudo apt install linuxcnc-uspace linuxcnc-uspace-dev
   
However, to date the installed version is the following
   LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
   
If you want version 2.9.2 you can do it this way:
   
cd /tmp
wget linuxcnc.org/dists/bookworm/2.9-uspace/b...pace_2.9.2_arm64.deb
wget linuxcnc.org/dists/bookworm/2.9-uspace/b...-dev_2.9.2_arm64.deb
wget linuxcnc.org/dists/bookworm/2.9-uspace/b...doc-en_2.9.2_all.deb

sudo apt install ./linuxcnc-uspace_2.9.2_arm64.deb
sudo apt install ./linuxcnc-uspace-dev_2.9.2_arm64.deb
sudo apt install ./linuxcnc-doc-en_2.9.2_all.deb

The result of the latency-histogram (latency-histogram --nobase --sbinsize 1000 --show --servo 35000) is however always very interesting
 
For those who do not want to retrace all the steps previously exposed, you can find the ready-made image (Lcnc292_pi5.img) here:
drive.google.com/file/d/1dd8oiYhcs_UComc...fNF/view?usp=sharing

In the meantime you can try with the image you find here:

forum.linuxcnc.org/9-installing-linuxcnc...i-5?start=170#295779

I would keep with the RPI OS and install Linuxcnc once booted.

Be aware that Linuxcnc does not have support for SPI as of yet, even tho on the downloads page it says is does.

Oh another thing the Linuxcnc image is a debian based image and is a little different to the mainstream Raspbian OS. The config.txt and cmdline.txt are not in the same folder as per a Raspbian image.

You may have to play around with config.txt as I'm not sure if it has the lines to detect an DSI screen connected. This will need to be edited by hand, can't remember exact location so you will have to hunt around in the /boot directory and sub directories.

www.raspberrypi.com/documentation/comput...ays-and-touchscreens

I retried the full linuxcnc_uspace image approach on an SD card known to run raspian, debian, etc on my RPi 4B using the latest RPi imager. It failed as usual to boot the RPi 4B.
Using the same micro SD card 32 GB sandisk, I used disk mgmt. on the Lenovo desktop with win 11 to make clean new volume at 32 GB FAT 32. Next came the option on RPi imager to choose
"2023-12-05-raspios-bookworm-arm64-full.img.xz" [ the 2,732MB version ]
as the operating system (downloaded from Raspberrypi.com). Of course the device was RPi 4. A bootable SD card was created. RPi 4B was booted!
Here is the simple part that I missed in all my efforts to put Linuxcnc on my RPi 4B.
At terminal window on RPi 4B:
sudo apt-get update
sudo apt-get install linuxcnc-uspace linuxcnc-uspace-dev

Linuxcnc was installed in the menu with how to manuals and appears to be fine. I am experiencing problems with apps that popup over the entire window and only a reboot will regain control of RPi. I will try a more stable version of RPi operating system next.

I've been trying to get Remora running on RP2040 via Ethernet on a Raspberry pi 5. The error i'm getting when trying to run LinuxCNC is:

The error doesn't seem to be related to the pi 5 specifically so I'm hoping to get the pi 5 working with remora-ethernet, does anyone have a clue what I can try to fix it?

I've used the RP-2040-Ethernet-Remora firmware from:
github.com/scottalford75/Remora-RP2040-W5500
(UF2 file from the standard build folder, tried compiling it myself but came across multiple problems, I can give details if needed)

and using config and component from
github.com/scottalford75/Remora-NVEM/tre...Components/Remora-nv
and
github.com/scottalford75/Remora-NVEM/tre...es/remora-nvem-basic

When powering the RP-2040 all outputs seem to be flickering, can anyone tell if this is normal?

I tried measuring the signal and it's lots of seamingly random peaks, my logic analyser only goes up to 24Mhz and it's all peaks at minimal time period. 

In my setup I'm also connecting the W5500 with dupont wires, could this cause my problems maybe? (Read somewhere that the SPI communcation at stock speeds and these wires might not work)

Besides that I also read somethwere that the ethernet cable between pi and RP2040 needs to be a crossover cable. I've tried quickly making one but that also doesn't seem to make a difference.

I don't really know how to debug the error i'm getting so hopefully someone can help me.

I made a list of all commands I used to get my pi up and running, maybe it is usefull for someone trying to do the same or debugging my problem so here is what i've done:

Setting up my crappy touchdisplay:
in /boot/broadcom/config.txt adding
hdmi_force_hotplug=1
hdmi_drive=2
config_hdmi_boost=4

in cmdline.txt
adding "video=HDMI-A-1:1920x1080@60D" at the end

Setting up tightVNC:
Setting up other vnc servers was difficult, got this one working by
nano ~/.vnc/xstartup
change to:
#!/bin/sh
xsetroot -solid grey
export XKL_XMODMAP_DISABLE=1
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
startxfce4 &

To automatically start it at boot:
sudo nano /etc/rc.local
add this:
sudo -u cnc /usr/bin/tightvncserver :1 -geometry 1920x1080
before the exit 0:

To automatically log in to linuxcnc account at boot:
sudo nano /etc/lightdm/lightdm.conf
autologin-user=cnc

Setting up the static ethernet connection on Raspberry pi 5:
in sudo menu-config I changed ipv4 to manual and set the adres to 10.10.10.11 and gateway 0.0.0.0
(There is no /etc/dhcpcd.conf anymore on pi 5 it seems but this does the trick it seems)

installing nvem-remora component:
sudo halcompile --install remora-nv.c

Settings up RP2040
first uploading remora.uf2 to the pico board
(for upload_config.py tftpy is needed, installing tftpy normally didn't work, forgot the exact error)
python3venv venv
source venv/bin/activate
pip install tftpy
deactivate
./venv/bin/python3 upload_config.py nvem-basic-config.txt

In basic config I changed pin designators from PE_13, PE_12 to GP2, GP3 and left nvem board designator the same, is this correct?

Is there any way to check the communication over ethernet and if everything is going correctly? when I do ping 10.10.10.10 it responds back perfectly fine it seems.

To run Linuxcnc:
linuxcnc remora-nvem.ini

and in the ini i changed AXIS to qrvcp qtdragon_hd (axis didn't want to run for some reason but qtdragon seems fine)

Not sure as this was a while back, but i do recal something about rpi4 not supporting OpenGL or similar.
Also recal reading about using VTK (Vulcan) instead of OpenGL for running Probe Basic on RPI, but no idea if that would work for Vismach.

hello i have been trying to install linuxcnc on raspberry pi 4b for a couple of days i have download on the raspberry pi the debian os in the documentation that has linuxcnc already installed on it but the vismach simulations dont work even the demos on the software

Hello forum members, I am new to LinuxCNC. I wanted to understand what it is and what it is used for.
I chose a lathe as a model and started building a system with feedback.

Here's the configuration of what I use:
Brains -Raspberry pi 5 with linuxcnc 2.9.2
Main board - 7i92 (with .bit for lpt-dptr)
Interfece board - LPT-DPTR 1.03
Microstep driver PLD545-G4
Stepper motor - PL57H76
Encoder - linear converter LIR-7M

I put all this together and faced a problem: LinuxCNC sees and processes signals from the encoder, the motor starts and works fine, but as soon as I try to "connect" them in the hal file nothing works! I picked up the direction and scale of linear movements, but the program gives the error ~joint 0 following error~. I thought that the mismatch is due to differences in indicators and set FERROR and MIN_FERROR to 10. The error disappeared, but the motor screams and the driver goes to sleep. I don't understand what to do next, what can be the problem? I will attach configuration files.

linuxcnc.org/downloads/

The documented processes work. I have done this many times on both RP-400 (basivcally a RPi4 and the newer RPi5)

Unfortunately "does not boot" does not give a lot of information.

First off I would try a standard RPi image, to rule out a faulty SD Card.
If this doesn't work I would try a different SD card.
I would also check that the image has been downloaded with no errors.
I would also check the PSU.


I would read thru the RPi image announcement thread as this may provide so more information.

Sometimes the firmware may need updating, this is out of the scope of Linuxcnc, and the Raspberry Pi Foundation website has this informattion.

I created a kind of step by step instruction for the customisation of the RPI Image Builder: github.com/golyakoff/linux-info/blob/mai...Debian12OS/README.md 

Hope I covered the majority of the customization cases in different places of the framework written by rodw.

Please feel free to write your comments

I think it's supposed to be stable; the Etherlab folks have a specific driver for it, but I don't have any specific details on using it handy.

Installation LinuxCNC 2.9.2 auf RPi4 (RPi 400) + MESA 7i76e

Hallo rodw, tommylight,
bitte diesen Beitrag sinnvoll zuordnen.

es wäre sehr hilfreich,
das Paket <raspi-config> in dem nächsten .img einzubauen.

Mit ein wenig Konsole-Erfahrung ist unter Xfce in wenigen Minuten das
gerade neu installierte LinuxCNC 2.9.2 auf RasberryPi4 auf deutsch oder
beliebig andere Sprache eingerichtet.

hier meine Anleitung kurz und bündig:
(schnellste Instalation)

rpi-4-debian-bookworm-6.1.54-rt15-arm64-ext4-2023-11-17-1731.img.xz
nur auf einen USB-Stick kopieren (ohne "dd" oder "rufus")
LAN mit RPi verbinden
RPi ohne SD-Karte / USB-Stick starten
RPi-Imager "net-install" aus dem Netz holen (Umschalt-Taste halten)
SD-Karte oder USB-Stick in RPi einstecken
RPi-Imager kann Ziel-LW löschen (-> formatiert fat32)
(kann ich nur empfehlen,
beschriebene Speichermedien verursachen Probleme)
(nun verabschiedet sich RPi-Imager, reboot
"net-install" erneut holen)

USB-Stick mit ".img.xz" anstecken
Quelle ".img.xz" und Ziel "SD-Karte/USB-Stick" anklicken -> starten
in ca. 15 Minuten download und install macht RPi ein reboot,
nach Neustart ist System (nach Vorgabe des Entwicklers) installiert
user: cnc pw: cnc

ein erster latency-Test oder LinuxCNC-Sim bringt Freude auf,
nun ja erst mal nur in englisch, umstellen auf DE + Tastatur-DE
ist mir unter Xfce nicht gelungen.
Wenn man "Lxqt" installiert,
kann man dieses recht einfach auf der grafischen Oberfläche erledigen.

Unter Xfce kann man dieses auf der Konsole auch in wenigen Minuten erledigen,
wenn man <rpi-config> installiert. siehe auch:
raspberrypi.stackexchange.com/questions/...lack-of-raspi-config

-> auf Konsole:
sudo nano /etc/apt/sources.list
(diese Zeile zufügen:)
deb archive.raspberrypi.org/debian/ bookworm main
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 7FA3303E
sudo apt update
sudo apt install raspi-config
sudo raspi-config
locale, keyboard -> anwählen -> einstellen
(im WEB gut beschrieben)
finish
(und schon ist alles wie gewünscht)

sudo apt update && sudo apt full-upgrade
sudo reboot

-> nun LinuxCNC einrichten:
sudo apt install mesaflash hostmot2-firmware-all linuxcnc-doc-de mpv
("mpv" eignet sich sehr gut für eine USB-Kamera an der Z-Achse,
wenn angesteckt erscheint das Kamera-Bild):
mpv /dev/video0
pncconf
(2x Verknüpfung auf Desktop markieren)
(dieser Wizard erstellt .hal .ini und weitere Dateien im "home")
(LAN vom Internet trennen, RPi mit Mesa-Karte verbinden)
sudo ifconfig eth0 10.10.10.1 netmask 255.255.255.0
ping 10.10.10.10
(auf Desktop <CNC-Maschine> starten
sudo nano /etc/network/interfaces
(IP dauerhaft einstellen, diese Zeilen zufügen):

auto eth0
iface eth0 inet static
address 10.10.10.1
netmask 255.255.255.0

sudo reboot


-> Kamera einrichten:
ergibt ein nützliches Fadenkreuz,
kann nach belieben angepasst werden, siehe auch:
tallar83 (für LinuxCNC2.9 mpv)


(diese 3 Zeilen in der <CNC-Maschine.ini> unter [Display]zufügen):

# USB-Kamera - Bildgröße 640x480
EMBED_TAB_NAME = Kamera
EMBED_TAB_COMMAND = mpv /dev/video0 -wid {XID} --vf-add=drawbox=320:100:1:280:t=1 --vf-add=drawbox=180:240:280:1:t=1 --vf-add=drawbox=300:220:40:40:t=1 --vf-add=drawbox=280:200:80:80:t=1 --no-border

-> hilfreiche Lektüre:
raspberrypi.stackexchange.com/questions/...lack-of-raspi-config
www.elektronik-kompendium.de/sites/raspberry-pi/1906291.htm
forum.linuxcnc.org/38-general-linuxcnc-q...stieg-auf-mesa-7i76e
docs.google.com/document/d/1jeV_4VKzVmOI...ading=h.macj649sy0yq
docs.google.com/document/d/1jeV_4VKzVmOI...m1x7oiw8VcLFdiY/edit

ich wünsche allen Lesern dieser Anleitung eine gute Nacht,
mir haben die Recherchen viele Stunden gekostet.

stz60