Advanced Search

Hi, I'm very new to CNC, and I have a Maxnc15CL from around the year 2000 and am using a Raspberry Pi 5 to communicate with it using LinuxCNC. The Pi 5 has a parallel port hat from Byte 2 Bot, and I'm able to control the spindle, detect the limit switches, enable the motor encoder feedback loop, and make the motors make noise when I tell the axis to move. I suspect that the motor timing is off, but im not too sure if when I change the values, if it's getting closer or further away from actually moving. If anyone has any ideas on how to make this work, I would greatly appreciate it, and im leaving my hal file and .ini file below. Thank you 

I haven't been on the Forum for ages but today I noticed that someone asked if I could post my RPi 5 ethernet settings on this thread.

I think they have been posted a few pages back by someone else, nevertheless the following wider context may be helpful.

As an aside, my RPi 5 and Mesa setup has worked perfectly since the ethernet issue (below) was fixed.

================================================================
The following is copied from another thread.
================================================================

I ran my RPi 5 and 7i96s overnight and completed 40 million pings with zero errors.

sudo chrt 99 ping -i .001 10.10.10.10 -c 40000000

At the same time in the background, I ran Latency Histogram and two Glxgears. I have attached photos in case anybody is interested in seeing the results.

I’m not sure what to make of the maximum ping time of just over 10 ms.

It seems that "hardware-irq-coalesce-rx-usecs 0" has fixed the issues I was having (aside from the 10 ms issue) at least on RPi 5 * GB with LinuxCNC 2.9.2.

======================================

What is this "coalesce" thing?

Interrupt coalesce settings ( access.redhat.com/documentation/en-us/re...ing_networking/index )

"By using interrupt coalescing, the system collects network packets and generates a single interrupt for multiple packets. This increases the amount of data sent to the kernel with one hardware interrupt, which reduces the interrupt load, and maximizes the throughput."

=====================================
My /etc/network/interfaces looks like this:
=====================================

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 10.10.10.11
hardware-irq-coalesce-rx-usecs 0

=========================== 

Cam -> Raspberry PI3 -> 7Inch Touchscreen -> TCP -> WIFI -> LinuxCNC

www.youtube.com/shorts/sAEmJ-vLgHY
 

I have installed linuxcnc 2.10pre on raspberry pi4. Now I want to update qtdragonHD to latest GIT version. Can anyone guide me how to do it?

Some notes on what has been working for me:

Currently my go-to PLC+HMI setup is LinuxCNC+Node Red dashboard. Sometimes also Glade user interfaces.

I use a combination of Mesa Electronics boards and/or Beckhoff ethercat remote I/O at locations on the machine where you'd normally expect to find a PLC. My logic runs on hal + custom hal components coded in basically C.

Non real-time logic, recipe selections etc. can be configured in node-red pretty much without writing a single line of code unless you want customized functions.

LinuxCNC also has a ladder logic PLC built-in but I cannot inform you of its capabilities, having never used it. I don't care for ladder logic in any form. I have spent way too much time trying to automate complicated machine sequences in expensive proprietary PLC ladder programming software that did not always function the way I expected or wanted.

With node-red for the HMI, all the software lives in the LinuxCNC 'server'. The physical HMIs consist of panel mount touchscreen IPCs booting pretty much any os, autostarting a web browser fullscreen, pointed at the LinuxCNC sever's Node Red web page. The hmi is simply a web page(s) in the server. Placing a duplicate HMI at an additional operator station consists of whatever device you wish, running a web browser displaying the server's web page(s)

I think node-red supports multiple user logins, but I have not tried that feature. In the projects I did so far, I am the only programmer, and the operators don't know how to access the programming back end. Everyone is logged in as me.

On a recent project I set up a router blasting WIFI over the premises. The operator driving the payloader can log into the WIFI with his phone and access the HMI to monitor the processes and switch the machines on/off that he is tending. From the payloader cab.

The entire network is air-gapped from public internet except the server has access to ntp time.

E-stop, safety lockouts, etc are all hardwired with physical safety hardware.

With this system an operator station needs the following wiring:
1. A power cord for the pc.
2. A network cable.
3. A 2 to 6 conductor cable for the E-stop circuit.

When I get more time I'd like to provide some documentation on all this, and some example configs. Currently I'm in the middle of several half finished projects like this, plus a customer running a proprietary PLC I programmed in ladder logic is starting to have random crashes of the PLC, so he is due for an upgrade to LinuxCNC with Glade user interface. This is one more basic machine, so I will skip the node-red. The glade user interface is an app that runs on a monitor plugged directly into the LinuxCNC pc. Then there is a sizable project I'm currently drafting a quote for.

node red getting started:
nodered.org/docs/getting-started/local

I use this for installing node-red:
nodered.org/docs/getting-started/raspberrypi
Although it says raspberry pi, it can be used on an x86/64 pc. During the installation it asks whether I want to install Pi specific nodes, I opt out of that because my x86/64 pc is not a Raspberry pi.

I have been using mqtt messaging to communicate between the LinuxCNC program(s) and node-red. That entails setting up an mqtt server, I have been using mosquitto:
sudo apt install mosquitto

then I run a python-hal component to communicate with node-red via mqtt

Doing all the above configuration pretty much requires a a person to first know his way around linux configuration in the /etc directory extensively.
Default installation of mosquitto and node-red I think listen only on localhost for connection.

Wow, I was going to attach a copy of my python-hal-mqtt connector, but my backup of it seems to be missing. I will have to retrieve a copy from customer's machine as soon as I can.

Hi all,I’m currently having trouble setting up a tool presetter in LinuxCNC. My setup consists of a Raspberry Pi 5 running LinuxCNC, three Leadshine servo motors, and a Beckhoff unit handling the toolsetter input.

The main issue is that when I press “Set Tool Offset PSO,” LinuxCNC does not apply the current machine coordinates. Also, when attempting to perform a tool height setting, nothing happens.
I’m also experiencing problems with manual tool changes. When using the Unload Tool or Load Tool commands, nothing occurs. The only way I can trigger a tool change is by using an M6 T"x" command, which brings up a popup asking for confirmation that the tool has been changed.I have not yet connected the solenoid valve that will actuate the drawbar. 

I’ve attached my HAL and INI files. Any suggestions or ideas would be appreciated. 

Thank you for your response, and also for your subtle sarcasm in calling me ignorant every time I comment or ask for help in the threads you also participate in. But I think it's better to be considered ignorant than to learn nothing, even if you're treated like garbage. What I'm trying to figure out is how to create an .img file of my hard drive's contents without having to reinstall applications that aren't included in the .img file, like the one you created for the Raspberry Pi 4 with Debian 13, which I've already installed on four Pi 4s. After installation, I add other applications and compile some components that aren't included in the official LCN version, and doing all that every time I install the image you created wastes a lot of my time.

If using the RPi Trixie image you will need to update Linuxcnc to 2.9.8.

This will be the situation until late March\early April.

forum.linuxcnc.org/37-international-linu...version-cnc-software

This can be taken a look at

@3404gerber thanks for your all response. Finally I was able to make it working. Added spi_clk_div=32 in remora-spi arguments.
But it was never required earlier. I am using raspberry pi 4b.

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.