I have not been keeping up with machinekit as much as I should, but it does look like they are moving to server/client. Looks like they have moved the UI, task scheduler, RS274 interpreter, and basic machine commands to use API's. Trajectory planner, kinematics, hardware drivers, etc, etc remain on the Beaglebone. If I am reading this doc correctly, I would think that you could program pretty much anything to connect to the API's. Should be OS agnostic where the UI is running. I do know they are doing the development against tablets as I have downloaded that.
Hmm.. there even looks to be a thread for windows machinekit clients.. https://groups.google.com/forum/#!searchin/machinekit/machinekit$20windows/machinekit/fHCykq4nXHA/3VYwQEQAFgAJ If I am reading this correctly, they just don't have a lot of developers working compared to the tablet option. Personally, I have been more interested in an industrial setting whereby I could integrate a lot of systems into a monitoring and tracking system to show where systems are in their machine cycle. If nothing else, then maybe something as straightforward as SNMP traps so that monitoring systems - such as Nagios - could pick that up. Or, a single UI driving multiple machines, which would be possible with an API model - similar to octoprint. With the cost of BBB and similar x86 or ARM systems, linuxcnc as a standalone PC is not necessarily where things will end up long term. (conjecture on my part. I am not involved in an architectural discussions and I'm a weak coder). On Tue, Sep 22, 2015 at 1:45 AM, Gregg Eshelman <g_ala...@yahoo.com> wrote: > On 9/21/2015 2:20 PM, Charles Buckley wrote: > > Well, you can eliminate windows completely, if you have a phone or > android > > tablet. > > > > > https://play.google.com/store/apps/details?id=io.machinekit.appdiscover&hl=en > > > > I would argue that the ability to split the GUI from the engine is a good > > thing overall, but at your core, you're still looking at having a full OS > > sitting out there and the underlying architecture and filesystem layout > can > > not easily be circumvented. > > What that would be is a client-server type of system, with LCNC running > on a micro-system in the role of the server, with the GUI running on the > Windows or OS X or other system as the client. > > The trick is to achieve transparency of operation so that GCODE and > commands for start, stop, E-stop etc sent to the LCNC server and > feedback returned to the client operates seamlessly and without > interference with the micro-system actually operating the CNC machine. > > It would (should) also be simpler to adapt the client to different > versions of its host OS since the data going both ways from the server > wouldn't change. > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
