IIRC, the Arduino systems cache a series of incoming g-code lines, then runs them out to the printer.
When you look at moving Linuxcnc onto Beaglebone and Raspberry Pi, the implementation of a modified drip-type system might work better. You take a pretty significant hit if you are trying to run a GUI. If you move to a Drip type system with the Linuxcnc operations split between a small system on the printer and a second remote system to do all the GUI type stuff, you have a much more flexible system. Don't do it as a full drip. Use it as a caching, spool out type implementation. At that point, you really could port the Linuxcnc GUI environment to any number of other Operating Systems. On Mon, Jun 24, 2013 at 10:52 AM, Jon Elson <[email protected]> wrote: > andy pugh wrote: > > On 24 June 2013 15:50, Charles Steinkuehler <[email protected]> > wrote: > > > > > >> I have some folks from the 3D printer world asking me if LinuxCNC can > >> be used in a "gcode mode" similar to how the Arduino currently > >> operates these machines (a serial terminal that accepts gcode and > >> spits out the occasional status message). > >> > > > > This was historically called "DNC" or "drip feed" and you might find > > something with those as search terms. > > However, as far as I know (and it isn't very far) LinuxCNC has never > > supported that. > > > There are good reasons not to support true drip feed, as it is not > guaranteed > real time. If the sending computer loses the connection, the part ends up > half finished. It was useful on machines with severely limited buffers. > > I know at one time, LONG ago, there was discussion of a scheme to > use FTP or nfs to transfer a file to a particular directory, a cron job > would detect the file, mv it to another place and then trigger EMC > to run it. (I say EMC to indicate how long ago this was.) > LinuxCNC still has this functionality, to load a file by name and > give the run command. The main component is halui, see the > integrator's manual for more info. That section is pretty terse, > I'm not sure if there is any more comprehensive doc on halui > anywhere else. > > I think in today's world, sending G-code via a real serial port > is no longer appropriate, especially for 3D printer files. USB > or network makes much more sense. > > Jon > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
