Advanced Search

Seems to align time wise:

forum.sheetcam.com/t/the-end-is-nigh-well-sort-of/7103/8

Though looking at the “not sell it to someone who will milk it for what it’s worth” reply, I’m not sure that goal was realized.

My money is on Langmuir, seeing as they sell it on their website …

All good things come to an end I reckon.

Is this the Machine Kit you refer to:

www.machinekit.io/

I'm sorry, what am I supposed to find in that thread? I don't have any questions about the LinuxCNC-provided image and never had. I came here to report a broken dependency in the apt repo, not to ask how to run LinuxCNC on an RPI.

Just to be clear, I have seen that thread, it is kinda hard to miss, and I've played with the image. For my personal preferences, I've decided to go with Raspberry Pi OS instead and I'm totally happy with it. What are we even discussing at this point?

I agree it looks to me like someone bought them. I wouldn’t be surprised is it’s Langmuir Systems. The whole feel of the website, etc changed.

What a shame for the community but good for Les I guess if he wanted to move on from it.

Like I said there's a large thread covering just about everything related to the RPi image, wifi works fine by the way even better when the power saving is turned off. And there is even a sticky thats an index to that thread with the intention being topics are grouped together.
But sometimes I wonder why I bother sometimes.

I'm converting from Masso to Linux so while I have a working machine, it's not working on Linux

You should start with Axis GUI first, till you get the machine working properly, then switch to any other GUI.
You can freely ignore this if the machine is working.

f355 wrote:

I'm sorry if that came out sounding arrogant, that was not the intent. I totally understand why Tommy suggested apt update, I just wanted to quite literally save his and my time.

Writing is an inferior way of communicating for humans as it lacks the visual and auditory ques humans are used to, hence very often misunderstood.
BTW, i wrote a reply and promptly deleted it, as it was not obvious till you look at the version numbering, and back then i did not look, i just shot off the hip as that is usually what you get on a new install without updating first.
Thank you.

I'm sure I paid less than 100 Euro for my v7 license.

From their website: "SheetCAM v8.0 will launch at an introductory retail price of $279." So yea, it seems like the price bump is for version 8. I'm not seeing anything that justifies the increase in the promotional video. Kind of makes me wonder if they got bought or if someone else is running the company and trying to capture more value.

SPI works fine, it is in fact what I'm using - my little pet project is here , it is basically a rewritten Remora for a particular off-the-shelf machine. The servo latency is alright too.

I'm not insisting my approach is better for everybody, I just found it easier for myself to write a few shell scripts (install.sh and linuxcnc/pi_init/ in the repo) that set up things on the stock RPi OS image. The official linuxcnc image might have ssh enabled, but the wifi is not, or at least I couldn't find a way to configure it with my SSID quickly, and connecting Ethernet is about as much hassle as connecting a display

@Andy
Not too sure where to add this, but the Trixie repo doesn't contain the host2-firmware.
Found this out whilst build a test Trixie ISO.

That's ok mate.

What I found with the RPi Dbeian kernel is that it didn't allow for overlays, so things like SPI were an issue. There's quite a few customisations for the RPi compared to a "vanilla kernel".

The official image, which gives an easy way to start for most users, uses a kernel built from the RPi github sources and configured for real time. It took a bit of time to find the "right kernel" from their sources, but eventually it was found and the image was an easy task from there on in.
There's quite a large thread with the first post explaining what it's all about. And as ssh is enabled out of the box you technically don't have to connect a keyboard and Display.

Yeah, no love. I'm going to go with QTDragon instead.

I'm sorry if that came out sounding arrogant, that was not the intent. I totally understand why Tommy suggested apt update, I just wanted to quite literally save his and my time.

I can certainly build it myself, or use 2.9.4 that works just fine for my purposes, or whatever. I don't have a problem, LinuxCNC has a problem, and being unable to fix it for everybody, I'm reporting it here in hopes that someone blessed with permissions does that.

Raspberry Pi OS Lite doesn't come with a desktop environment or a window server pre-installed, so I'm free to choose what to use (XFCE obviously lol). PREEMPT_RT kernel is available as an official package from Raspberry Pi debian repos these days and works fine. I'm not sure what the "official" linuxcnc raspberry pi image would give me at this point, and it is much harder to use for me personally - it requires me to connect a display/keyboard, for example. As to libgpiod or axis, I don't use either so I can't say anything about them.

With your 20 years experience if you really want 2.9.5 on arm you can always build it yourself.
As for the version differences that will depend on the system the packages were built on.
Was there any reason, apart from the official arm image being based on Bookworm, that you went with Raspberry Pi OS Lite ?
Does that give you the choice of Wayland or X11.
Look we get a lot of users with varying degrees of Linux Experience, as we can't tell your experience usually we start advice with the basics. So no it's not a waste of time starting with said basics.
From memory when I attempted to build an RPi image based on Devuan, based on Trixie or maybe unstable, there was an issue with the libgpiod library. At the time the libgpiod driver would not compile against version 2.0 so I abandoned that idea due to that. As far as I know I'm unaware of that situation has changed. Bear in mind that there are some issues that affect Axis in 2.9.5 and 2.9.6 that have been well reported on the forum. It would appear they have been resolved but looks like we need to wait for a 2.9.7 version.