I am putting together some software that will generate toolpaths. It works with piecewise linear polygons.
1.) When running an arc, is there any pro- or con- to feeding LinuxCNC either a series of a few dozen straight moves to approximate the arc, or a single G2/G3 arc? As I mentioned, I am working with line segments only, but I can regress these into arcs with a bit of trouble at the post-processing stage. Any reason to do that? Clearly, it will produce much less g-code; but the size of the g-code is not a factor. 2.) Can someone point me to some reference (code, whitepaper, wiki) on how the motion-planner works? I need to know at least approximately in order to optimize the sequence of moves. My base assumption is that it works with infinite look-ahead, and will push the tool to both acceleration and velocity limits as appropriate. Is that pretty close? Even if that is the case, I'd like to see some analysis so that I don't recreate the wheel with understanding some of the motion equations... Thanks! T ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
