Advanced Search

I've had good luck getting everything to run well enough to get deep into learning and configuring LinuxCNC, Mesa 7i95T and the needed .ini and HAL files.  However, I just ran into my first problem when LinuxCNC errors on start when I configure QtDragon as the interfaces. 

I've already worked my way through several prior fail-on-start situations chasing down reported errors from the usual sources but this one is stumping me because I can't seem to find the actual error in the outputs I'm aware of.I will attach everything I can think of if someone could take a peak and spot what I'm missing.

Thanks

Stop overthinking.
With mesa hardware you don't need a base thread, only a servo thread is required. With that, latency isn't such a huge issue either. Trying to get an extra bit here and there does nothing.
The pre made image Rodw recently linked to is perfectly fine to run a machine, the only exception would be if you are using the RPi 5 spi interface to talk to a 7c81 or 7c80 as this requires a driver that isn't included in Rods image , this is not required for ethernet.
Invest more into learning the ins and outs of hal . This is more important that fussing over software as the images provide what is required, remember the only task these images are meant for is running a CNC machine.
If one reads the online docs one will fine some simple exercises that do not require a CNC machine.

Dear jjdege.
How can you solve the error when you install the ethercat package by command "sudo apt install -y linux-headers-(uname -r) ethercat-master linuxcnc-ethercat?

I read your post and it took a while to sink in how well running the native RaspianOS with the 6.12 kernel for what I want to accomplish.  I'm guessing that 6.12+ might be a real game changer across the board but I remember discussions about certain run-time flags being used to determine if PREEMPT_RT was part of the build and people commented that some don't match up yet.

Do you think that might be a hurdle in the short / mid  term?

Do you think someone familiar with the run-time testing code might already be working on a fix to any of those problems?

I finally feel like my basic Pi5 (NVME boot) / Mesa 7i95T system is basically functional.

I used Rob's link to what I think is his Google Drive to get what I believe is a LinuxCNC 2.9.3 / Kernel 6.6 RT ISO.

Because of being new or very rusty on virtually every level, I wound up stumbling my way through that process relying on the gracious help from the community.

I will attach a number of files for anyone to glance at or comment on if they wish.

Since I know now that there are many choices I should do differently I ordered an inventory of NVME and SD cards to start over clean and also try out other combinations of options without abandoning what I have.

I have a few questions before I start over 'clean':

1) Is the Pi5 2.9.3 ISO that I downloaded (or a newer one) now attached to the link on the Downloads page or is the one I downloaded still the latest?

2) I installed NetworkManager because I was struggling getting my WiFi working for internet access while dedicating the cable Ethernet to the Mesa board. Would it be better for me to avoid NetworkManager this time around?

3) I installed the Raspberry KVM because I thought that it might be useful sometimes, but I have never really used it so far. I'm wondering if there might be some latency implications to its presence or use?

I also included a screen capture for the latency histogram if anyone is curious.

Thanks

I have never used EtherCat with Raspberry so I can't answer you.
However, I read on the forum that others have had a similar problem
(forum.linuxcnc.org/9-installing-linuxcnc...ectory-lib-modules-6 -1-0-25-rt-amd64#310761).
Maybe you can find some useful information there.

Dear elovalvo
Did you install successfully igh ethercat for Rasp 5?
I tried to install, but I got the error.
This error is " modprobe: FATAL: Module ec_master not found in directory /lib/modules/6.6.21-rpi999-rpi-2712"

Hi Scott,First, I want to thank you for your incredible work on the Remora firmware!Two weeks ago, I received my NVEM V5 board and started working on flashing it. Unfortunately, I couldn't find my STLink dongle (seems like I lost it), and I couldn't wait for a replacement. So, I decided to get creative and used what I had available. I flashed an STM32F103C8T6 using a Raspberry Pi Zero W with the "CMSIS-DAP" firmware you mentioned in one of your YouTube videos, using OpenOCD.As you described in the video, I then uploaded the "stm32f103xb_mimxrt1060_qspi_if.bin" to the mass storage device of the STM32F103C8T6, and it seemed to program itself as expected. I then connected it to my NVEM V5 board and dropped the firmware file onto it, but unfortunately, it didn't work.I spent the next three days troubleshooting but eventually gave up and purchased an STM32-Link, along with two CMSIS-DAP Probes (USB-A and USB-C). I received both of these items recently and tried again, but I’m still having issues.The CMSIS-DAP probes aren’t detected at all, neither by MCUxpresso IDE nor PyOCD. The STM32-Link is recognized by PyOCD, but I still can't get it to work as intended.Do you have any suggestions on where I should focus my efforts next? Any guidance would be greatly appreciated.Thanks again for all your help!

Nevermind

I doubt very much whether this would be an issue related to the hm2_spix driver. I would suggest you start another topic related to the qtdragon issue.

With qtdragon I have blank toolpath screen, but it only appearing when exit prompt appear.
I tried with fkms,kms -pi5 etc but without results, regular axis display working correctly.

We don't use it but I have in the past.. Debian do offer an image for the pi
raspi.debian.net//
Its very minimal (command line only), You can build it up to run linuxcnc. Its interesting to read their FAQ page for reasons why they don't include configuration packages and why they don't include a build for the Pi5

Our approach to compile the Pi kernel instead of using Debian's solves some issues but we follow their minimalisitc approach. be thankful we provide menu-config

I concur with Rod, and will also state again that the linuxcnc images are not meant to be daily drivers.
The partition managers and such are not required to run a cnc machine.
Forget about the Raspberry Pi utils, this is a Debian installation, apart from the kernel and overlays.
I’d stay away from anything KDE, there will be libraries and other stuff installed that will be basically only for that particular application. GTK apps will be far lighter weight.
The Linuxcnc images are purely for running a cnc machine, if you need want other programs you are free to install what you want but don’t hope them to be included in the supplied image.

No. The linuxcnc image uses Debian so it uses the Debian repository for all packages.
You can find what is available in APT by checking with the Debian Package Seatch.
packages.debian.org/index
If you want to run PI OS, burn another image from the official  Pi images
None of what you mention is required for a Linuxcnc installation

The image is deliberately minimal because of the limited resources of these single board computers.
 

Many of the choices I made during this bumpy configuration journey were driven by reliance on general Linux configuration information sources as I tried to figure out what problem I was actually having at any given moment.

Since I have an inventory of additional uSD & NVME cards I assumed that as my Linux understanding crept up from the near-zero mark I would be starting over at least once reevaluating those choices targeting a less 'chaotic hackers playground' configuration.

Examples of this were installing both GDebi / Synaptic package managers as well as GParted / KDE Partition managers.

I had no idea in either case which would work best or what I would like to choose in the long term, but when I'm in the early learning phase I always know that there will be outright mistakes and sub-optimal choices to say the least.

BTW, I do get your point about the RPi config tools not being necessary for those who know where to go in the Linux config hierarchy to achieve possibly better optimized results but the installation of those tools could always be rolled up in a script as I suspect their inclusion into the XFce application menu for those at their first rodeo.

Now one last actual question:

Even in the situation where someone was going to take a pass on installing the GUI config tools wouldn't it still be valid for all Raspberry builds to have updated APT sources and PGP / keyrings signatures to enable archive.raspberrypi.com (and maybe archive.raspbian.org).

Please correct me if I'm off the mark but wouldn't that be the appropriate 'deb' sources for things other than GUI config tools. Guessing out loud: firmware, eeprom (etc) and possibly purpose built Pi kernels or OS components.

Just wondering.