LinuxCNC on Raspberry Pi 5

Agree with Tommy.
Users skipping steps.
Users not typing in commands properly.
Users not relaying requested information.
Users blaming Linuxcnc when it’s a mechanical issue.
Users blaming Linuxcnc when it’s an electrical issue.
Users not bothering to look at the docs.
Cases of users editing config files with a word processor program.
Users not understanding the prepared Linuxcnc images are not meant to be a general purpose OS.
Users believing the fear mongers who will say you need to be a programmer.
Users thinking they are the first and only ones to have a particular issue.
Users who don’t know how to form a proper question.
The effing “Maker Community” that tells poor saps that a CNC machine is easy to use by anyone.
People that wear gloves near rotating machinery.
People that insist on soldering crimped connectors.
Ah fuck it just people in general.

Hello tommylight,

That Google excerpt could be way off. I don't know. The only way to know what the current state of (LinuxCNC/Pi 5) is to poll it users and those attempting to use it. As you say they may have a working system and be doing something else.

Your comment about "Set it once and never again" is true for a lot of software until you change something (like a controller or the software itself).

I know newbies don't read things. For me "usability" includes reducing the need to read stuff as much as possible.

A issue list/process has several attributes besides being a pain in the neck. One is to track issues that surface and ensure that the issue is fixed and available for download. Another is for the developers to assess how to improve the user's encounter with the hardware and software itself.

I offered to help. If there is no issue list (for PI 5 for now) maybe I could help to create one. It would help centralize some aspects of the development work. Also, people age out. It may allow the current crop of wizards help the next generation of users.

Thanks,
Tom

Any issues related to the Linuxcnc code is well reported thru the github channels.

Lists and the like on the forum don’t really work as, I mentioned before, users think that their problem is unique to themselves.
We started a thread a while back to gather issues related to Parallel Port cards. Every so often within a month 3 to 4 users will start a new thread with the same issues.
Apart from not having a SPI driver for the RPi5, due to the RP1 chip (which caused issues for many utilities in general use for accessing gpio on the RPi 4 and below) there is no real issue.
There was a big push at the end of 2023 to update the existing RPi images and create one for the RPi5, Rod worked hard on that and bounced a few ideas around with myself. Now it’s at a stage where it is quite mature and very usable. The only real “issue” is that the RPi imager utility cant be used with it for reasons discussed in this thread with the solution.
So far the hm2_spix driver works quite well and the gent who wrote it made some code changes to the original hm2_rpspi driver.
Once new packages are built I’m sure the RPI5 will be fully supported “out of the box” for it does require building Linuxcnc from the current code base for either the master branch or the 2.9 branch. Not a difficult task if one follows the instructions as set out in the docs.
Every cnc machine is different so one can not hope to have a plug and play solution unless one buys a cnc machine that has been preconfigured by the manufacturer.
There are many boards available from Mesa that people use for a variety of applications. On top of that there are a number or alternative projects Remora and Linuxcnc-RIO are just 2.
Myself I’ve taken a different path by using a Spartan 6 dev board, designing some boards that take care of level shifting and built firmware to suit using the Mesa sources, for some of the firmware I’ve tweaked the existing drivers to suit the IO config. Using the same hardware I can also use firmware from the Linuxcnc-RIO project.
There’s a lot of choice available.

Oh I forgot, development is very centralised via github. It’s a very mature project which can trace things back to a NIST proposal quite a few years ago.

Also sometimes users want something that doesn’t work within Linuxcnc’s model.
Mostly this will boil down to USB motion cards, usually ones the Mach supports and using Linuxcnc to send gcode to an external board. Most are accepting this is not supported and not in the pipe line, once every often someone will spit the dummy and throw all their toys out of the pram.
For other support channels you may want to jump over to the Linuxcnc homepage and see what the other options are and links to said options.

Now that I have my Pi 5 / Mesa 7i95T basically working (still re-reading Docs and tweaking ini/hal configs) I do like it and don't regret starting with it.

I faced the most challenges from the following:

• Very rusty on Linux distro's, package managers and Kernel versions
• The Docs, Form and Wiki are AWESOME but it's often a challenge to remember where something was documents to find and re-read the details once I hit a problem.  (Fortunately Google search will usually find Forum threads for error outputs.
• Since the Pi4/5 are ARM based its more challenging to find Deb packages and APT sources for certain things.
• I always started with the LinuxCNC Debian imaging for all my builds - then would screw it up from there.

I am planning to build up an Intel platform machine next to smooth out some of the ARM related challenges.  If I had it to do over I would have chosen Intel.

Here are a few of the options I'm looking at and I've used other boards for other projects.

LattePanda Mu ($105 on sale)
    A Micro x86 Compute Module (N100 CPU,8GB RAM,64GB eMMC)
     On DfRobot

Lite Carrier Board for LattePanda Mu Compute Module ($39)
(USB 3.0, Ethernet, PCIe 3.0, M.2 M key, HDMI)
     On DfRobot

The carrier has two PCIe slots (1x/3x) but most people will need to add wifi Intel M.2 Wifi ($19)
     On Amazon

So that's around $170 plus shipping then you have to choose a DC supply and this one is really fast if that matters.

LattePanda 2 Delta 432
A Pocket-sized Powerful Windows/Linux Single Board Computer (4GB RAM/32GB eMMC)
     On DfRobot

M.2 PCIe card riser ($30)  On Amazon
This one comes with WiFi so it just needs power. It has less memory than the Mu and needs the riser to plug in full sized PCIe cards but it comes with a fan.

LattePanda V1 (~160 on sale) On DfRobot
The Smallest Windows 10 Single Board Computer (Unactivated, 4GB/64GB)
Both the V1 and Delta 432 come with a built in Arduino with standard HAT connections but since this one does not have a PCIe compatible M.2 using PCI Mesa cards would be out. It would be Ethernet only.

I think it would be facinating to see what the built in Arduino might make possible for controlling odds and ends using the HAT boards.

 

Hi resmond,

Thank you for the summary of your interactions with the Pi 5 world and its parallels. It sounds like a win.

Hi cornholio,

GitHub/LinuxCNC certainly has a lot going on including "issues". Let me ask some questions there about helping.

Thanks,
Tom

From memory the arduino is connected via a USB serial port so it’s very limited.

If you are looking at small form factor x86 based boards the Odroid h4 is probably worth a look. I’ve been using a h2 for years now, one of the good things about it is the dual Ethernet ports.

If your interest is in kernels and the pi 5, the Linuxcnc builder (for the Pi 5 and 4b)
github.com/LinuxCNC/rpi-img-builder-lcnc
Is a fork of my repo
github.com/rodw-au/rpi-img-builder-lcnc/tree/linuxcnc-2.9.3
Which in turn is a fork of
github.com/pyavitz/rpi-img-builder
with Linuxcnc and the PREEMPT_RT kernel installed

Note the builder cross compiles on a normal PC and builds the official Pi kernel, then wraps Debian around it before installing Linuxcnc and a few other goodies in this script github.com/rodw-au/rpi-img-builder-lcnc/....3/files/userscripts

I got as far as merging the latest upstream code into my  master over Christmas but have not pushed it to my 2.9.3 branch as the default kernel has rolled forward from 6.1 used by Debian Bookwoem to 6.6
It's quite a business finding a Pi kernel commit that agrees with the PREEMPT_RT patch kernel version. 
The latest upstream source now supports the 6.12 kernel so it would be good to build for it as there is no need to patch the kernel anymore
ref: github.com/rodw-au/rpi-img-builder-lcnc/.../patches/userpatches
(but you still need to set the fully preemptible kernel in  menuconfig)
Cornholio has asked in another thread for changes to config.txt to support spi so there is a nice kernel related project here.
 

Just created a Pull Request for the change required. So hopefully that can be ticked off the list.