Advanced Search

I have always had problems with named subroutines but lately I cannot get them to work at all.I get the following message;

LinuxCNC Error Near line 4 of/home/rpi-first-boot-wizard/linuxcnc/nc_files/Utility_G_Code/test.ngc:Failed to find sub 'Omyfile.ngc' before EOF

In this case I had a dead simple routine named 'test.ngc' that called a dead simple subroutine named 'my file.ngc'.

The location of the files and subroutines was called out in the .init file.

I have used named subroutines in the past.  I now use Raspberry Pi 4 and 5 with Axis 2.9.4 versions.

Any fool proof method for handling these subroutines would be appreciated.
I have a boat load of specializedsub routines lying dormant.

First thing I'd do is disable SPi if you haven't already.
Qtdragon and software step generation may not be the best combination, the RPi4 is not the most powerful.
For some reason you are missing a library as per "can not open shared library".
WORKINGDIRECTORY may not be correct either.
If you go to the big thread regarding the image, it's a sticky, there is a basic working config, that uses axis as the GUI. I would try working with that to begin with.
This a link to an index to the big thread.
forum.linuxcnc.org/38-general-linuxcnc-q...official-images-only

Hello guys!

I have been trying to switch over from an online system with GRBL Teensy 4.1 with ioSender to a Raspberry Pi 4B LinuxCNC configuration for an 3-axis milling machine. The tricky part is that I am trying to make a configuration that uses the GPIO pins from the RPi instead of using a parallel port hat or a Mesa board. I am an absolute noob, with this being my first post.

Going based off some instructional files I found online and demos for the few who have done this, I have gotten to where I am today. The PDF is in Italian but can be easily inserted into Google Translate. The .hal was the demo I referenced for setting up my .hal.

   

My version, rpi-4-debian-bookworm-6.12.11-arm64-ext4-2025-01-27-0404.img.xz, should have PREEMPT-RT. These are my .ini and .hal files that I have made for my 3-axis CNC machine.

 
   

The problem is that when I run cd ~/linuxcnc/configs/my-rpigpio/ linuxcnc my-rpigpio.ini linuxcnc will tease me with the bootup screen, and then in the terminal I get this:

LINUXCNC - 2.9.4 Machine configuration directory is '/home/cnc/linuxcnc/configs/my-rpigpio' Machine configuration file is 'my-rpigpio.ini' Starting LinuxCNC... linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod Note: Using POSIX realtime Found file(REL): ./my-rpigpio.hal motion: dlopen: /usr/lib/linuxcnc/modules/motion.so: cannot open shared object file: No such file or directory ./my-rpigpio.hal:7: waitpid failed /usr/bin/rtapi_app motion ./my-rpigpio.hal:7: /usr/bin/rtapi_app exited without becoming ready ./my-rpigpio.hal:7: insmod for motion failed, returned -1 Shutting down and cleaning up LinuxCNC... Note: Using POSIX realtime LinuxCNC terminated with an error.  You can find more information in the log:     /home/cnc/linuxcnc_debug.txt and     /home/cnc/linuxcnc_print.txt as well as in the output of the shell command 'dmesg' and in the terminal

With none of my hardware connected, should I even be expecting the LinuxCNC GUI to open? I feel I have too much stuff in my .hal file and it may be looking for components that don't exist, and that is why my LinuxCNC GUI is not opening.

Please use this image:
drive.google.com/file/d/1CoO_2y7iDTwtubG...VSw/view?usp=sharing

Usually a no carrier issue would be a cable issue between the RPi5 & Mesa board (the drivers have been loaded), has the Mesa board booted correctly ?

Bear in mind that the kernel used is directly from the Raspberry Pi repos, ie it is not a custom kernel other than being RT capable. The RPi kernel build instruction make no differentiation between any of the "5" series. The all use the same kernel. Neither is there special options related to ethernet for the CM5 in the config.txt file.

It may help if you can provide a link to the carrier board.

The best place for any issues relating to the current Trixie images is at the link below as I don't use the forum as often as I used to. There is no need to raise an issue as I'm aware of it.
github.com/ozzyrob/linuxcnc-rpi-2.9.7-image-issues

Hello, I am testing LinuxCNC 2.9.7 (official Raspberry Pi 4/5 image, Debian Trixie, uspace) on a Raspberry Pi Compute Module 5 (CM5) with a Mesa 7i95 Ethernet card.
The same LinuxCNC version, Mesa card, cable, and network configuration work on another Raspberry Pi platform, but on CM5: • eth0 stays NO-CARRIER • ethtool eth0 shows Link detected: no • Forcing speed/duplex has no effect • RP1 PCIe device is detected in kernel logs Network: • eth0: 10.10.10.1/24 • Mesa: 10.10.10.10
Is CM5 fully supported by the current LinuxCNC Raspberry Pi 4/5 image, or is newer kernel / device-tree support required for RP1 Ethernet on CM5? Thank you.

    Good morning, I am new to this community and joined in hopes you could help me step into the world of CNC’ing. Couple of years back I purchased this multi-cam CNC that had been sitting for a while. It had been used to machine deep pockets into Ovation guitar bodies. After cleaning out all the fiber material I found all the slide bearings in almost new condition. I took a bunch of picts and proceeded to completely disassemble the unit for restore. All the wiring too! I thought I would I’ll just look up what information I need to put it back together… bad plan! Not only can I not find how to wire these components I’m not even sure where to begin, what to keep and what to ditch.I will replace the spindle but would like to keep using the x,y,z motors. These are Allen-Bradley N-3412 B series brushless servo motors powered by Electro-Craft DDM-009 drives. All the rest I want to have new. I figure to use LinuxCNC on a Raspberry 5 with Unbuntu to control these x,y,z axis and (maybe) control the spindle (whatever that will be) separately. What add-on board and how to finally connect the motors escapes me.I have looked and looked but don’t know where to start. I need help.I would greatly appreciate any advise or direction. 

Es ist gar nicht so einfach Bilder hier hochzuladen, ich habe es jedenfalls nicht geschafft (waren auh nicht zu gross).
Ich habe die Bilder unter github.com/freylax/riocfg/img eingestellt. Es ist ein alter selbstbau Plotter aus DDR Zeiten den ich als CNC Testobjekt verwenden moechte bevor ich mich an die richtige Maschine bei meinem Freund ranwage.

Raspberry PI5, Olimex ICE40 EVB, Adapter und CNC Breakout Board, Stepper Driver.

Ich kann die Mikrosteps einstellen, allerdings scheint das nicht ganz zum Erfolg zu fuehren. In der rio-test app kann ich den 
Motor schrittweise steuern, das klappt. Aber wenn ich in der axis app Manuell zb 5mm anfahre und auch eine geringe Geschwindigkeit einstelle, dann vibriert der Motor nur und es werden  keine richtigen Schritte daraus. Was mach rio-test anders?
Ich studiere auch den Code um das zu verstehen.

liebe Gruesse,
Robert 

I did a similar thing a few years back, I used Clough42's Electronic lead screw project and made a few changes to the program to make this work for my needs. all I needed to do was mount an encoder and put a motor on one of my dividing heads. I have since taken apart the electronics as I needed them for other projects but I am now using the DR-DRO Raspberry Pi-based rotary controller for stuff like this. The DR-DRO is much more flexible to do crazy stuff on manual machines. I am thinking about doing the same setup on my mh800e that is retrofitted to linuxcnc

Oh no, something else not quite right with my build. The halrun binary seems to be missing. I will try to find out how that dropped out. I will need it for the project where I plan to use this pi3.

Another latency test. The previous one I shared was run a couple minutes with nothing else running. This time I gave it the works. How about 10mS latency.

Here are the error reports I get trying to wake QtDragon. seems to be a complaint about the ngc path. I'm using run-in-place. I've got to look at this again. Just writing it up gave me more ideas.

Wow, I can hardly believe I did this to a pi 3. The simulation is running. Next I want to check if gpio and a couple other basics work. The latency numbers look a bit sad.
Still no luck starting QtDragon.

Got LinuxCNC built. Running latency test. Tried running Axis and QtDragon, gui just crashes, need to spend a little more time on it, maybe tomorrow. I think I got some missing dependencies going on.

This is catching my interest. I think I will try it. I have at my fingertips a Pi 3 Model B+ but it is not working, not sure why. Maybe I dropped it a while back. I also have a Pi 3 Model B V1.2, I have it running a fresh install of Debian 12 Bookworm.

Now it is installing LXDE.
Next up is realtime kernel, I'm looking at linux-image-6.1.0-41-rt-arm64
And then LinuxCNC....
Fingers crossed...

There are no premade RPi3 images available for download.

You have a couple of options.
1: Someone maybe able to make one, but it would require that person having access to a Rpi3.
2: Find someone with Linux knowledge who can also speak english and is willing to help.
3: Have a go following someone's instructions, all is not lost if you make a mistake.
4: Look into using grbl.

A bit of a warning regarding the RPi3, you may have latency issues, which there may not be a solution for fixing it. Increasing thread period may not give smooth operation.

Saying that you don't understand all the time wont help. I'm sorry I really wish it was different.