LinuxCNC on Raspberry Pi 5

Pleas use Balena Etcher instead of the Pi Imager if you can't burn an image. It is much more reliable

Thanks for getting back to me.

I wanted to that that I got the image to burn onto a card through random internet searches / and re-try's. I'm sure we are all familiar with middle of the night stubbornness. LOL

Once burned the image seemed quite quite good to me with the caveat that my next step will be to get my 7i95T board configured so I haven't yet tested end-to operation.

I used saved versions of all the raspberypi.org and raspbian.org config files for apt including the keyring files that are needed. So it was quick to update/upgrade/apt install a reasonable collection of Pi specific config tools.

So thanks for making that image available.

I do have a few questions/hopes about embedding some of those tweaks into the Pi 4/5 specific IMG's.

1) Include the Pi specific APT/PGP files on the conditional build you are using for the Pi.

2) Include the core Pi executables as well with serious bonus points for adding those to the default app-lauch UI like is being done for LinuxCNC.

Those two things would substantially reduce the newbie headwinds for those that are either new or rusty on Linux.

Thanks so much for all your work!

Richard

The builder we have forked is based on Debian, not Rpi but we do fetch and build the Rpi  kernel from source.
That way you get the best of both worlds.
Linuxcnc is a Debian application so all the menu features are installed from Linuxcnc deb files.
Its not intended as a generic Rpi installation so it won't include any standard pi applications which could add additional latency.
 

Just checked out your new image that you linked a couple of posts ago. Video works ok when using min hdmi to DVI adapter.
Just for those of us that are a bit silly what is the correct procedure & values to setup
1: LANGAUGE (currently unset)
2: LC_ALL (currently unset)
LANG = "en_AU.UTF-8" is fine.

Currently starting to test the new hm2_spix driver

Thanks, that image was prepared by James Walker (Joco) one of the qtpyvcp developers.
All of these features can be set using sudo menu-config which brings up this menu.

 

Doesn't have an option for setting LANGUAGE.

Had to use
Then log out and login for it to take effect.

The default  settings come from userdata.txt github.com/rodw-au/rpi-img-builder-lcnc/...9.3/userdata.txt#L40
I.m not sure LANGUAGE  needs to be set for the locale if its en_US.UTF-8 as we use for the default config 

On my chrome book,  locale reports
rod@penguin:~$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

On my Debian PC in my office, I get 
rod@debian:~$ locale
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
LC_CTYPE="en_AU.UTF-8"
LC_NUMERIC="en_AU.UTF-8"
LC_TIME="en_AU.UTF-8"
LC_COLLATE="en_AU.UTF-8"
LC_MONETARY="en_AU.UTF-8"
LC_MESSAGES="en_AU.UTF-8"
LC_PAPER="en_AU.UTF-8"
LC_NAME="en_AU.UTF-8"
LC_ADDRESS="en_AU.UTF-8"
LC_TELEPHONE="en_AU.UTF-8"
LC_MEASUREMENT="en_AU.UTF-8"
LC_IDENTIFICATION="en_AU.UTF-8"
LC_ALL=

 

Perl complains if LC_ALL or LANGUAGE isn't set.

Why on earth are we using perl in a Linuxcnc project? What's wrong with Python? At least its supported by the project.

Debian dpkg-buildpackage uses perl, perl complains when running menu-config without LANGUAGE set.

So perl hasn't anything to do with Linuxcnc but when building packages, I had to build linuxcnc to have the hm2_spix driver for the Rpi5.