<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openthread SED multicast</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/73432/openthread-sed-multicast</link><description>Hi Nordic team, 
 
 Experimenting with nRF NCS v1.5.0, Openthread CoAP. 
 When the client send a message to server, CONFIG_OPENTHREAD_MTD_SED is enabled, I reduced the poll period to 5 seconds, and I can see the SED node checking in every 5s (Data request</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 31 Mar 2021 13:22:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/73432/openthread-sed-multicast" /><item><title>RE: Openthread SED multicast</title><link>https://devzone.nordicsemi.com/thread/302758?ContentTypeID=1</link><pubDate>Wed, 31 Mar 2021 13:22:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b9ceede1-216b-4bc3-841a-acfd9c374e38</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello Farhang,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I needed to confer with our OpenThread experts.&lt;br /&gt;&lt;br /&gt;Question 1 -&amp;nbsp;SEDs do no receive the ff03::1 multicast messages by design. There are different multicast addresses that are used by SEDs. From Thread 1.1 Spec - Chapter&amp;nbsp;5.2.3.2:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/7774.MicrosoftTeams_2D00_image.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;You should be able to use the following addresses:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="powershell"&gt;ff33:40:fde2:3960:66dd::1
ff32:40:fde2:3960:66dd::1


&lt;/pre&gt;&lt;/p&gt;
&lt;div&gt;These are Link-Local All Thread Nodes and Mesh-Local All Thread Nodes addresses. For more information, please see RFC3306 -&amp;nbsp;Unicast-Prefix-based IPv6 Multicast Addresses.&lt;/div&gt;
&lt;p&gt;Question 2 - If the board board was&amp;nbsp;programmed&amp;nbsp;from FTD to MTD FW and the persistent storage has not been cleared, you may observe issues similar to that. Then flashing the device, make sure to use:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="powershell"&gt;west flash --erase&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Question 3 - The Zephyr CoAP API implementation is simpler than OpenThread. In Zephyr&amp;#39;s case the CoAP implementation will prepare the frame, but you will need to send it yourself. Also retransmissions are not handled automatically. There are plans to port the CoAP server, however, I have no timeline for this I&amp;#39;m afraid.&lt;/p&gt;
&lt;p&gt;Please note that the following days are Easter holidays in Norway and one must expect a delayed answer due to short staff in the Technical Support team.&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>