Am 07.10.2013 um 00:10 schrieb "Steve Stallings" <steve...@newsguy.com>:
> >> Am 06.10.2013 um 23:09 schrieb Ricardo Moscoloni >> <rmoscol...@gmail.com>: >> >>> this is great!, could you think adding a pin that defines last >>> resuming move along an axis (z on a mill as an examlple), to avoid >>> collisions will be useful? >>> >>> As cartesian as my brain could think, moves will be: >>> hit pause >>> jog(here you have to avoid collisions!) >>> hit resume >>> auto move to last x,y >>> last approach move along z, if theres any (z is the axis that you >>> define previously) >>> continue machining fun. >> >> that's an interesting idea >> >> the return move certainly warrants some thinking - just a jog >> from current to the pause position is a bit narrow in application >> >> a generalisation could be this: >> >> - add a pause and a return offset pose via HAL pins >> - transit through these offset positions on pause/resume respectively >> >> your scenario would be covered by setting a resume offset >> pose with z != 0 only, and it retains some of the flexibility >> of the purely HAL-based solutions as the offset poses can be >> modified at runtime >> >> I'm open to more flexible ideas >> >> -Michael >> >> > Just keep in mind that for a lathe, Z is not likely to be the > last move of a restore. well since it's a pose offset, any axis could be the last move (or first for the pause initial move) -m ------------------------------------------------------------------------------ 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=60134791&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
