On Dec 26 2013 2:47 PM, Viesturs Lācis wrote: > 2013/12/26 Andrew <[email protected]> > >> > Yes, that is very reasonable. Just calculate the scale and use >> usual >> planning. >> The task can also be reversed: increase world velocity to the >> maximum >> allowed by joint constraints. This can be useful for G0 moves. >> > > Umm, sorry for offtopic, am I the only one to be missing out > something > obvious and think that this whole problem would apply _only_ to rapid > (G0) > moves? > All the other moves are feedrate limited - they are executed at the > requested feedrate and intentional deviation from that does not seem > right, > so I am missing, how the whole concept of checking for worst-case > velocity > violations and scaling down appropriately will not break the purpose > of > requesting particular feedrate in code.
I was going to ask the same thing... If the issue is with the rapid traverse that is set limited with the max velocity. Are you sure that the max velocity is set correctly? EBo -- ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
