> Yes. I tried to get EMC2 to include rotary axes in the velocity > calculation, but was overruled. > So, you have to use inverse time mode, G93, to specify the time the move > is to take. > The deal is if you are going to include the rotary axis in the feed > velocity, the radius needs to > be taken into account. G code doesn't formally specify this, so EMC > would have to ASSUME > that in the active coordinate plane (G17 - G19) the vector distance from > zero would be the > radius. That was too big an assumption for the purists, so all angular > axes have no feedrate.
What happens if you have 3 stacked rotaries and you want to move them all? What happens when the radius changes during a move? What happens if the A/B/C rotations aren't actually rotary tables, but head tilting for a non-carthesian machine? I think it's a lot more difficult than the simple case: only one rotary, fixed radius during the move, etc. Regards, Alex ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
