<?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>On nRF Master Control Panel and weird behaviors of nRF51822</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11736/on-nrf-master-control-panel-and-weird-behaviors-of-nrf51822</link><description>Best Regards, 
 while messing around with nRF51822 S130, timeslot API and nRF Master Control Panel, we noticed that: 
 Issue : if a packet is formatted correctly, but the declared Manufacturer Data size is larger than the manufacturer data inside the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 12 Feb 2016 09:45:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11736/on-nrf-master-control-panel-and-weird-behaviors-of-nrf51822" /><item><title>RE: On nRF Master Control Panel and weird behaviors of nRF51822</title><link>https://devzone.nordicsemi.com/thread/44375?ContentTypeID=1</link><pubDate>Fri, 12 Feb 2016 09:45:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:361e4479-3c3c-4802-9a58-938a01d721c9</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Ok, let us know if you have any further questions. Please consider accepting the answer if you find this did solve your issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: On nRF Master Control Panel and weird behaviors of nRF51822</title><link>https://devzone.nordicsemi.com/thread/44376?ContentTypeID=1</link><pubDate>Thu, 11 Feb 2016 16:49:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ecbca20-a4ec-421e-aebb-3e54d6be414a</guid><dc:creator>leo_91</dc:creator><description>&lt;p&gt;Thanks run_ar,&lt;/p&gt;
&lt;p&gt;I naively mistook the 0x16 to be part of the non-connectable advertising specification. Apart from that, we send a non connectable advertising because we don&amp;#39;t do scan response, therefore setting to 0x40 would have hidden the packet from nRF control panel.&lt;/p&gt;
&lt;p&gt;I will check whether the overflow of data from the device fixes just with this or not, else I will research some more, double checking the specifications next time. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: On nRF Master Control Panel and weird behaviors of nRF51822</title><link>https://devzone.nordicsemi.com/thread/44374?ContentTypeID=1</link><pubDate>Thu, 11 Feb 2016 16:15:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:913ec691-b154-49a7-91b0-0610e2f412ae</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;There area few things that confuses me. Length seems to be 22 bytes (0x16), while you only got 13 (14 if you add the extra manufacturer specific data byte). You are also missing the flags ad type. and I assume you have changed the address type sine you have 0x42 and not 0x40. Note that we have a timeslot advertiser example in nRF5_SDK_11.0.0-2.alpha_bc3f6a0\examples\ble_peripheral\experimental_ble_app_multiactivity_beacon\hrs_advertiser&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: On nRF Master Control Panel and weird behaviors of nRF51822</title><link>https://devzone.nordicsemi.com/thread/44373?ContentTypeID=1</link><pubDate>Wed, 10 Feb 2016 10:16:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f959fb8c-0e16-4090-9ae9-cf9783b70f47</guid><dc:creator>leo_91</dc:creator><description>&lt;p&gt;Hi run_ar, thanks for the question, sorry for the delay.&lt;/p&gt;
&lt;p&gt;The packet we send is:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;0x42 0x16 - 0xFF 0xEE 0xDD 0xCC 0xBB 0xAA - 0x02 0x09 0xAB - 0x04 0xFF 0xB0 0xFA
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It is a nonconnectable advertising (0x42) with general MAC (FF:EE:DD:CC:BB:AA), name AB (0xAB), and 3 bytes of advertised manufacturer data, whereas we send just 2 (len 0x04 type 0xFF manufacturer data  0xB0FA).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: On nRF Master Control Panel and weird behaviors of nRF51822</title><link>https://devzone.nordicsemi.com/thread/44372?ContentTypeID=1</link><pubDate>Mon, 08 Feb 2016 08:48:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0073322-3d87-4427-95b3-138067641ac5</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;The master control panel is Bluetooth compliant. The maximum advertisement packet length is 31bytes. How does your complete advertisement packet look?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>