Communication solution on my own CNC Machine

I am aware that the io management I mentioned is not real time. Does anyone have any information about the size of this job? My goal is not to convert a huge vertical machining center, but to make my own hobby machine by sacrificing some real-time features. I'm wondering if it's possible to do this with ordinary non-realtime TCP packets. I think there must be a solution between simple grbl builds and "superior" mesa builds.

Two computers very close together can exchange data between them very quickly, although not in real time. What are the challenges of driving axes with this data? I want to discuss this.

I wonder how possible this could be. My conclusion from this topic is that I can only approach the idea of using this solution as a simple handheld terminal or keypad.

Once again, I want to know "to what extent" this is possible. Will there be a huge millisecond delay or momentary drops? Will a communication not in RT mode suddenly crash? Or could using a hobby machine at low speed and acceleration with a few milliseconds of delay be "instantaneous enough"?

Most importantly, can anyone explain how to send these pulse signals as ethernet packets with Linuxcnc? Please don't worry about the real time. Maybe I'm making a turtle feeding device, you never know slow but how slow? I want to know this.

You’re building a fixed gantry router to process aluminium of about 600mm x 400mm.

So no you’re not building a turtle feeding machine.

I think your best solution is to ignore all the advice you’ve been politely given and go and do it your own way. It may work it may not.

srknyxl wrote:

Most importantly, can anyone explain how to send these pulse signals as ethernet packets with Linuxcnc?

github.com/LinuxCNC/linuxcnc/blob/master...a-hostmot2/hm2_eth.c

forum.linuxcnc.org/18-computer/42414-lin...sing-esp32?start=130

It seems like they managed to do what I was thinking of doing in real time stably at 100khz with esp32. As a newbie to LinuxCNC, what I was trying to learn here was to send data from "hal" to udp.

Real-time packets can also be processed by a single-board computer with 64MB of RAM. this should be possible. But even an esp32 with a 200 mhz processor and a few mb ram can do this. I just learned this.

I think this solution is a low budget, real time solution. What are you thinking?

srknyxl wrote:

What are you thinking?

I am thinking i should stop watching MythBusters on youtube and go to the shop as i have 2 of 3D printers running 24h for several days now, i need sleep, just had popcorn, been working for 4 days on building another Voron 2.4R2 printer and i am close but having to shove 2 control boards with power supply and a huge amount of cabling inside a small box is to much work.



Back on topic, i am thinking you did not do your homework before asking and you are asking the wrong questions, so here is a summary :
LinuxCNC can work with
-parallel port
-ESP32 -there are two separate projects with this on this forum
-ESP32 through ethernet
-3D printer boards using SPI and RPI3/4/5
-3D printer boards through ethernet, i think
-NVEM boards through ethernet
-quite a long list of EtherCAT equipment
LinuxCNC will not work with
-mach3 boards through USB
-ESP32 and Arduino through USB, although this has been done several projects here for real time and non real time applications
LinuxCNC can control almost any machine you want to invest the time in.

I was actually looking for such an answer instead of memorized "mesa" part codes

Can you share links to ESP32 projects?

I hope you got some sleep and were able to fit a large amount of cable into the small box. Because I need to learn a little more to start asking logical questions