<?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>Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5661/multiple-advertisements-using-the-timeslot-api</link><description>Hello, 
 I am currently designing a project that will advertise as two different beacons simultaneously using the Timeslot API. I have successfully implemented the nRF51-multi-role-conn-observer-advertiser example on GitHub and by using the nRF Master</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Jun 2015 17:46:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5661/multiple-advertisements-using-the-timeslot-api" /><item><title>RE: Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/thread/19834?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2015 17:46:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:27b494e5-c56a-4d1d-9084-e1c78e10dccc</guid><dc:creator>Cory Mast</dc:creator><description>&lt;p&gt;The primary reason is because I am trying to conform to the iBeacon spec set by Apple but I also want my own custom advertisement as well, since the fastest undirected advertisement interval I can achieve is 100ms, changing the advertisement data means I will miss an iBeacon advertisement which isn&amp;#39;t a violation of the spec, i&amp;#39;m just shooting for no missed packets. Another reason is that I can use timeslot to advertise only non-connectable advertisements every 100ms and use the softdevice to advertise connectable advertisements every 1000ms. Using this implementation i can save power by having the majority of my packets be non-connectable. I know I can toggle the connectability of my advertisements as well but this also eliminates me having to come up with a toggling scheme where I have to have a tradeoff between power savings and having an easy time connecting to the device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/thread/19833?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2015 17:34:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:215790f4-6ead-4582-b6f7-bb46638a47cf</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Great that you found a solution! I wonder though, why isn&amp;#39;t just changing the advertising data regularly enough for your implementation? Do you require very different advertising parameters for the two beacons?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/thread/19832?ContentTypeID=1</link><pubDate>Tue, 09 Jun 2015 14:57:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ca614fb-878e-4a80-a8d1-ffe598856293</guid><dc:creator>Cory Mast</dc:creator><description>&lt;p&gt;After much investigating I believe I finally understand the timeslot well enough to update with a response.&lt;/p&gt;
&lt;p&gt;It appears that if the advertisement interval of the soft device and the timeslot interval are too close together, and even if they are spaced far apart, there is the chance that the soft device and the timeslot advertisement can collide. When this was happening, my event handler was aborting the timeslot and then ordering another timeslot advertisement. I believe the multiple advertisement burst was occurring when my code would order another timeslot advertisement while still being blocked by the soft device and attempt to abort and order and then abort and order until it finally wasn&amp;#39;t being blocked any more. By using the extend functionality of the timeslot api i was able to overcome this problem.&lt;/p&gt;
&lt;p&gt;Thank you for your help and great support!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/thread/19831?ContentTypeID=1</link><pubDate>Thu, 26 Feb 2015 12:17:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7bbca568-1eeb-481b-afe9-762abe0410c0</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;So this occurs only if you use timeslot advertisements with 100 ms or less intervals? If you set it to more than 100 ms you don&amp;#39;t see the 4 advertisements? The maximum timeslot length will depend on your BLE link/advertisement. If you have shorter time between each Softdevice advertisement, you timeslot will be shorter as well to fit in between them. You say this occurs about once a second. How are they placed in time compared to the regular softdevice advertisements? Are they regular right in front/after the softdevice?&lt;/p&gt;
&lt;p&gt;You can a timeslot of 940 ms, so you should get 9 time slot advertisements inside that frame, do you see this and is it just one of them that are behaving differently?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/thread/19830?ContentTypeID=1</link><pubDate>Wed, 25 Feb 2015 01:30:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c43c3da-2b94-4670-81ee-071d1d1b14fe</guid><dc:creator>Cory Mast</dc:creator><description>&lt;p&gt;I use the term irregularity because the radio should only advertise one time on all three channels, not the four seen above. I believe I have tracked down to issue to be related to the SoftDevice blocking advertisements. If I schedule another radio advertisement with normal priority for some time greater than the initial 100ms, the radio seems to behave as expected by only advertising once on all three channels. I have also noticed that the maximum timeslot length I can achieve is about 940ms. Does any of that seem correct or did I just get lucky and achieve the desired result with the improper method?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Multiple Advertisements Using the Timeslot API</title><link>https://devzone.nordicsemi.com/thread/19829?ContentTypeID=1</link><pubDate>Mon, 23 Feb 2015 13:14:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:138caba5-a49a-40da-88a9-e3a6c009553f</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;I&amp;#39;m not sure what it is that you are seeing as irregularities. In the screen shot above it seems like the radio is advertising on three channels four times within a short time frame. Is this what you have in mind or am I missing something?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>