Advanced Search

HI i am trying to use rapberry pi 5 and Linuxcnc and i made sucsess with my instalation of 3 axis mill config but when I make a new setup for my lathe I get this mesege . 
Debug file information:
Note: Using POSIX realtime
4652
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
Can anyone point me in the right direction so I can try to solve this
Regards Krister

 

github.com/iforce2d/weenyPRU

check in with this guy, he installed it recently on a pi zero

We need to mash this file into our drivers, as this is the new RPi5 spi driver
github.com/raspberrypi/linux/blob/rpi-6....rs/spi/spi-dw-mmio.c

RPi5 doesnt use the same broadcom IO stuff as previous models, they made a their own IO chip. instead of bcm2835 controlling the SPI, the new chip used this designware driver

Thank you very much for your answer. I will try to switch to the Bookworm system, but I can only use a 32-bit system because using a 64-bit system on the Zero-2 W causes the core to hang and fail to start after installing preempt-rt.

1GHz and 512MB......does you instructor not like you ?Once you have it installed, if you can run a config all power to you.If the instructor asks you to machine this, maybe you should get them some help. 

 

Sorry, newbie, but there is one question from the experience of forum members, because time has passed, and experience is power.
Is the Raspberry Pi4 network controller with Ethercat stable?
If so, on which versions of Linuxcnc and on which Linux kernel?
Thank you all for your responses and feedback.

Here is how to do this on the Raspberry Pi,
docs.google.com/document/d/1S0K-UBlXnsYC...b_0/edit?usp=sharing
BUt to install linuxcnc, try the script I mentioned first.
 

Sometimes you need to google a bit to find what package to install
Debian 11 support was not great.
A alternative might be to use a Debian Bookworm image instead of the pi raspi.debian.net/tested-images/
They appear to have one for your hardware. You can also look at the daily images if you know what one to use.
You will also need to create a user as it just gives you a root user, then add it to the sudoers group.
the PREEMPT_RT kernel should be able to be installed from the debian repositories
You can install a gui  while logged in as the root user with
apt install tasksel
tasksel

then select the XFCE desktop.

If you look at the 2.9 getting linuxcnc doc, there is a script which will install linuxcnc for you without building from source. It may work for you but not sure if you are going to end up with 32 bit or 64 bit.

Yes, I have already attempted this operation, but unfortunately, it didn't work. I also tried "sudo apt-get install lxml" based on some online suggestions. It showed that I have already installed this package under Python 3, but it seems that what is needed now is lxml for Python 2, which is causing me quite a headache.

Additionally, I can install the dh-python package, but it brings up another issue: "The following packages have unmet dependencies: dh-python : Breaks: python E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages." This results in two other dependencies, python and python-dev, being unable to be detected.

Did you do
sudo apt update
Before trying to install missing packages?

I hope this message finds you well. I am currently trying to install LinuxCNC on a Raspberry Pi Zero 2 W for a course requirement. Unfortunately, most of the installation guides I have found online are outdated.The Raspberry Pi's current system version is Debian 11 Bullseye. I have successfully applied real-time patches to the Raspberry Pi, and the system version is as follows:
Linux raspberrypi 6.1.74-rt13-v7 #1 SMP PREEMPT_RT Thu Feb 29 16:17:14 CST 2024 armv7l GNU/Linux.My main issue arises when following the official LinuxCNC build instructions. When I use dpkg-checkbuilddeps, it prompts me with the following error: "dpkg-checkbuilddeps: error: Unmet build dependencies: dh-python python-lxml." However, when I try to install these two packages, I receive an error indicating that the packages cannot be located. I have tried several methods to resolve this issue but have been unsuccessful.I would greatly appreciate any assistance or guidance you can provide on how to resolve this issue. Thank you very much for your time and support.Best regards

rodw wrote:

I can't help you with as I don't have the hardware. But I can put you on the right track!.
Homing is managed in Linuxcnc by homing.c
github.com/LinuxCNC/linuxcnc/blob/master.../emc/motion/homing.c

Master branch has recently released the homecomp.comp compoonent
linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html
and the source file here github.com/LinuxCNC/linuxcnc/blob/master...onents/homecomp.comp
The purpose of homecomp is to give a method to override homing.c behaviour to build a custom homing behaivour

You should also look at Domminic Braun's ethercat cia402.comp and supporting hal file github.com/dbraun1981/hal-cia402
which predates homecomp and also attempts to deal with hardware which homes externally. He also deals with the conversion of motion units between Linuxcnc and external hardware. Look at how he uses read and write functions. This might be able to be done in halcomp as there are procedures that read all pins and writes all pins.
Your homecomp needs to be able to deal with following errors that will ocur when the extenral drives move without lcnc's knowledge. This can be done by equating the feedback position with current position during external homing.
There are a large number of homing states that can be skipped or ignored when external homing is done so you homecomp basically just needs to initiate homing and wait intil homing is completed ,Tell Linuxcnc you are homed, and then let Linuxcnc continue on.

God luck with this, its complex because in a homecomp, you need to deal with all joints at a time where a component like cia402.comp has a seperate instance of the component for each drive being homed...
 
 

some time left after that - but i continued working on that. firs a short update on current status:

-> for homing 2.9+ is necessary (took some time that i recognized that i was still on 2.8. on my raspberry)
-> on my Raspberry the user COMP does not work on 2.9.2 (first i tried the bookworm image of dec23, and also tried to run on Buster with manual install based on instruction and froum thread)
-> anyway my pokeys.comp seems to work fine on a laptop using the "linuxcnc_2.9.2-amd64.hybrid.iso"
-< for the problems due to not yet created pins when halfile tries to write on them, i created two dummy components that add some millisecond delay during loading of Hal (e.g. loadusr -W start_delay_5000), these use the extra_setup option during start to wait for 5000 ms or 3000 ms.

i created a first version of pokeys_homecomp.comp. As pokeys.comp itself is userspace and the homecomp is RT, as a first step the homecomp is a dummy, which receives the hal-commands and routes it to the pokeys.comp using pins and signals.
-> it seems to compile fine BUT when i try to load that in [EMCMOT]HOMEMOD=pokeys_homecomp i get a cyclic errors like "USRMOT: ERROR: command timeout", so i added some debugmessages in hope that it helps to find out which function is causing that.
-> so far no idea yet.

on a second path i try to get that poKeysLib usable in a RT. Currently it compiles and EMC was starting but it did not show up in HALMonitor. But since i added references & calls for PokeysLib i get a "undefined symbols" when i try to start a hal that contains that comp.
-> here i assume that pokeyslib is not yet ready to run on RT (i assume because lubusb1.0) so i started to create a copy of that H file which excludes that (using the #undef POKEYSLIB_USE_LIBUSB), but it seems that there's more work on that to do.

You would be better off looking for debian packaged VNC software here packages.debian.org/index
It will tell you if there are ARM64 packages but the way debian works, it builds for all platforms 

Rods tool chain creates a Debian based image, not a Raspberry Pi OS based image. Whilst the are similar there are some differences, you lose some of the customizations that Raspberry Pi Foundation has.
On my Raspberry Pi based image I used this tutorial:
pimylifeup.com/raspberry-pi-vnc-server/

Can't remember if I checked latency, if I did it doesn't stick in my mind there were any latency issues. One thing I forgot to add is I changed from the wayland backend to the X11 backend using raspi-config. The X11 layer in wayland was very very slow in some of the tests I tried.

just a brief status of my experiments...

I spent several days trying to setup the feasible VNC server on the Debian 12 LinuxCNC image but unfortunately looks like I can't. The only successful result was reached with x11vnc, but jitter grew up to ~280 μs (280,000 ns) just after I run x11vnc process (even with no connections).

I also tried to install there wayvnc like on raspberry OS, but debian sources contains too old version 0.5xx. On raspberry it is 0.8xx RC and several days ago they released regular 0.8. But I didn't understand how to resolve the dependency hell with all the required packages...

Will try to use Rod's toolchain to prepare the image based on the Raspberry Pi OS — I'm really loved in the way how can I customize all the required packages and appearance before the image has been flashed.

If someone resolved the lightsweight enough VNC server on Debian, I would be pleased to take a look. Thanks,