<?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>Is an hvn tx queue allocated per characteristic?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47092/is-an-hvn-tx-queue-allocated-per-characteristic</link><description>I&amp;#39;m wondering about how the notification queues are allocated when setting hvn_tx_queue_size using ble_cfg.conn_cfg.params.gatts_conn_cfg.hvn_tx_queue_size. 
 
 If I set it to some length, say 30, does that mean that a queue of size ( 30 * max_characteristic_length</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 May 2019 04:14:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47092/is-an-hvn-tx-queue-allocated-per-characteristic" /><item><title>RE: Is an hvn tx queue allocated per characteristic?</title><link>https://devzone.nordicsemi.com/thread/186051?ContentTypeID=1</link><pubDate>Thu, 09 May 2019 04:14:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ffec8d2b-3314-4bcc-8140-cba750f6da6b</guid><dc:creator>Andy</dc:creator><description>&lt;p&gt;No, it&amp;#39;s a single queue that the softdevice&amp;nbsp;uses to send notifications to everything, i.e. to all characteristics from all services of every peripheral link.&lt;/p&gt;
&lt;p&gt;Having a bigger queue just means that you&amp;#39;ll be able to queue more notifications before you get NRF_ERROR_RESOURCES. And this can happen no matter what the queue size is. For example, if you call sd_ble_gatts_hvx in a for loop you will only be able to queue X notifications before you get errors.&lt;/p&gt;
&lt;p&gt;You have to handle these errors somehow. A popular approach is clearing a flag on HVX_TX_COMPLETE.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>