Advanced Search

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

I try to convert a mill setup to a Lathe setup . And now next problem , what is this meaning

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.1
Machine configuration directory is '/home/cnc/linuxcnc/configs/my-svarv'
Machine configuration file is 'my-svarv.ini'
INIFILE=/home/cnc/linuxcnc/configs/my-svarv/my-svarv.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=
DISPLAY=axis
COORDINATES=X Z
KINEMATICS=trivkins coordinates=XZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./Min_svarv.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
Shutting down and cleaning up LinuxCNC...
task: 119 cycles, min=0.000009, max=0.015490, avg=0.008914, 0 latency excursions (> 10x expected cycle time of 0.010000s)
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
note: MAXV max: 6.000 units/sec 360.000 units/min
note: LJOG max: 6.000 units/sec 360.000 units/min
note: LJOG default: 3.000 units/sec 180.000 units/min
note: jog_order='ZX'
note: jog_invert={'X'}
pyvcp_options.hal:11: parameter or pin 'scale.0.gain' not found
3224
3258
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime


Were is the pin 'scale.0.gain to be ?

Yes its the capital letter syndrom ,I find it

rodw wrote:

elovalvo wrote:

I think many posts in this thread are completely unrelated to the topic I started it with.
My idea was to compare the performance of the Raspbian Bookworm (and not the Debian) on Pi4 and Pi5....
ITs difficult for users to compare the products until they have a robust installation method for the pi5. But it has been reported latency is much improved.

The OP has describe a robust installation method within the opening couple of posts. Having tested both methods for the RPi5, the Raspbian OS based method appears to be the better setup.

elovalvo wrote:

The results are definitely surprising
 
 
[code][code]Regarding this...  is it understood why the latency was so much better in the RPi 5 test, than the RPi 4?  Is this purely a result of improved processor performance, or is there some other underlying reason?  (And, has that result been reproduced?)

Unless I'm misunderstanding, I think that latency is quite a bit better than I currently get on my 10 y.o. AMD PC, which implies I could potentially replace it (and its parallel port) directly with an RPi 5 and its gpio pins.  Which I confess excites me a bit.  :-)

paul

[/code][/code]

If you look at the thread announcing this release the first post gives clear instructions how to fix this.

I gave up on the official iso the other day as it could not load the firmware for my Ethernet card, even tho when booting to a live session it did. I did also mention it.
As to the raspi firmware that is a bug in the installer from Debian. I don’t know why the issue isn’t mentioned on the download page, but the download also mentions the RPi 5 image supports SPI, which it doesn’t.
So to install the latest Debian version and linuxcnc 2.9.2 on my x86 system I used the Debian netinst image, installed the need kernel manually, used the script mentioned in the docs to install linuxcnc, for less frustrating than trying to use the official image.
Now I’m no slouch in this area, I’ve made my own respin of Mint for Linuxcnc, made my own Raspberry Pi images and messed around with Mesa firmware to run on a couple of Xilinx dev boards. This was absolutely the worst experience trying to install linuxcnc on a machine. It amazes me newbies actually get anywhere.

Cannot find file for:Min_svarv.hal

This file needs to be in the same folder as your ini and main Hal files.
Could be a typo in your ini file.

If you see a line stating it can’t find a file or a pin doesn’t exist that is the error. Mostly it will be a typo somewhere.

I think it's pretty clear that if I download LinuxCNC_2.9.2-amd64.hybrid.iso from official the link at linuxcnc.org/downloads/ , and the installation fails because unnecessary Raspberry Pi firmware is inoperable on my x86 PC, then it's a bug.

Perhaps it's an unavoidable bug, or very inconvenient to fix. But the release is over 2 months old. Plenty of time for there to be a note on the downloads page with a warning, and the (trivial) fix.

paul