Michael Haberler wrote: > > Now comes the hard part, reentering the original motion context, and that > part is the one I'm most fuzzy about. If the machine pose matches the pose > when 'pause' was hit, then restoring modal state (spindle, coolant..) and > waiting to spin up might suffice. If the poses dont match, a move might be > required. I am not sure if this can be done fully automatic. In fact, in the > presence of cycles this could be quite complex to do. Also, changed offsets > by touchoff arent yet covered. I have no idea which role acceleration and > blending play here. > Yes, for sure this gets hard. If you just want to be able to restart after a tool change, it might not be real difficult to remember the last position, and just do a direct move to that position before restarting. But, the operator may have done some things with global effect, like changing the tool table, changing a G92 offset or something like that, and he intends for that change to be used when restarting. > It is debatable wether such an effort makes sense for the yield, and also > wether this is actually doable within the current EMC2 project structure and > process. I'd be curious what people think about it. > A truly comprehensive way to restart after a manual or MDI move would remove one of the biggest shortcomings of EMC2 compared to commercial controls. Just getting spindle and coolant to start when doing a run from line would also help. I still don't understand exactly what IS and what ISN'T processed when doing a run from line on a program with subroutines and loops.
Jon ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
