Difference between nrf8001 C and D

[Schaller]

Hi,

I'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, the application works good with a chip D and now i want to do the same for a C.

That's the problem because each time i connect to a C and trying to discover services, i received an error. I know that the revision C must be paired before trying to discover the services unlike the D, but the same error occure when the device is previously paired.

It is possible to connect a C revision and a D revision on the same app or the specifications are totally incompatible? And if there are compatible, what am i doing wrong and how can i correct this?

Thanks

Jiu Schaller

[Schaller]

I'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:

    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

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't be connected on an Android phone.

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.

Jiu