<?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>Problem with Application based on &amp;quot;MasterEmulator-&amp;gt;ProximityDemo&amp;quot;</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2056/problem-with-application-based-on-masteremulator--proximitydemo</link><description>HI,
I wrote my application based on &amp;quot;MasterEmulator-&amp;gt;ProximityDemo&amp;quot; for testing device with nrf51822. My device have to switching between Gazell and BLE stacks so all the time BLE is breaking. The problem is that when i read data from pipe using PC application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 May 2014 15:16:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2056/problem-with-application-based-on-masteremulator--proximitydemo" /><item><title>RE: Problem with Application based on "MasterEmulator-&gt;ProximityDemo"</title><link>https://devzone.nordicsemi.com/thread/8821?ContentTypeID=1</link><pubDate>Mon, 05 May 2014 15:16:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:749c6154-e31c-4d35-b1bb-6babd9996383</guid><dc:creator>Firek</dc:creator><description>&lt;p&gt;Thanks for the correction. It works well.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem with Application based on "MasterEmulator-&gt;ProximityDemo"</title><link>https://devzone.nordicsemi.com/thread/8820?ContentTypeID=1</link><pubDate>Wed, 23 Apr 2014 14:22:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ccdfaa58-1b19-4132-9d96-15ae007b3f2d</guid><dc:creator>Bj&amp;#248;rn Inge</dc:creator><description>&lt;p&gt;The problem seems to be caused by a race condition between an outbound ATT request and an inbound disconnect event. The ATT request gets sent just as the link has been terminated, and MCP  keeps waiting for up to 30 seconds for the response which obviously never gets received as the link is terminated.
Latest version of Master Control Panel, v3.6.0, includes an improvement that should cover the issue you are seeing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>