Hey there, I was wondering the following - and mainly really to understand how LinuxCNC works. Since I couldn't get a proper answer in the user chat I thought I would try here.
IIUC the GCODE interpreter runs in the non-realtime part. It sends the step instructions to a card to execute the steps. This is obvious when using a LPT port, but how does this work via Ethernet? Are the steps compressed into instructions and then applied on the Mesa cards? Poking around it seems like there are motion commands and status commands? So it probably sends "go there" and "where are you" and the card generates the steps required and reports back. Does that sound right? Is there a definition of the protocol to look at? I assume the code of what gets pushed to the Mesa's must be somewhere, too. And now I hope I don't get lynched for asking: How is that ethernet protocol different from the Mach3 ethernet protocol? Are there significant differences between the protocols that would prohibit LinuxCNC speaking the Mach3 ethernet protocol? Or maybe no one knows or cares? But I was wondering if implementing the protocol could be another alternative to flashing Remora to supported boards. While waiting for Mesa stocks to recover, I am really just curious to understand the technical side of the LinuxCNC vs Mach3 comparison. cheers, Torsten _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
