<?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>Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1282/difference-between-nrf8001-c-and-d</link><description>Hi, 
 I&amp;#39;m currently working on an Android 4.3 app who must communicate with a model of a specific device.
This device contains a Bluetooth low energy chip nrf8001 and there was a lot of devices with a chip nrf8001 C who was sold. 
 For the moment,</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 Jan 2014 09:55:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1282/difference-between-nrf8001-c-and-d" /><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5888?ContentTypeID=1</link><pubDate>Tue, 21 Jan 2014 09:55:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b57e6fa7-cffe-4d22-9f41-6c8b8eec9c59</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Please open a support case and request a beta release. I am uncertain if the request can be honored but you can ask.
&lt;a href="http://www.nordicsemi.com/eng/Support/Contact-Support-Team"&gt;www.nordicsemi.com/.../Contact-Support-Team&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5887?ContentTypeID=1</link><pubDate>Fri, 17 Jan 2014 10:18:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:734c6fc8-9f11-4ade-b76e-b8616f474c5f</guid><dc:creator>Schaller</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Ok Thx! But can we do something manually to the setup without waiting the update? If not, do you know approximatively when this issues will be fix because i&amp;#39;m little short in time?&lt;/p&gt;
&lt;p&gt;And if i created a support case in the nordicsemi website, do you think the fix will comme earlier?&lt;/p&gt;
&lt;p&gt;Jiu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5886?ContentTypeID=1</link><pubDate>Thu, 16 Jan 2014 16:42:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31075ec7-1fff-425b-8808-b7451fbafc3d</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I think the nRFgo studio is supposed to automatically fix or partially fix the PAN #4 while generating the Setup.
However I think an nRFgo studio issue may have created this issue for you. I will request an update of the nRFgo studio to fix this issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5885?ContentTypeID=1</link><pubDate>Thu, 16 Jan 2014 12:52:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6001812f-7dc1-44b9-8905-6f756a816657</guid><dc:creator>Schaller</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thx for the fast reply! =)&lt;/p&gt;
&lt;p&gt;Your files works good on Android! So i must success to connect our devices, but i can&amp;#39;t find what&amp;#39;s wrong in our setup. I think that we avoid all the workaround from the PAN #4, but there is perhaps a misunderstanding from one of those.&lt;/p&gt;
&lt;p&gt;If you have time, can you check our setup?
Perhaps you will directly find what&amp;#39;s wrong&lt;/p&gt;
&lt;p&gt;Jiu&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/1832.ublue_5F00_setup.gen.out.txt"&gt;ublue_setup.gen.out.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/8787.services.h"&gt;services.h&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5884?ContentTypeID=1</link><pubDate>Tue, 14 Jan 2014 17:23:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b86fc54b-6e33-4426-a506-0b90464ab0df</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I think the issues that you are seeing are related to the C version PAN #4.
I have attached a services.h file and a ublue_setup_gen.out.txt that should work for the Android 4.3 and the C version of nRF8001.&lt;/p&gt;
&lt;p&gt;You may need to reset your phone before testing it to remove any cached GATT handles.&lt;/p&gt;
&lt;p&gt;Let me know how it goes.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/services.h"&gt;services.h&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/ublue_5F00_setup.gen.out.txt"&gt;ublue_setup.gen.out.txt&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5883?ContentTypeID=1</link><pubDate>Mon, 13 Jan 2014 16:35:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bdf7342a-8e6c-45e0-bacc-c521e3b9ba78</guid><dc:creator>Schaller</dc:creator><description>&lt;p&gt;I&amp;#39;ve done two tests on a C revision: One with a bluegiga dongle and one on a Samsung S4 with Android 4.3.
Here is the result from the bluetooth chip using UTF-8 Tera Term Pro:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;    Dongle:
        Ready
        Bonding...
        Connected: I00120, L0000, T01000, A050
        Bond OK
        Pipes open: 00, 02, 03, closed:
        Pipes open: 00, 02, 03, 04 closed:
        Pipes open: 00, 01, 02, 03, 04 closed:
        Data:?
        +000.000
        DC:+1
   

     Android:
        Ready
        Bonding...
        Connected: I00048, L0000, T07000, A100
        Bond OK
        Pipes open: 00, 02, 03, closed:
        Disconnected: Remote user terminated
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;As we can see, the process is exactly the same for the two methods. Just for Android, I terminate the process after ten times trying to discover services but nothing happened during these. Perhaps C revision can&amp;#39;t be connected on an Android phone.&lt;/p&gt;
&lt;p&gt;If someone has successfully connected a C revision to an Android phone using the build-in API, can this person send me the corresponding piece of code or just explain me how he manages the connection and the services discovery.&lt;/p&gt;
&lt;p&gt;Jiu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5881?ContentTypeID=1</link><pubDate>Mon, 13 Jan 2014 13:31:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b3a53fc-ae51-4915-8209-38bfc3b1d782</guid><dc:creator>Schaller</dc:creator><description>&lt;p&gt;I&amp;#39;m using a Samsung Galaxy S4 with Android 4.3 and a Nexus 5 with Android 4.4.2. These two are relatively stable when I use them to communicate with a revision D.
At first, i&amp;#39;ve worked with a Nexus 7 with Android 4.3 and with this device I had pairing issues (can&amp;#39;t unpair, pairing request doesn&amp;#39;t show), unstable bluetooth (randomly disconnecting) and a lot of headache ^^&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5882?ContentTypeID=1</link><pubDate>Sat, 11 Jan 2014 22:14:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2023192e-a0f4-41b9-8c59-5cc3057d6fa5</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;When using a C version of the nRF8001 you should use the Setup format for the C Revision, when the D version of the nRF8001 supports both the Setup Format for D and C revision. So any code created for C should work on D. However any code for C may not work on D and must be explicitly tested.
The Setup Format is selected in the nRFgo studio -&amp;gt; nRF8001 Configuration -&amp;gt; Device in the top of the configuration page.&lt;/p&gt;
&lt;p&gt;The Product Anomalies that exist for the C revision are fixed in the D revision. See the list of anomalies &lt;a href="http://www.nordicsemi.com/eng/nordic/Products/nRF8001/PAN-025/17532"&gt;here&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The Product change notification between the C version and the D version is &lt;a href="http://www.nordicsemi.com/eng/nordic/download_resource/17533/2/16519814"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You should check the status code of the Command Response Events that you are receiving from the nRF8001, this will give you required guidance to fix the issues.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Difference between nrf8001 C and D</title><link>https://devzone.nordicsemi.com/thread/5889?ContentTypeID=1</link><pubDate>Fri, 10 Jan 2014 16:34:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30c74a8c-5ea5-47d2-a274-894bd5ed7b42</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Which Android device are you using? Some devices has pairing issues when running Android 4.3.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>