Hmm, that would be a bit invasive. I was hoping I could just hook into an existing function rather then modifying the core EMC code. Is there any other way to sniff the messages before they hit task?
To be honest, this isn't a major issue. In most cases the code can be deduced from the machine movement and emcStatus. About the only thing that could be an issue is threading. Les On 19/04/2011 14:51, Michael Haberler wrote > I think the only realistic way is to log the MDI execution in task because > that's where the two command streams are coming together (from two different > processes, halui and axis) in sequence > > basically you'd want to log the command field of EMC_TASK_PLAN_EXECUTE > messages if emcStatus->task.mode == EMC_TASK_MODE_MDI > > emctaskmain.cc around line 934, case EMC_TASK_PLAN_EXECUTE - log > emcCommand.command > > -m ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
