>My work on this will continue, initially getting the required network
>code in place for both TCP and UDP connections and also the Redis base
>to handle the distribution of Cmd, Status and Error data to where ever
>it is needed. Once that is done change my routing commands away from the
>NML remote TCP ports into the newly created TCP server ports for further
>testing and evaluation and development of any additional code
>requirements. The same for status and errors.
Do you mean linuxcnc would NML into a redis database and then network out of
redis?
A couple of things come to mind that I run into as a UI builder:
How does HAL fall into this? Many things the uis currently interact with are
HAL related.
Error handling is terribly difficult. The 'consumed' error messages make it
very difficult to detect errors and act accordingly, particularly if you have
multiple ui sources.
The fact that linuxcnc doesn't have an internal memory of say jog rate, means
every ui has one, yet unless you use HAL you can not communicate between uis.
This is what I think you mean by 'python based addons' we worked around this in
qtvcp and gladevcp by adding jograte to python's status module. Mostly because
linuxcnc and NML are too big of a black box with no docs/examples.
Can your proposal help with the 'no docs blackbox' problem too? Redis is
certainly mainstream.
Chris
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
