Mark Haynes wrote: > For recording movements at every 1/2 second intervals is the g-code file that > you play back consist of a new line for each 1/2 second? So that every line > of g-code is a x,y,z, and feedrate value for that 1/2 second interval. If so > I think there would need to be some preprocessing of the G-code to remove > redundancies. Such as if you move in a straight line from x0. to x10. at > constant velocity the preprocessing would simplify the command to one line of > code instead of showing what to do for each half second interval. In my own > personal experience with building a CNC system I found the time it takes for > the computer to interpret a line of g-code and break it down into machine > motion very taxing on the PC. This may be why it doesn't work at high speeds > on 1/10s intervals. (However, I'm not sure if this is true for LinuxCNC). > > I'd be interested in learning more on your work so far. > I did some tests a few years ago that showed a 600 MHz Pentium III could handle 750 or so blocks of G-code a second. No doubt it can go higher on more modern CPUs.
Jon ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
