Advanced Search

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.

Ok the description is a little vague.

I don't think a clean install will "fix it". I don't think an update would have anything affect as the kernel,kernel modules and firmwares should not be touched during an update. In all honesty unless you are wanting to update Linuxcnc, there shouldn't be a need to do an update, most updates are just minor fixes that really don't affect the way Linuxcnc operates. The biggest "security threat" to cnc machine is someone getting physical access, and it would be the machine it self I would be the most worried about, blood gets everywhere, it's hard to clean and the injured party may want to blame you. I only will have wifi on when transferring files to the cnc machine, other than that I disconnect wifi.

I think you maybe experiencing an issue similar to what is discussed in this thread. Which it would is not Linuxcnc related, it's the ethernet port going to sleep/shutting down, tho it should be tx\rx ing packets more or less continuously. Yes I know it's a direct connection from the Pi to the Mesa card and the thread mentions switches a few times.
forums.raspberrypi.com/viewtopic.php?t=305820

It seems to be somewhat random to which boards are affected but I haven't noticed this on my RPi400.

Tho it might be an idea to check the power supply for the Pi & the mesa card. But if ti was the mesa card "dropping out" you would get notifications.

I installed LinuxCNC onto a RPi 400 with a touchscreen and GMOCCAPY. It works very well, but something has changed on the system and it is now unstable. LinuxCNC, is locking up after periods of inactivity. Running a Mesa 7i96 board. Wonder if doing another clean install will fix it. Might have had a bad update along the way. Will let you know what I discover....

Hi everyone,I've started developing an I/O board using the Raspberry Pi Pico. The prototype will feature 8x 24V outputs and 16x 24V inputs, communicating over Ethernet UDP with a real-time HAL driver. If everything works well, I plan to develop additional boards with step generation, analog outputs, and encoder inputs.At the moment, things are still evolving—I'm currently having the first batch of 5 PCBs manufactured and have already ordered the necessary components. Communication between the Pico and the real-time HAL is already working. :)I'll keep you updated as the project progresses!

Wifi setup is by running

Be sure to edit to choose option 5 "Edit wpa_supplicant" with your country code, ssid & password.

To setup network for a mesa fpga Ethernet card, choose option 6 "Edit interface" and modify eth0 to match post above if you have jumpered the board for "FIXED FROM EEPROM"
If you have jumpered for "FIXED 192.168.1.121" replace 10.10.10.100 with 192.168.1.100.

If your home wifi network is on the 192.168.1 network, use the 10.10.10 network for your Mesa card, refer to you card's manual for jumpers to change.

After config reboot
To check the network type in a terminal
Taken from 7i92 Manual

A final note, there is no network notification applet for the desktop, so you will not get any notifications when the network connects, disconnects or reconnects.

I am new to linuxcnc and I cannot get my Raspberry pi running linuxcnc to connect to wifi or to my mesa 7I92TM board. I tried ip a but the mesa board is not showing have looked everywhere online and read multiple forums but can't seem to find a proper solution to my problem. Please help.

Funny thing is, the Mesa 7c81 and a stacked RPi look like a more compact solution.

NVME would be nice, the RPi5 with a NVME drive is blazingly fast.


Did you stick with the Mesa fpga pin to 7c81 layout ? Or did you change it to make routing easier ?

If you change things around, especially the clock signal, the SPI_CLK for comms is a little tricky to work out to begin with.

Sorry don't mean to add feature creep, man I wish I could design a simple board for the KSZ8851 Ethernet chip for my mesa clone thingy. So hats off to you Old Chap.

I have this one, used on my mill with a PC platform: Expensive
Planar Pct 2235 22" 1920X1080 Full HD Touch Screen VGA HDMI DISPLAY PORT USB

For the RPi5: Cheap
www.ebay.com.au/itm/225953008741

I would assume if the touchscreen interface is USB you should be fine. Tho the raspberry pi forums maybe a better resource, just look\ask for usb hid compatible touchscreen, stipulate USB HID is the only option.

The serial steppers are nice because they are easy to setup and they are also very quiet. I dont know if there is an fpga firmware for it thought. The SPI ones, someone has done a custom firmware to work with those.

What is W13 doing? Is it just for swapping between the usb or the green connector?
Consider adding a jumper that can disconnect power to the FPGA or separate the 5v rail between FPGA and RPi5. I found it convenient having a separate jumper for that, incase you needed to either separate the power between the 2, or if you need to reset the MCU/FPGA, you dont need to turn off the RPi

When you are done will you post the design on that easyeda website so I can clone it to modify it? Im also hesitant about a 1 board thing, but I wanted to make something with a swappable MCU/FPGA , and the formfactor looks pretty decent sized.

Thank you guys for the interest and the suggestions! I will try to respond to a few of them here:

"I have occasionally thought that there should be a niche for a similar board, but with on-board stepper drivers (Trinamic or some other serially-controlled driver)
That would, of course, need a dedicated HAL driver, but those can be surprisingly straightforward."

I was actually planing on designing a seperate IO Board featuring the Trinamic 5160 Drivers, as they would allow me to run high current stepper motors. They come with UART and SPI interface functionality but I haven't really seen an advantage in interfacing them serially. Maybe someone has a good argument as to why it would be worth it to go through the integration troubles?

"I like having the boards seperate, just in case my butter fingers cause one the voltage translation chips to blow a smoke valve and damage the PCB."

That was my thought process as well. I'm a little hesitant to put everything on one big PCB, as i feel like that would make errors more catastrophic. I also like the modularity of having seperate PCBs, especially in these early prototyping stages. I did actually bring the JTAG out, but realize that better labeling was neccesary, which I've since added.

"I am liking the look of this board. Did you do this in easyeda?
Suggestion, add the rpi 40pin header. Aside from being able to add stuff rpi side, I find it valuable for debugging the MCU/FPGA side of the board using a regular rpi without having to keep removing a cm module and you can use it as a backup incase you damage the 100pin hirose connectors or theres another RPi/chip shortage"

Yes, I did do this in EasyEDA. I started the project with EasyEDA becuase I foud the integration with the JLCPCB services appealing.
Including the 40pin Header is a great idea, which I will definitly add. Unfortunatly that will require major rerouting. Before rerouting everything I will continue collecting and thinking about additions/optimizations. That way I'll hopefully save money on design itereations.


I'd love to here if you guys have any other sugestions. The design philosophy behind this board is to make it the Compute Module 5 version of the Mesa Electronics 7c81, and I will probably finish this project making exactly that but I'm also open to brainstorming other ideas for potential future projects.

Thank you everybody!

I'm also designed a mesa clone for a Raspberry Pi, currently in the process of testing everything.
Except for the reversed Sserial Pinout it looks like I got everything right.
You can take a look at my schematic for reference: github.com/jstjst/stmbl-fpga-master/blob...tmbl-fpga-master.pdf
Be careful the SPI In Out labels in the 7c81 schematic are reversed compared to the ucf file. Luckily I could fix that in the ucf file.
I routed some signals under the fpga, I see no problem with it. But try to have no completely hidden tracks so you can fix them if you got some connections wrong. In my opinion one of the more important things is the placement of the decoupling caps.

There are some pitfalls with the whole (fpga) programming (especially when using the Ethernet host interface). But with some reading through the forum I got everything pieced together, including recompiling mesaflash and linuxcnc. So it is totally doable (for reference, this is my first deep dive into linuxcnc and mesa/hostmot2, only used the RPi GPIO interface before, didn't use/own a mesa card).

Big thanks to Peter for providing the schematics and all the information that is on the forum!