<?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>pc-ble-driver v4.1.2: Bugfix question</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64282/pc-ble-driver-v4-1-2-bugfix-question</link><description>Hi, 
 The release notes of v4.1.2 at https://github.com/NordicSemiconductor/pc-ble-driver/releases 
 mention the fix 
 &amp;quot;Fixed an issue where USB connectivity firmware hangs after receiving many notifications&amp;quot; 
 I could not find more details on this. Can</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 18 Aug 2020 11:34:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64282/pc-ble-driver-v4-1-2-bugfix-question" /><item><title>RE: pc-ble-driver v4.1.2: Bugfix question</title><link>https://devzone.nordicsemi.com/thread/265072?ContentTypeID=1</link><pubDate>Tue, 18 Aug 2020 11:34:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:787d11ef-85b6-4c22-943e-09507c680a74</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Please try with the following answer from our expert:&lt;/p&gt;
&lt;p&gt;One can get more extensive logging by setting the driver log level to trace. An example of this is the test_rssi.py test:&lt;br /&gt;python test_rssi.py --port-a COM20 --port-b COM&lt;br /&gt;16 --driver-log-level trace --log-level debug&lt;/p&gt;
&lt;p&gt;The timestamps are output in the log.&lt;/p&gt;
&lt;p&gt;Example output:&lt;/p&gt;
&lt;p&gt;2020-08-18 10:59:55,010 [18692/LogThread] evt&amp;gt; severity(10) message( 20 -&amp;gt; [N/A] type: ACK re&lt;br /&gt;liable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0)&lt;br /&gt;2020-08-18 10:59:55,010 [18692/LogThread] 21 -&amp;gt; [00 88 00 00 00 00 ] type: VENDOR_SPECIFIC reliable:yes&lt;br /&gt;seq#:4 ack#:0 payload_length:6 data_integrity:1 header_checksum:ce err_code:0x0&lt;br /&gt;2020-08-18 10:59:55,010 [18692/LogThread] evt&amp;gt; severity(10) message( 21 -&amp;gt; [00 88 00 00 00 00 ] type: VEN&lt;br /&gt;DOR_SPECIFIC reliable:yes seq#:4 ack#:0 payload_length:6 data_integrity:1 header_checksum:ce err_code:0x0)&lt;br /&gt;2020-08-18 10:59:55,011 [18692/LogThread] 17/ 0 &amp;lt;- [N/A] type: ACK reliable: no seq#:0 ack#:5 p&lt;br /&gt;ayload_length:0 data_integrity:0 err_code:0x0&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver v4.1.2: Bugfix question</title><link>https://devzone.nordicsemi.com/thread/264831?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2020 10:56:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01b5c661-9660-4318-bed9-104e69eb4dd2</guid><dc:creator>Franz</dc:creator><description>&lt;p&gt;Ok, thanks! So that should NOT be related to the problems i observed. Can you maybe shortly check with your colleague if he/ she has an explanation for the behaviour i described in the question? We have a number of devices connected (e.g. 6 devices), that all deliver notifications to the nRF52840 dongle running the connectivity firmware. Data is collected in python. Sometimes, it seems like the driver is &amp;quot;slowing down&amp;quot;. i.e.&amp;nbsp; notifications arrive late and the mean interval of notifications (about 3 notifications/s/device) is increasing. I am not sure on how to debug the cause for the increasing delay&amp;nbsp; -is there some &amp;quot;timestamping&amp;quot; in the driver layer which I could use?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver v4.1.2: Bugfix question</title><link>https://devzone.nordicsemi.com/thread/264389?ContentTypeID=1</link><pubDate>Thu, 13 Aug 2020 08:43:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:23c7de72-6e35-4bba-8d6e-eb06d81ddaf6</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Finally got an answer on the fix. The issue was&amp;nbsp;&lt;span&gt;too small app_scheduler queue size for USB transport. This&amp;nbsp;is&amp;nbsp;increased in the&amp;nbsp;fix in v4.1.2.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver v4.1.2: Bugfix question</title><link>https://devzone.nordicsemi.com/thread/264245?ContentTypeID=1</link><pubDate>Wed, 12 Aug 2020 11:35:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:babb4f00-9c11-486e-b8d2-9bc98f8d5f91</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&lt;br /&gt;&lt;br /&gt;My apologies for the late reply. Our pc-ble-driver expert got back on Monday. He will provide me an answer as soon as possible.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver v4.1.2: Bugfix question</title><link>https://devzone.nordicsemi.com/thread/262255?ContentTypeID=1</link><pubDate>Wed, 29 Jul 2020 18:13:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3cdadf8c-9f1e-4822-b528-0f75e289a784</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;The developers in charge of pc-ble-driver are currently on vacation, and one must expect a slow response. I will forward your question and get back to you within this week.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>