I’m trying to update @keen’s document with a bit more information. I already, before asking this question, added to that document the information about RDworks and LightBurn, which was not in what @keen had written so far.
In addition to that information that I hunted down during my editing process, I wanted to be complete. Meerk40t is new software, and @Tatarize is working on it very actively. If you haven’t been following it, you wouldn’t know that. But he’s made a point of making it somewhat modular, and there are K40-class machines with Ruida, so asking about his current state of implementation and intentions is reasonable for the purpose of updating summary documentation that we’re trying to make complete.
This question was directly asked about MeerK40t in the Meerk40t category, and was not related to RDworks or LightBurn.
My expectation when I asked it was that we might just wait and let @Tatarize speak for himself instead of jumping in front of him and answering on his behalf.
But… I went and looked at the Meerk40t source code, which in LhymicroInterpreter.py says:
LhymicroInterpreter provides Lhystudio specific coding for elements and sends it to the backend to write to the usb
the intent is that this class could be switched out for a different class and control a different type of laser if need
be. The middle language of generated commands from the LaserNodes are able to be interpreted by a different driver
So adding Ruida support, while I don’t see it there today (I read source code in the mean time), isn’t an unreasonable idea for Meerk40t at some point in the future, if the existing protocol documentation is good enough.