Advanced Search

Correct, they are visible under /dev/

It is PREEMPT_RT

enabled RT when building.

With regards to the RPi5 images Rodw linked to a new one on his google drive that seems to fix the screen issues. This is the one I used recently with my RPi5.

If the SPI interface isn't enabled mesaflash will give
open: No such file or directory

So I would guess the SPI interface has been enabled and the nodes created under the /dev directory.

The kernel is not going to work anyway since its not realtime

The way I built my RPI5 test system was that I downloaded the RPI5 image
from the LinuxCNC website:

www.linuxcnc.org/iso/rpi-5-debian-bookwo...23-11-17-1520.img.xz

Installed it and then built linuxCNC master from source.

I wonder if something in config.txt could be an issue also... (since the cable and 7C80 seem to work)

On a lathe the m codes for a Main spindle are m3,m4 and m5. Fwd,rev,stop

if I had a second sub spindle what are the m codes for those?

thanks john

Could be. Looks like it could be a self built kernel, there are a couple of options relating to the real time kernel built.

Be interesting to know the origin of the installation. To get the hm2_spix driver I think you still need to build from source as the Rpi packages seem to have a July changelog.

Note: Using POSIX non-realtime

Is it possible that this is a kernel issue?

Hello Paul,

Also have a MH600W, although mine is a bit older with the 432/10.

Did you try manually updating your version of mesaflash by downloading and compiling directly from the github repository? Instructions are directly in the readme.MD

github.com/LinuxCNC/mesaflash

sorry guys,

I'm not sure what i'm doing at the moment. Feel like a lost sheep.

Anyway.



When i get in, this is what i see, note the plank page where there should be a drawing.

I can't get the estop to unload to engage power.

Where should I start from? wipe everything and try reloading it all again?