-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API's missing #35
Comments
Comment by mhaberler After looking at this code (halrmt, linuxcncrsh, schedrmt), my conclusion is: delete it, start from scratch. It is just too bad, no point in wasting time on this. A relatively sane C API is shcom.{hh,cc}: https://github.com/machinekit/machinekit/blob/master/src/emc/usr_intf/shcom.hh it seems that basic API can be retained across the 'no more NML' transition. Going forward, the submission of commands could be based on a zeroMQ/protobuf based RPC (remote procedure call). Operations requiring status retrieval through EMC_STAT will need to be adapted to the new style, and that is still shaking out. But that can come later. restate problem: specify a zeroMQ/protobuf based RPC interface to LinuxCNC. |
Issue by mhaberler
Wed Apr 2 19:56:40 2014
Originally opened as machinekit/machinekit#99
API's should cover programmatic access to core functionality, optionally remote
The core component interfaces currently are:
Axis UI interfaces: axis-remote: specific to Axis and tkinter. Not a general API.
Others: none known
Problem: programmatic/remote access to LinuxCNC is currently utterly inadaequate.
The text was updated successfully, but these errors were encountered: