> From: [email protected] > To: [email protected] > Date: Sun, 3 May 2015 06:22:32 -0400 > Subject: Re: [Emc-developers] where the whole path is divided into segment > by segment > > Ahh, I see. It will help if you mentally substitute the "0" with "where > it is at", its already there from the previous move so you don't have to > restate it for the next move, so you supply only the "target" to move > to, and bear in mind the target can be selected as either an absolute > location, or a move relative to where it is at. Also controlled by a > G-code, its in the user manual. The machine doesn't come to a full stop > (generally, but you can command it to) but that is how I think about it. > > This generally is how one would do a "step & repeat" operation series, > you position the machine to the start of the each series in absolute > mode, switch to relative, and call the same subroutine each time, > returning to the absolute mode to set the step position of the next > repeat. > > If you look at some of our code, you will often see a large surplus of > precision stated where .001" is close enough but we'll > write .0010000000, but that is how the accumulation of rounding errors > is best handled. Works for me anyway. OTOH, I'm not carving new lenses > for the hubble either. :) > > I hope this helps.>
Thanks. Usually, how much is the length of the target? In which function is the target calculated from G-code?Best regards. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
