Now, you suggested me an idea! The whole in/out thing in interfacing could be helped by shared memory! The realtime system supports some definitions on this. We just need to design all the names and their correct placement and agree on that and it can be moved there! This is much how it is done in MCU processors, where you have little memory anyway. This system would be a bit faster too, it avoids the slow stack load/unload, so it could be faster.
Hou much would we need? I suggest 32-bit fixed point each. Signed or unsigned? Signed, right? We would have simple field of (mainly unified) variables that would the EMC system read on occasions, like the speed override scaling factor, so there may be a unified place to work with. Maybe I miss this one, but you were rather talking about actual implementation in programming languages? Defining this memory field will help also with actual implementation, since you will have ONE table, manual where to find particular variable in the memory cluster. Various control bits (STOP, ESTOP, and milion others) can be also defined here, so you could simply interfere with machine state trough manipulation of the shared memory part. This has to be thought with caution. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
