<?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>BLE ESB timeslot versus 2 BLE</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67541/ble-esb-timeslot-versus-2-ble</link><description>Hi there, 
 We&amp;#39;re using NRF52840 and nRF5_SDK_15.3.0_59ac345. We have a product where 2 nRF52840&amp;#39;s have to talk to 1 device (say, an iPhone or a computer). We were thinking of doing the following initially: 
 OPTION1: 
 iPhone ---BLE---&amp;gt; nRF52840 ---</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Nov 2020 19:28:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67541/ble-esb-timeslot-versus-2-ble" /><item><title>RE: BLE ESB timeslot versus 2 BLE</title><link>https://devzone.nordicsemi.com/thread/278161?ContentTypeID=1</link><pubDate>Mon, 02 Nov 2020 19:28:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ccc2bc1f-e049-4d5a-9903-c449da14cded</guid><dc:creator>Cecylia</dc:creator><description>&lt;p&gt;Okay, we&amp;#39;re already planning on using the UART over BLE example, so we&amp;#39;ll start from there. &amp;nbsp;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE ESB timeslot versus 2 BLE</title><link>https://devzone.nordicsemi.com/thread/277782?ContentTypeID=1</link><pubDate>Fri, 30 Oct 2020 11:21:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d75b6454-20b0-4279-8881-9c122ee6d193</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am not sure if we have anything pushing large amounts of data from smartphone to nRF, but we do have something the other way around:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/NordicPlayground/nrf52-ble-image-transfer-demo"&gt;https://github.com/NordicPlayground/nrf52-ble-image-transfer-demo&lt;/a&gt;&lt;br /&gt;&lt;a href="https://github.com/NordicPlayground/Android-Image-Transfer-Demo"&gt;https://github.com/NordicPlayground/Android-Image-Transfer-Demo&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Admittedly that example uses Android, not iOS, for the smart phone side. Even though the stream direction is opposite of what your project needs, you should still get reasonable ballpark figures.&lt;/p&gt;
&lt;p&gt;Otherwise you could use the &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v17.0.2%2Fble_sdk_app_nus_eval.html"&gt;UART over BLE example&lt;/a&gt;, and make an application on the smartphone that connects to two devices and streams (for instance random) data at a given rate. We do have a &lt;a href="https://github.com/NordicSemiconductor/iOS-nRF-Blinky"&gt;blinky example for iOS&lt;/a&gt;, which may serve as a starting point for iOS BLE app development.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE ESB timeslot versus 2 BLE</title><link>https://devzone.nordicsemi.com/thread/277222?ContentTypeID=1</link><pubDate>Tue, 27 Oct 2020 18:12:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f9471a1-fc26-4913-9f6a-4b80ea7f22a7</guid><dc:creator>Cecylia</dc:creator><description>&lt;p&gt;Thank you &lt;a href="https://devzone.nordicsemi.com/members/tesc"&gt;tesc&lt;/a&gt;!&lt;br /&gt;&lt;br /&gt;Do you have some sort of example for the &amp;quot;&lt;span&gt;Two (identical) nRF52840 devices using only one protocol (BLE)&amp;quot; so that we can get some benchmark numbers to compare?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE ESB timeslot versus 2 BLE</title><link>https://devzone.nordicsemi.com/thread/276653?ContentTypeID=1</link><pubDate>Fri, 23 Oct 2020 13:43:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d7918ad-e18c-4469-a6c9-9d55405e0f2a</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;So the question is whether to connect each nRF52840 individually to the smartphone, or to connect one nRF52840 to the smartphone and let it send both its own data and relay data from another nRF52840 (that it receives over an ESB link)?&lt;/p&gt;
&lt;p&gt;Two (identical) nRF52840 devices using only one protocol (BLE) sounds like both the least complex project, as well as giving less latency (although 100 ms should be more than enough to get data and relay it.)&lt;/p&gt;
&lt;p&gt;Throughput wise you should have more than enough at the nRF52840 end, as per &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsds_s140%2FSDS%2Fs1xx%2Fble_data_throughput%2Fble_data_throughput.html"&gt;Bluetooth Low Energy data throughput&lt;/a&gt;, as long as you use the right method for sending the data and can get a short enough event length / large enough ATT MTU size for the connection.&lt;/p&gt;
&lt;p&gt;Having the two nRF52840 devices operate as individual BLE devices will however require that the end user pairs / connects with two BLE devices in order to use both. If it is desired to use this as &amp;quot;one product&amp;quot;, and only connect with one BLE device from the smartphone, then you can go with an ESB solution (or normal BLE connection) between the nRF52840 devices, but at the cost of complexity, one more protocol to understand (ESB), and slight increase in latency.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>