On Sun, Mar 29, 2015 at 02:06:39AM +0000, matic bie wrote: > "motion is supposed to:* increment "head"* set all the other felds in > the emcmot_command_t* increment "tail"if it does this, then task is > supposed to be able to:* make a complete copy of the emcmot_command_t* > compare head and tail* if they are equal, it has a consistent copyand it > can act on the contained command* if they are unequal, then it is an > inconsistentcopy and it will try again after a short time (typically > 1servo period or 1ms) -- this is a "split read""1) In the explaination > above ,do you make "motion" and "task" reversally?2) From your > description, can i conclude that the change of head++ and tail++ are > made by hardware not by soft code?
(your messages come through with everything run together and hard to read like the above. please see whether you have settings on your end which are set wrong. remember that this list does not use HTML mail, but only plain text) It's quite likely that I mixed up "motion" and "command" in my explanation. It is the sending side that increments head/tail and the receiving side that checks their equality. No, the increment is not done by magic or "hardware". If it's not there in the source code, it is a mistake. Jeff ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
