Advanced Search

@cornholio:
Thank you for the reply.
"Have you tried htop when running gcode and actually running a machine ?"
No, so far I only did "dry-tests".
I plan to retrofit a EMCO F1 CNC Woodworker. For this machine I bought a Benezan Tripple Beast ( a long time ago...). My plan is to set up LinuxCNC on a Raspberry Pi 5 to control the Tripplebeast.
My last machine was a portal router (DIY) that was (still is) controlled by DC-Servos with UHU3.0-controllers that I build (also a very long time ago)

Regarding the RP5: I hope I can find time to test the setup on the bench next week.
When I have news, I'll post them here.

Than you for your help.

Don't worry about it.

Everything will work fine when running a machine.

Have you tried htop when running gcode and actually running a machine ?

You can modify the isolcpu parameter, it's under the /boot folder in a subfolder, mind tho the boot folder has a different structure to the standard RPi one. It's been a while since I've used my RPi5 since helping Rod put the image together (due to the lack of a SPI driver for Mesa hardware).

Long story short latency will suffer without isolation. And depending how cache is shared between the cores there can be a performance hit by isolating the incorrect pair of CPUs (this was from a long forgotten paper). At the end of the day it's not outright performance this is vital with Linuxcnc but latency. Having a responsive interface and more importantly having latency within spec is all that matters. It's not as if you'll using the machine as a desktop whilst running a machine. Remember it's a single use computer, not a desktop.

Play around with isolating CPUs run some latency tests and see how you go. BTW what hardware are you using to control your machine.

Even on a multi core machine with no cpus isolated if the load doesn't require it you will have cores that are more or less idle.

The third CPU (Number "2") of the Raspberry is not running.
LinuxCNC ("realtime stuff") only uses Core Number 3 (the fourth)

Is there something that can be done to use both Cores (Number 2 and 3 = third and fourth) for LinuxCNC?

2 cores run the day to day stuff
2 cores run the real-time stuff

Without isolating 2 cores latency takes a hit. It’s a common fix for latency on all platforms.

Hi,
I used this image: rpi-5-debian-bookworm-6.1.61-rt15-arm64-ext4-2023-11-17-1520.img.xz
to set up a Raspberry Pi 5 with LinuxCNC.
So far it worked fine. Thanks a lot to all the people that put this image together!!

Now I discovered, that the third CPU (Number "2") of the Raspberry is not running. When LinuxCNC is started, using "htop", I can see, that the third CPU has no load, it is idleing. In the cmdline.txt there is this entry: isolcpus=2,3 and it seams, that LinuxCNC only uses the fourth (Number "3") CPU.
Is there something that can be done to use all the computing power of the Raspberry Pi 5?

Hi everyone,

I'm currently working on setting up an EtherCAT master on a Raspberry Pi using LinuxCNC. I've followed the steps for installation and successfully detected slaves. Specifically, I've connected an EK1100 and an EL7-EC400F driver.

However, upon proceeding with the setup, I encountered an error related to "lece_conf failed." I've made changes to the XML file as per the instructions provided.

Could someone please assist me in troubleshooting this issue? Any insights or suggestions on resolving the "lece_conf failed" error would be greatly appreciated.

Thank you for your help!

Hi No I have not make any progress but i conekt a home switch to my Gpio pin for spindle index and when i click manualy on the switch the reading moved a bit , when I click fast i reach 60 rpm o the display so I think the problem is in the filter for the signal , i have to optical sensor and there are signal from both index and fase a, so my problem is to find the value for this part and if anybody can help me sort it out i be very happy ./krister

Thanks for the pointer - updates are disabled

In the meantime, I managed to put a new RT kernel on: looks much better, right?
I followed the github.com/by/RT-Kernel instructions - probably not ideal as you, but I avoided a reinstall (and it's kernel 6.9.1 :D)...

Mehta_123 wrote:

how to hand edit input output (GPIO) in hal and ini? 
please give me one example.
Thanks!!!!!
 

I am not sure if I undestand your question correct; but:
The *.hal and *.ini-files are plain text-files. you can edit them using any editor (notepad++ for instance).
I attached an excample for a *.hal- and *.ini-file. These excamples are for a RaspberryPi5 using only the GPIO-Port (useing the "Generic driver for any GPIO supported by gpiod" described here: linuxcnc.org/docs/stable/html/drivers/hal_gpio.html)

I hope this is helpfull.

I have a raspberry pi5 and this is the code of how I started the SPI communication of the RPI5 - TangNano9K. (Not yet machine tested)

OS: 

• LinuxCNC 2.9.2  Raspberry Pi 5 OS based on Debian Bookworm  Raspberry Pi 5 Uspace compatible with Mesa Ethernet and SPI interface boards.

In /boot/broadcom/config.txt check is SPI is enabled (reboot if not)

# uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

In /dev/
Check do you have listed spidev0.0, should be!

In RIO.h define:

#define TRANSPORT_SPI5

In RIO C add lines:

#ifdef TRANSPORT_SPI5
#include <linux/spi/spidev.h>
#include <sys/ioctl.h>
#endif

/***********************************************************************
*                STRUCTURES AND GLOBAL VARIABLES                       *
************************************************************************/

#ifdef TRANSPORT_SPI5
int spifd;
static uint8_t mode = SPI_MODE_0;
static uint8_t bits = 8;
static uint32_t speed = 1500000;
#endif

/***********************************************************************
*                       INIT AND EXIT CODE                             *
************************************************************************/

#ifdef TRANSPORT_SPI5
    rtapi_print("Info: Initialize SPI5 connection\n");
    spifd = open("/dev/spidev0.0", O_RDWR);
    if (spifd < 0) {
        rtapi_print_msg(RTAPI_MSG_ERR,"Failed to open SPI device\n");
        return -1;
    }

    // Set SPI mode
    if (ioctl(spifd, SPI_IOC_WR_MODE, &mode) == -1) {
        rtapi_print_msg(RTAPI_MSG_ERR,"Failed to set SPI mode\n");
        close(spifd);
        return -1;
    }

    // Set bits per word
    if (ioctl(spifd, SPI_IOC_WR_BITS_PER_WORD, &bits) == -1) {
        rtapi_print_msg(RTAPI_MSG_ERR,"Failed to set bits per word\n");
        close(spifd);
        return -1;
    }

    // Set max speed
    if (ioctl(spifd, SPI_IOC_WR_MAX_SPEED_HZ, &speed) == -1) {
        rtapi_print_msg(RTAPI_MSG_ERR,"Failed to set max speed\n");
        close(spifd);
        return -1;
    }
#endif

//Edit rtapi_app_exit function, add close(spifd)

void rtapi_app_exit(void)
{
    close(spifd);
    hal_exit(comp_id);
}

//In fuction void rio_transfer()  near end of it add: 

#ifdef TRANSPORT_SPI5

    struct spi_ioc_transfer tr = {
        //.tx_buf = (uint64_t)tx_buf,
        //.rx_buf = (uint64_t)rx_buf,
        .tx_buf = (uint64_t)txData.txBuffer,
        .rx_buf = (uint64_t)rxData.rxBuffer, 
        .len = SPIBUFSIZE,
        .speed_hz = speed,
        .delay_usecs = 0,
        .bits_per_word = bits,
    };

    // Perform SPI transfer
    if (ioctl(spifd, SPI_IOC_MESSAGE(1), &tr) == -1) {
rtapi_print_msg(RTAPI_MSG_ERR,"Failed to perform SPI transfer\n");
        //close(spifd);
        //return -1;
    }

#endif

//Save and do hallcompile...
 

I'm not familiar with the Parallel Pi Hat but looking at the config files in this post it seems to me that you may need to load a gpio component to get it working. I'm not sure that the StepConf Wizard does that for you.
forum.linuxcnc.org/9-installing-linuxcnc...i-5?start=180#297833

I have been using G-code sender with a FluidNC board successfully.  Decided to give LinuxCNC a try.  Current setup is Raspberry PI5 to a Byte2bot parallel port RaspberryPI Hat to a generic 5-axis breakout board.  Connected a DM556T digital stepper drive from Steppersonline to Nema23 motor.  I followed the instructions on creating a setup using the LinuxCNC Stepconf Wizard then replacing the hal file with the one downloaded from Byte2bot.  When I get to the motor test screen the motor doesn't jog.  I've tried several other setups for machines, Sherline, Tormach, ...  So it seems my software configuration is not setup right.  this forum has a lot of discussion areas.  Which would be the best to start a conversation about trouble shooting my setup issue?  I've watched too many videos and read a lot of documentation files that have not yield a good result.  Appreciate some direction.

It looks like the answer might be the Wayland version of xrandr, wlr-randr.

This is based solely on forums.raspberrypi.com/viewtopic.php?t=357766 and I don't have a Pi to hand right now to test.

At a glance a MDR and LRS Meanwell have similar specs with the LRS being cheaper.  Din rail mount is nice, but I'm trying to keep cost down.  

Any technical reason not to use a RS or LRS PSU for a Mesa board and Raspberry Pi?

StoneB wrote:

Hello all, 
first thanks so much for building this image - it really works nicely (although I still need to get my touchscreen working but assuming this is just a driver issue).

The main question I have before connecintg and configuring a MESA card is that my latency looks decidedly wrong - I am wondering if I have the RT kernel enabled at all? When I make uname -r, I get this, which doesn't mention RT:
6.6.28+rpt-rpi-2712

All I did was load the GDrive image a few posts ago, and run a update && upgrade.

Is there any way to check and correct?

 

Blindly running an update is not a good idea.

The easiest way is to reflash the image. The kernel really should have been "pinned" to prevent updates. The RT kernel is a "custom" one.
So you really shouldn't be updating, it's fine as is.

If you are the type that "must update" read this
www.snel.com/support/how-to-block-packag...l-updates-in-debian/