<?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>nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51460/nrf52-setup-client-and-server-examples-to-send-serial-packets-over-mesh-and-print-on-uart</link><description>Good day, 
 
 I am starting a new project where I am using the ANNA-B112 BLE device from ublox in a custom design. The ANNA-B112 interfaces with a host MCU over UART. I would like to be able to set up a mesh network with one client device and several</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 15 Oct 2019 09:40:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51460/nrf52-setup-client-and-server-examples-to-send-serial-packets-over-mesh-and-print-on-uart" /><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/215016?ContentTypeID=1</link><pubDate>Tue, 15 Oct 2019 09:40:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a377226-0367-4520-b203-c3aecee45d5a</guid><dc:creator>Heidi</dc:creator><description>&lt;p&gt;Hi, this case is 2 months old and not being supported anymore. Please make a new ticket for your issue.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Heidi&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/214498?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2019 06:39:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:95e622f5-c31f-4766-894f-979a00ef0460</guid><dc:creator>NikhilIngale</dc:creator><description>&lt;p&gt;Hi Hung, I am currently using nRF mesh 3.2 and nRF SDK 15.3. I have integrated the uart module to light switch server and client both. I have one client (BT840) and 3 servers (BT832) as of now. Tested the application and working as per the requirement and also able to print the messages on on/off actions based on button press on UART terminal. Now i want to send the data (20 bytes) from client application to the servers (groups basically) over uart.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you please guide how to add the ble_uart so that messages can be sent to specific devices in mesh network (publish data to specific publish address). I went through some threads here in forum and found that simple message server would do the similar thing which i want to do. But that model is not present in nRF mesh 3.2.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also if i add ble_uart service it would be able to communicate with only one device, right?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;client (20 bytes)----&amp;gt;publish-----&amp;gt;subscribe 20 bytes (all the servers in network), this is what i want to do.&lt;/p&gt;
&lt;p&gt;Seeking for some quick response. Thank you&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206928?ContentTypeID=1</link><pubDate>Thu, 29 Aug 2019 14:41:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c35990d5-08c1-40b6-800c-27e66ce591b4</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;The link should work.&lt;/p&gt;
&lt;p&gt;If not please open &lt;a href="https://infocenter.nordicsemi.com/"&gt;https://infocenter.nordicsemi.com&lt;/a&gt; and navigate to here:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/729x1019/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-732b3b042c74419dbc4656799d16b226/pastedimage1567089675656v1.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206923?ContentTypeID=1</link><pubDate>Thu, 29 Aug 2019 14:28:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26f27a5b-8b44-4dca-a092-c654c03e9940</guid><dc:creator>nish</dc:creator><description>&lt;p&gt;the link you posted is not opening .&amp;nbsp;&lt;br /&gt;The exact function at like 214 is&amp;nbsp;&lt;strong&gt;NRF_MESH_ASSERT_DEBUG(bearer_event_in_correct_irq_priority());&lt;/strong&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206919?ContentTypeID=1</link><pubDate>Thu, 29 Aug 2019 14:22:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:56f337b1-a273-45bc-88fc-990545788e08</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Make sure when you call a mesh API inside an interrupt handle it follows the interrupt level rule as mentioned &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v3.2.0/md_doc_introduction_mesh_interrupt_priorities.html?cp=5_2_0_4"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If that wouldn&amp;#39;t help, could you check which error code and which exact function was at line 214 ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206895?ContentTypeID=1</link><pubDate>Thu, 29 Aug 2019 13:29:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f07400cf-c5ff-4f72-b2a0-1e5d734ec740</guid><dc:creator>nish</dc:creator><description>&lt;p&gt;Hi Hung,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I am using the nRF mesh sdk3.2.0 together with nRF sdk 15.3.0. I have added the UART/UARTE functionality into the light switch client and light switch server code examples, and I am able to do a simple print to port.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I then added functionality to be able to use the uart input as replacement for buttons, I am able to provision both the client and teh server using the nRF mesh app. However when i use the UART to &amp;quot;simulate&amp;quot; a button press, I get an error &amp;quot;app_error_weak.c,&amp;nbsp; 108, Mesh assert at 0x0002AF10 (:0)&amp;quot; using the addr2line tool, I am able to identify that the issue is at line 214 in the timer_scheduler file.c file.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I think it has something to do with interrupt priority levels, but I am nnot sure how to resolve the problem.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;simulating the button press from the RTT debug terminal, does not give me the same error.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206777?ContentTypeID=1</link><pubDate>Thu, 29 Aug 2019 08:10:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de748605-e73b-45b8-a380-4361915dfa72</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;I don&amp;#39;t think the serial example would be best match for you. The main purpose of the serial interface is to do serialization. You can control mesh from the external MCU. In your case, maybe the external MCU is only used for collecting data from the sensor, and most of the mesh operation can be executed/processed on the nRF52 ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If that&amp;#39;s the case, you can just make your own vendor specific model with your customized data. I would suggest you to have a look at the simple on off model that we provided. To communicate with the external MCU, you can simply use the normal UART/UARTE peripheral.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206748?ContentTypeID=1</link><pubDate>Thu, 29 Aug 2019 05:54:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f8dbbca4-48ac-4f96-9c45-ae9cd7af5bf2</guid><dc:creator>nish</dc:creator><description>&lt;p&gt;Hi Hung,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I have looked at the light switch example. The part im am not sure about is how and where do i pack my packet of data into for transmitting over the mesh.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My idea is to have the host MCU send data to the uart on the BLE chip, once the BLE chip recieves any data on the uart, it should then forward it to the mesh network. Looking at the serial example, that might work for me, but is there a way to provision the serial example on a mesh network?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 setup client and server examples to send serial packets over mesh and print on uart</title><link>https://devzone.nordicsemi.com/thread/206698?ContentTypeID=1</link><pubDate>Wed, 28 Aug 2019 15:39:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:151214c3-25ff-4d13-9aee-01a92af4c3ce</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Nishant,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you tried the light switch example&amp;nbsp; ?&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t see any problem doing what you are planning. In our light switch example you can have multiple servers reporting to a client (in the example the client turn off and on the light on the servers, but you can actively publish data from the server without the client asking as well).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You just need to implement your own proprietary model (you can refer to our simple_on_off model) and make a network similar to the light switch example.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>