On Mon, Dec 9, 2013, at 03:54 PM, Michael Haberler wrote: > > > you might want to look in halcmd at the > motion-command-handler.time > motion-command-handler.tmax > motion-controller.time > motion-controller.tmax > values; this could give a hint if something takes too much time. >
Better yet, halscope motion-command-handler.time (or the .time pin associated with any other RT function you are suspicious of). If you are already triggering the scope on a constraints violation you should get a good idea of whether a time over-run might be involved. -- John Kasunich [email protected] ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
