Advanced Search

Thank you for the images. There are a few kernel/driver changes I'll be working around, but the experience was super easy.

Backstory: I tried to upgrade my successful installation, and the pi wouldn't boot, giving the "missing firmware" error. I copied my existing linuxcnc config files using another Linux system. I installed your image on windows. I copied the config onto the new SD card. It booted and nearly all was well.

Thank you.

Like I said before, log in via SSH, wifi it would have to be, run Linuxcnc as you would and if things lock up and SSH is still good start with dmesg then looking through logs.
Also it would be interesting to know if this happens when using axis.
A lot of the investigation will have to be done by yourself.
Obviously it's not a complete machine lockup, as you reported your pendant can still be used to move the machine, so Linuxcnc is able to receive and transmit to your mesa card.
What happens when the machine is left idle without a Linuxcnc session running ?
If are unable, unwilling to address the queries in this post and my previous post I'm afraid I can't offer any help.

I used the image from this page. The only other thing I added was Filezilla, to transfer files to and from my PC where I generate the gcode files.

And yes, pressing Ctrl-esc brings up the main rPi menu where I can select to run other applications. If I have LinuxCNC up, I can use that to launch Filezilla without exiting LinuxCNC. That functionality has to my knowledge always existed in the image.

Is this OK or any better idea?

One thing you can try is logging in via ssh, before things lockup, and when they do see if anything untoward shows up in dmesg or any of the other log files.

Does it occur when just running one of the sims from the Linuxcnc menus.

Are you able to use a config that uses Axis, if so does this give the same problems.

Just to confirm your are using one of the images from the downloads page, without an extra packages installed, cos I'm not sure if ctrl-esc gets the task manager. On the RPi5.which is the same apart from the kernel support, it doesn't bring up a task manager.

Before the title was changed, it was mainly to do with the Linuxcnc images, not Linuxcnc on Raspberry Pi OS.


Tommy if you see this can you change the topic heading so it reflects this is support for the Official Linuxcnc Rpi Images, I didn't intend for it to support Linuxcnc on the Raspberry Pi OS. That should be dealt with elsewhere.
I'm pretty sure the original tile reflected that.

I have a second Pi 400 on my Ham Radio station, so I switched the two keyboards and fired up LinuxCNC on the "new" board.  I let it sit for awhile trying to duplicate what happens.  Basically the display becomes unresponsive to anything.  The cursor moves around, but I cannot select between pages on GMOCCAPY. However I can still jog the machine around using my pendant, so It is still communicating with the Mesa 7i96 board. Also I cannot ctrl-Esc the Pi to access the task switcher, so something is locking up. 

Sorry, did not think it would affect the whole thread.

I think Scotta did some work with the Pico. Might be worth a look.

github.com/scottalford75/Remora-RP2040-W5500

i have options to push the poll rate even further with PIO&DMA + using the W5100s interrupt pin.I won't be bored for a few days.

i do not post it but i compiled my benchmark to windows also with nearly same results, so the pico is the bottleneck here.

i dont think all functions are able to handled with one pico, i have more time now for testing because the first PCB-s are only shipped on mar.23 and the components is in the coming week.

actually not using PIO now, the UDP data transfer runs on core0 and all io handling runs on the second core, i use the W5100s-evb-pico for the project with the wiznet library (using arduino ide) (for PIO testing i make a frequency generator (later stepgen) and send velocity from 1 of linuxcnc joint to it, it makes 2Mhz signal but dont have a fancy scope to find its jittering. Shock settled on my face, and a small smile appeared at the corner of my mouth when I saw the signal on the scope.

Looks promising. Many LinuxCNC hardware interfaces run at 1kHz, and that works fine for most purposes.
Are you using the PIOs to handle the communications? Maybe there are gains to be made there?

Does the Pi-Pico handle UDP natively?

i make another test this time with raspberry pi4 (4gb)
 

Hi everyone,
I recently ran a benchmark test on my LinuxCNC setup to measure the data request speed, and I thought I’d share the results with you all. I’d love to hear your thoughts or any suggestions for further optimization!
The setup was connected as follows: [Linux 4.19.0-27-rt-amd (core i5) PC (3 byte send 5 byte receive)] -> [switch (TL-SG1005D)] -> [W5100S-Pico]. This was a non-realtime throughput measurement, and the result I got was a stable 2500 requests/second, which I think is pretty solid. I’m curious about your experiences—has anyone else done similar benchmarks, and what do you think of this performance?

Thanks in advance for your input!