<?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>Need help to setup connection to a Raspberry pi with a beacon interval of 10 seconds</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69843/need-help-to-setup-connection-to-a-raspberry-pi-with-a-beacon-interval-of-10-seconds</link><description>Hi, 
 
 i am using a nRF52840 with sdk v17.0.2 on soft device s112. using the ble beacon example. i can set up the connection from the raspberry pi with a 2 second beacon interval and a timeout of 12 seconds using peplin / pygatt. but when i use a 10</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 Dec 2020 10:12:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69843/need-help-to-setup-connection-to-a-raspberry-pi-with-a-beacon-interval-of-10-seconds" /><item><title>RE: Need help to setup connection to a Raspberry pi with a beacon interval of 10 seconds</title><link>https://devzone.nordicsemi.com/thread/286975?ContentTypeID=1</link><pubDate>Wed, 30 Dec 2020 10:12:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0fa913c-c92e-4c6f-b27c-0aa02d592f97</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;You are probably correct that it connects on the second. The first it uses to check the address of the device it wants to connect to, and then it connects on the second event. Unless you are specifically using the peripheral address when connecting. Can you check the scanning interval on the RPi side? If it&amp;#39;s not overlapping two advertising interval it might take a while before it gets another chance to connect. But if it &lt;em&gt;never&lt;/em&gt; connects I&amp;#39;m suspecting that there are some sort of timeout. Did you check that the nRF52 side does not have an advertising timeout? That is default in many of the examples.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need help to setup connection to a Raspberry pi with a beacon interval of 10 seconds</title><link>https://devzone.nordicsemi.com/thread/286956?ContentTypeID=1</link><pubDate>Wed, 30 Dec 2020 09:25:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bef80bab-82f4-45c0-8597-ac0f3255ecab</guid><dc:creator>Ing.CR</dc:creator><description>&lt;p&gt;hi Stian,&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Have you tried anything between 2 seconds and 10 seconds? &lt;span&gt;Is there a hard limit when it&amp;#39;s not able to connect?&amp;nbsp;Does it eventually connect, or never?&lt;/span&gt;&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;It is possible to connect with a limit of 4 seconds. everything after 4 seconds will never connect.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Have you tried waiting for longer than 60 seconds?&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;doesn&amp;#39;t matter if the wait is longer than 60 seconds. it also looks like the connection is never made at the first advertising packet, but rather the second.&amp;nbsp; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;could it be a error on the raspberry pi side the way the connection is made?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need help to setup connection to a Raspberry pi with a beacon interval of 10 seconds</title><link>https://devzone.nordicsemi.com/thread/286798?ContentTypeID=1</link><pubDate>Tue, 29 Dec 2020 09:14:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c67aaf08-af66-4641-8c26-8407be26d472</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;Hi, it is possible to connect with a 10 second advertising interval. But if a packet is missed, the scanner has to wait 10 seconds before it can try again. However, if you&amp;#39;re not in a very noisy environment it usually connects at the first advertising packet.&lt;/p&gt;
&lt;p&gt;Have you tried anything between 2 seconds and 10 seconds? Is there a hard limit when it&amp;#39;s not able to connect? Have you tried waiting for longer than 60 seconds? Does it eventually connect, or never? I&amp;#39;m asking because if it never connects, maybe the scanner just shuts down after a while? Maybe some sort of power saving feature or similar. Just guessing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>