Advanced Search

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!

 

Fixed title.

unknown wrote:

Dude please don't change the subject, it makes things hard. I check this thread regularly.

I think it is useful to change the title from
"Linuxcnc & the Rpasberry Pi"
to that 
"Linuxcnc & the Raspberry Pi"

Dude please don't change the subject, it makes things hard. I check this thread regularly.