<?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>Advertisement duration limited to 0xFFFF milliseconds</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/81083/advertisement-duration-limited-to-0xffff-milliseconds</link><description>Hi team, 
 When we set fast advertisement timeout (uint32_t ble_adv_fast_timeout; /**&amp;lt; Time-out (in units of 10ms) for fast advertising. */) to a value greater than 0xFFFF, the adv duration is actually set to the time = ble_adv_fast_timeout % 0xFFFF.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 28 Oct 2021 13:17:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/81083/advertisement-duration-limited-to-0xffff-milliseconds" /><item><title>RE: Advertisement duration limited to 0xFFFF milliseconds</title><link>https://devzone.nordicsemi.com/thread/336501?ContentTypeID=1</link><pubDate>Thu, 28 Oct 2021 13:17:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08ac07fe-2d12-4882-a5ec-f48671607988</guid><dc:creator>sboudaud</dc:creator><description>&lt;p&gt;Thx for the response.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Advertisement duration limited to 0xFFFF milliseconds</title><link>https://devzone.nordicsemi.com/thread/336405?ContentTypeID=1</link><pubDate>Thu, 28 Oct 2021 10:22:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c3af27c-71b5-40e2-a691-6e440c15b67b</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;unfortunately the internal structures inside the softdevice that store duration are also uint16_t so changing this to uint32_t in the application will not have any results in this. I am not sure why this is limited to unt16_t but for not this seems to be a limitation without a workaround in the app. If you need a longer advertising duration, you can set the duration to 0 (unlimited) and use an internal timer to stop the advertiser after certain duration in the application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>