<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Wireless MCUのトピックRe: How do I detect a QN9080 connection loss?</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/How-do-I-detect-a-QN9080-connection-loss/m-p/993059#M8362</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You usually should get a timeout disconnection event. Does this happen only with your custom application ? Or if you use the IoT Toolbox do you have the same issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a chance that you can share your connections parameters for both the phone and the QN9080 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Estephania&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Dec 2019 18:36:13 GMT</pubDate>
    <dc:creator>stephanie_m</dc:creator>
    <dc:date>2019-12-04T18:36:13Z</dc:date>
    <item>
      <title>How do I detect a QN9080 connection loss?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/How-do-I-detect-a-QN9080-connection-loss/m-p/993058#M8361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using a custom BLE app on Android and iOS to connect to my QN9080. As expected, when I gracefully close the connection from my app, I get the gConnEvtDisconnected_c event in my connection callback function. However, there are times when the phone moves away from my device and I get a connection loss and I do not get the&amp;nbsp;gConnEvtDisconnected_c event in my connection callback function. The result is that I don't know that the phone has disconnected so I permanently stay in a connected state. Is it expected that I would not get the&amp;nbsp;&lt;SPAN&gt;gConnEvtDisconnected_c&amp;nbsp;event when I unexpectedly lose the connection? If so, what is the best way to detect that situation?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have noticed that when I have the unexpected connection loss, I get a gTxEntryAvailable_c event in my generic callback function. I do not get that even when I gracefully close the connection. Other than the comment where the enum is defined, there isn't any documentation on&amp;nbsp;gTxEntryAvailable_c. Can someone explain what that is and tell me if it is a reliable predictor of a non-graceful connection loss?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2019 17:14:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/How-do-I-detect-a-QN9080-connection-loss/m-p/993058#M8361</guid>
      <dc:creator>rickdickerson</dc:creator>
      <dc:date>2019-12-02T17:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: How do I detect a QN9080 connection loss?</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/How-do-I-detect-a-QN9080-connection-loss/m-p/993059#M8362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You usually should get a timeout disconnection event. Does this happen only with your custom application ? Or if you use the IoT Toolbox do you have the same issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a chance that you can share your connections parameters for both the phone and the QN9080 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Estephania&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2019 18:36:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/How-do-I-detect-a-QN9080-connection-loss/m-p/993059#M8362</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2019-12-04T18:36:13Z</dc:date>
    </item>
  </channel>
</rss>

