> 30 updates/second is rather slow, servo control loop is usually 1kHz which is > about 30 times more often.
Indeed. That was why I was a little shocked to find the NML round trip takes so long. > As I understand it NML use TCP/IP and then you probably to not send a new jog > command until previous finished. As far as I know the communications between real-time and user space uses shared memory rather than sockets. I don't know if that has any effect on how fast I can throw data at the trajectory planner or not. Les ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
