I have an application where I need to send jog commands at a high rate (anything up to 30 updates/second on two axes). Basically the machine needs to chase a moving target. Using sendJogCont with emcWaitType set to EMC_WAIT_RECEIVED takes over 100ms per axis which is way to slow. If I set emcWaitType to 1 (undocumented use of emcWaitType ) sendJogCont returns virtually immediately. I understand that doing this means that I have no way of knowing if the jog command has actually been executed but in this application an occasional missed command won't make a huge amount of difference. Is there a limit to how fast I can send commands? Presumably there is a buffer somewhere that is going to fill up if I send more data than the realtime side can consume. Are there any other likely issues with doing this?
Les ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
