There are shared memory buffers between task and motion. (Independent of the HAL shared memory space). Task and motion access those buffers by using a pre-agreed name (or number, or some other identifier). If running more than one instance of task and corresponding motion, you would need to figure out a way for each pair to get the proper buffer(s).
On Thu, Mar 15, 2012, at 11:21 AM, Michael Haberler wrote: > at this point largely a theoretical question, nevertheless: > > besides HAL pin & function, and NML channel naming - are there any strong > reasons why motion is a singleton module? > > (unique externs for instance?) > > I'm not talking about the status quo where (I think) you cant run more > than one task instance > > -m > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > -- John Kasunich [email protected] ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
