Mick Thanks for joining in.
I should point out that this idea was formed and brought up me me alone. There has been no internal discussion in linuxcnc. That was the point of this - to gauge interest and see if there are immediate road blocks, such as license, philosophy, or complete lack of interest. I personally don't have the technical programming skill to understand how to do this. If the work is mostly mechanical - I can be helpful. I would guess that a lot of it is mechanical - particularly since you guys support legacy components. I am hoping some more linuxcnc developers chime in their opinions - good or bad. Could you summarizer what was required to breakout the cnc stack from the HAL stack? Thank you Chris M ________________________________ From: schoone...@gmail.com <schoone...@gmail.com> Sent: September 9, 2018 10:27 AM To: emc-developers@lists.sourceforge.net Subject: Re: [Emc-developers] Breakout of HAL/ machinekits's HAL Hi Chris, As my paws are all over a lot of the work you are mentioning (multicore in collaboration with Michael Haberler some years back) and the splitting into HAL and CNC stacks, why not contact me direct to discuss. I think there is scope for collaboration which could be to both our projects benefit, not least from a reduction in maintenance. The multicore work you mention, primarily adds atomic operations and other measures to prevent things like the side effects of multi core, multi cache operations, where values can be updated by one cache before another has finished. Machinekit's HAL generally has hugely diversified from the original linuxcnc, instantiated components for instance which can be added or removed at any time, even in a running system. Because of backwardly compatible measures however, its use is not visibly greatly different. The splitting out of HAL, not only allows the stack to be used for non CNC projects, such as ROS, but is arranged so that installing machinekit-cnc on top of machinekit-hal, brings you back to a fully functioning machinekit again. We are contemplating moving to a 2 package installation and deprecating the original machinekit repo and packages. If you were to split out your CNC stack, which has some features we do not have, with the correct tweaks it could even sit on our HAL stack and result in a fully functioning CNC controller again. Unfortunately we have not replaced NML with zmq, that would be the 'holy grail'. Michael Haberler and Alex's protobuf message headers and zmq (machinetalk) would probably be the way to go there It is something we would be interested in discussing, I am sure. regards Mick _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
