<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Hi,<br><br>So there's a possibility that the sync manager would react with datagrams that satisfy the length? A datagram not for the slave but with appropriate length may be supposed to be the datagram corresponding to that slave?<br><br>Best regards,<br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><br>Hi <br><br>>When reading the EtherCAT Master documentation about FMMU, I meet this sentence: "In order to >make a sync manager react on a datagram accessing its memory, it is necessary to access the last byte >covered by the sync manager." <br><br>>I do not understand: which access to the last byte? Whose last byte? The last byte in the datagram? or EtherCAT
frame?<br>The byte on the last address within the mailbox address range (see configured mailbox size) <br><br>>How can sync manager identify its datagram by just the last byte?<br>By comparing the given address and the size of the transferred data. A master must either write the full size of the mailbox (even if the real payload is much smaller) or it has to write 2 datagrams: One with the real payload, addressed to the start of the mailbox, and an additional datagram that writes just one byte at the end of the mailbox address range.<br> <br>Regards, <br>Martin<br><br><br>Note:<br>This e-mail is for the named person's use only. It may contain confidential and/or privileged information. If you have received this e-mail in error, please notify the sender immediately and delete the material from any system. Any unauthorized copying, disclosure, distribution or other use of this information by persons or entities other than the intended recipient
is prohibited.<br>Thank You.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br><span>URL: <<a target="_blank" href="http://lists.etherlab.org/pipermail/etherlab-users/attachments/20110712/9d8bbd59/attachment-0001.htm">http://lists.etherlab.org/pipermail/etherlab-users/attachments/20110712/9d8bbd59/attachment-0001.htm</a>></span><br><br>------------------------------<br><br>_______________________________________________<br>etherlab-users mailing list<br><a ymailto="mailto:etherlab-users@etherlab.org" href="mailto:etherlab-users@etherlab.org">etherlab-users@etherlab.org</a><br><a href="http://lists.etherlab.org/mailman/listinfo/etherlab-users" target="_blank">http://lists.etherlab.org/mailman/listinfo/etherlab-users</a><br><br><br>End of etherlab-users Digest, Vol 50, Issue 5<br>*********************************************<br></div></div>
</div></body></html>