<?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>Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13962/strange-behaviour-while-sending-real-time-data</link><description>Hi all, i have an application with a smart beacon kit; i won&amp;#39;t resume the whole project because it&amp;#39;s long and boring, i will just say that i have a service that every 100 ms (temporized by a timer counter of the nrf51822) takes a value (in the real project</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 23 May 2016 10:29:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13962/strange-behaviour-while-sending-real-time-data" /><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53331?ContentTypeID=1</link><pubDate>Mon, 23 May 2016 10:29:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c5fdce90-a7a5-4e46-9f35-8b9d34dd516c</guid><dc:creator>Revo</dc:creator><description>&lt;p&gt;thanks, i accept the answer!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53330?ContentTypeID=1</link><pubDate>Mon, 23 May 2016 10:26:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a22c94f0-0e9e-4745-9dc6-65c753db136e</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;You can skip the connection parameters negotiation library, so that you don&amp;#39;t send a connection parameter update request. You can make the central ignore the connection parameter update request.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53329?ContentTypeID=1</link><pubDate>Fri, 20 May 2016 15:30:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4b991fd-cd25-495b-9d76-59cde5f45407</guid><dc:creator>Revo</dc:creator><description>&lt;p&gt;so what do you suggest to solve the problem? At this point i changed the minimum connection interval to 8 ms and the maximum to 10 ms, both on the peripheral and the central; this seems to solve the
problem, but it is the best way? Why should i use a large range of possible connection interval instead of a very strict one to be sure to know the &amp;quot;frequency&amp;quot; of transmission?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53328?ContentTypeID=1</link><pubDate>Fri, 20 May 2016 13:08:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8e99af3e-fc57-4609-8ea4-ce5bdd10829a</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;You are using the Connection Parameters Negotiation library. This will send a connection parameter update request after FIRST_CONN_PARAMS_UPDATE_DELAY, then the central device will increase the connection interval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53327?ContentTypeID=1</link><pubDate>Fri, 20 May 2016 07:28:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8a21afb-0c4a-4e06-9ad4-ae8e03db9366</guid><dc:creator>Revo</dc:creator><description>&lt;p&gt;Ok thanks, while i wait the answer of more expert people than me that want to take a look at the code i will also check by myself :) btw what are the connection parameters that should affect the frequency of this transmission?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53326?ContentTypeID=1</link><pubDate>Thu, 19 May 2016 22:14:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c9a31805-57b6-4207-8a12-062f7da7c13a</guid><dc:creator>FI</dc:creator><description>&lt;p&gt;I&amp;#39;d check on the connection interval. At a minimum of 7.5ms, I have seen the jitters bettween each send session was 30ms max on my bench, I was sending hundreds bytes each session pretty consistently. 100ms should not have problem, and the amount of data you are sending is minimal as well, but you should expect some uncertainty in delivery time due to use conditions. Best!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53325?ContentTypeID=1</link><pubDate>Thu, 19 May 2016 17:08:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b981c8c-4b72-4902-b367-a56b00d29c5e</guid><dc:creator>Revo</dc:creator><description>&lt;p&gt;First of all thanks both for your help. To help you understand i loaded a zip with my projects; one is for the beacon i mentioned (peripheral), the other is for the nrf51 DK that i use to receive the values as central device and send them via uart to the pc (so for Petter, yes i am sending them over uart via the board, and this should happen as soon as a value arrives via BLE from the beacon, as done in the example ble_app_uart_c!).&lt;/p&gt;
&lt;p&gt;All the useful connection parameters should be in the files for the beacon since this problem happens not only with the DK but also with the phone as i said, so if you find something suspicious i will be very grateful to you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53324?ContentTypeID=1</link><pubDate>Thu, 19 May 2016 14:42:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ec3fd00b-bf4d-4cf5-b713-ba6385abf6a0</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Could it have something to do with the connection interval? That the connection interval is increased after a while? When you say termite on your pc, are you printing over uart from the beacon kit? If you are, when are printing? Please include the code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange behaviour while sending real time data</title><link>https://devzone.nordicsemi.com/thread/53323?ContentTypeID=1</link><pubDate>Thu, 19 May 2016 14:42:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a4eab47-e218-4329-8741-5d1a2d436073</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Use the nRF Sniffer and see the ATT Handle Value Notifications on the air to understand your issue better. Post a copy of the trace file for better support.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>