I'm trying to write my own "GUI" frontend to emc2. All it would do is take a gcode file as one argument and pass along the relevant commands to emc. in writing this frontend, would it work if I simply transplanted the sendProgram* procedures from emcsh.cc?
well, there's a lot to the machine other than g-code
machine on/off, estop on/off/reset ...
execution mode: manual, auto, MDI
you'd also want to use parts of the status buffer to see what's happening
is the "emcWaitType" variable the status buffer?
at least in emcsh.cc?
I'm not sure
it's emcStatus I think
You can turn up the debug level and observe the NML messages that are sent as you use an existing GUI to perform the actions you want
emcStatusBuffer / emcStatus are the so-called "status buffer"
I notice that those two are not accessed in either sendProgramOpen or sendProgramRun. why not?
emc/NML isn't a "command/response" system
you send commands down channel, and you find out that they were executed by looking at the status
I think you can wait until the command has been sent, or get confirmation that it was received
oh, I see...emcCommandWaitReceived calls updatestatus
ve7it is now known as LawrenceG
jepler: time to unveil jdi? another person is asking about it now
you want to reply on the list or should I?
nice for low-level use of emc
like a multipurpose axis controller
Wow - cool
jepler data entry
Jepler Data Input
Jepler Did It :)
who is this mario guy anyways ;)
I don't know, but his advice is bad, I corrected him
(politely, I hope)