<?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>How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8803/how-to-turn-on-off-mesh</link><description>I am using the RBC mesh in a networking product using the nRF51422. We would like to turn the mesh on and off at selected times, say once per hour for a minute or two. I know how to turn on (init) the mesh. But, what is the best way to turn it off such</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 07 Jan 2016 14:22:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8803/how-to-turn-on-off-mesh" /><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32306?ContentTypeID=1</link><pubDate>Thu, 07 Jan 2016 14:22:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f38c731-902a-436b-876b-88c6949b0445</guid><dc:creator>Trond Einar Snekvik</dc:creator><description>&lt;p&gt;That seems reasonable. If you don&amp;#39;t want to push data to the sensor, you can actually do this only by advertising, if you follow the packet format. Enabling the mesh will force you to do some scanning, and it might take up to 100ms to get a response from the master, but it&amp;#39;s not an unreasonable approach. The end node does not need to reestablish its network role, or negotiate some slot from the master in any way. It can wake up, send, and go back to sleep, without any management overhead.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32305?ContentTypeID=1</link><pubDate>Thu, 07 Jan 2016 14:17:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28265357-f3ea-4fd1-8ff4-995c93ab9281</guid><dc:creator>d21d3q</dc:creator><description>&lt;p&gt;How about waking up end node (some sensor) from deep sleep, ask some Master through mesh for instructions (to transfer some data) and go back to sleep? In this case question is if end node needs to discover network on reconnection as ZigBee does?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32304?ContentTypeID=1</link><pubDate>Thu, 07 Jan 2016 12:54:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88bec6e1-e221-4236-b6c6-f66f7865d25f</guid><dc:creator>Trond Einar Snekvik</dc:creator><description>&lt;p&gt;Unfortunately, no. When turned off, the mesh doesn&amp;#39;t use the radio at all, and will not be able to send or receive anything. The mode you&amp;#39;re requesting requires a surprising amount of extra functionality, as the battery powered node cannot be in RX mode constantly (it&amp;#39;s extremely power consuming). Therefore, the &amp;quot;router&amp;quot; node has to buffer all incoming messages while waiting for the end-node to attach in some low-power fashion, like a regular BLE connection. This is the approach I would recommend for the mesh; let router devices scan for end node&amp;#39;s advertisements, and connect. Transfer all data since the last connection, and disconnect again. Alternatively, keep a connection running, but keep the connection interval high, as to conserve power in the end node. If you want several end-nodes at each router, you should make the router the master in the connections (requires SD120 or SD130).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32303?ContentTypeID=1</link><pubDate>Thu, 07 Jan 2016 12:39:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ce4954d-4350-4e43-83f3-3b5eebd973bc</guid><dc:creator>d21d3q</dc:creator><description>&lt;p&gt;Does it mean that devices with turned off mesh is working like ZigBee end node? Only listening and not participating in forwarding messages?
I would like to have mesh end nodes running on battery and some routers with no power constraints .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32302?ContentTypeID=1</link><pubDate>Tue, 08 Sep 2015 18:45:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d0aa7a2-5749-4bb9-bbf3-6fe6e86366b6</guid><dc:creator>sphudson</dc:creator><description>&lt;p&gt;Thank you very much, Trond!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32301?ContentTypeID=1</link><pubDate>Tue, 08 Sep 2015 07:16:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f2a0620-e734-4569-8814-baef18b3b148</guid><dc:creator>Trond Einar Snekvik</dc:creator><description>&lt;p&gt;The framework now supports start/stop actions for the radio activity, see &lt;a href="https://github.com/NordicSemiconductor/nRF51-ble-bcast-mesh/releases/tag/v0.6.9-SD8"&gt;release v0.6.9&lt;/a&gt;. Note that this only stops radio activity, while the memory remains allocated and local functionality is kept.&lt;/p&gt;
&lt;p&gt;It works by aborting the running timeslot, and stops all ordering of new ones from the Softdevice.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32300?ContentTypeID=1</link><pubDate>Fri, 04 Sep 2015 06:19:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f45029b-e6a7-4a09-8548-2c848de8442a</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I am not sure, is there any events that you were expecting?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32299?ContentTypeID=1</link><pubDate>Thu, 03 Sep 2015 00:50:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d89836c6-997a-4599-8dc0-22a60b6e0dba</guid><dc:creator>sphudson</dc:creator><description>&lt;p&gt;Aryan,
My last comment got deleted for some reason.  The problem is that  ts_sd_event_handler() is never called.  Can you please provide some clues as to why it isn&amp;#39;t being called?
Thanks -stan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32298?ContentTypeID=1</link><pubDate>Wed, 26 Aug 2015 07:51:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0e6cad1-342e-4cfc-95e0-16085b0ff043</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I forgot to check the error return value of sd_radio_session_close. I have edited the answer now.
Did you check if it returned NRF_SUCCESS? After that it should atleast get NRF_EVT_RADIO_SESSION_CLOSED event.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32297?ContentTypeID=1</link><pubDate>Tue, 25 Aug 2015 21:07:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16723282-795a-4d43-90d7-1a51826c8387</guid><dc:creator>sphudson</dc:creator><description>&lt;p&gt;Aryan,
I tried what you suggested above and it isn&amp;#39;t working.  In fact, the ts_sd_event_handler() function isn&amp;#39;t even being called.  Nor is the rbc_mesh_sd_irq_handler() function. I&amp;#39;m using the template example on a PCA10031 dongle.  And, I have confirmed that the mesh is working because it is periodically sending (and receiving) updates between the dongle and another board running the mesh.  Can you please confirm that your suggestion is correct?  thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32296?ContentTypeID=1</link><pubDate>Mon, 24 Aug 2015 16:53:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:509c3607-434a-4a77-b59f-478c6277dcf2</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;the receiver is switched off before the slot has ended, and if no new slot is requested, then it remains off.
Timeslots can be used both for transmission and reception of data&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32295?ContentTypeID=1</link><pubDate>Mon, 24 Aug 2015 15:46:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:179655bf-fde8-46cb-889f-d561316fb695</guid><dc:creator>sphudson</dc:creator><description>&lt;p&gt;Thank you for the quick reply.  I&amp;#39;ll implement that solution.  Does the sd_radio_session() call turn off the receiver as well?  I am not completely familiar with the inner-workings of the mesh and timeslot handler, but is the receiver basically on all of the time and the timeslots are used to process not only transmissions but also reception of data from other nodes?  Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to turn on/off mesh</title><link>https://devzone.nordicsemi.com/thread/32294?ContentTypeID=1</link><pubDate>Mon, 24 Aug 2015 12:10:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81534a20-d265-4afc-bd58-4a102f79e837</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;The turning on and off of mesh is not exposed. It should be, but we didn&amp;#39;t really consider it at first. I think the easiest fix is to stop the timeslots. you would have to modify the way the radio events are handled to keep it from restarting the session, but it should be pretty straight forward.&lt;/p&gt;
&lt;p&gt;in ts_sd_event_handler
instead of renewing the timeslot, renew it based on some condition something like this for example&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;        case NRF_EVT_RADIO_SESSION_IDLE:
            if(!switch_it_off)
                  timeslot_order_earliest(TIMESLOT_SLOT_LENGTH, true);
            else
                  err_code = sd_radio_session_close();
                  if (err_code != NRF_SUCCESS) {handle_error}
            break;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;so when the timeslot-start signal isn&amp;#39;t triggered, there should be no unexpected hardware usage.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>