@Rda,
I agree with you. And that was the reason to use Thermal Dynamics high def for me.
But how do you send the commands? I would assume that json would be pretty good at sending commands too? So you read states/parameters from the received json and you could also send json messages to change speeds, set states etc.?
Yes, the transfer protocol for recieve and send is in json format. It's just a text string, but then uses a json layout.
EDIT: Sorry if this is confusing but on the server side you would have all the commands etc. mapped.
Yes indeed. You need at least a map or a list. In json we can use an array of Id and Value.
For example you send id="load" value="/home/gcode.ngc"
Or just send the id="run" value=""
Or send multiple id's and value's in one message, i have to test if we can send 30.000 lines of gcode in one message.
Then the client could send json messages to ask the server to do what it can.
Yes. The client can send id="stop value="" or the client can ask to load a mdi command like id="mdi" value="G01 X0 Y0 Z0"
And so on.
But everything from and to the server has to be mapped.
I am now trying out webassembly. This is c++ code compiled into html and java to run on a webbrowser.
Edit, my previous post : i could connect the websocket server to the linuxcnc nml's server in c++.
This is likely not the case, as we can better create a linuxcnc nml client that connects to the linuxcnc nml service or server.
Then we make a bridge from the linuxcnc nml client to a websocket server. This then should work excellent.
We already have the nml mapped, so we know all the command and status channels. It just a matter of coding it to the finish line.
