The limitation of 1 emc instance in one PC would not be an easy one to lift. It is a simplifying assumption that by now has sunk pretty deeply into many levels of the software today. A few things that come to mind are * each emc instance assumes it can start and stop the realtime environment when it starts/exits * the motion realtime component assumes throughout that there is only one motion controller * the task controller and motion controller compute using a hard-coded shared memory segment, so there's no way to run two task controllers that communicate with two motion controllers * in hal, all instances are created at startup, so there's no way to e.g., add and remove step generator instances within the running system; you can only stop realtime and start it again with new instances configured. * in hal, a lot of the names of pins and parameters don't make sense with multiple motion controllers, such as axis.0.motor-pos-cmd.
.. and those are just the things that come to mind within a few minutes, not the unanticipated ones that inevitably appear when working on big project. Jeff ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
